On Sun, 11 Oct 2015 13:04:31 +0200 hasufell <hasuf...@gentoo.org> wrote:
> On 10/11/2015 09:52 AM, Ian Delaney wrote: > > > > To my observation the reaction to this has been between displeasure > > and dismay. Yesterday the dev-ML was flooded with the first day's > > publication of the members' reviews. Firstly the gentoo-commits ML > > to my understanding is intended to be used for and by qa members. > > This project has one whom we presume has the discretion to declare > > the use of the qa hat at whim. > > > > People have been responding to gentoo-commits ML on dev ML since > years. But mostly on smaller scale. I have no knowledge that this is > restricted to QA members. True > The reason this dev-ML attempt was chosen is that we got very hostile > and aggressive opinions about our Github activity, telling us it is > not only against the social contract, but also not properly "public" > and everything in gentoo should be public on our own infra channels > (they said). > > So it seems... however you do it, you do it wrong. Github reviews are > not on our own infra channels, private mails are not public, don't > spam bugzilla, don't spam the ML... It's not particularly easy to not > do it wrong when you have so little options. Draw some line: Stuff that concerns a single, isolated issue, is sent privately. Repeated issues go to -dev, to let everyone know, stating clearly that the commit is random and that the issue has been repeatedly found in various commits from various people. Once this line is drawn, you'll probably realize what kind of doc or guide is missing :) > I suspect this is not even primarily about the chosen platform, but > about the fact that review culture can introduce a few negative > thoughts such as embarrassment. In order to fix that, we are going to > focus the reviews on Github (for developers who are known to be > active there), private mails and semi-private mails to aliases. In > addition, it will also require a shift of thinking. Reviews are not > about exposing a person, but about improving quality and knowledge. > For both parties. For what concerns me, please use emails even if I'm active on github: I've failed to receive several notifications from github in the past, and I don't monitor everything that happens here. [...] Alexis.
