Contributing code
You are welcome to change ViSP and are invited to contribute your improvements back for the benefit of the community.
Important before submitting a contribution
- Before contributing to any ViSP folder in https://github.com/lagadic/visp, the contributor must transfer the rights of the work to Inria (France) by providing a copyright transfer agreement (except for people payed by Inria, CNRS, or University of Rennes, see next section). If you intend to do this, download the transfer form, fill it, and send us back a scan.
- Contributors paid by Inria, CNRS or the University of Rennes do not need to complete the transfer of rights document. In fact, Inria, the CNRS and the University of Rennes are co-owners of the ViSP software and have signed a “Simplified Co-ownership Agreement” or “Règlement de Copropriété Simplifié” (RCS). This RCS allocates co-ownership shares in the ViSP software to the CNRS, Inria and the University of Rennes. It also specifies that Inria is authorised by the other co-owners to manage and promote the software. The contributors will be mentioned in an amendment to this RCS, as co-authors of the software, in the next release of ViSP.
- The work must follow the ViSP coding standards.
- We also propose to the community a dedicated contrib repository https://github.com/lagadic/visp_contrib to collect modules from contributors. For contribution in this repository, the contributor don’t have to transfer the rights of the work to Inria. The license associated to the contribution should be explicit.
- In all cases, the contributor will be considered as the author of the contributed work, and be acknowledged for it in the release notes, web documentation, and other places that may apply (such as source code for contributed modules). Note that all contributions are individually considered for inclusion by the ViSP dev team and may be rejected. If you have any questions about making a contribution, please do not hesitate to contact us.