https://bugzilla.wikimedia.org/show_bug.cgi?id=52409
--- Comment #3 from Krinkle <krinklem...@gmail.com> --- I think the /topic changes would get rather verbose and create even more channel noise. If we want, we could equip a bot with a PRIVMSG status protocol. E.g. !deploy in #wikimedia-operations (or in PM to the bot directly) would respond (in the channel or in PM) with a dynamically inferred deployment status (based on it tracking !log calls it should be able to determine whether a scap/sync is running). And for assignee we have the deployment calendar/schedule I suppose. But I see how it can be useful to have this information more readily available. Rejecting the channel noise of puppet for a moment, I think one way to go about this is simply by social convention. E.g. !deploy doesn't have to do anything for it to have meaning. It'd just be like stating the obvious or telling greg-g, except you're doing it in a more scannable way. e.g. <FooBar> !deploy take .. <logmsgbot> !log fbar synchronized wmf-config/InitialiseSettings.php .. <logmsgbot> !log fbar Started scap: OH YEAH .. <logmsgbot> !log fbar Finished scap: OH YEAH .. <MrQuux> meh..? <FooBar> meh .. <MrQuux> !deploy take .. <logmsgbot> !log quux synchronized php-1.24wmf6/includes/HistoryBlob.php 'Backport fix for X' .. .. .. <MrQuux> !deploy done -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
