Policy regarding license statements
Posted: Fri Mar 16, 2018 12:05 pm
In the comment section of PR#2049 a discussion sprung up about our handling of license statements. Being about something which must be considered project policy, that discussion should take place here on the forum, so I opened this thread to continue it here.
The exchange so far:
The exchange so far:
Dilvish wrote:@geoffthemedio looking through the README and CONTIRBUTING.md I see references to FO source being licensed under GPLv2, but I am not seeing anything explicitly akin to our old requirement for new contributors to explicitly state that their contributions are so licensed. Are we just leaving it implicit now?
adrian_broher wrote:No, the contributor must state that he releases his contributions under the terms of the project. The placement where and how to state this is AFAIK dubious. I'm sure there were explicit forum posts for that but I can't find them. @Vezzra pingDilvish wrote:Are we just leaving it implicit now?
Also this is maybe a good point to introduce a formal Developer Certificate of Origin (DCO)?
Geoff the Medio wrote:@adrianbroher could you clarify what that means?
adrian_broher wrote:@geoffthemedio
The DCO? It's a statement that needs to be posted by a contributor before accepting the contribution to a project. The Linux Foundation formalized this:
https://developercertificate.org/
Probably the best idea would be to insert this into a commit message so this can't be tampered by deleting a forum or issue comment.