18f / code-of-conduct Goto Github PK

18F's code of conduct.

Home Page: https://18f.gsa.gov/code-of-conduct/

License: Other

code-of-conduct's Introduction

TTS Code of Conduct

This repository contains the official Code of Conduct of TTS, a digital delivery team within the General Services Administration.

Read the TTS Code of Conduct.

Credits

TTS is greatly appreciative of the multiple sources that we drew from to build this Code of Conduct, including:

Relevant legal considerations:

Public domain

This project is in the worldwide public domain. As stated in CONTRIBUTING:

This project is in the public domain within the United States, and copyright and related rights in the work worldwide are waived through the CC0 1.0 Universal public domain dedication.

All contributions to this project will be released under the CC0 dedication. By submitting a pull request, you are agreeing to comply with this waiver of copyright interest.

code-of-conduct's People

Contributors

Stargazers

Watchers

Forkers

rossetti-gov leahbannon geertgiebens pebsconsulting jwchumley zorro2000se isabella232 meto87 novidwi tanviralam mattdryan ashenwijesingha

code-of-conduct's Issues

Missing button on page

I just noticed that on 'Accessibility for teams' there seems to be a button missing to move from the Information Architecture page to the Video and Multimedia page below the WCAG references.

adapt for the public chat rooms

We don't currently have a Code of Conduct for our public chat rooms, but really should. What would need to be added to this repository (or elsewhere) to cover our butts? Is there anything specific for public chat that differs from in-person working, non-public Slack channels, events, repositories, etc? A few things that come to mind:

Link to the policy from https://chat.18f.gov and/or the room /topics
State the circumstances that would get someone blocked/booted

Bind the public to the code for digital forums

In order to give us the right to moderate comments (wherever they are given) the Code needs to be incorporated into our Terms up front on all of our websites.

Previous example I worked on: http://www.consumerfinance.gov/comment-policy/

Supe guidelines: clarify responsibilities between official and unofficial supervisors

make repo public

Any remaining steps needed?

[Guidelines] Clarify guidelines for non-supervisors

Folks who are not in official supervisory positions may have code of conduct concerns brought to them. We need to clarify guidelines for these folks.

Web form to file reports easily

Recognizing that there may be formal process requirements that make it difficult, it would be nice to see the reporting system be as easy as possible. The current informal process says:

if you are being harassed in an 18F space, please speak to the organizer/admin of that space. If you can't reach them or are uncomfortable talking to them, any member of the 18F team can put you in touch with 18F Acting Executive Director Aaron Snow or Deputy Executive Director Hillary Hartley. GSA employees also have the option of raising their concerns with the Office of Human Resources Management or the Office of Civil Rights.

These are a lot of options, and require a fair amount of decisionmaking and effort on the part of the reporter. Additionally, they require a reporter to reveal him or herself--both by speaking with a representative of 18F and, at events, by publicly approaching that person--in order to make the report. It's possible that this has a chilling effect on making reports.

One possible alternative is to create a page on the 18F site with a form for submitting code of conduct reports. That form can send the report by email to the appropriate people, post in an appropriate Slack channel, or whatever else you want. Ideally, this form would have optional name and contact fields, so that reporters can choose to submit anonymously where privacy or retaliation is a concern. To make things easier for 18F, that page could also include some text about what information is useful as part of a report. It should also be clear where the report will go once submitted.

Check the "Contributing" language

We discussed the change process for the Code of Conduct, but the notes in the doc on that discussion are incomplete. Can folks (@leahbannon, @jackiekazil, @NoahKunin, @ultrasaurus) look at https://github.com/18F/code-of-conduct/blob/master/CONTRIBUTING.md#requesting-changes and confirm that it reflects your understanding of what we decided?

Reporting Process

I put in a placeholder for a real reporting process. @quepol, @aaronsnow, do either of you have time to think about how 18F should handle harassment reports?

Put reporting language in the Code of Conduct itself?

The reporting mechanism seems like a crucial piece of the Code and could fit well at the beginning (or end) of the document.

Can you make the Guideline for Supervisors publicly accessible?

This document linked to in code-of-conduct.md is locked down by permissions. Can you make it publicly accessible if indeed the contents of this repo are public domain?

Additional suggestion: make it a .md file rather than a link to Google docs?

Clarify reporting language

I'm assuming the Code should not state a preference as to where to report (18F staff or GSA). If that's the case, some changes might help clarify that. Happy to pull request some edits to that end if people want that.

Credits section coming back?

Is the Credits section from the original draft coming back? Feels important to acknowledge all the work that helped inform this discussion. Could be in the README of the repo, as long as we link to it/acknowledged.

How do outside contributors report Code of Conduct violations?

As an outside contributor on github, it's unclear how one would report a violation of the Code of Conduct. The language around enforcement refers to "contacting your supervisor" which an outside contributor wouldn't have. Instead, we should have a clear path for outside contributors to report so the Code of Conduct can be enforced on their behalf as well.