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

Violation of code of conduct in https://github.com/openstreetmap/iD/issues/6409#issuecomment-495231649 #6442

Closed
SomeoneElseOSM opened this issue May 27, 2019 · 8 comments

Comments

@SomeoneElseOSM
Copy link

@SomeoneElseOSM SomeoneElseOSM commented May 27, 2019

iD has a code of conduct at https://github.com/openstreetmap/iD/blob/master/CODE_OF_CONDUCT.md and I believe that #6409 (comment) breaks a number of the rules outlined there. Specifically it

  • clearly fails to "Please be respectful to one another."
  • does not "assume that the person with whom you disagree is a smart person with good reasons for believing something different"
  • includes "Trolling or insulting/derogatory comments"

To be clear, I don't think that anyone doubts that the sometimes iD developers sometimes have to make difficult and unpopular decisions, and sometimes threads need to be locked to keep the same old questions being raised over and over again. That doesn't however seems to have been what's happened here - there's been relatively little discussion on #6042 and #6409 was closed with what can only be described as something of a rant.

I would suggest that, in line with the "When you make a mistake, apologize." clause of CODE_OF_CONDUCT.md , that a personal apology is made to the people referred to in that comment. This should include:

  • the "people on a mostly dormant mailing list" (the tagging list, I presume)
  • people who contribute to the osm wiki
  • people who contribute to "the weekly osm tabloid" (http://weeklyosm.eu I presume)

Best Regards,

Andy

PS: For the avoidance of doubt this is written in an entirely personal capacity. Full disclosure - I do occasionally edit and review http://weeklyosm.eu prior to publication (as can anyone else if they wish to sign up to do so).

@tastrax
Copy link
Contributor

@tastrax tastrax commented May 27, 2019

@bhousel
Copy link
Member

@bhousel bhousel commented May 28, 2019

@SomeoneElseOSM I take code of conduct violations very seriously. I'll ask for an independent volunteer who has been trained to take a report to follow up with you as soon as possible. This would normally be an anonymous process, but since you have opened up a public issue about it, we can't guarantee that for you.

Anyway, I'm asking you to limit your interaction with the iD project while the investigation happens, and I'll do the same.

I'm locking this thread - I know people hate when I do that, but further discussion of a CoC complaint is really not a good thing. (In the previous situation, I locked the thread because people where asked elsewhere to drop in and complain, not because there was a discussion happening).

In the future I'd really appreciate if people follow the part that says "Instances of unacceptable behavior may be reported privately to the project maintainers." Yes, I know it's about me and I'm the maintainer, but we would still follow the process and try to treat everyone fairly.

@bhousel bhousel closed this May 28, 2019
@openstreetmap openstreetmap locked and limited conversation to collaborators May 28, 2019
@openstreetmap openstreetmap unlocked this conversation Jun 20, 2019
@jonahadkins
Copy link

@jonahadkins jonahadkins commented Jun 20, 2019

Hi,

I’m an OSM-US & OSMF community member with prior training in CoC response. I was asked to adjudicate this incident. Here’s a synopsis of my review:

I reached out to the reporter (@SomeoneElseOSM) via 1:1 email on May 28th, 2019 to take a report of this incident. I reviewed the details of that report, which included the information in this Github issue above.

After this review, it is my belief that while the comment goes to great lengths to cordially state the view of the reportee (@bhousel ), parts of it do contain a derogatory tone. It is recommended that @bhousel should adhere to the stated iD Code of Conduct guideline of “When you make a mistake, apologize.” Specifically, its asked that an apology is posted below his comment on the iD Project GitHub issue. Both parties received a formal CoC response letter via email and I have personally discussed the response with them over phone/video chat.

I’d also like to add that this CoC review and report was difficult due to the lack of more formal processes for reporting and reviewing CoC issues. While reviewing, I consulted with two other community members (not involved with the incident) about CoC procedures in OSM. Therefore, I'd also like to recommend that the iD Project:

  • Creates a safe space for iD Project Code of Conduct reports to be made, such as a standard form available as a link from the CoC.
  • Designates individuals not involved with the project to handle Code of Conduct issues, ideally through a committee or working group made of diverse community members.
  • Work with other community members to develop a formal iD Project Code of Conduct process/procedure.

Please feel free to reach out to me with any comments, questions, or concerns.
Jonah Adkins
jonahadkins@gmail.com

@SomeoneElseOSM
Copy link
Author

@SomeoneElseOSM SomeoneElseOSM commented Jun 27, 2019

@jonahadkins I don't see an apology here (or at #6409 (comment) ). What's the next step?

@bhousel
Copy link
Member

@bhousel bhousel commented Jul 8, 2019

Thanks @jonahadkins for agreeing to step in as an independent responder. I agree that my tone on #6409 and other recent issues has been derogatory and I apologize for that.

When I established the Code of Conduct in #3051 I wrote:

I'm resolving to do a better job of keeping this project a friendly place where anyone can feel comfortable contributing.
When I fall short of this goal, please call me out on it.

Thank you @SomeoneElseOSM for “calling me out on it”.

I’d also like to add that this CoC review and report was difficult due to the lack of more formal processes for reporting and reviewing CoC issues. While reviewing, I consulted with two other community members (not involved with the incident) about CoC procedures in OSM.

I agree with all of Jonah's recommendations on improving the reporting process and I’m happy to implement these improvements with the help of the wider community. It would be great to see OSM-US take the lead on establishing an independent and shared CoC reporting process for projects that want to opt in to it.

@SomeoneElseOSM
Copy link
Author

@SomeoneElseOSM SomeoneElseOSM commented Jul 8, 2019

Thanks Brian.

As suggested above, would it also be possible to apologise on the tagging list directly? I can see that it would be technically difficult to do so to the OSM wiki as it doesn't really have a place for "announcements", and likewise I'm sure that http://weeklyosm.eu will see your message and can link to it if they want to, but the tagging list is something that it's possible to post to.

@bhousel
Copy link
Member

@bhousel bhousel commented Jul 8, 2019

As suggested above, would it also be possible to apologise on the tagging list directly?

It was not suggested above.

I will not be apologizing to anyone on any mailing lists or weekly OSM, nor do I expect any apologies from any of them for their behavior towards me.

Knock it off already. You've made your point.

@openstreetmap openstreetmap locked as too heated and limited conversation to collaborators Jul 8, 2019
@openstreetmap openstreetmap unlocked this conversation Jul 8, 2019
@SomeoneElseOSM
Copy link
Author

@SomeoneElseOSM SomeoneElseOSM commented Jul 9, 2019

For the avoidance of doubt, it was suggested in the initial comment at #6442 (comment) (and further comments at https://lists.openstreetmap.org/pipermail/talk/2019-May/082609.html et al reinforced in my mind the need for it).

As a community we have to work together - sometimes with people who hold different views. The first step along that road is always trying to engage with people and trying to understand where they're coming from, and that can't really happen if there's a refusal to communicate.

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

Successfully merging a pull request may close this issue.

None yet
4 participants