An archive of programming conferences' & organizations' Code of Conduct policies. In tasty plain text & metadata, so they can be diffed painlessly and optionally jekyllized.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
CONTRIBUTING.md
EXAMPLE-CONFERENCE.md
EXAMPLE-ORGANIZATION.md
README.md
apachecon-na-2013.md
codemotion-2015.md
django-weekend-cardiff-2014.md
eurucamp-2013.md
frozen-rails-2014.md
geek-feminism-long-20140204.md
geek-feminism-medium-20140204.md
geek-feminism-short-20140204.md
google-developers-groups.md
google-events.md
goruco-2013.md
heroku-2013.md
jrubyconfeu-2013.md
lambdajam-2014.md
linux-tag-2014.md
open-source-bridge-2014.md
papers-we-love-org.md
pass-summit-2012-draft.md
plone-foundation-2012.md
plone-symposium-midwest-2014.md
ploneconf-2013.md
pycon-australia-2013.md
rails-camp-nz-2014.md
rubyconf-2013-long.md
rubyconf-2013-short.md
rubyconf-au-2014.md
rubyconf-uruguay-2014.md
stumptown-syndicate-2013.md
write-speak-code-2013.md
yet-another-perl-conference-north-america-2014.md

README.md

code-of-conduct-diffinator

An archive of programming conferences' code of conduct policies. In tasty plain text, with metadata, so they can be diffinated painlessly.

===

Why

Ability to explore programming conference codes of conduct -- how they derive, adapt, and inspire others -- gives us valuable insights; as programming conference organizers who seek create a code and refine it, as community members who are held accountable for upholding it, and as sponsors who evaluate whether to support it.

Exploring a spectrum of approaches, and their nuances of language, gives us insights into conferences' values, vision, and expectations.

IMPORTANT: Inclusion of a particular code of conduct is neither intended as endorsement nor disapproval. A dataset of varied examples gives everyone a useful basis for more thoughtful conversations. You can help add to the conversation by contributing pull requests for additional programming conferences and organizations.

Usage

$ git clone https://github.com/cczona/code-of-conduct-diffinator.git

$ cd code-of-conduct-diffinator

$ diff -y conference-1.md conference-2.md

Alternate Usage

There are many alternatives to the diff command. For comparing codes of conduct, word or character diffs are more informative anyway.

opendiff

Xcode Commandline Tools includes a nice GUI called FileMerge.app, which does word diffs. Filemerge is invoked at the commandline as opendiff.

$ opendiff

wdiff & colordiff

$ wdiff conference-1.md conference-2.md | colordiff

(Mac users: these are available from Homebrew.)

gvim

$ gvim -d

Crediting

When developing a code of conduct for your programming conference, please attempt to credit the sources it draws upon, so others can likewise benefit from understanding differing approaches. For example:

Adapted from the codes of conduct by JsConfEU <http://2013.eurucamp.org/policies> and Geek Feminism <http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy>, using source materials archived at <https://github.com/cczona/code-of-conduct-diffinator>

Contribute!

Does your conference publish a code of conduct? We <3 pull requests. See CONTRIBUTING.md for info.

===

code-of-conduct-diffinator is maintained by @cczona for CallbackWomen <http://callbackwomen.com\>