From: Dean Stephens <desultory@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] ComRel / disciplinary action reform proposal
Date: Mon, 16 Jan 2017 23:30:19 -0500 [thread overview]
Message-ID: <18821535-bac6-95bb-bfb9-0e461d554a6c@gentoo.org> (raw)
In-Reply-To: <90538aac-9b25-6e0e-a59a-bb662f061ccc@gentoo.org>
On 01/16/17 08:40, Kristian Fiskerstrand wrote:
> On 01/16/2017 02:22 PM, Paweł Hajdan, Jr. wrote:
>> Maybe routine things like spam could go through forums-specific channel.
>> I don't see a reason to get a bug filed for each of these.
>
> There should be a general notice that resolution should be attempted at
> the lowest possible level. E.g a developer dispute within a project
> should be attempted to be resolved within the project by involving team
> lead before it is escalated anywhere. This in particular goes for IRC
> channels in project scope etc, removal of members from within a project
> etc etc.
>
Do you mean something beyond what ComRel already has on their project
page on the wiki[1]?
Specifically: "Community Relations may also act after all other attempts
to solve the issue have failed. Developers are encouraged to try to
solve the issue among themselves in a civil manner before they reach out
to Community Relations. Developers within a project engaged in a
personal conflict may wish to consult with the project lead. Although
leads are not necessarily qualified to resolve personal disputes,
technical issues resulting in conflict can often be resolved within the
project without Community Relations involvement."
[1] https://wiki.gentoo.org/wiki/Project:ComRel
next prev parent reply other threads:[~2017-01-17 4:30 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 19:23 [gentoo-project] ComRel / disciplinary action reform proposal Michał Górny
2017-01-15 19:38 ` Raymond Jennings
2017-01-15 20:06 ` Rich Freeman
2017-01-15 20:02 ` Rich Freeman
2017-01-15 20:13 ` Kent Fredric
2017-01-15 23:05 ` M. J. Everitt
2017-01-16 17:54 ` Alec Warner
2017-01-15 21:59 ` Dale
2017-01-16 5:00 ` Dean Stephens
2017-01-15 22:55 ` M. J. Everitt
2017-01-16 0:25 ` Jorge Manuel B. S. Vicetto
2017-01-16 0:44 ` Raymond Jennings
2017-01-16 0:55 ` Rich Freeman
2017-01-16 11:16 ` Jeroen Roovers
2017-01-16 19:35 ` Jorge Manuel B. S. Vicetto
2017-01-17 17:38 ` Michał Górny
2017-01-16 4:56 ` Dean Stephens
2017-01-16 13:22 ` Paweł Hajdan, Jr.
2017-01-16 13:40 ` Kristian Fiskerstrand
2017-01-17 4:30 ` Dean Stephens [this message]
2017-01-17 4:29 ` Dean Stephens
2017-01-17 17:41 ` Michał Górny
2017-01-20 5:02 ` Dean Stephens
2017-01-16 20:57 ` William L. Thomson Jr.
2017-01-17 17:49 ` Michał Górny
2017-01-17 18:54 ` William L. Thomson Jr.
2017-01-17 19:03 ` Rich Freeman
2017-01-17 19:40 ` William L. Thomson Jr.
2017-01-17 20:20 ` Rich Freeman
2017-01-18 5:33 ` Raymond Jennings
2017-01-18 17:07 ` William L. Thomson Jr.
2017-01-17 14:38 ` Daniel Campbell
2017-01-17 15:26 ` Rich Freeman
2017-01-17 18:05 ` Michał Górny
2017-01-17 18:13 ` Kristian Fiskerstrand
2017-01-18 17:31 ` William L. Thomson Jr.
2017-01-18 18:25 ` Michał Górny
2017-01-18 18:31 ` William L. Thomson Jr.
2017-01-18 19:05 ` Rich Freeman
2017-01-18 19:13 ` William L. Thomson Jr.
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=18821535-bac6-95bb-bfb9-0e461d554a6c@gentoo.org \
--to=desultory@gentoo.org \
--cc=gentoo-project@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox