-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update code.md #36
Update code.md #36
Conversation
The plan is to start with a small list and grow it as users make PRs? Should there be a warning saying the some might not be compatible with the latest version o JuMP? Should we do any curating, like a GHA to run the packages with the latest JuMP? Julia had it at some point. |
I don't think we need to test they work with the latest version of JuMP. It's a list of external packages. However, I think we can keep it pretty tight, packages would need to meet a certain minimum threshold of having docs+tests, etc. Other candidates would be
List of JuMP dependents https://juliahub.com/ui/Packages/JuMP/DmXqY/0.21.5?t=2 |
Good idea. Nice list!
There is also the MOI ones like MOO, QuadraticToBinary, Dualization. These are very useful and could be mentioned. Any idea about what to do with things like Coluna? |
|
Fair enough, this is a great start! Dualization as a submodule of MOI looks good. |
In the mean time, it makes sense to add it in the list. The point of having it separate is to have it tested by the users and get feedback so that it matures so highlighting it here is relevant. We can add MOI extensions in a later PR though. |
This JuMP issue jump-dev/JuMP.jl#2388 raised the point that we no longer have a way of mentioning JuMP extensions.