Conversation
|
Would love to hear from @dahlbyk and @jrusbatch in particular for a 👍, but also in general from the community on any tweaks to this that you think are worth considering... |
| ## Enforcement | ||
|
|
||
| Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
| reported by contacting the project team at **<conduct@brendanforster.com>**. All |
There was a problem hiding this comment.
Fiddling with DNS/Google to get conduct@up-for-grabs.net set up.
There was a problem hiding this comment.
This sounds like a good idea to me.
There was a problem hiding this comment.
Yep, if we have a shared inbox for this I'm 👍 with switching this over. LMK if you need anything from me.
There was a problem hiding this comment.
(On vacation this week, will fiddle as time allows.)
There was a problem hiding this comment.
I believe up-for-grabs is hosted on Namecheap (at least, says whois). If so, here's a quick guide on free e-mail forwarding for domains there: https://www.namecheap.com/support/knowledgebase/article.aspx/308/2214/how-to-set-up-free-email-forwarding. I think it would be possible to set up conduct@up-for-grabs.net to forward to one or more of your addresses without incurring a cost.
|
💯 for taking initiative on this. I'm good with Contributor Covenant. I do wonder if there's a risk of misrepresenting our relationship to the projects listed herein. The up-for-grabs.net site project is community effort subject to this code, but the projects we're linking out to aren't necessarily. Just something to consider... |
|
This sounds good to me! I can see @dahlbyk's point, though. I think we should make his point more explicit in this. |
|
@dahlbyk @jrusbatch an excellent point - I'll endeavour to make sure the mentions of this indicate it applies to this project only, and I'll add a preamble to the code of conduct itself. |
|
Pushed some changes, dropped the task to update the site (I think we can get away with it for now). 👀 plz |
README.md
Outdated
| git clone https://github.com/up-for-grabs/up-for-grabs.net.git | ||
| ``` | ||
|
|
||
| If you have a fork of the repository, change `dahlbyk` for your GitHub account name above. |
|
Tidied up the last round of feedback - @dahlbyk did you make any headway on that shared email address? |
There was a problem hiding this comment.
Hey all! I like this and I like this idea and that the project is doing it, so I wanted to add some comments to hopefully help it move along.
I don't have write access so can't resolve the merge conflicts, but I assume they're minor. Added minor suggestions on wording (truly nit-picky) and a reference article for e-mail forwarding, which I hope might be helpful to get this un-jammed.
@dahlbyk If I can be of assistance on the Namecheap side, let me know. My username there is my e-mail (SeanKilleen at gmail) and if you're comfortable, you can delegate authority to me to make changes on a pretty granular basis (and then remove them when I'm done). If it would be helpful, let me know.
| This document outlines how contributors to the Up-For-Grabs project | ||
| should interact with each other, and the process for resolving issues. | ||
|
|
||
| Projects listed on Up-For-Grabs are not covered by this code of conduct. |
There was a problem hiding this comment.
I think this is worded nicely and clearly. 👍
There was a problem hiding this comment.
Only because "should" is used in place of "must". In actual reality it codifies behaviour, and requires pledging allegiance to it to participate. How rosy it sounds is beside the point of how authoritarian that is.
Not that undermining meritocracy (which is what it is actually meant to do) isn't riding fundamentally on signalling virtue.
How you caught "deemed" and still believed in this I don't understand.
|
|
||
| ## Our Standards | ||
|
|
||
| Examples of behavior that contributes to creating a positive environment |
There was a problem hiding this comment.
| Examples of behavior that contributes to creating a positive environment | |
| Behaviors that contribute to creating a positive environment |
tiny nitpick suggestion on wording.
There was a problem hiding this comment.
If you run the caveat on the one below, this doesn't appear to mean the same thing as what it replaces.
Not that it wasn't badly written in the first place, but alas.
| ## Our Standards | ||
|
|
||
| Examples of behavior that contributes to creating a positive environment | ||
| include: |
There was a problem hiding this comment.
| include: | |
| include, but are not limited to: |
| * Focusing on what is best for the community | ||
| * Showing empathy towards other community members | ||
|
|
||
| Examples of unacceptable behavior by participants include: |
There was a problem hiding this comment.
| Examples of unacceptable behavior by participants include: | |
| Unacceptable behavior by participants includes, but is not limited to: |
There was a problem hiding this comment.
This is already superfluous to how project maintainers are meant to react to "any unacceptable behaviour" below.
However, that is only an expectancy.
"Unacceptable" thus functionally maintains parity with "acceptable".
The only "responsibility" is to instrument censorship for anything that isn't aligned to the CoC, or for "behaviors that they deem inappropriate, threatening, offensive, or harmful."
That is a police state with the law above the people, and its enactor. Made worse in the newer version btw.
In it the least amount of vested interest is tied to the same vagueness and whim, with zero oversight.
| Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
| reported by contacting the project team at **<conduct@brendanforster.com>**. All | ||
| complaints will be reviewed and investigated and will result in a response that | ||
| is deemed necessary and appropriate to the circumstances. The project team is |
There was a problem hiding this comment.
| is deemed necessary and appropriate to the circumstances. The project team is | |
| is necessary and appropriate to the circumstances. The project team is |
deemed is an interesting word choice here because there's no implicit understanding of who would "deem" it so.
Recommend removing the word, because it phrases it from the stance of the authors of the content (in this case, the maintainers), which seems appropriate.
There was a problem hiding this comment.
Yes there is, "Project maintainers". Changed to "Community leaders" in Covenant CoC 2.0.
Project maintainers are responsible for clarifying the standards of acceptable
behavior and are expected to take appropriate and fair corrective action in
response to any instances of unacceptable behavior.
Project maintainers have the right and responsibility to remove, edit, or
reject comments, commits, code, wiki edits, issues, and other contributions
that are not aligned to this Code of Conduct, or to ban temporarily or
permanently any contributor for other behaviors that they deem inappropriate,
threatening, offensive, or harmful.
An anti-meritocratic and complex text-file, is supposed to undo antisocial behavior how?
By making sure unwritten rules worthy of mention are somehow less poignant than disobeying a text file for said people.
Sure the updated one goes even further in attracting anti-social people and granting them ultimate power, but the point remains escalation of conflict beyond the control of individuals involved.
Other conduct which could reasonably be considered inappropriate in a professional setting
To think this is a good idea I find puzzling.
Just as much as "harassment-free" is unattainable, it is also redundant to law. If the focus isn't intent, but here and other places equated to the ability and amount of offense taken, how do you communicate anything?
Undoing sexuality is going to work how?
The control group here is the 5 years without one.
|
|
||
| In the interest of fostering an open and welcoming environment, we as | ||
| contributors and maintainers pledge to making participation in our project and | ||
| our community a harassment-free experience for everyone, regardless of age, body |
There was a problem hiding this comment.
Is it very welcoming to single out people for the non-immutable characteristics?
Is there no universality to it, or do you for some reason need to do it for just these ones, is that the kind of community this is?
| Examples of behavior that contributes to creating a positive environment | ||
| include: | ||
|
|
||
| * Using welcoming and inclusive language |
There was a problem hiding this comment.
How does prescribing a particular ideology of language contribute to a positive environment.
Where has compelled speech ever done anything of the sort?
|
So much has changed since I first authored this, and given I'm mostly the one reviewing contributions these days - and I'm not interested in managing an email address for more OSS activities - I'm going to close this out as unnecessary. |
Probably some other things to do around this, but opening this up early to get feedback:
up-for-grabs.netdomain[ ] update site to mention this?