transfer to jump-dev?

[mlubin]

@stevengj, we're moving repositories out from JuliaOpt and into jump-dev, an organization more explicitly centered around JuMP. JuliaOpt will become an obsolete organization. While we'd be happy for the jump-dev org to be the home for NLopt.jl, for better or worse there's currently minimal overlap between JuMP developers and active contributors to this repository, and moving the repository into jump-dev has some branding implications worth considering (given how NLopt is easily usable without JuMP). What are your thoughts on where this repository should be hosted?

[stevengj]

I don't have any strong opinions on hosting, but since I don't use JuMP myself I haven't had time to work on keeping the JuMP integration up to date.

[blegat]

We are checking that NLopt continues to pass MOI tests with SolverTests before any new release of MOI so it should work fine with JuMP

[stevengj]

That's good to hear.

As I said, I don't have strong opinions on which org this should be in, but I suppose if jump-dev has more active developers then moving this might make sense.

[odow]

Any more thoughts on this? It seems to be doing okay here, but it's the only repo left in JuliaOpt that is active

[odow]

I think this would be useful to move to JuMP-dev from a developer/maintenance perspective. (More visibility, it'd show up in my default notifications, etc)

But I understand the not wanting to become too attached to the JuMP brand when it can (and perhaps should) be used separately.

[blegat]

I don't think the jump-dev org is about what is used with JuMP but it's more about what is maintained by the JuMP developers. As a matter of fact, many solvers used with JuMP are not in the JuMP org. So I'm in favor of moving it to jump-dev

[odow]

Somewhat related. I've updated the README to deprioritize mentions of JuMP and MOI. Previously, using with MathOptInterface came before the basic tutorial: https://github.com/JuliaOpt/NLopt.jl/tree/v1.0.3?tab=readme-ov-file#using-with-mathoptinterface

[odow]

The conclusion of the monthly developer call was that there was no point keeping NLopt in an obsolete organization, and that the JuMP developers are happy to take over long-term maintenance of NLopt.jl.

I've moved this to jump-dev and sent @stevengj an invite for admin access.