| === txwikinger2 is now known as txwikinger | ||
| mhall119 | james_w: ping, I'm working on a summit deployment, are there any special instructions that are needed for your unsubscribe change? | 13:09 |
|---|---|---|
| james_w | just a migrate | 13:10 |
| mhall119 | ok | 13:10 |
| mhall119 | james_w: I've got one quick review that we need before going to production | 13:42 |
| james_w | ok | 13:43 |
| mhall119 | https://code.launchpad.net/~mhall119/summit/auto-set-user-openid/+merge/80070 | 13:44 |
| james_w | mhall119, what would that do to people who already have <lpuser>2 as their username? | 13:47 |
| mhall119 | james_w: I'm going to have IS run manage.py update-openids, which will switch their openid association over to the <lpuser> User record | 13:48 |
| mhall119 | next login, they'll be identified as <lpuser> | 13:48 |
| james_w | excellent | 13:48 |
| mhall119 | this just prevents us from having to run update-openids after every lpupdate | 13:48 |
| james_w | approved | 13:48 |
| mhall119 | thanks, I'll get the production branch ready | 13:49 |
| mhall119 | james_w: cjohnston: nigelb: requested summit deployment | 14:10 |
| nigelb | mhall119: \o/ | 14:10 |
| james_w | woop | 14:11 |
| james_w | mhall119, I'm thinking we shouldn't hide the details of private meetings any more, what do you think? | 19:05 |
| mhall119 | why would we want to stop hiding them? | 19:08 |
| james_w | I mean just the title | 19:16 |
| james_w | given that only admins see them now | 19:16 |
| james_w | and by just clicking "Edit" they can see the title | 19:17 |
| nigelb | \o/ I c | 19:40 |
| mhall119 | james_w: talk to jcastro to see what the reason for hiding the data initially was important | 19:42 |
| james_w | they used to be shown on the main schedule | 19:42 |
| james_w | but now they are only allowed in private rooms | 19:43 |
| james_w | and only admins can see private rooms | 19:43 |
| nigelb | (ugh, sorry) | 19:43 |
| james_w | an argument could be made that it makes shoulder surfing harder | 19:43 |
| mhall119 | james_w: no, private meetings can still be held in open rooms | 19:46 |
| mhall119 | they just have to be manually scheduled, IIRC | 19:47 |
| james_w | oh, true | 19:47 |
| mhall119 | FYI, vanguard said it'd take a few days before the deployment, but tiaz was going to bump the RT | 19:48 |
| james_w | I saw, thanks | 19:48 |
| james_w | if it had gone to the linaro RT I could have done that :-) | 19:49 |
| mhall119 | done the deploy? | 19:49 |
| mhall119 | or done the bumping | 19:49 |
| james_w | done the bumping | 19:52 |
| james_w | I have priority powers in the linaro RT | 19:52 |
| mhall119 | do those come with a cape? | 19:53 |
| james_w | heh | 19:54 |
| cjohnston | james_w: since you have priority powers in linaro rt, file to get loco.u.c updated, saying it will help the server ;-) | 20:17 |
| james_w | :-) | 20:18 |
| james_w | https://code.launchpad.net/~james-w/summit/usability/+merge/80108 is pretty important for creating private meetings | 21:14 |
| mhall119 | james_w: approved | 23:06 |
| mhall119 | james_w: nigelb: the new summit code it out | 23:10 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!