[00:25] cjohnston: nigelb: james_w: https://code.launchpad.net/~mhall119/summit/enhance-next-session/+merge/80746 === head_v is now known as head_victim [14:01] mhall119: why did you change _local_now.date() to _now.date():? [14:02] That's the only thing that strikes me. [14:02] Neat fix for the chrome issue that we noticed last time. [14:04] nigelb: the slot.start is in UTC, so it should be compared to UTC now, not local now [14:04] ah, cool. [14:05] I was having trouble testing it last night because it was 2011-10-29 in FLorida, but 2011-10-30 UTC [14:05] heh [14:05] Nice catch [14:07] can someone investigate bug 883407 [14:07] Launchpad bug 883407 in summit "Summit fails to show all my subscribed talks (affects: 1) (heat: 6)" [Undecided,Incomplete] https://launchpad.net/bugs/883407 [14:07] I did investigate [14:07] looks like for some reason some BPs arent being updated [14:07] looks like all the participants are not showing up [14:07] Like atleast 5 people in that BP didn't show up [14:07] and he says it worked on other blueprints [14:08] right.. [14:08] I'm going to try a manual local run of lpupdate [14:16] there was a blueprints that jcastro pinged me about yesterday that wasn't in the LP export [14:16] design-design-theatre I think it was [14:16] OH WIN, thanks launchpad. [14:16] ? [14:18] what do you guys think about instead of displaying LP id's for session attendees, listing names? [14:19] mhall119: wrong status, I think [14:19] nigelb: could be, I'm not really sure what makes them qualify for that export feed [14:19] mhall119: I think it needs to be in Discussion. [14:20] Daviey would know more. We should document this. [14:20] oh [14:20] nigelb: since it's an LP feed, you can probably as an LP dev too [14:20] Actually, lol. Let me look at lp source code. [14:20] heh [14:20] heh, forgot you're an LP dev now [14:21] I did make some fixes to blueprints [14:21] so did i [14:21] omg, you broke it! [14:21] Like the subscriptions are now sorted by name. [14:21] * mhall119 blames everything on you two [14:21] cjohnston improved the required attendee thing. [14:21] cjohnston: SO glad you did that :) [14:21] * cjohnston blames jcastro and mhall119 for summit [14:21] nigelb: me too.. lol [14:21] i think summit will thank me too [14:22] what is preventing us from moving to login.u.c now mhall119 ? [14:22] summit it a thankless ..... [14:22] cjohnston: nothing that I know of, but we're not doing it the day before UDS starts [14:22] no, i know.. [14:22] im just thinking of things to do this cycle [14:23] mhall119: New, Discussion, Draft. [14:23] we'll need to update the database to convert openid identity_urls from launchpad to login.u.c [14:23] It has to be one of them. [14:24] mhall119: I think we need to have some kind of FAQ page for summit. [14:24] Static page in the code. [14:25] So, instead of going to file a bug, they can be redirected there first. [14:25] cjohnston: ^ [14:25] * cjohnston goes to file a work item for nigelb [14:25] Yes, please do [14:25] I'm creating content for websites that the community runs [14:25] nigelb: https://blueprints.launchpad.net/linaro/+spec/linaro-summits-server-1 is 'new' [14:26] cjohnston: Is it not showing up? [14:26] i think thats the one that isnt updating is it not? [14:26] oh. [14:27] Once something is in summit [14:27] we check it by reverse looking it up. [14:27] So, it need not be on temp-meeting [14:28] cjohnston: I wish we had a generic community-webdev session lined up. [14:28] I should have thought of this earlier. [14:28] we can.. what would we discuss [14:28] Recruiting more people. [14:28] i dont know how much that would work at uds [14:28] we can add a session anytime, without a blueprint [14:28] And generic webdev stuff that doesn't include ld and summit [14:28] Like say - the themes [14:29] Is it big enough for that? [14:29] How do you check if something is in summit? [14:30] i.e., a blueprint. [14:30] what bp [14:30] (we can't, can we? [14:30] the one you linked earlier [14:30] its scheduled.. [14:30] look at his comment on that bug [14:30] ah, you checked. okay. [14:31] i beleive that is the one that isnt updaitng [14:31] ah, its there but not updating/ [14:32] I wish we could sprint together :( [14:32] Can we get Linaro to pay us to sprint for a week? We could rewrite summit from scratch! [14:32] nigelb: im working onit [14:33] cjohnston: the bug or the sprint thing? ;) [14:33] sprint [14:33] \o/ [14:33] also, europe or asia *please* [14:34] asia could be cool [14:35] * nigelb goes to figure out the bug [14:36] I'm about 90% its a Launchpad thing. [14:37] FUUU [14:37] LAUNCHPAD [14:37] cjohnston: Launchpad doesn't have updated names [14:38] I thought james fixed this issue. [14:38] Launchpad seems to be caching the meeting export page. [14:39] nice [14:39] id say see if you can get ahold of an LP dev.. thats kinda really bad and important [14:40] Ok, the only people who have any chance of being online on Sunday is wgrant or StevenK, sadly its too late for both of them. [14:40] try anyway i guess [14:40] Grab francis if you can grab him at UDS. [14:41] Its 4 am for them [14:41] Its late :) [14:41] Well, actually early! [14:52] what do yall think about clearing the migration history once a cycle? [14:54] what happens to production when we do that? [14:55] Is it safe? [14:55] I'm cool with starting with a clean slate at the start of the cycle. [14:55] dunno.. we have done it oonce [15:02] mhall119: do we need the login failure stuff on summit? [16:28] mhall119: did you get a summit error email earlier [16:28] I got a 500 error [16:51] cjohnston: I've gotten several 500 emails [16:52] today? [16:55] cjohnston: mostly mal-formatted URLs and karmic's ical that I'm getting 500s for [16:56] i got one earlier while naving admin [16:56] cjohnston: hmmm, I didn't get an email for that [16:58] I don't get any summit eemails. [16:58] oh right. [16:59] only mhall119 gets them [17:09] Daviey gets them too [18:44] mhall119: nigelb anything else we need to do prior to packaging up and pushing live? [18:45] cjohnston: you two are running this, I'm not sure what you've got in progress right now [18:53] mhall119: https://code.launchpad.net/~summit-hackers/summit/trunk r205+ is what's up for being added [18:54] mind taking a quick glance to see if you can see any issues/things that need to be checked into a little more? [19:39] cjohnston: those look okay to me [19:58] james_w: ping [19:58] mhall119: im wondering if we need to fix bug 868567 [19:58] Launchpad bug 868567 in summit "Private room schedules not limited to admins (affects: 1) (heat: 6)" [High,Triaged] https://launchpad.net/bugs/868567 [19:59] cjohnston: I'm getting 500 emails [19:59] just forwarded one to you [19:59] looks like editing the schedule on the track view [20:01] lovely [20:01] want to move it? [20:01] Yay [20:01] I found our bug. [20:01] Well, its not a bug really. [20:01] Its because launchpad is designed in a particular way. [20:02] If you're not registered for the sprint uds-p, then your name doesn't go into +temp-meeting-export. And therefore, it doesn't come to us. [20:02] broken by design? [20:02] nigelb: sounds fair enough [20:02] Until this UDS, we used one sprint. [20:02] everybody is supposed to register for the sprint [20:02] So, everything was fine. [20:03] Now we have 2 sprints, one for uds and one for linaro. [20:03] Linaro folks of course registered for the linaro one, not necessarily the uds one. [20:03] but shouldn't it still import them? [20:03] Nope. [20:03] We don't import linaro ones. [20:03] We only import from UDS. [20:03] or does LP not show people registered for UDS sessions if they're only registered for the linaro sprint? [20:04] Nope [20:04] we should import linaro attendees [20:04] That's not easy. [20:04] we need a bit (well, maybe more) summit code changes. [20:04] We need to be able to override the variable sent to LP to get temp-meeting-page from commandline [20:05] so for one summit, we should be able to import from multiple sprints. [20:05] Do you really want that code change this late? :) [20:11] nigelb: I'm pretty sure we already do that [20:11] mhall119: There's another problem. [20:12] should I just get up tomorrow morning and say hey.. register! [20:12] :-P [20:12] Yes, please. [20:12] lol [20:12] BEST. FIX. [21:01] we do import attendees from the linaro sprint alreadyt [21:10] james_w: we do? [21:10] how? [21:11] by pulling both +temp-meeting-exports [21:11] oh [21:11] Is there code for that? [21:12] This might exlain the breakage, still. [21:14] james_w: how often does the cron for linaro sprint run? [21:14] the same as Ubunti [21:14] ubuntu [21:14] it does them both in one transaction [21:15] ./manage.py lpupdate uds-p && ./manage.py lpupdate linaro [21:15] ? [21:15] Ok, now I'm lost then. [21:17] nope [21:18] ./manage.py lpupdate uds-p does both [21:18] which problem are you looking at? [21:18] james_w: some users from BP not getting synced into summit. [21:18] is this Riku? [21:19] Yeah [21:19] But a whole bunch of users on that BP didn't get synced over. [21:31] Anyway, off to bed. Will debug later. [21:46] ah, I think I know what it is [21:47] Launchpad only exports someone's subscription to a blueprint if they are registered as attending the same sprint as the blueprint is for [21:47] damn [21:47] not sure how to fix that [21:47] Yeah, that's what I ran into [21:47] which is why we need everyone being in the same sprint [21:47] Or we need patch launchpad not to do that. [21:48] (yay insomnia) [21:49] james_w: My suggestion was to get everyone to register for uds-p [21:49] That's probably announcable at the opening plenary. [21:50] everyone has to register for both [21:50] but that sucks massively [21:50] Yeah. [21:51] We need to bring it up to Francis. [21:52] we should ditch using Launchpad blueprints for this [21:52] james_w: <3 [21:52] if canonical is okay with that, we would be happy. [21:52] And Linaro. [21:52] So much of work is tracked through BPs, its not easy to migrate. [21:53] they won't really care [21:53] we don't have to change that part [21:53] But migrating will solve our headaches *so* much. [21:53] Oh, make the scheduling independdant? [21:53] and summit could make a blueprint for a session on request if that was important [21:53] yeah [21:53] what do they provide? [21:54] Nothing much really. [21:54] just a name and title, an accept/decline interface, and subscriptions to mean "attend the session" [21:54] We'd improve a lot breakage this way. [21:54] the accept/decline thing would be the most work [21:54] Yeah. [21:54] and notifications if they were important to people [21:54] We'll need to configure permissions correctly and notifications. [21:55] anyway, I have to go [21:55] thanks for looking in to this [21:55] Will you be at the summit ession? [21:55] *session [21:55] If so, please being up our discussion. I'll try, but I'm remote ;)