Changes between Version 1 and Version 2 of License/MandatorySignOff
- Timestamp:
- Feb 8, 2013, 1:13:46 AM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
License/MandatorySignOff
v1 v2 1 1 = Rules for contributions = 2 Rules set forth hereunder are meant for discussion, but might become binding for contributions on plugin authors and maintainers discretion. 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.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. 3 3 4 4 == General rules == 5 5 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 6 7 Developers, that register a new hack 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.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. 8 8 9 9 == Third party contributions == … … 34 34 35 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 get covered by the code base's license at the time of the initial publication. Acceptance of later changes is entirely optional and athe discretion of the author or current maintainer respectively.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. 37 37 38 38 Rationale: