4 ms·

Except that is not what SQLite states at all. They accept outside work provided the contributors waive their rights to the code by dedicating it to the public d

Except that is not what SQLite states at all. They accept outside work provided the contributors waive their rights to the code by dedicating it to the public domain, and it's a high quality contribution. Which makes a whole lot of sense when the entire planet uses it. And of course, this is an academic publication so those requirements are basically lowest bar if you're serious. And consulting with your primary source during the research and iteration phase(s) and mentioning that in your publication is kind of expected?

IshKebab 2y ago
I quote: > In order to keep SQLite completely free and unencumbered by copyright, the project does not accept patches.
- TheRealPomax 2y ago
  Let's read the rest of that paragraph too: > [...] the project does not accept patches. If you would like to suggest a change and you include a patch as a proof-of-concept, that would be great. However, please do not be offended if we rewrite your patch from scratch. [1] As in, they don't blindly accept patches, if you do all the work and send your patch to them and go "I have done all of this without consulting you, please commit it", it'll get deleted because that's not how SQLite does external contributions. Instead, if you have high quality ideas and even some PoC code to go with that, contact SQLite and discuss whether it makes sense to integrate that. And we can even read the official response by SQLite to the continued claims that they don't accept contributions here on HN. [2] But of course, whether SQLite accepts patches or not was never at issue, what matters is whether or not this research team contacted SQLite at all, because academic collaboration is one of the pillars of academic research. I don't see that in their paper, which should make you go "why was this step skipped?" [1] https://www.sqlite.org/copyright.html https://www.sqlite.org/copyright.html [2] https://news.ycombinator.com/item?id=34480732 https://news.ycombinator.com/item?id=34480732

IshKebab 2y ago

I quote: > In order to keep SQLite completely free and unencumbered by copyright, the project does not accept patches.

TheRealPomax 2y ago
Let's read the rest of that paragraph too: > [...] the project does not accept patches. If you would like to suggest a change and you include a patch as a proof-of-concept, that would be great. However, please do not be offended if we rewrite your patch from scratch. [1] As in, they don't blindly accept patches, if you do all the work and send your patch to them and go "I have done all of this without consulting you, please commit it", it'll get deleted because that's not how SQLite does external contributions. Instead, if you have high quality ideas and even some PoC code to go with that, contact SQLite and discuss whether it makes sense to integrate that. And we can even read the official response by SQLite to the continued claims that they don't accept contributions here on HN. [2] But of course, whether SQLite accepts patches or not was never at issue, what matters is whether or not this research team contacted SQLite at all, because academic collaboration is one of the pillars of academic research. I don't see that in their paper, which should make you go "why was this step skipped?" [1] https://www.sqlite.org/copyright.html https://www.sqlite.org/copyright.html [2] https://news.ycombinator.com/item?id=34480732 https://news.ycombinator.com/item?id=34480732