| === forrestv_ is now known as forrestv | ||
| === dericcrago_ is now known as dericcrago | ||
| === cristiangsp changed the topic of #launchpad to: Help contact: @cristiangsp (08:00-17:00 UTC Mon-Fri) | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support and spam reporting: https://answers.launchpad.net/launchpad | ||
| dericcrago | hi cjwatson - don't mean to bother you, just checking in on https://answers.launchpad.net/launchpad/+question/695623 | 15:21 |
|---|---|---|
| cjwatson | dericcrago: Hi, sorry, I've been failing to get round to this. Could you start by creating the team that you eventually want to own the ~ansible name (say as ~ansible-team for now) and add the current ~ansible user to it? Then I'll see if I can invent the necessary transfer procedure this week | 19:02 |
| cjwatson | dericcrago: Just to clarify, would you want all the existing PPAs on https://launchpad.net/~ansible transferred? | 19:02 |
| dericcrago | cjwatson - ok, I'll get started on setting up `~ansible-team`, I think we could probably prune the PPA list down a bit if that would help (I'm guessing we'll want to migrate ~4, but I'll double check with the rest of the team) | 19:05 |
| cjwatson | dericcrago: I don't think it matters much, if you're OK with it we could just transfer the lot | 19:06 |
| cjwatson | Realistically it's going to be a small pile of SQL in any case | 19:06 |
| dericcrago | cjwatson - transferring all of them should be fine then, thanks! | 19:06 |
| cjwatson | Very tempted to just rename both person and team and transfer all the PPAs in a single transaction, but will need to work out the details and make sure that's safe | 19:07 |
| cjwatson | It's definitely easier to transfer all. If we left some of them on the bot account, then their publication paths on disk and their URLs would change and we'd have to work out what to do about that | 19:08 |
| cjwatson | dericcrago: Also could you (and/or your team) decide what you ultimately want the existing ~ansible bot account to end up being called? | 19:10 |
| dericcrago | cjwatson - sure | 19:11 |
| * cjwatson digs through the DB a bit | 19:18 | |
| cjwatson | Looks like a single-transaction approach should be possible | 19:18 |
| dericcrago | cjwatson - ok, the team has been created. To reinterate / clarify: `~ansible-team` -> `~ansible`, `~ansible` -> `~ansible-jenkins`, and migrate all the PPAs from `~ansible-jenkins` to `~ansible` | 19:27 |
| dericcrago | I guess I had my order of operations wrong there, `~ansible` -> `~ansible-jenkins`, `~ansible-team` -> `~ansible`, migrate PPAs from `~ansible-jenkins` to `~ansible` | 19:39 |
| dericcrago | cjwatson - I'm not sure when you're intending to make the change, but if you wanna give me a heads up, I'll be more than happy to do whatever user side testing | 20:57 |
| === Peng__ is now known as Peng | ||
| cjwatson | dericcrago: I need to spend most of tomorrow doing performance reviews, so, uh, we'll see | 23:59 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!