Code is unlikely to be accepted upstream because it very rarely is (assuming you mean by the SQLite team). They are very picky about code contributions and alm

Code is unlikely to be accepted upstream because it very rarely is (assuming you mean by the SQLite team). They are very picky about code contributions and almost always implement themselves. One part is legal - there has to be very clear lineage/authoring to the code, patent clearances etc. The second part is that the actual code to implement any particular functionality or even a bug fix is relatively trivial. There is far more effort and far more lines of code for testing: http://www.sqlite.org/testing.html http://www.sqlite.org/testing.html - and implementing code to enable the rigourous testing usually results in a different structure. The third part would be conflicting with the existing goals: http://www.sqlite.org/whentouse.html http://www.sqlite.org/whentouse.html OTOH if the intention isn't to be part of the core then upstream doesn't matter and the code can be distributed in any way you deem fit.