Migrate to robotology about osqp-eigen

[traversaro]

I think osqp-eigen is the most descriptive one, if you want to have c++ in the name I would go for cxx or cpp to avoid strange corner-case problems with having + in the package/repo name.

[GiulioRomualdi]

Since #5 and #7 were merged and the license was updated (now LGPL 3) we can move this repository to robotology.
@DanielePucci @S-Dafarra @traversaro

[S-Dafarra]

Maybe when migrating we could change Optimizator* to Optimizer* 😉 .

[GiulioRomualdi]

Ok, as regarding the name of the repo what do you prefer?

1. osqp-c++;
2. osqp-eigen;
3. osqp-c++-eigen;
4. ...

[traversaro]

The osqp-something naming scheme is also compatible with the names of the repositories of osqp bindings for Python, Fortran and MATLAB: https://github.com/oxfordcontrol .

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).

[GiulioRomualdi]

Ok the name of the repository will be changed into osqp-eigen. The master branch is fully tested while, in the next few days, I will write some tests for the devel_update_matrices branch.

[GiulioRomualdi]

Maybe when migrating we could change Optimizator* to Optimizer* 😉 .

Done! 😄

[GiulioRomualdi]

Porting can be performed when this issue will be closed.

[ahoarau]

@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

[traversaro]

Hi @ahoarau !
Yep the software is licensed under LGPL2/3, the content of the LICENSE file will be changed soon, thanks for pointing that out.

[S-Dafarra]

Just a couple of suggestions before migrating to robotology.
Maybe it is better to rename the files from Optimizer* to OsqpEigen*, to make clearer the inclusion of these files in external projects. In addition the name OptimizerSolver seems a repetition.
Another option could be to remove Optimizer* from the file name and place them all in a folder called OsqpEigen, so that the inclusion would seem like:

#include <OsqpEigen/Solver.hpp>

instead of

#include <OptimizerSolver.hpp>

I would suggest also to change the name of the namespace from OsqpWrapper to OsqpEigen to preserve consistency with the project name.

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.

[GiulioRomualdi]

I think we can close this issue.

[traversaro]

Yeah!