Accepting contributions should require the contributor to accept an agreement which effectively enables the contribution to come under maintenance of Phorge and for the changes to be re-licensed by the project as needed.
This site has some information along with a "chooser" for selecting an agreement.
Things we all agree on:
- a Contributor Agreement could be very useful to mitigate some legal issues - example risks:
- potential sue from a Contributor: make more explicit that a code contribution is under our default license (Apache 2.0)
- potential sue from an external copyright holder: add awareness to code contributors, so that they can't "steal code" of others (e.g. from Microsoft Flipper®) and release that code into Phorge
Things on which there are strong points of divergence:
- transfer code contributors copyrights to a central organization
Feel free to edit this stub: L2 Contributor Agreement (UNDER CONSTRUCTION)