Pulp

The fedora "Zodbot"[0] is a supybot IRC bot with some fedora-specific extensions. It's not clear to me how (or if) we can use Zodbot with pulp, but the source for the bot itself is (of course) available[1], and the "Meetbot" plugin that powers Zodbot's meeting tracking powers is also freely available[2].

[0]: https://fedoraproject.org/wiki/Zodbot
[1]: https://github.com/fedora-infra/supybot-fedora
[2]: https://wiki.debian.org/MeetBot

I have a lot of experience with meetbot, and it's a nice option. Is it pluggable?

Here are some ways an IRC bot could be valuable in our triage:

• formally start and end the meeting
• change the channel topic according to the meeting topic
• keep a record of the meeting
• note who participated in the meeting

And here are some ideas about redmine integration:

• add a comment to each issue that gets discussed, with a transcript of what was said about it
• automatically access the untriaged bug list and curate the meeting. A simple command like "next" could change the topic to the next bug in the list. We'd probably also want the ability to jump to a specific bug by number.
• It's interesting to think about how it could help facilitate the ultimate decision on how to triage a bug, but I don't see a natural and helpful way for it to do so. Is there some way it could formally note the current proposal, and +1s vs differing suggestions? My feeling is that this could be more cumbersome than actually helpful, and might be a solution looking for a problem. But maybe someone else has an idea?

semyers wrote:

Going with supybot + meetbot.

For now I'm hosting it in our CIOS tenancy (same place as jenkins slaves), but that is likely to change for the purposes of getting the meeting notes published online.

As evidenced by bmbouter's changes to this ticket, we've got more concrete ideas on where/how to host the meeting logs that should make the bot's current location be just fine.

We're hosting the logs on our fedorapeople site:
https://pulpadmin.fedorapeople.org/triage/

There's currently no automation set up for jenkins to push these logs up, but I plan to get that set up before the next triage meeting on Friday.

My currently plan is to give jenkins access to the logs on the automation server where they're currently stored (not sure how just yet, many options to choose from), and have it rsync them up to fedorapeople at that point.

The current favorite rsync command to push directly from the automation box (for my reference only, jenkins shouldn't do this) is rsync -avz /srv/supybot/meetings/pulp-dev/* pulpadmin@fedorapeople.org:public_html/triage

Here's an example log for reference:
https://pulpadmin.fedorapeople.org/triage/2016/pulp-dev.2016-07-01-14.30.html