I have around 5 instances of pocketbase running on a 10 USD/month Hetzner server, serving thousands of users a day without breaking a sweat.
Everything else in open source is a cultural projection entirely ancillary to the code and the license.
> I'll just say that if you think otherwise, whatever good you think you're putting out into the world, is not much better than keeping the software proprietary.
I have never seen someone so entirely miss the point of open source. This is not a house party, this is not a community support network. There are genuine disagreements about open source philosophy, if it should be more focused on user freedoms or developer convenience, but they are all incompatible with the idea that open-source licensed code in and of itself "is not much better than keeping the software proprietary".
Stallman did not invent the GPL because he wanted an issue tracker and complete documentation from HP. He invented the GPL because he needed to fix his printer drivers.
A ton of very important open source code was thrust into the world, created immense value, but was never further supported or developed by its original developers. Off the top of my head: git, Doom, Bitcoin, and basically everything Fabrice Bellard has ever done.
Licences also existed before FOSS, but open sources licences enabling the kind of freedoms that they allow did not exist. And as it happens, a license is not a technical artefact but a social contract. Stallman is activist, not simply a neutral combination of a technician and a lawyer.
The social contract and political vision are consequently not ancillary, but core to FOSS. Code is the medium, but the license is the innovation. Without that social contract, 'open' code is just abandonware.
The community doesn't need to be a 'house party,' but the license guarantees the right for a community to form when the original author walks away.
The only one I'm looking forward currently is the next version of Logseq which will enable collaboration on their existing block-based authoring model.
... I understand that's the theory, but in practice, I've never seen it working that way.
I don't see how having the CoC affects any of this. If someone is behaving poorly, first of all, a CoC will not deter them. If someone behaves so poorly that you decide you need to remove them, the community (the small portion of people who give a f) should see why you removed them, and again, a made-up "contract" will not be needed.
It's ok to stand up for yourself and simply say (without pointing to a document you put in your repo when you were bored), that: "John Doe was behaving poorly, and I don't want to deal with him, I banned him, you don't need to like it, but it's my decision".
Just my 2c... I don't want to add more procedures to my open source projects or voluntary organizing. I'm doing it because I like it, not because I want to pretend I'm at a townhall meeting.
1) point both involved and uninvolved people to the code of conduct when you end up taking action.
2) avoid disparity of enforcement within your team
3) funnel disagreements (from both teammates or community members) by focusing them on the rule, rather than on a general debate on how should the community should be managed.
If people commit a lot of energy to a community/project then for many "I didn't like this behavior, end of discussion" won't cut it.