Name

[odow]

MathOptComplementarity?

API should look something like:

using JuMP
import MathOptComplementarity as MOC
model = Model(() -> MOC.Optimizer(Ipopt.Optimizer))
set_attribute(model, MOC.Algorithm(), MOC.SmoothNonlinear())

# potentially

set_attribute(constraint[1], MOC.Algorithm(), MOC.SmoothNonlinear())
set_attribute(constraint[2], MOC.Algorithm(), MOC.BigM(100.0))

A good design for inspiration is https://github.com/jump-dev/MultiObjectiveAlgorithms.jl

[blegat]

Yes the API is expected to be similar to this. For the name, it doesn't follow the MathOpt... style but I kind of departed from that style with LowRankOpt, GenOpt and SeqOpt already.

[blegat]

Here is an other idea : Kakapo, it's a 🦜 in New Zealand.
As K sounds like Kah in french, Kaka can be Komplementarity Konstraints or alternatively KomplementArity KonstrAints
Then PO can be Package for Optimization or Programming for Optimization. What do you think ?
Technically possible but not recommended use of the package:

import Kakapo as 🦜

Alternatively, we can go for Kakariki, I saw some in the Tiritiri Matangi island which was the excursion of JuMP-dev, not sure what riki stands for though , maybe Reformulation Interface KIt ? The final I could also be Implementation, Integration or Infrastructure

[frapac]

I like Kakapo! I think three-syllabic words make great names for package.

We can also think of Kapapopt? But I don't think there is any bird with such a name.

[frapac]

Thinking more about it, I think it would be better to stick with JuMP's naming convention for package extensions and name this package MathOptComplements.jl

[blegat]

Bird names is also part of the convention, see for instance https://github.com/jump-dev/MultiObjectiveAlgorithms.jl, https://github.com/IainNZ/Pukeko.jl, https://github.com/jump-dev/Pajarito.jl, https://github.com/jump-dev/Pavito.jl

[odow]

I am pretty evenly split on this. MathOptComplements probably preferable. But I do love the bird chat