11:38 a.m.
All the bots (so many bots) are now on #rdo.
We now have helpful things like:
- openstack bot "expanding" links (ex: Giving a summary of a bugzilla
or launchpad bug when linked)
- Eavesdrop logging [1]
- openstackstatus bot providing openstack-infra updates (ex: outages,
maintenances, etc.)
- openstackgerrit bot posting review updates for Packstack from
review.openstack.org
- rdogerrit bot posting review updates for dist-git packaging
projects, rdoinfo, rdopkg, DLRN and config from review.rdoproject.org
- rdobot bot posting monitoring updates (only DLRN packages failing to
build right now)
We'll give it some time and collect feedback as to whether or not
these feel too "spammy" later and consider if the notifications should
be deferred to another channel.
[1]: http://eavesdrop.openstack.org/irclogs/%23rdo/
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Wed, Apr 20, 2016 at 4:43 PM, David Moreau Simard <dms(a)redhat.com> wrote:
Updates based on today's meeting on #rdo:
- We granted openstack-infra access to the #rdo channel (thanks rbowen)
- Reviews have been sent to openstack-infra to retire packstack-dev
and move notifications to #rdo [1]
- The 'rdogerrit' bot will notify #rdo about new reviews on
review.rdoproject.org for DLRN, rdoinfo, rdopkg and config
repositories
- Failure to build from source errors will now be sent from 'rdobot'
in #rdo, the rdo-alert bot has been decommissioned (thanks derekh)
[1]: https://review.openstack.org/#/q/topic:packstack-rdo
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Mon, Apr 18, 2016 at 3:02 PM, David Moreau Simard <dms(a)redhat.com> wrote:
> Hi,
>
> Recently, some individuals asked if we could keep the history of the
> #rdo channel somewhere.
> This is a "standard" feature of other OpenStack-related channels and
> is a service provided by eavesdrop [1].
>
> Before we go ahead and implement this, I think it's fair to reach out
> to the community first because:
> - We effectively need to give founder-level access to openstack-infra
> on #rdo [2]
> - Some may have privacy concerns or other thoughts about this
>
> Doing the required configuration and granting openstack-infra access
> to the channel has other benefits as well:
> - Status update broadcasts sent by openstack-infra (ex: "Jenkins is
> down" or maintenance updates) would be sent to #rdo
> - We could get messages every time a review is done on an RDO-related
> project (i.e, Packstack)
>
> For what it's worth I'm planning on setting up our bot to post
> notifications about reviews for RDO projects that are on
> review.rdoproject.org or gerrithub.
>
> If all this becomes too /spammy/, it could warrant being sent to a
> different channel but let's start with this and iterate on it if need
> be.
>
> Does anyone have any objections to #rdo being logged on eavesdrop ?
> What about status updates from openstack-infra or relevant projects
> gerrit reviews ?
>
> Thanks and I'll bring this up at the next RDO meeting.
>
> [1]: http://eavesdrop.openstack.org/irclogs/
> [2]: http://docs.openstack.org/infra/system-config/irc.html#access
> [3]: https://github.com/rdo-infra/rdobot
>
> David Moreau Simard
> Senior Software Engineer | Openstack RDO
>
> dmsimard = [irc, github, twitter]