=== Turl is now known as devnullbaseband === devnullbaseband is now known as N01_77_30P === N01_77_30P is now known as Turl === Pendulum_ is now known as Pendulum [16:33] mhall119: james_w nigelb... status.ubuntu.com continues to have issues where the script stops running due to the server running out of memory and then the lock file is not removed. I would think that this is not relevent to the apache setup? [16:33] I don't know [16:33] cjohnston: Apache is what usually ends up eating the memory. [16:34] We haven't figured out why yet. [16:34] I don't know why we don't get any error messages from the cron run [16:34] I thought IS was saying it wasn't [16:34] unless cron itself is what is getting killed [16:34] james_w: I get some sort of messages at times saying it ran out of memory [16:34] I've not had IS tell me that Apache wasn't causing the problem. [16:34] I don't see those ones I don't think [16:34] just the lockfile ones [16:35] well, ok, I haven't had one for a week [16:35] but it's apparently died several times in that week [16:35] ya [16:35] * cjohnston has g2g.. bbl [16:36] james_w: do we have a patch for the url-encoded blueprint links yet? [16:37] no [16:37] I was hoping to get to it today [16:37] ok [16:37] cause we need to request a production deployment soon to fix the private ical bug [16:39] mhall119, the one that breaks the link? [16:39] yeah, we should fix that soon [16:39] the private ical bug is throwing an exception because of the change to Schedule.from_request wasn't applied to that view [16:39] the url-encoding one should be easy, so I'll do that in a few minutes [16:40] trying to figure out how some sessions got scheduled on Monday morning currently [16:40] is there a way to see the admin log for all users, not just myself? [16:41] I think if you are superuser you can see all of it [16:41] but it won't show changes made outside of /admin/ [16:42] yeah [16:42] it says "my actions" at the top though [16:42] perhaps we should do something like http://stackoverflow.com/questions/987669/tying-in-to-django-admins-model-history [16:43] or https://bitbucket.org/q/django-simple-history/src [16:44] there are several to choose from [16:45] including https://bitbucket.org/mhall119/django-audit/wiki/Home === MichealH` is now known as Guest53887 === Ronnie1 is now known as Ronnie === MichealH` is now known as Guest6567 [17:23] mhall119, are you running the autoscheduler on cranberry? either by hand or from cron? [17:24] argh, it's enabled in cron [17:25] I've disabled it again [17:30] mhall119: http://summit.ubuntu.com/admin/schedule/crew/add/ why is it only listing those few attendees? I guess we need to somehow define the summit to make it easier and only have a list of attendees that are attending the summit [17:34] they are the ones tagged with "Willing to be crew" in their attendee record I guess [17:36] According to Daniel there are a whole lot more who are willing to crew. [17:38] james_w: that is the list of people who were at the last UDS and crewed. [17:39] >>> Attendee.objects.filter(crew=True) [17:39] [, , , , , , , , , , , , ] [17:40] http://summit.ubuntu.com/admin/schedule/attendee/2499/ [17:40] the box needs to be checked on those records as appropriate [17:41] nigel isnt even coming to this UDS, so I cant imagine he has willing to crew checked [17:42] and everyone that Daniel picked he said had marked "Willing to Crew" [17:42] plus, as I said, that's the exact list from last UDS [17:42] http://summit.ubuntu.com/admin/schedule/attendee/2809/ nigels box isnt checked [17:47] http://summit.ubuntu.com/admin/schedule/attendee/2226/ [17:47] it is for last UDS [17:47] I didn't filter by summit at all [17:47] there isnt a way to filter by summit.. they are just defined by days [17:47] right [17:48] So somehow it needs to know what summit its for, and then display a list of willing to crew for that summit [17:48] but that list I just pasted is anyone who has ever had that box checked for any summit [17:48] well, anyone who still has any box checked [17:48] you are right [17:49] but it also needs that box checking for some people for uds-p [17:50] ok.. [17:50] i just checked another one [17:50] why are they not remaining checked [17:50] because you click willing to crew in the sponsorship application [17:50] i guess because these are imported from [17:50] LP [17:50] as people actually attending [17:50] vs sponsorship? [17:51] So we need to check users marked as attending in LP against their sponsorship applications to see if they marked that they are willing to crew [17:53] I'm not sure [17:54] I've never looked at the sponsorship stuff [17:54] nigelb: ^ ? [17:57] Bug #855772 [17:57] Launchpad bug 855772 in summit "Attendees list not marking attendees as willing to crew (affects: 1) (heat: 10)" [Low,New] https://launchpad.net/bugs/855772 [18:16] james_w: why don't we want autoschedule running in cron right now? [18:26] mhall119, it's annoying Stephen Doel [18:26] he's trying to schedule a bunch of things at particular times, and it's throwing them all over the schedule complicating that [18:29] maybe we should make a new summit state, post-sponsorship but pre-scheduling [18:41] and have the autoscheduler not act during that time? [18:46] yeah [20:05] mhall119: Create a mutable item to where meetings in the past are muted I think really needs to be done so that we dont have issues of stuff getting moved around after it happens [20:08] we fixed what was causing it, but we didn't actually provide a way to make sure it never happens [20:08] also, I think there was confusion [20:08] the opposite of immutable is not muted [20:09] personally I think that entire line can just go away [20:12] Ok.. I do think that we need to provide a way to make sure it doesnt happen [20:16] Do you think there is any way that email came from info obtained by summit? [20:28] cjohnston: I don't think so [20:29] cjohnston: have we even determined yet if it was legitimate or spam? [20:30] the UDS registration form uses tfaforms.com [20:36] No idea... [20:40] I'm inclined to think they were legit [21:03] mhall119, https://code.launchpad.net/~james-w/summit/fix-overeager-escaping/+merge/76478 <- there's that fix [21:05] mhall119: and i didnt get it.. but ive completed my forms [21:46] mhall119: https://blueprints.launchpad.net/loco-directory/+spec/subteam-calendar thoughts? [22:49] nigelb: ping [23:24] cjohnston: I'm not sure there's enough demand to warrant it [23:25] we'd have to make LD aware of subteams to begin with [23:25] thats pretty much what my reply said [23:27] there may be a larger case to be made for making LD sub-team aware, in which case this request would be a more minor feature request on top of that [23:28] ya.. im not about to offer that though [23:29] as it is, it should be a wishlist bug, not a blueprint [23:30] * cjohnston says wont fix [23:30] I'm okay leaving it open as a wishlist item [23:30] I'm not opposed to the feature [23:30] summit doesnt have a virtual env setup does it? [23:30] I'm just opposed to putting in the effort unless I see more of a need or want [23:31] you can make one, it has a requirements.txt [23:31] thats why i say wontfix because as of right now i dont see enough need or want [23:31] I save wontfix for "over my dead body will this ever be implemented" [23:31] if someone submits a working patch to implement this, I'd accept it [23:32] i use "wontfix" when i want somebody else to do it [23:32] ;) [23:32] ;-) [23:33] it sucks that we are so far behind times with the version of django we use [23:33] you mean 1.2? [23:33] yes [23:33] if you run a current version of ubuntu, it becomes a pita [23:34] you mean like natty? [23:34] like oneiric [23:34] oneiric isn't current [23:34] it will be in a month [23:34] so whats the difference [23:54] a month [23:54] also support [23:54] make a make file for me for summit [23:54] ;-)