Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update FEP to include unacceptable behaviours. #234

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

spdegabrielle
Copy link
Member

Making the list of unacceptable behaviours a reference to another document just makes it harder to read and adds a dependency on the acm website. This PR copies the current text at https://www.acm.org/about-acm/policy-against-harassment verbatim.

Making the list of unacceptable behaviours a reference to another document just makes it harder to read and adds a dependency on the acm website. 
this PR copies the current text at https://www.acm.org/about-acm/policy-against-harassment verbatim.
@joelmccracken
Copy link

Are the bidirectional unicode characters embeded in this PR intentional? See the warning under "Files changed"; looks like a weird copy/paste thing from the acm site

@mfelleisen
Copy link
Contributor

@spdegabrielle {{ Sorry I am buried in work this week. I didn't notice your request until now -- by accident . ]]

I agree with you that an exploit list is overburdening the statement. We are friendly community. (Yes, I have been accosted on occasion on issues that are not listed. I have a thick skin, so I would never ever report something like that. if I had a thin skin, the list might deter me from reporting it.)

@spdegabrielle
Copy link
Member Author

@mfelleisen Thanks Matthias, no need to apologise.

on issues that are not listed

this is indicates to me the reference to the ACM list is not sufficient, and further reason to update this to meet the needs of everyone.

My goal is to make it clear that everyone is welcome, and set clear boundaries, so any undesirable behaviours are addressed quickly, before they can escalate or damage the parties involved.

Before we commit to this PR, would it be better to look at the Rust, Go and Julia* to see if they are a better fit?

If you think that is a good approach I'll raise an issue with those lists as a starting point, before jumping into a PR.

Please let me know how you want to move forward.

best regards

Stephen

[* I deliberately choose other open source language communities that I believe are well regarded]

PS
Thanks @joelmccracken for spotting the bidirectional unicode characters. Another reason not to depend on the ACM website.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants