Tails

#1 Updated by intrigeri 2013-07-19 01:31:00

• Type of work set to Sysadmin

Type of work: Sysadmin

#2 Updated by intrigeri 2013-07-20 02:11:41

• Subject changed from find another irc commit bot to Bot that announces commits on IRC
• Starter set to No

#3 Updated by intrigeri 2013-12-29 03:21:27

• Category set to Infrastructure

#4 Updated by BitingBird 2015-08-05 08:49:43

• related to Feature #9908: Bot that answers questions on XMPP added

#6 Updated by BitingBird 2016-06-27 02:29:33

• Subject changed from Bot that announces commits on IRC to Bot that announces commits on XMPP

The chans moved to xmpp -> that’s where the bot should be

#7 Updated by muri 2016-06-29 06:37:34

• Assignee set to muri

assigning to me, as i’m already maintaining an xmpp bot for tails

#9 Updated by intrigeri 2017-05-28 11:29:02

• Subject changed from Bot that announces commits on XMPP to Git bot on XMPP
• Description updated
• Status changed from Confirmed to In Progress
• Blueprint deleted (https://tails.boum.org/blueprint/find_another_irc_commit_bot)

#10 Updated by intrigeri 2017-05-28 11:46:31

• Type of work changed from Sysadmin to Debian

(Next thing to do needs to be done in Debian.)

#12 Updated by Anonymous 2017-06-30 10:44:04

• Assignee changed from muri to intrigeri
• QA Check set to Info Needed

@intrigeri: https://labs.riseup.net/code/issues/6033#note-11 there is a question for you in here :)

#13 Updated by intrigeri 2017-07-23 07:48:47

• Assignee changed from intrigeri to muri
• Type of work changed from Debian to Sysadmin

Hi!

> intrigeri, iirc you once said that having errbot as a debian package is not a requirement, now it seems it is. so, just to clarify: is it? ;)

I’ve explained the reason why we try very hard to avoid running non-packaged software in an email a few weeks ago. Now, surely we can find a compromise. Can you please list the exact components (including dependencies, recursively) that we would need to run from third-party sources, ideally Git checkouts? I hope that most errbot are packaged already. If that dependency tree is small enough, one option could be that:

• you’re responsible for maintaining a Git branch somewhere for each of these components: this means you’re the one responsible for ensuring both that we don’t run old crappy versions with security issues, and that upgrades don’t break the service;
• we track these branches and install from there with Puppet, like we do e.g. for https://git-tails.immerda.ch/puppet-tails/tree/manifests/pythonlib.pp;
• we can either track a production branch, or a production signed tag that you would update whenever you see fit (“signed” not for security, just to allow updated tags to be propagated).

What do you think?

> errbot ist just the basic bot functionality for multiple backends (irc, xmpp, slack, …). the functionality of reacting to ticket numbers of tails, debian and tor is provided by a plugin, which is very specific for tails’ needs. i’ve pushed the code to: https://0xacab.org/muri/errbot-plugin-tails

OK. I believe the setup described above would work for this one.

> the functionality of the git announcements is done by another plugin which i forked from https://github.com/errbotio/err-gitbot and which i fixed a bit and hardcoded tails’ git repository. it can be found on https://0xacab.org/muri/errbot-plugin-git

Ideally, it would be nice to merge your improvements upstream (and make it configurable if needed so 1. we don’t have to hard-code stuff; 2. we can track multiple Git repos) so we don’t have to run a fork. Other than that, same as above.

> i will have another look at the packaging side of errbot after the first week of july and give you an assessment of how realistic it is that i package (and maintain) errbot in debian.

Great, thanks. I’d rather see the above plan as a temporary workaround until errbot is packaged, but perhaps it’ll work well enough for everyone who’s affected that we don’t need to package errbot in the end.

#20 Updated by intrigeri 2019-06-02 15:28:58

• QA Check deleted (Info Needed)