[openstack-dev] Beyond IRC (was Re: Cinder Third-Party CI: what next?)
doug at doughellmann.com
Wed Mar 25 01:21:51 UTC 2015
Excerpts from Stefano Maffulli's message of 2015-03-24 15:13:09 -0700:
> On Tue, 2015-03-24 at 19:01 +0000, Rochelle Grober wrote:
> > So, how do we get timely first core review of patches in areas of the
> > world where Core presence in IRC is slim to none?
> I think that most core reviewers use bouncers, so notifying them in the
> channel would probably raise a notification in their clients when they
> connect back. I understand the feeling though: as the sender of a
> message over IRC, I have no good way to understand if the message was
> delivered to the recipient as expected.
> I'd start with advising to use the bouncer and ping the core reviewers
> on channel with review requests. (more about this below)
> > I can think of a few options but they don’t seem great:
> > · A filter for dashboards that flags reviews with multiple +1s
> > and no core along with a commitment of the Core team to perform a
> > review within x number of days
> This might work, modulo the 'committment' of core team which I think
> cannot go above a "best effort".
We have a few dashboards like this for Oslo:
> > · A separate mailing list for project review requests
> I'm skeptical about this being effective: just another source of
> incoming email that needs to be filtered out (at which point a mailman
> topic would have the same effect).
Yes, email notifications scale poorly for really active reviewers.
Between gerrit and launchpad, there is already a lot of notification
email being filtered out of inboxes.
> > · Somehow queueing requests in the IRC channel so that offline
> > developers can easily find review requests when looking at channel
> > logs
> Maybe we can hack an IRC bot so that it collects review requests and
> lists them on eavesdrop? Something like a user on irc writes:
> : please review https://URL because it's needed for GOODREASONS #review
> and on a web page like http://eavesdrop.openstack.org/ we add 'requests
> for reviews', maybe an rss feed.
We have a section of the weekly Oslo meeting dedicated to discussing
reviews that need to be prioritized. Anyone can add an item to the
agenda, even if they aren't present at the meeting. (I don't think
that was an original idea, but I'm not sure where I saw it first
so I can't give credit properly.)
> BTW, Thierry had a similar request a few weeks back for a system to
> quickly share 'good news' and create a stream of reasons for
> happyness :)
> > Solving this issue could help not just Third Party developers, but all
> > of OpenStack and make the community more inviting to Asian and
> > Australian (and maybe European and African) developers.
> In general, make it more resilient and asynchronous, not just because of
More information about the OpenStack-dev