> Rejoin core SQLite if its policy changes > We are strong believers in open source that is also open to community contributions. If and when SQLite changes it

> Rejoin core SQLite if its policy changes > We are strong believers in open source that is also open to community contributions. If and when SQLite changes its policy to accept contributions, we will gladly merge our work back into the core product and continue in that space. If libSQL is going Apache-2.0¹ rather than public domain, that seems extremely unlikely. The public domain nature of SQLite is rather important for its deployments. And in fact licensing is a rather important part of why SQLite is closed to contributions (though with some administrative overhead it could be opened to contributions from people from some countries). The fact that this announcement and project documentation seems to make absolutely no mention of the licensing situation perplexes me. —⁂— ¹ As they state in the text; but https://github.com/libsql/libsql/commit/f7c54b8f792aa502f02508f521e17cee74325998 https://github.com/libsql/libsql/commit/f7c54b8f792aa502f025... is entirely insufficient, not constituting application of the license. I find this a bad sign, in stark contrast to the meticulous care SQLite has taken to copyright matters.