<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Aug 22, 2016 at 2:47 AM, Niels de Vos <span dir="ltr"><<a href="mailto:ndevos@redhat.com" target="_blank">ndevos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mon, Aug 22, 2016 at 11:16:15AM +0200, Michael Scherer wrote:<br>
> Le lundi 22 août 2016 à 12:41 +0530, Nigel Babu a écrit :<br>
> > Hello,<br>
> ><br>
> > I've just switched the bugzilla authentication on Gerrit today. From today<br>
> > onwards, Gerrit will comment on Bugzilla using a new account:<br>
> ><br>
> > <a href="mailto:bugzilla-bot@gluster.org">bugzilla-bot@gluster.org</a><br>
> ><br>
> > If you notice any issues, please file a bug against project-infrastructure.<br>
> > This bot will only comment on public bugs, so if you open a review request when<br>
> > the bug is private, it will fail. This is intended behavior.<br>
><br>
> You got me curious, in which case are private bugs required ?<br>
><br>
> Do we need to make sure that the review is private also or something ?<br>
<br>
</span>I do not expect any private bugs. On occasion it happens that a bug gets<br>
cloned from Red Hat Gluster Storage and it can contain customer details.<br>
Sometimes those bugs are not cleaned during the cloning (BAD!) and keep<br>
the references to details from customers.<br>
<br>
All bugs that we have in the GlusterFS product in bugzilla must be<br>
public, and must have a public description of the reported problem.<br>
<span class="HOEnZb"><font color="#888888"><br>
Niels<br>
</font></span><br>______________________________<wbr>_________________<br>
Gluster-infra mailing list<br>
<a href="mailto:Gluster-infra@gluster.org">Gluster-infra@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-infra" rel="noreferrer" target="_blank">http://www.gluster.org/<wbr>mailman/listinfo/gluster-infra</a><br></blockquote></div><div class="gmail_extra"><br></div>Is it worth denying all posts from RHGS and causing people to manually submit bugs? </div><div class="gmail_extra">I realize that's using a hammer on an edge-case, but if someone is moving a bug to the <a href="http://gluster.org">gluster.org</a> project, I feel like it's on them to scrub it.</div><div class="gmail_extra">-- amye </div><div class="gmail_extra"><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Amye Scavarda | <a href="mailto:amye@redhat.com" target="_blank">amye@redhat.com</a> | Gluster Community Lead</div></div>
</div></div>