Gather up list of conflict resolution use cases updated [#1597254]

Let's use this issue summary to gather up cases of conflicts in the community so we can base our policy discussions on real-world scenarios.

#1446414: standard.inc does not match ISO 3166-1 alpha-2: Conflict is around geo-political issues and where we as a project draw the line.
#1553388: Offensive user name: Conflict is about choice of username.

Comments

Comment #1

Dave Reid

he/him

English

Nebraska USA

CreditAttribution: Dave Reid commented 23 May 2012 at 16:16

#1272560: Entity tokens duplicates field tokens created by token module: Conflict between maintainers

Comment #2

rfay

English

Palisade, CO, USA

CreditAttribution: rfay commented 23 May 2012 at 16:39

Title:

Gather up list of governance use cases

» Gather up list of conflict resolution use cases

Great initiative. Will be great to have these in one place.

Retitling because conflict resolution (and management) is just one small (we hope... and maybe we can make it smaller) corner of governance.

Comment #3

webchick

she/they

English

Vancouver 🇨🇦

CreditAttribution: webchick commented 23 May 2012 at 21:52

Here's a really great example of why I recommended in the other post that we (or someone in close contact with the conflict resolution team) keep an eye on Twitter. :\

This post http://www.modelbuzz.tv/2012/03/14/denver-modeling-agency-finds-success-... started making the rounds, as it's a modeling agency claiming to have done "booth babe" duty at DrupalCon Denver.

Ashe posts https://twitter.com/ashedryden/status/205017315287384064:
"I'd love to know who is hiring booth babes so I can be sure to never do business with them"

Which then prompts this: https://twitter.com/RobertCaracaus/status/205116026537521154
"Booth Babes!? I saw those grls & though maybe ‪#drupal‬ actually attracted a few good looking girls 4 a change!"

Which then prompts this: http://softpixel.com/~bbinkovitz/News/May-2012 ... a blog post from a prospective DrupalCon attendee who overheard this chatter and is now wondering if it's actually a safe environment for her to go to, given the opinions expressed.

Which then prompts this: https://twitter.com/RobertCaracaus/status/205400120991289344
"I didn't realize @ashedryden was female, young, AND cute. I have foot in mouth disease!"

Which then prompts this: https://twitter.com/ashedryden/status/205400526177845249
"It really isn't too much to ask to not be creepily sexualized as a member of the tech community."

Which then prompts a back-handed apology: https://twitter.com/RobertCaracaus/status/205403740247818241
"I understand the hostility towards judging people based on looks. Will be more careful. Sorry?"

Which then prompts me to practice the fine art of slapping people in 140 characters or less: https://twitter.com/webchick/status/205403448173277184
"Dude. Not cool. We don't treat women as objects in this community—they're contributors, and leaders. Apologize."

Which then prompts* an actual apology (we hope): https://twitter.com/RobertCaracaus/status/205412269658611712
"I sincerely apologise."

Which then ends the conflict (for now).

All of this happened within the space of about an hour. However, we've had situations like this that have escalated over days, too. http://funnymonkey.com/an-incomplete-history-of-sexism-in-drupal has a bunch. Intervention as swiftly and firmly as possible is generally the key to stopping these things from blowing up into a community-combusting fireball and causing people to feel attacked, threatened, unsafe, and ultimately leaving the project.

* I am not trying to take credit for ending this conflict; many other people were chiming in here too with great points. I'm not sure what ultimately led him to back off, this was just my view of the situation.

Comment #4

mariomaric CreditAttribution: mariomaric commented 5 June 2012 at 17:55

Would this use case count?

Post @ Best Practices in Drupal Security - http://groups.drupal.org/node/218139 and discussion below comment http://drupal.org/node/711000#comment-5734594.

Cheers.

Comment #5

webchick

she/they

English

Vancouver 🇨🇦

CreditAttribution: webchick commented 10 July 2012 at 09:26

More examples:

http://groups.drupal.org/node/237248 - Two Drupal NYC events, conflicts and assertions lead to the development of a joint statement. (Interesting, yet time consuming approach, and comments are still flowing in.)

http://drupal.org/node/1671102 - Marketplace guidelines, an example of where we need a policy creating policy, since this discussion is getting hung up in assumptions of bad faith.

http://drupal.org/node/1609760#comment-6192506 and down... I still have no idea what happened here, but once again a technical conflict boiled over into a seething community conflict that's still not resolved and has left a trail of wreckage in its wake.

Comment #6

willyk CreditAttribution: willyk commented 15 July 2012 at 05:31

Title:

Gather up list of conflict resolution use cases

» Timing to Complete List

Do these need to be gathered prior to the sprint, or is this a post-sprint action item?

If they are needed prior to the sprint I can try to expand on the list by Monday if that's be helpful.

Comment #7

willyk CreditAttribution: willyk commented 15 July 2012 at 05:34

Title:

Timing to Complete List

» Gather up list of conflict resolution use cases updated

Do these need to be gathered prior to the sprint, or is this a post-sprint action item?

If they are needed prior to the sprint I can try to expand on the list by Monday if that's be helpful.

Comment #8

gdd

he/him

English

Portland, OR

CreditAttribution: gdd commented 15 July 2012 at 06:05

This list wasn't started in relation to the sprint specifically, so I think any additional items would be useful to add in whatever case. I'm not sure that expansion on existing items is particularly helpful though. We're not necessarily trying to resolve these things, but just to collect data points that can serve as examples of the types of things we're concerned with.