On 1/19/19, Simon Slavin <slav...@bigfraud.org> wrote: > I suspect it [the docs] started out small and grew, without ever being > rewritten.
That is a reasonable conjecture. I agree that the documentation could use some work. I will eventually get around to doing this, but I feel like making enhancements and fixing issues in the code should have priority. Here's the deal: I'm very fussy about who can contribute *code* to SQLite, in order to protect the public-domain status of the SQLite source code and due to the intense nature of testing required to land a change. However, there is more flexibility for volunteers who would like to help change the world by improving the SQLite documentation. If you want to help, please let me know. There is a public-domain dedication form that you will need to fill out. You will also need to reside in a country that recognizes the right of authors to dedicate their work to the public domain (basically anyplace that derives their legal traditions from British common law). And with that, I will give you check-in privilege on the SQLite documentation repository (https://sqlite.org/docsrc) and as much guidance as you need to get starting making improvements. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
