Re: [Rdo-list] #rdo on freenode, logging and upstream OpenStack bots

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]