4 ms·
> I do not understand why it isn't open source. Because your software project then becomes a people management project.
by hombre_fatal 3y ago
> I do not understand why it isn't open source.
Because your software project then becomes a people management project.
- Sabinus 3y agoIt doesn't have to be. Just say you're not accepting PRs. Let people fork and develop their own implementations.
- jraph 3y agoYep, the SQLite way. And if you really like something about someone else's fork, you can even upstream stuff from it yourself (which, for clarity, SQLite won't do, but you can).
- whywhywhywhy 3y ago> Let people fork and develop their own implementations Then a fork gets made and if they improve it massively then half your users end up using it and the other half ends up bugging you to add the improvements into your version and it's no longer your project. I mean I agree too it should be open source if the dev doesn't really update it anymore but I can also completely see why they wouldn't want to do that.
- vonjuice 3y agoIn that case the person would be a bottleneck towards improving a piece of software that would benefit a lot of people. Sure, you're within your right to do that, but really?
- proaralyst 3y agoYou can have open source without open contributions, eg NetHack and (I think) Sqlite
- cowsandmilk 3y agoSQLite has other contributors, just a very curated list of who can contribute. https://sqlite.org/src/reports https://sqlite.org/src/reports
- lupusreal 3y agoThe curated list can be zero. You can just dump source code onto the net and then ignore everybody who messages you about it. This is perfectly valid in open source.
- Aeolun 3y agoI have many open source things that are essentially me looking at the PR queue once every 3 months. I don’t think thats anywhere close to people management. There’s nothing about open source code that requires you to do anything at all with it.