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

CoC: clarify personal-information bullet #1303

Closed
wants to merge 2 commits into from

Conversation

SethTisue
Copy link
Member

@SethTisue SethTisue commented Nov 14, 2021

I think the word "doxing" is slang; the boundaries of its meaning are disputed; and accusing someone of "doxing" is potentially a very serious accusation.

So I think it's better to be clear that something could fall under this bullet without actually necessarily qualifying as "doxing" per se.

I think the word "doxing" is slang; the boundaries of its meaning are
disputed; and accusing someone of "doxing" is potentially a very
serious accusation.

So I think it's better to be clear that something could fall under
this bullet without actually necessarily qualifying as "doxing" per se
@SethTisue
Copy link
Member Author

SethTisue commented Nov 14, 2021

Note that the bullet in question was taken verbatim from the Citizen Code of Conduct.

This change seems to me like a harmless clarification that doesn't alter what I understand to be the intention behind the text.

Regardless, I suggest we not merge it until:

  • We wait and see if any other such edits arise from the current community episode, where CoC issues are coming up.
  • We run the batch of edits by the major adopters of the code for feedback.

@SethTisue
Copy link
Member Author

fyi @darjutak @sjrd

conduct.md Outdated Show resolved Hide resolved
@SethTisue SethTisue changed the title CoC: clarify "doxing" bullet CoC: clarify personal-information bullet Nov 15, 2021
@SethTisue
Copy link
Member Author

in response to review feedback, I have pushed an additional commit that removes the word "doxing" altogether

@@ -101,7 +101,7 @@ Behavior that will lead to exclusion includes the following points, inspired by
* Violence, threats of violence or violent language directed against another person.
* Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.
* Posting or displaying sexually explicit or violent material.
* Posting or threatening to post other people’s personally identifying information ("doxing").
* Posting or threatening to post other people’s personally identifying information.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would help to clarify how this relates to public information

Suggested change
* Posting or threatening to post other people’s personally identifying information.
* Posting or threatening to post other people’s (non-public) personally identifying information.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the spirit of the change, but if personal identifying information is public but hard to find, and someone digs it out of an old usenet archive or something and posts it in the context of a heated argument, that is still very bad because it is frightening and potentially endangering them. Likewise, if someone happens to have a listed telephone number, tracking it down and posting it is bad. So I'm not 100% sold on this change. It might admit too much abuse for not enough clarification that sharing e.g. their twitter handle is fine.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we want to add wording that suggests that it's okay to 'post or threaten to post' other people’s public personally identifying information?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nafg - Well, if I am saying something like, "Hey I really like Li Haoyi's requests web server libraries" and someone else replies, "Oh really? That sounds good to me, but I have a few tricky requirements. I'd love to talk to him, if you think he'd not mind some questions" then I'm kind of in a bind if I can't mention any identifying information at all. You couldn't ever refer anyone to anyone if literally no personally identifying information could be posted.

@SethTisue
Copy link
Member Author

SethTisue commented Nov 15, 2021

I am voluntarily withdrawing the suggestion. I had considered it a harmless clarification, but it’s proving more contentious than I had anticipated.

UPDATE: see also https://contributors.scala-lang.org/t/taking-cyberstalking-seriously/5440/7 :

There was no intention to weaken the Code of Conduct, and the misunderstanding is now cleared up

@SethTisue SethTisue closed this Nov 15, 2021
@scala scala locked as too heated and limited conversation to collaborators Nov 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants