Code of Conduct

[gnarf]

Would close #104

• [x] Requires https://github.com/jquery/jquery-wp-content/pull/367
• [x] Requires Conduct committee
• [x] Requires conduct@jquery.org e-mail
• [x] Requires jQuery Board Approval
• [x] Requires jQuery Developer Leads Approval
• [x] Requires foundation@jquery.org or similar email for public to reach Foundation Board for appeals

Please comment, suggest changes, etc. This is a very quick copy/replace Django with jQuery to start with from Djano Project's CoC

[kborchers]

I have created the conduct@jquery.org address and currently those emails will go to @gnarf, @agcolom, @ajpiano, @jeresig and myself. As the committee grows/changes just let me know and I can update that list.

[gnarf]

Anne, feel free to add a commit with the typo fixes, or I can later today, also consider upstream fix on django too: https://github.com/django/djangoproject.com/edit/master/djangoproject/templates/conduct/enforcement.html

[robbbz]

Good to see jQuery as a foundation looking into this. Sad that it kinda came too late.

I have created the conduct@jquery.org address and currently those emails will go to @gnarf, @agcolom, @ajpiano, @jeresig and myself.

Would you also please consider adding some more active commiters? From what I can tell those people are mainly doing work in private or simply behind the scenes. That's alright, but aren't the best people to do this the people that are actively involved with communication and the projects of the foundation?

That also makes other way more likely to reach out when needed. To give another example, I lurk in #jquery frequently, and nobody on this list will notice if something goes wrong there.

[agcolom]

Sure, I'll see if I get a chance later

On 16 Jul 2015, at 14:40, Corey Frang wrote:

Anne, feel free to add a commit with the typo fixes, or I can later today, also consider upstream fix on django too: https://github.com/django/djangoproject.com/edit/master/djangoproject/templates/conduct/enforcement.html

— Reply to this email directly or view it on GitHubhttps://github.com/jquery/jquery.org/pull/105#issuecomment-121958600.

The University of Westminster is a charity and a company limited by guarantee. Registration number: 977818 England. Registered Office: 309 Regent Street, London W1B 2UW.

This message and its attachments are private and confidential. If you have received this message in error, please notify the sender and remove it and its attachments from your system.

[robbbz]

@agcolom Are you replying to me or to somebody else?

[sfrisk]

Most of my comments were pretty nitpicky, but overall you've done a great job, @gnarf!

[gnarf]

@ robbbz

Would you also please consider adding some more active commiters? From what I can tell those people are mainly doing work in private or simply behind the scenes. That's alright, but aren't the best people to do this the people that are actively involved with communication and the projects of the foundation?

Both @ajpiano and I are still lurking #jquery on the regular. @agcolom is the lead on the content team and quite active. @ajpiano is at every event, @jeresig is passionate about diversity and the CoC.

The "activeness" in the project of the people on the conduct committee is kind of irrelevant, we are looking for other people who are interested at some point, these 4 people are just a seed committee.

[agcolom]

@robbbz sorry my question was just a general reply.

[gnarf]

For example, I'd suggest these lists be phrased, punctuated, and capitalized identically:

Are there other overlaps? I feel duplicating some of the information on the reporting and enforcement pages would be okay, but perhaps for any big overlaps we should just link to the enforcement manual.

I do think the list should probably be duplicated.

• Who the bad actor was.

actor(s) were?

[lady3bean]

In the reporting guidelines, the section about what will happen after a report is made is a slimmed down version of the enforcement manual. The manual's sections on Acting Unilaterally, Conflicts of Interest, and the first paragraph under the Resolutions section are okay to leave out of the guidelines because that concerns the internal actions of the committee. However, the list that follows in the manual for possible responses to a report is much better than in the guidelines: one big difference here is that the manual talks about keeping names confidential even in a public report, unless the person involved instructs them otherwise. That's a pretty huge difference because without it, it could seem that by reporting an incident you might be publicly exposed for it, which is highly undesirable.

[gnarf]

That's a pretty huge difference because without it, it could seem that by reporting an incident you might be publicly exposed for it, which is highly undesirable.

agreed -- Is that another list that should be "carefully duplicated" on both pages or do you think we should link from one to the other for that information.

[lady3bean]

Having thought about it a couple ways, I think the guidelines should link to the manual for what happens after a report and not include that info itself, because the manual is being published instead of remaining an internal document so people can see what you'd be doing in the case of a report. The guidelines could therefore be focused on how to file a report and what to include, and the manual would then be the deeper explanation of how it will be handled.

[iamcarrico]

I like this, a lot. One change I have seen in other Codes of Conduct— include Drupal, Ubuntu, and Sass— is a paragraph about stepping down considerately. The idea behind it is to, as a guideline, ensure people don't leave a project in a lurch— especially when many others may rely on it.

The Sass guidelines use:

## Step down considerately

When somebody leaves or disengages from the community, we ask that they do so in a way that minimizes disruption to the projects using their published work. They should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off.

But overall, HUGE props to the jQuery community and the jQuery leaders for putting this out! @gnarf++ I'm excited to see another community adopt a good Code of Conduct to ensure the future of web development is an open and inviting place.

[jeresig]

I think this is all fantastic. Thank you so much, @gnarf, for tackling this - and thank you to everyone else for providing such great feedback. Excited to have this in place!

[gnarf]

@gabrielschulhof thanks for the very detailed comments - busy for the next few days, but will try to implement your corrections ASAP!

[gnarf]

I like this, a lot. One change I have seen in other Codes of Conduct— include Drupal, Ubuntu, and Sass— is a paragraph about stepping down considerately.

Hrm - I'm actually very on the fence about this one. I kind of feel like part of responsible management of projects makes the need for this to be specified moot. If we keep the process and code in the open, someone should have the tools needed to carry on if someone "disappears without notice". I'd also think it's well within anyones right to do so, for any number of reasons.

I'm going to resist adding this bit for now, unless other people have strong opinions that we should include it, in which case, please bring them to the table!

[arschmitz]

@gnarf :+1: for leaving that section out for now. I think proper open governance of projects makes this a non issue. I also think as you said any volunteer should have the right to leave at any time, things happen in peoples lives and we are not here to judge or impose on what may happen in others lives to cause them to no longer be involved. I understand the sentiment behind adding this but unless it comes up as an actual continuing problem hurting the projects, I am in favor of leaving this out.

[kborchers]

I think this looks great. From the board perspective, I believe we should be ok with this based on the silence but if anyone in @jquery/directors disagrees please speak now. Corey if no one objects in the next day or so I would say please move forward and thanks again for your and the committee's efforts on this!

[arthurvr]

@kborchers This isn't yet really ready to land as @agcolom wanted to make some changes (see https://github.com/jquery/jquery.org/pull/106). Besides from that this LGTM and is super awesome work! Thanks @gnarf!

[kborchers]

Any update on this? Would really like to get this landed and in place. I know there is now another PR against it so that needs to be reviewed and merged. Can the committee prioritized getting this landed? Do you need anything from me?

[gnarf]

I've pinged the @jquery/conduct committee - The "other PR" was already merged in, I think we are super close.

[kborchers]

There is still the PR from Sarah at #108 that has not been merged from what I can tell.

[gnarf]

There is still the PR from Sarah at #108 that has not been merged from what I can tell.

oops - didn't see that one!! Merged now! Thanks @sfrisk

[sfrisk]

No problem!

[kborchers]

Can we merge this today?

[gnarf]

Requires jQuery Developer Leads Approval

There's a meeting today - I'll make sure this happens