todo: fix #1871
todo: fix #1871
Conversation
|
Oh thank you, that was a major oversight on my part. We can use my contact or @tancnle's instead. Sorry for the spam Coraline >< |
CODE_OF_CONDUCT.md
Outdated
| @@ -60,7 +60,7 @@ representative at an online or offline event. | |||
|
|
|||
| Instances of abusive, harassing, or otherwise unacceptable behavior may be | |||
| reported to the community leaders responsible for enforcement at | |||
There was a problem hiding this comment.
suggestion: How does this sound to you? We already have the list of maintainers in the README
| reported to the community leaders responsible for enforcement at | |
| reported by contacting one of the [project maintainers](https://github.com/rouge-ruby/rouge#maintainers). |
There was a problem hiding this comment.
The more common thing is to list emails. Of the 4 maintainers listed, only 2 have emails (or indeed any contact method) listed on their profiles. It's possible that Goro has an email or other direct contact listed somewhere on his website, but due to my limited language skills I was unable to find it. In any case, the maintainers list does not even have clickable links to the profiles. To discover which ones had emails on their profiles I had to type each name in by hand. And having used github for years, I know that github.com/jneen will take me to jneen's profile (where I might possibly find an email), but not every contributor will know that. And the most important consumers of the CoC are the comparatively hesitant and unconfident n00b contributors, and I think we should not be putting lots of hoops and knowledge checks between them and making CoC reports, since it's extremely easy for us to underestimate the difficulty of these.
But I mean it's not actually worse than my version.
Actually, I don't think you should take out "responsible for enforcement" (changing "community leaders" to "project maintainers" is fine). I think identifying this responsibility, both to the reporters and those who are in fact responsible, is important. Or at least, that the decision to make this identification in the text of the CC was made advisedly, so you should only change it if you really think you understand why the decision was made. Personally, I would just change as little as possible, especially insofar as this is a PR to reduce Coraline's email backlog, so it should not be combined with copy changes to the CC anymore than other PRs should combine bug fixes and refactoring if they can avoid it.
There was a problem hiding this comment.
Thank you for your thoughtful feedback @dradetsky 👍🏼 Really appreciated it.
since it's extremely easy for us to underestimate the difficulty of these.
Yep, totally agree with this. Sorry for the oversight.
We could perhaps reword it to read like the following:
reported to the project maintainers responsible for enforcement at jneen@jneen.net or tan.le@hey.com.
What do you think?
There was a problem hiding this comment.
10/10. I laughed, I cried, I gave it 2 thumbs up.
|
Thanks, @dradetsky. LGTM 👍🏼 |
As I suspected, this was incorrectly copied from e.g. the actual CoC of https://github.com/EthicalSource/contributor_covenant/ or some such place. The below is obviously suboptimal, but it at least ensures that Coraline doesn't get any more unnecessary email.