[12:12] <stgraber> highvoltage: I'm done with the redesign of the package selection step. Next up is the installation type one (desktop, ltsp, server) then I'll have the fun one... the authentication step ;)
[12:35] <highvoltage> nice
[13:26] <highvoltage> stgraber: didn't there used to be a place where I can edit the contact form page content on http://edubuntu.org/admin/structure/contact/edit/1 ?
[13:27] <highvoltage> I can't seem to find where we used to enter things like "Don't use this for support" or "Sorry, we really really can't post you discs"
[15:05] <highvoltage> stgraber: I got my passport/visa back today, so at least that's not a problem
[15:07] <stgraber> highvoltage: good
[18:32] <highvoltage> stgraber: have you settled on flask or is that pretty much still up in the air?
[18:38] <stgraber> highvoltage: pretty likely to be flask, that's what I've been using so far (though the code isn't really flask specific)
[18:39] <highvoltage> stgraber: cool. I'm looking for a nice way to authenticate a flask app against samba4, so I'm (not so) secretly hoping that you'll be doing that for edubuntu to so that I could "steal" it :)
[18:41] <stgraber> highvoltage: oh, that part I already have, including changing password, it's everything else I don't have ;)
[18:41] <highvoltage> stgraber: oh awesome!
[18:43] <stgraber> highvoltage: code is in lp:~edubuntu-dev/edubuntu/edubuntu-server
[18:43] <stgraber> highvoltage: needs python-flask and python-ldap
[18:44] <stgraber> highvoltage: just replace the domain name and DN in access.py (hardcoded for now in the header)
[18:44] <highvoltage> cool :D
[18:46] <highvoltage> "Now on revision 67." heh, I think before I pulled I was still on revision 2, you've been busy :)
[18:47] <stgraber> yeah, took a few revisions to get something that works
[19:03] <highvoltage> stgraber: nice. there's nothing in that code that I don't understand. I guess having played with python3-lxc helped :)
[19:21] <highvoltage> stgraber: I think in the deployments confirmation mail, perhaps the confirm link should be higher up, or perhaps it should say in the first line that they need to click that link to confirm
[19:22] <highvoltage> stgraber: because the mail itself almost looks like a confirmation mail that the details have been received and I can see how many people won't read it until the end
[19:23] <highvoltage> stgraber: I just looked at the rejection mail too and it might be nice if it mentioned that a reason for rejection could be because the submission wasn't confirmed
[19:23] <highvoltage> (it looks a bit short-off)
[19:25] <stgraber> highvoltage: you know that you have commit rights to that branch right? :)
[19:25] <stgraber> highvoltage: the email templates are at the end of deployments.module
[19:26] <highvoltage> stgraber: ah, cool!
[21:42] <stgraber> highvoltage: http://www.stgraber.org/download/edubuntu-step-1.png http://www.stgraber.org/download/edubuntu-step-3.png
[21:44] <highvoltage> stgraber: nice!
[21:44] <highvoltage> stgraber: so if you choose server, will you get server package options on the software selection screen?
[21:45] <stgraber> yeah, you'll get a different screen to choose the roles, that'll be step-4 (and step-3 will just be hidden on servers)
[21:46] <stgraber> I still need to implement step-2 which is the standalone/join-a-domain/create-a-domain one
[21:46] <highvoltage> well, it's already really nice
[21:47] <stgraber> I'm hoping to get step-2 and step-4 implemented tomorrow evening so we can get that stuff uploaded when the archive opens
[21:48] <stgraber> obviously step-1 changes depending on what .squashfs you have on the media and will be skipped entirely if you only have one
[21:48] <stgraber> (so our arm image won't show that step)