| Summary: | Write a friendly IRC bot for the #yocto channel | ||
|---|---|---|---|
| Product: | [Infrastructure] Bugzilla | Reporter: | Darren Hart <dvhart> |
| Component: | bugzilla | Assignee: | Michael Halstead <mhalstead> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | janitors | ||
| Priority: | Low | CC: | infras.bug.watcher, Infras.watcher, richard.purdie, sgw |
| Version: | unspecified | ||
| Target Milestone: | Q3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
I have registered yoctobot and yocti nicks with the freenode staff and installed a copy of SupyBot with basic features on a VM. It is currently connected to #yocto. It can handle <anything>++ or <anything>-- via the included karma module. Saying yocti: karma <anything> will tell you its current score The praise module allows the bot to track specific praise given out. bugzilla and/or git integration will have to wait for now. I don't know about using the nick yocti vs yoctobot. They are both plenty cute but yoctobot is more clear. Awesome Michael :-) I think I prefer yocti (especially as there has been talk of using that for some kind of mascot). However, I don't care too much and if RP wanted to weigh in I'd certainly defer to him. /me thinks yocti is fine Once bz info is added, I think we should close this bug, and others can be opened as feature requests. Yocti can now understand and auto links to bugs as they are mentioned. |
There isn't a general infrastructure Product, so I used Bugzilla. Difficultly: Moderate Estimage: 1 Week (requires feedback and iterative development) Submitter: dvhart Possibly named "yocti" The bot should be either snarky or obsequious The bot should respond to at least the following commands: yocti help (send help privately to user on commands) yocti quiet (no more public output, should still respond to private msgs) yocti speak (start responding again) bug ### (provide a URL to the bug) bzinfo ### (display the bug summary, and possibly whiteboard) git ### (display the git commit subject) bbvar VAR_NAME (display the doctag) The bot could also respond to things like: user++ (track kudos points per user per day) user-- (remove kudos points) kudos (display the current kudos scoreboard) .*someday.* (suggest the user add a task to the Janitors list) I'm sure there are more, current recipe version, maintainer of a recipe, etc.