3 ms·
Could it be related to the fact that SQLite, while open source, does NOT accept contributions (closed development)? https://www.sqlite.org/copyright.html https
by alberth 4y ago
Could it be related to the fact that SQLite, while open source, does NOT accept contributions (closed development)?
https://www.sqlite.org/copyright.html https://www.sqlite.org/copyright.html
"SQLite is open-source, meaning that you can make as many copies of it as you want and do whatever you want with those copies, without limitation. But SQLite is not open-contribution."
- masklinn 4y agoThat's an exceptional bit of edition-based lying you're doing here. Here's the end of the paragraph whose start you quoted: > the project does not accept patches from people who have not submitted an affidavit dedicating their contribution into the public domain. So your statement that SQLite "does NOT accept contributions" is plainly wrong. SQLite is not "open contribution" because it requires an affidavit in order to ensure the project remains public domain.
- sgbeal 4y ago>> > the project does not accept patches from people who have not submitted an affidavit dedicating their contribution into the public domain. > So your statement that SQLite "does NOT accept contributions" is plainly wrong. SQLite is not "open contribution" because it requires an affidavit in order to ensure the project remains public domain. You're both right. It does require an affidavit, but the project does not simply accept affidavits from drive-by folks. It's effectively "by invitation." (Citation/disclaimer: i'm a member of the sqlite project team.)
- TheRealPomax 4y agoGiven that your browser history, localStorage, etc. are all stored in sqlite databases: no, why would that even remotely be a problem? Clearly sqlite works for everyone's needs, just expose it via an API. Nothing about that would even remotely require changing sqlite itself.