4 ms·
I would think then that you should be supportive of codes of conduct: you know up front that you have a fundamental distrust of the FreeBSD project leadership a
by geofft 8y ago
I would think then that you should be supportive of codes of conduct: you know up front that you have a fundamental distrust of the FreeBSD project leadership and GitHub organizational leadership, and not of the Go project's leadership, precisely because they have different codes of conduct saying different things.
(I'm opposed to cargo-culting codes of conduct for this exact reason. By all means, copy the Contributor Covenant word-for-word, but only if you truly agree with every word!)
- dijit 8y agoThat is a fair point, using it as a litmus test of what technology leaderships believe. However, I have this crazy idea that a technologies worth is not tied to the political affiliation of the creator or maintainer. I would like us all to focus on the technology and less on the individual or group.. I imagined it would be easy- as on the internet, nobody can tell you're a dog. But apparently I'm wrong.
- geofft 8y agoI don't think you're wrong - the technology's worth isn't tied to the politics of the creator or maintainer. It's important that free software is free for literally anyone to use without discrimination, and I think you'd find very few supporters of CoCs who disagree with that (at least, among those who also identify themselves with the free software or open source movements). But the problem is that the way technologies are developed is inherently not a technical problem, it's a social problem. If it were a technical problem, we'd have code writing and reviewing code, not humans. (I've never heard a single open-source project saying "The problem is that our maintainers have too much free time and there are too many high-quality patches to merge.") It's about how humans interact, and how humans work in community, and how humans provide each other feedback. And this unavoidably brings up all sorts of weird human behaviors that have very little to do with technology. As a random example, I'm writing this comment from the OpenStack Summit, which is an in-person event that you probably want to be attending if you're involved with development of OpenStack. If you can't get a visa to the country where it is, that's a problem. If the conference venue is located somewhere with laws about bathrooms and gender assigned at birth, and you refuse to use the bathroom that matches the gender assigned you at birth, you probably won't be at the venue for the entire day. Should the project care about these things? Should it decide that these laws are bad and we value our contributors who have these constraints enough to find a locality without them? This has zero to do with technology, but (apparently) we've decided that technical projects give better results with in-person meetings, and if you're going to be expected to attend in-person meetings, you want to know whether the community will have your back. Nobody cares if you're a dog, if you can interact with the other humans (or dogs) on the project in a productive way. An obvious (and entirely unfortunate) example is how the language of almost all open-source communities is English; if your native language is something else, you'd better pick up a working understanding of technical English. If you're a dog (or a human) who can't do that, and you try to work inside a technical community, people will care - not about who you are, but about how you interact. But again, this is all about how technologies are developed. If you just want to use it, nobody cares if you're a dog or a corporation or a missile guidance system. And if you want to fork the project (which is really a misnomer, what is being forked is the community), you may. And if you produce patches that are worthwhile and license them freely, and someone in the original community wants to engage that community in cherry-picking your patches, they may.