ci: license new contributions under both apache 2.0 and lgpl 2.1 or later - #1909
Conversation
|
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 agree that this new contribution is offered under Apache 2.0. This notice does not affect your previous contributions. If you would like to consent to relicensing those as well, please post the consent statement on #1835; silence is never treated as consent for past work. If offering this contribution under Apache 2.0 does not work for you, no hard feelings; reply with the exact phrase |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1909 +/- ##
=======================================
Coverage 99.87% 99.87%
=======================================
Files 33 33
Lines 3911 3911
Branches 568 568
=======================================
Hits 3906 3906
Misses 3 3
Partials 2 2 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
1 participant
Summary
The goal of #1835 is reducing licensing friction for downstream projects. There have been questions about GPL-2.0-only compatibility, so both licenses are being considered for the final shape: Apache 2.0 alone, or Apache 2.0 with LGPL-2.1-or-later kept as an OR option. No decision has been made yet; right now we are just collecting consent.
This updates the per pull request license notice so new contributions arrive under both Apache 2.0 and LGPL-2.1-or-later, which covers inbound code under either outcome. The objection phrase and close flow are unchanged.