Adrian Cochrane
Input please! Which Code-of-Conduct should I apply to #Haphaestus & its underlying #ArgonautStack components?
To cut so such comments off at the source: I don't care about attracting supposed 10x devs, I care about attracting devs who are aware of where computing need to improve.
P.S. My plan is to link to it on any project-related public forum, that's what makes sense to me. I wouldn't even need to fork SourceHut to do so!
Boosts welcome.
Adrian Cochrane
@phryk I've got a collaborator, but he didn't have any strong feelings about it. Thought it'd be better to hear from others.
And yes, I do have an attitude that how well/appropriately a CoC is enforced is far more important.
phryk 🏴
@alcinnz Do you already have contributors?
If so, I think an in-depth discussion with them might be in order. Maybe with some candidates to refer to.
I've thought about this a bit over the years, too – but I never came to a satisfactory conclusion.
Most of the commonly used CoCs feel like they're more about corporate ass-covery than about fostering a healthy community.
phryk 🏴
Another thing is what I always brought up when the hackerspace was discussing CoCs:
No matter what CoC you adopt, it's worthless if you don't have an awareness team – potentially even worse, because people will *think* the space is safe for them when it's not.
You *have* to have some sort of contact point and procedure for when the CoC is violated and I think it's this rather than just the bare fact of having a CoC where most projects fail.
phryk 🏴
I think* for smaller projects it's totally fine to have a custom CoC that grows with the actual needs of the community – just make it clear that you're open to proposals for new extensions from prospective contributors.
*: personal view, not evaluated in practice
phryk 🏴
> "And yes, I do have an attitude that how well/appropriately a CoC is enforced is far more important."
If that's where you arrived on your own, I think you're already further ahead than many projects loudly touting their CoCs. 👍
phryk 🏴
@alcinnz A thing to keep in mind for conflict resolution is also that privileges and prejudices are often clustered.
One common example I've seen is that affluent, well-educated people tend to be LGBT-friendly but foster classist views while lower-class people tend to be less classist but more homophobic.
phryk 🏴
A common point of contention between the two is language: I've seen entirely too many conflicts over homophobic or other slurs involving these two groups that were 100% miscommunication.
The more well-educated people tend to prioritize "non-violent speech" while coarse language is both a class identifier and a sign of trust for lower-class people.
phryk 🏴
The point I'm trying to make here is… there is no "right" solution.
The lower-style class of communication can be a hurtful experience for people who aren't in the in-group, but seeing attempts to ban coarse language as an attack on lower-class identity is also a valid perspective.
You will always have to weigh peoples needs, privileges and deprivations against each other and anyone saying that's simple is either lying or completely clueless about how much damage they're doing.
Adrian Cochrane
I think I like the look of Django's code-of-conduct, and might tweak its text to be specific to my project. Though I would want to include text regarding how I'll be enforcing it on the same page.
https://www.djangoproject.com/conduct/
Thoughts? Is that a good one to adopt?
ocdtrekkie
@alcinnz Have you considered the Contributor Covenant? https://www.contributor-covenant.org/
Adrian Cochrane
@ocdtrekkie Yeah, I've looked at that one. Personally I'd prefer the introduction include an "etc", and more importantly I want a CoC with enforcement provisions I'm prepared to follow.
Adrian Cochrane
@ocdtrekkie Oh, and one issue with the Contributor Covenant for me is that my codeforge is built around email. So more nuance would be needed around clauses against disclosing email addresses which is in that text.
(I am willing to provide public project-specific email addresses)
Adrian Cochrane
@ocdtrekkie Fair enough, yes they did.
ocdtrekkie
@alcinnz That all makes sense. I just an generally in favor of relatively standardized CoCs, such that I can assume they're reasonable at a glance. It looks like Django got theirs from someone else too, mind you.
０７６萌ＳＮＳ is a social network, courtesy of ０７６. It runs on GNU social, version 2.0.2-beta0, available under the GNU Affero General Public License.
All ０７６萌ＳＮＳ content and data are available under the Creative Commons Attribution 3.0 license.