4 ms·
> 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 t
by duskwuff 7y ago
> 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 the project as a representative of their employer.
- derefr 7y agoThat assumes a monolithic design style, I think. 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.)
- zozbot234 7y ago> would make it essentially impossible for anyone to participate in the project as a representative of their employer. Freedom to fork is a thing. Start a CoC-friendly fork of the project, for the benefit of those who require this as a condition of participation; but stipulate that both forks will freely share code between one another. (Meaning, no PNG-like clause whatsoever. This ensures that the choice between the "nice, CoC" and "sticks and stones" project leadership styles is kept free and open, with nobody being forced into one choice or the other. This of course is a compelling reason to actively reinforce the status quo of Persona-Non-Grata clauses in a copyright license being regarded as incompatible with the OSD or any other definition of FLOSS.)
- dandellion 7y agoIn some cases that would be a feature.