Changes between Version 3 and Version 4 of License/MandatorySignOff
- Timestamp:
- Dec 8, 2015, 1:51:31 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
License/MandatorySignOff
v3 v4 1 = Rules for contributions = 2 Rules set forth hereunder are meant for discussion, but might become binding for contributions at the discretion of plugin authors and maintainers. We're thinking about setting similar constraints for all contributions to this site to prevent potentially dangerous legal ambiguity for all hosted content, as soon as a broad agreement among currently active developers has been reached. 1 [[PageOutline(2-5,Contents,pullout)]] 3 2 4 == General rules == 3 = Rules for contributions 4 5 These guidelines are meant for discussion, but might become binding for contributions at the discretion of plugin authors and maintainers. We're thinking about setting similar rules for all contributions to this site to prevent legal ambiguity for hosted content, and as soon as a broad agreement among currently active developers has been reached. 6 7 == General rules 8 5 9 Authors, whether they directly commit to trac-hacks.org's repository or just add/edit wiki content and append ticket comments, are exclusively responsible for all contributed content. 6 10 7 Developers , that register a new hack must ensure that each hack has a valid license attached to it, and that code changes match the respective license. In absence of an explicit license we assume,that the license of the underlying framework applies, always meaning the latest t:TracLicense. However this is only meant as a starting-point, if such license-free code is encountered the first time, especially with older contributions predating this set of rules.11 Developers who register a new hack must ensure that each hack has a valid license attached to it, and that code changes match the respective license. In absence of an explicit license we assume that the license of the underlying framework applies, always meaning the latest t:TracLicense. However this is only meant as a starting-point, if such license-free code is encountered the first time, especially with older contributions predating this set of rules. 8 12 9 == Third party contributions == 10 A significant part of code changes is driven by other developers, who report issues and/or propose code enhancements, partially accompanied by patches or similar suggestions, what should be changed. 13 == Third party contributions 11 14 12 === Explicit declaration === 15 A significant part of code changes is driven by other developers, who report issues and/or propose code enhancements, partially accompanied by patches or similar suggestions on what should be changed. 16 17 === Explicit declaration 18 13 19 The preferred way of legal clearance regarding contributions is an explicit sign-off notice include in the contribution itself or as supplementary comment with unambiguous reference to the contribution it is meant for. Example: 14 20 … … 31 37 }}} 32 38 33 Here by the patch author declares explicitly,to waive any copyright and release the contribution under the terms set by the respective license of the code base, that he/she's contributing to.39 Here the patch author declares explicitly to waive any copyright and release the contribution under the terms set by the respective license of the code base, that he/she's contributing to. 34 40 35 === Implicit waiver === 36 In absence of other unambiguous declaration by the author of a contribution, or in case of an anonymous contribution, a contribution will be covered by the code base's license(s) at the time of the contribution is submitted to trac-hacks. Acceptance of the contribution is entirely optional and at the discretion of the author or current maintainer respectively. 41 === Implicit waiver 42 43 In absence of other unambiguous declaration by the author of a contribution, or in case of an anonymous contribution, a contribution will be covered by the code base's license(s) at the time the contribution is submitted to trac-hacks. Acceptance of the contribution is at the discretion of the author or current maintainer respectively. 37 44 38 45 Rationale: 39 * One key factor for the value of code provided by many individual authors here is determined by the freedom to use it, share, study, modify, redistribute etc.40 * While this is mostly about copyright and legislation, t opics often unsuitable for the general audience, terms of use and contributions must be still as simple and clear as possible.41 * We recognize ,that the freedom of use can only be ensured permanently, if all contributions are covered by suitable, legally binding free licenses.42 * Contributions must usable for developers without neither obvious nor hidden pit-falls.46 * A key factor for the value of code provided by individual authors here is determined by the freedom to use it, share, study, modify, redistribute etc. 47 * While this is mostly about copyright and legislation, terms of use and contributions must be as simple and clear as possible for it to be understandable to the general audience. 48 * We recognize that the freedom of use can only be ensured permanently, if all contributions are covered by suitable, legally binding free licenses. 49 * Contributions must be usable for developers without obvious or hidden pit-falls. 43 50 * Ultimately, users must be trusted to know before-hand, if they want to contribute code, knowledge or other properties of their own or not. 44 51 45 == Discussion == 52 == Discussion 53 46 54 (advice and comments welcome, add your questions and thoughts here) 47 55 48 56 -- hasienda 49 57 50 51 - Instead of requiring explicit declaration in each patch (and ticket comment, wiki edit, ...), you could just handle this in the ''Terms of Service''. (Similar to how by using the ''Wikipedia'' website you agree to [http://wikimediafoundation.org/wiki/Terms_of_Use#7._Licensing_of_Content licensing ToS] so any contributions are automatically licensed as appropriate.) Require agreeing to the ToS on the account registration page or once when logging for existing users to make it explicit. 58 Instead of requiring explicit declaration in each patch (and ticket comment, wiki edit, ...), you could just handle this in the ''Terms of Service''. (Similar to how by using the ''Wikipedia'' website you agree to [http://wikimediafoundation.org/wiki/Terms_of_Use#7._Licensing_of_Content licensing ToS] so any contributions are automatically licensed as appropriate.) Require agreeing to the ToS on the account registration page or once when logging for existing users to make it explicit.
