Why SQLite Does Not Use Git

Re:Why SQLite Does Not Use Git by joshlemer on Tuesday April 10, 2018 @11:06PM (#16807722)

Do you know why they have this philosophy? Why would they not accept patches and pride themselves on having few contributors? Seems very odd.

[ Parent | on HN ]

Re:Why SQLite Does Not Use Git by SQLite on Wednesday April 11, 2018 @09:41PM (#16817358)

If we accept patches, then the person who has submitted the patch owns the copyright on that patch, and that means the software is no longer completely in the public domain. Unless, of course, the patch submitter has filled out a lot of legal paperwork to dedicate their code to the public domain, which rarely happens.

[ Parent | on HN ]

Re:Why SQLite Does Not Use Git by Aissen on Wednesday April 11, 2018 @03:34AM (#16808853)

It's hinted in the linked page:

> In order to keep SQLite completely free and unencumbered by copyright, the project does not accept patches. If you would like to make a suggested change, and 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.

[ Parent | on HN ]

Re:Why SQLite Does Not Use Git by gmueckl on Wednesday April 11, 2018 @05:21AM (#16809349)

Because they can sell licenses that way and make money off the product.

[ Parent | on HN ]

Re:Why SQLite Does Not Use Git by lsaferite on Tuesday April 10, 2018 @11:16PM (#16807753)

Tight control? Consistent vision? Less overhead? All of the above?

[ Parent | on HN ]