Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAGHyZ6+ywF0omV7TcYjH1MZEq66FGaMCEi44nUcqooPn83A0TQ@mail.gmail.com>
References: 
 <CAGHyZ6+26i2rvpgC8R9JF04ecNroqxDy1LkZEpFV8huLFUTJ1A@mail.gmail.com>
 <BB2C8E1A-69E5-47BB-B274-E33A12138F61@gmail.com>
 <CAGHyZ6KAb=-A9ZSfTanZG3-C6Ww2qzBPDhuggui=Dc-3hhM-nQ@mail.gmail.com>
 <CA+RK=_DxFXRPgj+yLt+LcqRVGkKUxU05r4umvP7vAeyw9TQX5Q@mail.gmail.com>
 <CAGHyZ6+ywF0omV7TcYjH1MZEq66FGaMCEi44nUcqooPn83A0TQ@mail.gmail.com>
From: Nick Dimiduk <ndimiduk@apache.org>
Date: Tue, 4 Aug 2015 12:27:32 -0700
Message-ID: 
 <CANZa=GtOb1zqpycfRRV5Tbd1VFvd=7SNF9_jG_WhKO61+2Oojg@mail.gmail.com>
Subject: Re: [DISCUSS] non-public comments on jira
To: hbase-dev <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=f46d0438951b46f472051c8148b7

--f46d0438951b46f472051c8148b7
Content-Type: text/plain; charset=UTF-8

Such a harassed individual can email private@ to raise awareness of their
situation. They may not *know* they can do this, probably no more than they
know they can restrict visibility of JIRA comments (as none of us realized
this either), but they can.

I suggest we remove the capability from JIRA and add a "harassment" or
similar section to our site with instructions for community members to
report/escalate issues via appropriate Apache channels.

-n

On Fri, Jul 31, 2015 at 9:00 AM, Sean Busbey <busbey@cloudera.com> wrote:

> So the primary scenario I can think of for non-public comments on jira
> would be if one of our community members was dealing with harassment from
> outside of our community. In that case, their visibility would draw in more
> grief for themselves and our community generally.
>
> Unfortunately, the structure of ASF projects would still leave such a
> person incapable of participating due to the public nature of all the rest
> of our interactions. Their best coping mechanism would be to operate under
> a pseudonym and in that case their jira comments need not be any less
> public.
>
> Another data point: when non-public comments are deleted AFAICT there's no
> visible record of the comment having existed even as a project
> administrator (I presume there is still some record available to jira-wide
> admins). So only folks watching the ticket will have an email record.
>
> On Wed, Jul 29, 2015 at 8:29 PM, Andrew Purtell <apurtell@apache.org>
> wrote:
>
> > I also think that's hard to justify. Anyone have a good reason?
> >
> >
> > On Wed, Jul 29, 2015 at 6:25 PM, Sean Busbey <busbey@cloudera.com>
> wrote:
> >
> > > A commenter expressly has to change the visibility when posting the
> > > comment.
> > >
> > > --
> > > Sean
> > > On Jul 29, 2015 5:59 PM, "Andrew Purtell" <andrew.purtell@gmail.com>
> > > wrote:
> > >
> > > > I agree, JIRA comments should be exclusively public. Doesn't someone
> > have
> > > > to change comment visibility from default to restrict? Or did a
> default
> > > > change ?
> > > >
> > > >
> > > > > On Jul 29, 2015, at 1:41 PM, Sean Busbey <busbey@cloudera.com>
> > wrote:
> > > > >
> > > > > Do we intentionally allow non-public comments on jira?
> > > > >
> > > > > That is, currently commenters on our issue tracker can choose to
> > > restrict
> > > > > their comments to the roles we've defined (like contributors,
> > > developers,
> > > > > project admins, etc).
> > > > >
> > > > > Comments so restricted do not go to the issues@hbase list and so
> > > "don't
> > > > > exist" from the asf's stated policies.
> > > > >
> > > > > My thinking is that any sensitive topics that need to be brought up
> > > > already
> > > > > have a mechanism: private@hbase. For anything else, speakers
> should
> > > > stand
> > > > > by their words.
> > > > >
> > > > > --
> > > > > Sean
> > > >
> > >
> >
> >
> >
> > --
> > Best regards,
> >
> >    - Andy
> >
> > Problems worthy of attack prove their worth by hitting back. - Piet Hein
> > (via Tom White)
> >
>
>
>
> --
> Sean
>

--f46d0438951b46f472051c8148b7--