[00:25] <tsimonq2> Cas: You should probably email rt@ubuntu.com with what you need, those are the dedicated sysadmins that can also help.
[11:54] <cjwatson> tsimonq2: please don't give that incorrect advice again
[12:10] <cjwatson> Cas: sorry for the delay, responded in the ticket - let's keep it there, we'll try to keep delays shorter for this in future
[17:03] <nacc> for the git importer, I presumably need to have some sort of ssh auth configured for the importer itself to run independent of my user running. Is there precedence for this sort of thing? I would like to start doing test runs of the importer running automatically for a set of packages relevant to the server team.
[17:06] <cjwatson> You'd want a separate bot user.
[17:06] <nacc> cjwatson: ah sure, and then give them a key, add them to the appropriate team, etc.
[17:07] <nacc> cjwatson: do i have to request that user be created? or can I create a second user?
[17:09] <cjwatson> if it's going to be a devops thing, you should create it yourself; if you intend it ultimately to be an IS-maintained service, you should ask IS to create it and pass credentials to you
[17:09] <nacc> a fair question :)
[17:09] <nacc> rbasak: --^
[18:16] <rbasak> nacc: a question for jgrimm I think. We could always change the bot user though, if the only thing it's doing is uploading git repos?
[19:05] <nacc> rbasak: ack
[19:40] <nacc> cjwatson: if I setup a test user to do this, do i have to setup pgp keys (to sign the code of conduct) before I can add it to the appropriate team? Not getting an option to request being added as that user, and not able to search for that user as the admin of the team
[19:42] <nacc> cjwatson: nm! maybe was just a delay while the user got created, i was able to add it now