3 ms·
> SQLite is maintained by... 3 guys. ... And they don't accept public patches or fixes. > "SQLite is open-source, meaning that you can make as many copies of
by pavel_lishin 3y ago
> SQLite is maintained by... 3 guys. ... And they don't accept public patches or fixes.
> "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."
This doesn't feel like a great example; it seems like if those 3 guys got hit by 3 buses, the source being available means that someone could fork it. (Assuming the license allows it.) At worst, folks could compile it for their own use.
- rgrieselhuber 3y agoAgreed. The TZ example is a lot stronger. That said, the overall point -- that the stance of these mega corps that rely on these projects do very little to ensure their longevity -- is well made.
- benfortuna 3y agoIf you follow the tz mailing list you will see their are many willing volunteers that would step up if needed. So I don't think even this is a good example..
- readthenotes1 3y agoI once gave the "cross train so you don't have a bus number of one" speech to a bunch of managers. Got some push back from one middle manager who said the complex driving their business line was understood by someone had been there by 20 years and was getting rebuilt in a year or two and there's no point in wasting anyone's time meanwhile. I saw them a few months later where I got a free lunch as an apology. The only man who understood the complex code died of a heart attack while trying to prepare the next release. No one had a clue where to start making the required changes. And you know what? That's not my only story of someone dying and no one being able to figure out the code that only they understood.