|
|
|
|
|
by pwgentleman
1915 days ago
|
|
Maybe that says more about you than about the document authors, or the document itself. They have gone through the trouble of changing this from a Code of Conduct to a Code of Ethics, for the specific purpose of avoiding quarreling (their rule 66). You want to move away from SQLite just because you heard some developers are religious. I really prefer their attitude towards disagreement. |
|
This "Code" isn't saying that this is what the founder believes, and that they would like others to follow it. It's making a pretty unequivocal statement that the founder (and developers) believe that this is the "better" way to live: "Anyone who follows The Rule will live a happier and more productive life"
First of all, this is really unrelated to software or the utility of sqlite. But then we have "The founder of SQLite and all current developers have pledged to follow the spirit of The Rule to the best of their ability. They view The Rule as their promise to all SQLite users of how the developers are expected to behave"
Well then, this is a pretty strong statement of their intention to limit the pool of sqlite contributors to those who follow this rule.
"But sqlite is open source" you might think... but here's what they say:
> SQLite is open-source, meaning that you can make as many copies of it as you want and do whatever you want with those copies, without limitation. But SQLite is not open-contribution. In order to keep SQLite in the public domain and ensure that the code does not become contaminated(!!) with proprietary or licensed content, the project does not accept patches from unknown persons ... > 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."
So this is all news to me, and I think it's a pretty terrible way to run an open source project, or any project really. I wouldn't work at a company that had this rule. If the rule said "1. Only have sexual relations with people of the opposite sex, in the context of marriage" I suspect many people would wash their hands of it completely.
But really, they've done a great job with sqlite as a piece of software, so kudos to the dogmatic yet exclusive group of authors for their work and dedication. In the meantime, I would be thrilled to see another file-based relational db take its place