> Any hints for how to get Richard's attention enough and to possibly convince him? SQLite isn't published under a viral software license, so a person cannot just drop a patch on a public site, if their goal is to get the patch into SQLite. drh couldn't legally apply your patch even if he wanted to. The author of that patch has full copyright protections in that patch in [virtually every country in the world][1] until it is explicitly licensed in a way that allows it to be copied. In the case of SQLite, that means drh needs the legal right to re-distribute your change under [the same terms as SQLite: public domain][2]. This means you must explicitly relinquish your legal rights to that patch. That link also goes into more detail about your very question. You can try sending [a signed copyright release][3] to [HWACI's postal address][4]. That would at least allow drh to accept the patch as-is. However, it is also the case that this patch doesn't provide a feature SQLite needs, so you'd have to justify asking drh to carry the maintenance load for it. What's been the cost to your project to carry the patch? How often do you have to update it to track upstream changes? If it almost always applies cleanly, then I don't see why you need to upstream it. That's FOSS working like it should. [1]: https://en.wikipedia.org/wiki/Berne_Convention [2]: https://sqlite.org/copyright.html [3]: https://www.sqlite.org/copyright-release.html [4]: http://www.hwaci.com/contact.html