From: Alec Warner <antarus@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] pre-GLEP: Gentoo Developer status
Date: Fri, 13 Apr 2018 21:10:39 -0400 [thread overview]
Message-ID: <CAAr7Pr9ENmyHwXTYQt2jvm23gTvZhVm6NYny9VBzJBq9h80VWA@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_mcdFypPcV-Z8MJ5y2_EiHhDicu+yusUvgfAr2g37Z3wQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2922 bytes --]
On Fri, Apr 13, 2018 at 6:41 PM, Rich Freeman <rich0@gentoo.org> wrote:
> On Fri, Apr 13, 2018 at 6:29 PM, M. J. Everitt <m.j.everitt@iee.org>
> wrote:
> > On 13/04/18 23:25, Rich Freeman wrote:
> >
> >> One form of transparency I have suggested is that when
> >> disciplinary actions are given the person being disciplined should be
> >> given an explanation for why the action is being taken, and that at
> >> their option that explanation would be made public verbatim. I've
> >> seen Debian do this and I thought it was a good way to balance
> >> privacy/transparency/risk. The person being disciplined can at their
> >> option keep the whole matter quiet, or they can have it publicized in
> >> an official way. However, if they decide to publish their own account
> >> of events while denying Gentoo permission to publish its side, then
> >> those listening will probably be skeptical that they're getting the
> >> full story. Since Gentoo would not make any public statements without
> >> permission from the person impacted there would be little risk of
> >> legal repercussions.
> >>
> > I think that if this is the process, people are more likely to buy into
> > it, and accept that if that's the way it works, they can take it or
> > leave it - and the risk is more theirs than that of the organisation. I
> > think that in itself will garner more respect than the current situation
> > at least ..
> >
>
> I hate to drag out this tangent further, but there is another matter
> that I think that the community should probably vote on: whether
> Comrel will accept testimony/evidence/complaints that will be withheld
> from the target of the complaint.
>
> Currently the policy is that this kind of evidence will be accepted,
> which generates frustration because people feel like they cannot
> confront their accuser. The obvious defense of this policy is that
> without it some would not come forward with legitimate complaints out
> of fear of retaliation (by the person they're accusing, or others who
> care about them), or just concern for having their names come up in
> Google associated with the incident, since they might trust Gentoo to
> keep it private but not the person they're having problems with.
>
> I'm sure there are plenty of examples of organizations that do it
> either way, and since we aren't an employer/etc I don't think we
> really have any legal constraints here.
>
> Either way the policy should be clear to anybody bringing forward a
> complaint so that they can trust us to keep things confidential, or
> not, in accordance with the policy.
>
I'm totally supportive of this conversation, but I think its tough to be OP
and have your threads de-railed like this; I'd really prefer if we forked
this thread to have it.
Whether or not we should do any of these things is really orthogonal to
this GLEP which just seeks to clarify the existing state.
-A
>
> --
> Rich
>
>
[-- Attachment #2: Type: text/html, Size: 3865 bytes --]
next prev parent reply other threads:[~2018-04-14 1:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 17:31 [gentoo-project] pre-GLEP: Gentoo Developer status Michał Górny
2018-04-13 21:28 ` Francisco Blas Izquierdo Riera (klondike)
2018-04-13 21:57 ` Rich Freeman
2018-04-13 22:07 ` M. J. Everitt
2018-04-13 22:25 ` Rich Freeman
2018-04-13 22:29 ` M. J. Everitt
2018-04-13 22:41 ` Rich Freeman
2018-04-14 1:10 ` Alec Warner [this message]
2018-04-14 1:05 ` Raymond Jennings
2018-04-14 1:23 ` Rich Freeman
2018-04-14 1:33 ` Alec Warner
2018-04-14 5:59 ` Ulrich Mueller
2018-04-15 12:01 ` Francisco Blas Izquierdo Riera (klondike)
2018-04-15 12:25 ` Ulrich Mueller
2018-04-14 7:24 ` Michał Górny
2018-04-15 11:44 ` Francisco Blas Izquierdo Riera (klondike)
2018-04-15 12:03 ` Rich Freeman
2018-04-15 12:22 ` Michał Górny
2018-04-15 16:55 ` Francisco Blas Izquierdo Riera (klondike)
2018-04-15 17:22 ` M. J. Everitt
2018-04-22 17:24 ` Kent Fredric
2018-04-23 20:01 ` Robin H. Johnson
2018-04-23 21:30 ` M. J. Everitt
2018-04-24 2:58 ` Kent Fredric
2018-04-15 17:58 ` Michał Górny
2018-04-21 17:21 ` Francisco Blas Izquierdo Riera (klondike)
2018-04-14 6:57 ` Matthew Thode
2018-04-14 7:19 ` Michał Górny
2018-04-14 7:32 ` Matthew Thode
2018-04-14 20:58 ` Daniel Robbins
2018-04-14 21:16 ` Raymond Jennings
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=CAAr7Pr9ENmyHwXTYQt2jvm23gTvZhVm6NYny9VBzJBq9h80VWA@mail.gmail.com \
--to=antarus@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