[00:14] <daker> i think separation
[00:14] <daker> there is*
[00:15] <daker> https://code.launchpad.net/~linaro-connect-theme-devs/ubuntu-community-webthemes/light-django-linaro-theme
[00:15] <daker> i see that you already have done that https://code.launchpad.net/~debconf14-dev/ubuntu-community-webthemes/light-django-dc14-theme
[00:16] <slangasek> daker: the charm makes me check out two different branches; that's not the same thing as there being actual separation
[00:17] <slangasek> because half the things I need to change, I find myself configuring in the code branch
[00:19] <daker> well i see what you are talking about, but i am unable to give an concrete answer :)
[00:40] <cjohnston> slangasek: so its really a horrible split unfortunatly...
[00:40] <cjohnston> and yes, you would have to do a bunch of changes in lp:summit branch
[00:41] <cjohnston> the 'adding other sites' was very much an after thought and hacked into place by linaro people in a hurry for their requirement
[00:41] <cjohnston> s
[00:41] <slangasek> cjohnston: that's been my assessment thus far ;)  Is there any likelihood that this will improve in the near future?  If not, I'm just going to make my own branch of the code (already done), and ignore the theme branch entirely by deploying in a separate subdir (which was what I'd started out doing)
[00:42] <slangasek> in case you're interested, here's the site I'm currently puttering on: http://dc14-summit-test.dodds.net/debconf14/
[00:43] <cjohnston> slangasek: I believe that mhall119 has some work planned for summit, but without you talking to ev, the odds of me doing a whole lot other than helping you is slight
[00:43] <cjohnston> slangasek: I see an error
[00:43] <slangasek> cjohnston: this is nothing I would be asking ev about
[00:44] <slangasek> hah, yes, there's an error there now, isn't there?
[00:44] <cjohnston> I know. :-)
[00:45]  * slangasek ho-hums and tries to recreate the relation
[00:48] <slangasek> ok, well I seem to have done a crackerjack job of botching that
[00:48] <slangasek> and now I'm afk, guess I'll fix it in a few :)
[00:56] <mhall119> slangasek: I'd be happy to help out with the debconf site as part of my community work
[00:56] <cjohnston> mhall119: it would really be nice if we could make the theme branch give everything that would be needed to change summit
[00:56] <mhall119> I even got model-mommy packaged and in debian's archives so you can run summit's test suite :)
[00:56] <mhall119> cjohnston: what do you mean?
[00:57] <cjohnston> 20:16:52 slangasek | daker: the charm makes me check out two different branches; that's not the same thing as there being actual
[00:57] <cjohnston>                    | separation
[00:57] <cjohnston> 20:17:08 slangasek | because half the things I need to change, I find myself configuring in the code branch
[00:57] <mhall119> what's he changing?
[00:58] <mhall119> so make it a "summit theme" instead of a "django theme"?
[00:59] <cjohnston> hrm.. I guess it might actually not be so bad.. I just did a grep for Linaro and there are only a handful of mentions
[00:59] <mhall119> as long as he doesn't want to change the *content* of the pages, just the header/footer/visuals, the current separation should work
[01:00] <mhall119> but it sounds like maybe he wants to change what content is displayed and where
[03:34] <slangasek> mhall119: hey, certainly wouldn't mind the help :)
[03:34] <slangasek> mhall119: fwiw, here's the wiki page I've been preparing for the DebConf team's purposes: https://wiki.debconf.org/wiki/Summit
[13:33] <mhall119> slangasek: is debconf for sure going to use it, or still being decided?
[17:01] <slangasek> mhall119: provided we can get it all up and going in the next couple of weeks, I think we'll definitely use it
[17:01] <slangasek> mhall119: the team has been stuck on pentabarf for years after they've wanted to, because it's too hard to migrate; this is a year when migration is easier because part of the registration is (necessarily) handled by the venue
[17:03] <mhall119> slangasek: people will still need to register in summit, which means having an Ubuntu SSO account at a minimum, and a Launchpad profile preferably
[17:03] <mhall119> though they can view the schedule without it
[17:03] <slangasek> mhall119: no, we're not using Ubuntu SSO for this
[17:03] <slangasek> we're going to use Debian SSO
[17:04] <mhall119> ok, we haven't tried Summit with another OpenID provider, so there may be bugs
[17:10] <mhall119> slangasek: do you want to schedule a hangout so you can bring me up to speed with (a) what you've got going so far and (b) what you need changed?
[17:11] <slangasek> mhall119: I'll do you one better, I have this written up as a wiki page: https://wiki.debconf.org/wiki/Summit
[17:12] <slangasek> mhall119: note that we're also not using openid, the requirement on the Debian side is oauth2 - so yeah, I'm sure there will be bugs
[17:17] <mhall119> oh...fun
[17:17] <mhall119> well, as long as there's a django app that makes it easy, we should be good
[17:30] <slangasek> yeah, that's the idea :)
[17:38] <mhall119> daker: ping
[17:38] <daker> mhall119: pong
[17:39] <mhall119> daker: hey, you wanted to replace Wordpress with Django on developer.u.c, well I'm going to need to put some of that funcitonality into summit.u.c (shouldn't affect you slangasek), did you have a specific CMS app that you think would work best?
[17:41] <daker> mhall119: no, but if you can liste the functionalities you want on it, that would be helpfull :)
[17:42] <mhall119> daker: hmmm, all I have right now is "what Wordpress offered, plus translations and better staging->production workflow"
[17:42] <mhall119> for summit.u.c, it's really just the ability to manage page content and navigation
[17:47] <daker> django-cms is known to work very well
[17:49] <daker> and maybe if you can detail the "what Wordpress offered, plus translations and better staging->production workflow" would be help more
[17:49] <daker> what Wordpress offered ? pages/posts/media revisions ?
[17:49] <daker> password protected content ?
[17:50] <daker> translations ? translations of dynamic content posts/content ?
[17:52] <daker> and how this staging->production workflow works
[17:57] <jose> loco.ubuntu.com is in django and translated
[17:58] <daker> yes but i think here he want to translate the dynamic content...
[17:58] <jose> hmm
[17:58] <jose> judging the fact that developer.u.c is going to be in chinese also, yes
[17:58] <daker> like the api doc translated in chinese
[18:41] <slangasek> mhall119: so is there any piece of the debconf summit deployment that you think you could help out with?  I think the part where we're most in need of help, and where you might be best able to help, is getting the registration form going - since that needs someone with a better understanding of django forms than I have
[18:47] <mhall119> slangasek: I can help with that
[18:47] <mhall119> slangasek: are you wanting to use sponsorship?
[18:48] <slangasek> mhall119: we do sponorship, yes
[18:48] <slangasek> sponsorship
[18:48] <mhall119> to be honest, the summit sponsorship system was never that great and hasn't been worked on in a while
[18:50] <slangasek> mhall119: well, DebConf, despite doing quite a lot of sponsorship every year, has never had anything approaching a decent workflow for it in the webapp :)