I like this update. It adds the things that need to be added without adding a
ton of text, and focuses the manifesto itself while keeping the same spirit.
I will update the PR with these changes shortly.
On Sunday, February 3, 2019 5:28:42 PM CST Margaret Staples wrote:
> I've done a lot of research in the last few years on serving
> underrepresented developers in tech community spaces, which has
> unsurprisingly included a ton of info on what's important in a CoC.
> Here are the things I have turned up as important to an effective Code of
> (removing the bits that are only relevant to events)
> Code of Conduct provides...
> - a clear reporting process*
> - multiple ways to report
> - an anonymous reporting option**
> - options for reporting to humans of different gender presentations
> Code of Conduct is...
> - prominent on the website
> - discussed openly and supportively by leadership
> Code of Conduct contains...
> - clear language on expected behavior including zero tolerance for
> derogatory language about or harassment of people of color, women, LGBTQ,
> those with disabilities
> - clear language on potential consequences for bad behavior
> - clear language emphasizing intervention and safety
> 1. *Discrimination harms us*. This includes discrimination, derogatory
> language, or harassment on the basis of race, gender, sexual orientation,
> disability, age, nationality, technology and any other arbitrary
> designation of a group of people.
> 2. *Boundaries honor us*. Your comfort levels are not everyone’s comfort
> levels. Remember that, and if brought to your attention, heed it.
> 3. We are our biggest assets. None of us were born masters of our trade.
> Each of us has been helped along the way. Return that favor when you can,
> and be respectful of others' place in their journey.
> 4. *Respect defines us*. Treat others with respect and compassion unless
> they abuse that trust. Make your discussions, criticisms and debates from
> a position of respect for the humanity of all involved. Ask yourself, is it
> true? Is it necessary? Is it constructive? Anything less is missing the
> 5. *Reactions require grace*. Angry responses are valid, but neither
> abusive language nor harmful actions are acceptable. If something happens
> which concerns you, address it directly or report it, but be respectful.
> Allow the organizers time to discuss the incident with the offender and
> possibly correct the issue.
> 6. *To err is human; always be iterating*. You might not intend it, but
> mistakes do happen and contribute to build experience. Tolerate honest
> mistakes, and don't hesitate to apologize if you make one yourself.
> Remember, apologies are hallow without also correcting the behavior.
> On Tue, Jan 29, 2019 at 9:06 AM Chuck Burgess <demon...@gmail.com
> > Looking over both the manifesto and the covenant, I didn't really notice
> > anything that would conflict between the two, if we wanted to simply
> > include *both*... doing so would just be presenting an intersection of
> > their requirements. Is that too much verbiage overall? Maybe just link
> > to
> > both, since they are standalone entities (that seem to be versioned, or at
> > least versionable)? Stating that we want to abide by both, then
> > delineating how those in FIG positions can act to enforce, ... maybe that
> > would cover the concerns mentioned?
> > CRB
> > *about.me/ashnazg
> > <https://groups.google.com/d/msgid/php-fig/CANsgjnv%2BtYJxR15i17QMRGJT%3D
> > %3D2QtjmeDEYO4p%2B3fbgQ5Pg-QA%40mail.gmail.com?utm_medium=email&utm_source
> > =footer> .