drm: Document code of conduct

freedesktop.org has adopted a formal&enforced code of conduct:

https://www.fooishbar.org/blog/fdo-contributor-covenant/
https://www.freedesktop.org/wiki/CodeOfConduct/

Besides formalizing things a bit more I don't think this changes
anything for us, we've already peer-enforced respectful and
constructive interactions since a long time. But it's good to document
things properly.

v2: Drop confusing note from commit message and clarify the grammer
(Chris, Alex and others).

Cc: Daniel Stone <daniels@collabora.com>
Cc: Keith Packard <keithp@keithp.com>
Cc: tfheen@err.no
Signed-off-by: NDaniel Vetter <daniel.vetter@intel.com>
Reviewed-by: NDaniel Stone <daniels@collabora.com>
Reviewed-by: NSumit Semwal <sumit.semwal@linaro.org>
Acked-by: NArchit Taneja <architt@codeaurora.org>
Reviewed-by: NMartin Peres <martin.peres@free.fr>
Acked-by: NThierry Reding <treding@nvidia.com>
Acked-by: NJani Nikula <jani.nikula@intel.com>
Acked-by: NVincent Abriou <vincent.abriou@st.com>
Acked-by: NNeil Armstrong <narmstrong@baylibre.com>
Reviewed-by: NMaarten Lankhorst <maarten.lankhorst@linux.intel.com>
Acked-by: NBrian Starkey <brian.starkey@arm.com>
Acked-by: NRob Clark <robdclark@gmail.com>
Reviewed-by: NDavid Herrmann <dh.herrmann@gmail.com>
Acked-by: NSean Paul <seanpaul@chromium.org>
Reviewed-by: NHarry Wentland <harry.wentland@amd.com>
Reviewed-by: NEric Anholt <eric@anholt.net>
Acked-by: NAlex Deucher <alexander.deucher@amd.com>
Acked-by: NGustavo Padovan <gustavo.padovan@collabora.com>
Acked-by: NMichel Dänzer <michel.daenzer@amd.com>
Acked-by: NLaurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: NSumit Semwal <sumit.semwal@linaro.org>
Acked-by: NKeith Packard <keithp@keithp.com>
Acked-by: NGabriel Krisman Bertazi <krisman@collabora.co.uk>
Acked-by: NAdam Jackson <ajax@redhat.com>
Signed-off-by: NDave Airlie <airlied@redhat.com>

Documentation/gpu/introduction.rst

@@ -85,3 +85,14 @@ This means that there's a blackout-period of about one month where feature work
 can't be merged. The recommended way to deal with that is having a -next tree
 that's always open, but making sure to not feed it into linux-next during the
 blackout period. As an example, drm-misc works like that.
+
+Code of Conduct
+---------------
+
+As a freedesktop.org project, dri-devel, and the DRM community, follows the
+Contributor Covenant, found at: https://www.freedesktop.org/wiki/CodeOfConduct
+
+Please conduct yourself in a respectful and civilised manner when
+interacting with community members on mailing lists, IRC, or bug
+trackers. The community represents the project as a whole, and abusive
+or bullying behaviour is not tolerated by the project.