All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stewart Smith <stewart@linux.ibm.com>
To: Emily Shaffer <emilyshaffer@google.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Community Code of Conduct
Date: Wed, 10 Oct 2018 17:23:07 +1100	[thread overview]
Message-ID: <87va6ab9ro.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAJoAoZn3CSHRrtTi3r-B3aWn6t1CH3W3SLk_b_BJ3wiPsWrQvg@mail.gmail.com>

Emily Shaffer <emilyshaffer@google.com> writes:
> Hi all,
>
> As I briefly mentioned at the end of Brad's presentation today, I'd like to
> propose adding and enforcing a code of conduct for us to follow.
>
> For now, I am planning to grab a copy of the Linux CoC and put it up for
> review in /docs. If anybody has a different CoC source to suggest, I'd be
> happy to discuss.
>
> Brad asked me whether I had seen an issue so far and I had not, so please
> don't take this email as some kind of retaliation - it's not. I think we've
> got a great, positive community and as we grow I'd like to preserve that
> culture, and the code of conduct is a great way to do so.

Now's the time to do it. Taking an existing one is likely a really good
idea as no doubt corporations are about to start looking at these along
with contributor agreements and licensing before engaging in a project.

-- 
Stewart Smith
OPAL Architect, IBM.

  parent reply	other threads:[~2018-10-10  6:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09 18:27 Community Code of Conduct Emily Shaffer
2018-10-09 18:31 ` Jeff Osier-Mixon
2018-10-09 18:53   ` Emily Shaffer
2018-10-10  6:53     ` Jeff Osier-Mixon
2018-10-10 14:03       ` Emily Shaffer
2018-10-10 14:58     ` krtaylor
2018-10-11  2:51       ` Patrick Venture
2018-10-11 21:21         ` Emily Shaffer
2018-10-11 21:26           ` Patrick Venture
2018-10-11 21:28             ` Emily Shaffer
2018-10-15 18:24               ` Emily Shaffer
2018-10-10  6:23 ` Stewart Smith [this message]
2018-10-10 14:44 ` krtaylor

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=87va6ab9ro.fsf@linux.vnet.ibm.com \
    --to=stewart@linux.ibm.com \
    --cc=emilyshaffer@google.com \
    --cc=openbmc@lists.ozlabs.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.