Re:How ‘open’ should your open source be?
by stock_toaster on Sunday May 14, 2023 @06:47AM
(#35937012)
It works for sqlite (public domain though, not apache-2.0)
The reasoning is specific and pretty interesting IMO. Contributions are accepted as long as they stay public domain.
“In order to keep SQLite in the public domain and ensure that the code does not become contaminated with proprietary or licensed content, the project does not accept patches from people who have not submitted an affidavit dedicating their contribution into the public domain.”
I’d guess this compares to the GPL in interesting ways too (i.e., unlike GPL public domain code can be used/copied/distributed without license, even in proprietary settings and for profit, but attribution, credit & copyright must be waived first).
Don't get me wrong, doing so does make sense for this specific case where the author has many important things going on in their life other than the project (I feel it, I don't even want to read email after duty time). But for project like this, maybe one of the GPL is better? Because with GPL, you force other people to open source their forks under the same license, this enables you to cherry-pick the fork you want back to the origin, at the time of your own choose.