From: Laura Abbott <labbott@redhat.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: ksummit-discuss@lists.linuxfoundation.org,
gregkh@linuxfoundation.org, Tim.Bird@sony.com, olof@lxom.net
Subject: Re: [Ksummit-discuss] [TECH-TOPIC] Review - Code of Conduct: Let's revamp it.
Date: Thu, 27 Sep 2018 01:30:17 -0700 [thread overview]
Message-ID: <e3cb7b83-2680-aadb-6c3b-aa6fb0ba6439@redhat.com> (raw)
In-Reply-To: <20180926144703.GC3321@thunk.org>
On 09/26/2018 07:47 AM, Theodore Y. Ts'o wrote:
> On Wed, Sep 26, 2018 at 01:04:30AM -0700, Laura Abbott wrote:
>>
>> Fedora is going through a similar process to revamp its code of conduct.
>> It's not fully released yet but from talking to some people involved,
>> they started from the contributor covenant and made some changes and
>> amendments. Some of the amendments were to clarify the purpose of the
>> code of conduct. Given Fedora also has a heavily e-mail based workflow,
>> I think this is a good indication it should be possible to make
>> modifications to meet our needs.
>
> Is there someone from the Fedora community who is working on this who
> might be willing to share some private comments, suggestions,
> reflections, etc. with the TAB? I imagine Fedora is working on this
> on their own schedule, and it might not be done before the
> Maintainer's Summit, but if there is any wisdom, potential pitfalls,
> concerns, etc., that they might be willing share, I'm sure it would be
> most helpful.
>
> (Speakinig only for myself.)
>
> Thanks,
>
> - Ted
>
I'll reach out to several of the people involved to see if they
would be willing to share their insights. In the meantime,
https://pagure.io/Fedora-Council/tickets/issues?status=Open&tags=code-of-conduct
is the public tracker if anyone is interested in the types of
issues Fedora has/is thinking about. In particular, I think
https://pagure.io/Fedora-Council/tickets/issue/105
provides a nice summary.
Thanks,
Laura
next prev parent reply other threads:[~2018-09-27 8:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 14:24 Shuah Khan
2018-09-24 17:51 ` James Morris
2018-09-24 18:11 ` John W. Linville
2018-09-24 19:54 ` Josh Triplett
2018-09-24 20:46 ` Olof Johansson
2018-09-24 22:21 ` Thomas Gleixner
2018-09-25 4:26 ` Daniel Vetter
2018-09-25 6:21 ` Olof Johansson
2018-09-25 8:45 ` Thomas Gleixner
2018-09-25 16:42 ` Daniel Vetter
2018-09-25 20:03 ` Shuah Khan
2018-09-25 6:46 ` Dan Williams
2018-09-24 19:31 ` Jason Cooper
2018-09-26 20:57 ` Mauro Carvalho Chehab
2018-09-24 23:15 ` James Bottomley
2018-09-25 1:35 ` Joe Perches
2018-09-26 6:54 ` Jani Nikula
2018-09-26 9:19 ` Jan Kara
2018-09-26 9:58 ` Hannes Reinecke
2018-09-26 12:35 ` Mauro Carvalho Chehab
2018-09-26 16:43 ` Mark Brown
2018-09-26 17:03 ` Tim.Bird
2018-09-26 12:30 ` Mauro Carvalho Chehab
2018-09-26 12:51 ` Geert Uytterhoeven
2018-09-26 14:01 ` Shuah Khan
2018-09-25 10:56 ` Jani Nikula
2018-09-25 13:38 ` Jonathan Corbet
2018-09-25 15:22 ` Shuah Khan
2018-09-25 16:51 ` Tim.Bird
2018-09-26 8:04 ` Laura Abbott
2018-09-26 14:47 ` Theodore Y. Ts'o
2018-09-27 8:30 ` Laura Abbott [this message]
2018-10-04 16:27 ` James Bottomley
2018-10-05 18:10 ` Shuah Khan
2018-10-06 21:39 ` James Bottomley
2018-10-07 15:27 ` Shuah Khan
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=e3cb7b83-2680-aadb-6c3b-aa6fb0ba6439@redhat.com \
--to=labbott@redhat.com \
--cc=Tim.Bird@sony.com \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=olof@lxom.net \
--cc=tytso@mit.edu \
/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