[00:04] daker: mhall119 could you mark https://code.launchpad.net/~chrisjohnston/summit/i18n/+merge/152525 approved please [00:08] done [00:10] tr [00:10] ty [01:15] https://groups.google.com/forum/?hl=en&fromgroups=#!topic/django-developers/HrWXBwe9BHU [01:18] interesting [01:27] Happy birthday mhall119 [01:49] thanks daker :) [02:37] so, mhall119 what are you wanting to do with summit now [02:50] cjohnston: use it for developer/open/sdk week sessions [02:50] more info please [02:51] so we're going to run an SDK Week, similar to open week or developer week [02:51] but instead of #ubuntu-classroom, it'll use hangouts (with IRC for questions) [02:51] ok [02:52] so we create a Summit record called "Ubuntu SDK Week 13.03" or something [02:52] one room, one track, a handful of slots [02:52] k [02:52] so the issues I've thought of are: [02:52] No Sprint, therefore no Attendee import [02:53] which isn't so bad, all we need Attendee records for are the people running the session, and whomever will be creating the hangout [02:53] we can manually create those [02:53] people don't necessarily need to mark themselves as participating [02:53] thought it might be nice in the future [02:55] yup [02:55] we can use the proposing feature, then whomever is running the week can approve and schedule them [02:56] which is more work than they currently do with the wiki, but they can get over it [02:56] oh. I want to make it not a requirement to be an attendee to propose a session [02:56] is that currently a requirement? [02:56] I think so [02:57] the other thing is, do we want to use the exact same instance, or would a training instance be more betterer [02:57] maybe a separate instance [02:58] I think seperate would be more betterer [02:58] prodstack? [02:58] good luck [02:58] they wont redeploy summit without the charm being 'fixed' [05:07] mhall119: daker https://code.launchpad.net/~chrisjohnston/summit/update-django-1-4/+merge/152552 please test it well