Earlier quoted context omitted.
> Real jerks in f/oss are also a real problem. f/oss groups should ABSOLUTELY eject bullies: not for wrongthink, but for bullying. We must be kind. So, is it illegitimate, then, to have a FOSS project with an intentional/cultivated "culture of abuse", where the idea is that nobody is kind to anybody and that's how everybody likes it? Sort of a... "BSDM but we build something along the way" thing? (For example, pictur…
> So, is it illegitimate, then, to have a FOSS project with an intentional/cultivated "culture of abuse", where the idea is that nobody is kind to anybody and that's how everybody likes it? Sort of a... "BSDM but we build something along the way" thing? It's nonviable for anything beyond a small hobby project, for the simple reason that such a culture would make it essentially impossible for anyone to participate in…
There are a lot of projects that are factored into small pieces with separate maintainership, where the project as a whole—or its "core"—might be corporate-sponsored; yet individual parts/plugins/connectors—including fairly-critical ones!—might turn out to be one person's hobby-project.
How many maintainers do you think the average Kafka connector has? The average Postgres extension? The average Redis or Nginx module? Etc.
These ecosystem components move the project-as-a-whole forward, and yet they don't necessarily need to be as "corporate" as the project-as-a-whole does to accomplish that. Even though, in the end, a corporation might use one of them, it won't really matter as long as nobody sees them doing so. (If they ever need to patch the un-corporate extension, though, they'll probably fork the thing and flense out all references to the original. I've seen that happen a lot, and done it a few times myself.)