From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Keith Packard <keithp@keithp.com>,
tfheen@err.no,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Daniel Stone <daniels@collabora.com>
Subject: Re: [PATCH] drm: Document code of conduct
Date: Tue, 11 Apr 2017 12:01:33 +0200 [thread overview]
Message-ID: <735535aa-eb54-555c-d7cb-50bc560106bd@linux.intel.com> (raw)
In-Reply-To: <20170411064815.5399-1-daniel.vetter@ffwll.ch>
Op 11-04-17 om 08:48 schreef Daniel Vetter:
> 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.
>
> Note: As Daniel Stone mentioned in the announcement fd.o admins
> started chatting with the communities their hosting, which includs the
> X.org foundation board, to figure out how to fan out enforcement and
> allow projects to run things on their own (with fd.o still as the
> fallback). So the details of enforcement (and appealing decisions)
> might still change, but since this involves the board and lots more
> people it'll take a while to get there. For now this is good enough I
> think.
>
> For the text itself I went with the same blurb as the Wayland project,
> didn't feel creative yet this early in the morning:
>
> https://cgit.freedesktop.org/wayland/wayland/commit/?id=0eefe99fe0683ae409b665a8b18cc7eb648c6c0c
>
> Cc: Daniel Stone <daniels@collabora.com>
> Cc: Keith Packard <keithp@keithp.com>
> Cc: tfheen@err.no
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
> Documentation/gpu/introduction.rst | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/Documentation/gpu/introduction.rst b/Documentation/gpu/introduction.rst
> index 05a82bdfbca4..0f5173e29bdc 100644
> --- a/Documentation/gpu/introduction.rst
> +++ b/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.
Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-04-11 10:01 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 6:48 [PATCH] drm: Document code of conduct Daniel Vetter
2017-04-11 7:08 ` Daniel Stone
2017-04-11 7:33 ` Sumit Semwal
2017-04-11 7:51 ` Archit Taneja
2017-04-11 8:25 ` [Intel-gfx] " Martin Peres
2017-04-12 12:59 ` Sumit Semwal
2017-04-11 9:03 ` Daniel Vetter
2017-04-11 9:52 ` Neil Armstrong
2017-04-12 9:35 ` Laurent Pinchart
2017-04-11 9:09 ` Chris Wilson
2017-04-11 9:19 ` Thierry Reding
2017-04-11 9:24 ` Jani Nikula
2017-04-11 9:43 ` Vincent ABRIOU
2017-04-11 10:01 ` Maarten Lankhorst [this message]
2017-04-11 10:04 ` Brian Starkey
2017-04-11 12:37 ` Rob Clark
2017-04-11 13:12 ` Luc Verhaegen
2017-04-11 13:24 ` Daniel Vetter
2017-04-11 13:30 ` Luc Verhaegen
2017-04-11 13:36 ` Daniel Vetter
2017-04-11 13:39 ` Luc Verhaegen
2017-04-11 13:58 ` Jani Nikula
2017-04-11 15:14 ` Luc Verhaegen
2017-04-11 15:31 ` Daniel Vetter
2017-04-11 15:48 ` Alex Deucher
2017-04-11 13:35 ` David Herrmann
2017-04-11 13:48 ` Sean Paul
2017-04-11 15:40 ` Harry Wentland
2017-04-11 15:50 ` Alex Deucher
2017-04-11 16:09 ` Daniel Vetter
2017-04-11 17:17 ` Alex Deucher
2017-04-11 16:19 ` Eric Anholt
2017-04-11 17:28 ` Gustavo Padovan
2017-04-12 9:26 ` Michel Dänzer
2017-04-12 13:34 ` Keith Packard
2017-04-14 2:43 ` Gabriel Krisman Bertazi
-- strict thread matches above, loose matches on Subject: below --
2017-04-18 10:10 Daniel Vetter
2017-04-18 19:32 ` Adam Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=735535aa-eb54-555c-d7cb-50bc560106bd@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=keithp@keithp.com \
--cc=tfheen@err.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox