Repository navigation
chore: add modification notices to headers and require affirmative consent for past contributions - #1885
chore: add modification notices to headers and require affirmative consent for past contributions#1885bdraco merged 1 commit into
Conversation
Sorry, something went wrong.
…nsent for past contributions
|
Thanks for contributing! A quick note: this project is in the process of moving from LGPL-2.1 to Apache 2.0, see #1835. By continuing with this pull request you are okay with your contribution, and your previous contributions to this repository, being offered under Apache 2.0. If that does not work for you, no hard feelings; reply with the exact phrase I do not agree to the Apache 2.0 license or simply close this pull request, and nothing of yours will be included in the change. |
Sorry, something went wrong.
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## master #1885 +/- ##
=======================================
Coverage 99.87% 99.87%
=======================================
Files 33 33
Lines 3910 3910
Branches 568 568
=======================================
Hits 3905 3905
Misses 3 3
Partials 2 2 ☔ View full report in Codecov by Harness.
|
Sorry, something went wrong.
Summary
Two hardening items from outside legal review of the relicensing work.
LGPL 2.1 section 2 asks modified files to carry prominent modification notices; the short headers from #1861 now state the work is continuously modified with dates recorded in git history, alongside the existing license pointer.
The license notice workflow no longer treats continuing a pull request as consent covering previous contributions. The new contribution is offered under the incoming license as with any project, and consent for past work happens only through the explicit statement on #1835; the notice now says silence is never treated as consent for past work.
Test plan