enhancement: adopt a formal code of conduct

[stapelberg]

Currently, i3 core contributors and/or i3’s BDFL (see PR #2675 for formalization) tell people when they are out of line within the i3 projects. For examples, see i3/i3status#43, i3/i3status#175, #1307 or i3/i3lock#56.

We should make it more clear to people what acceptable behavior within the i3 projects is. To that end, I propose adopting Django’s Code of Conduct, which I like because it lines up with the values that the current core contributors/BDFL uphold, is brief and easy to understand and was written specifically for a project where most interactions happen online (as opposed to an in-person conference).

I intend to move forward with this next weekend.

[Airblader]

I like the proposal. Short and on the spot. :-)

[nmschulte]

Sorry to derail, but I have a question: @stapelberg how did you manage to close an issue for i3/i3 from a different repository?

[Airblader]

The commit message directly refers to the i3 repository via i3/, so I assume that if you have the necessary privileges, Github does the magic.

[stapelberg]

Just put the full URL of the issue into the commit message. As @Airblader mentioned, GitHub verifies permission and closes the issue accordingly.