All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luc Verhaegen <libv@skynet.be>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	members@x.org, DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm: Document code of conduct
Date: Tue, 11 Apr 2017 15:12:47 +0200	[thread overview]
Message-ID: <20170411131247.GC18682@skynet.be> (raw)
In-Reply-To: <20170411064815.5399-1-daniel.vetter@ffwll.ch>

On Tue, Apr 11, 2017 at 08:48:15AM +0200, Daniel Vetter wrote:
> 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

"started" and "chatting"? That is very weakly formulated.

> X.org foundation board, to figure out how to fan out enforcement and

This was not voted upon or even mentioned during the last board meeting. 
And i think the next board meeting is only in 2 days time. As such, this 
seems like it is not something that's officially sanctioned by the X.org 
foundation board, but you sure do try to make it sound like such.

Luc Verhaegen.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-04-11 13:12 UTC|newest]

Thread overview: 39+ 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:06 ` ✗ Fi.CI.BAT: warning for " Patchwork
2017-04-11  7:08 ` [PATCH] " 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
2017-04-11 10:04 ` Brian Starkey
2017-04-11 12:37 ` Rob Clark
2017-04-11 13:12 ` Luc Verhaegen [this message]
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
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=20170411131247.GC18682@skynet.be \
    --to=libv@skynet.be \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=members@x.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.