-
Notifications
You must be signed in to change notification settings - Fork 121
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
Migrate to robotology #2
Comments
Ok, as regarding the name of the repo what do you prefer?
|
I think |
The If you want visibility for the library, once you are a bit confident that the API interface is stable (ish), you could propose to OSQP's authors to include the link to this Eigen interface to OSQP in the OSQP Interfaces page: http://osqp.readthedocs.io/en/latest/interfaces/ (there are already some 3rd-party interfaces such as cutest). |
Ok the name of the repository will be changed into |
Maybe when migrating we could change |
Done! 😄 |
Porting can be performed when this issue will be closed. |
@traversaro You are everywhere I look ! 😃 Question : Isn't the default licensing for robotology LGPLv2-3 ? I'd like to use this but not put my code GPL |
Hi @ahoarau ! |
Just a couple of suggestions before migrating to robotology. #include <OsqpEigen/Solver.hpp> instead of #include <OptimizerSolver.hpp> I would suggest also to change the name of the namespace from I can deal with these modification if you like, maybe adding them to https://github.com/GiulioRomualdi/osqp-eigen/pull/5. Clearly this would break the code which has been written according to the current version, but it may be reasonable to change it when migrating organization. |
Since #5 and #7 were merged and the license was updated (now LGPL 3) we can move this repository to robotology. |
I think we can close this issue. |
Yeah! |
Ad discussed with @GiulioRomualdi and @S-Dafarra, it would be useful to move this repo to robotology .
For this, we should rename the repo to have a name compliant to robotology organization style.
@GiulioRomualdi let me know when you are ready to move (note that GitHub handles renaming quite well, so this should not be problematic in any way).
cc @DanielePucci
The text was updated successfully, but these errors were encountered: