[00:03] <cjohnston> Daniels @require_login
[00:08] <mhall119> rebase
[00:08] <cjohnston> already done
[00:08] <mhall119> sorry, I got distracted, someone way yacking at me in PM
[00:09] <cjohnston> np.. i know what to do now.. youve tought me well
[01:00] <cjohnston> mhall119: would                             team.expires_date = datetime.strptime(approval.date_expires[:19], "%Y-%m-%dT%H:%M:%S") have anything to do with bug 494950
[01:00] <ubot4> Launchpad bug 494950 in loco-directory "Team Approved/Expire dates don't require time. (affects: 1) (heat: 3)" [Medium,Confirmed] https://launchpad.net/bugs/494950
[01:13] <mhall119> could be
[01:45] <cjohnston> mhall119: does the strptime take out the HMS?
[01:45] <cjohnston> or is it supposed to
[02:05] <mhall119> I'm not sure
[04:28] <mhall119> cjohnston: still awake?
[04:29] <mhall119> cjohnston: progress so far: https://code.launchpad.net/~mhall119/loco-directory/team-events-localtime
[04:31] <mhall119> it'll get the timezone from the venue if there is one, otherwise it defaults to UTC
[04:32] <mhall119> on display it'll include the timezone and offset
[04:32] <mhall119> on editing it'll assume you're entering time local to the venue, and convert it to UTC when it saves it do the database
[04:34] <mhall119> and with that, I'm off to bed, talk to you tomorrow
[06:39] <YoBoY> bonjour
[08:42] <dholbach> good morning
[09:06] <czajkowski> aloha
[09:11] <dholbach> hey czajkowski
[09:14] <czajkowski> dholbach: ello happy friday to you
[09:15] <dholbach> and the same to you
[11:55] <mhall119> morning
[11:55] <mhall119> dholbach: https://code.launchpad.net/~mhall119/loco-directory/team-events-localtime <- progress
[11:57] <dholbach> mhall119, NICE
[11:57] <dholbach> looks like it's been quite a bit of work already :)
[11:59] <mhall119> I need to track down all of the places that should display in localtime
[11:59] <mhall119> I went through several iterations last night trying to find a solution that would work
[12:00] <dholbach> you'll make a lot of people very happy
[12:00] <mhall119> do you think we should give teams a default_timezone field?
[12:01] <czajkowski> hmmm
[12:01] <czajkowski> will it allow for DST ?
[12:01] <mhall119> I'm thinking that would be useful to most teams, so they don't have to specify for each venue
[12:01] <dholbach> but they'll have to change it between summer and winter?
[12:01] <mhall119> czajkowski: yes, because I'm keeping timezone, not offset from UTC
[12:01] <mhall119> dholbach: nope
[12:01] <mhall119> right now, a venue is said to be in "US/Eastern"
[12:01] <dholbach> but one British venue will be in BST in summer and in GMT in winter
[12:02] <mhall119> dholbach: nope
[12:02] <mhall119> they would be in the "Europe/London" timezone
[12:03] <mhall119> when I convert datetimes from UTC to localtime, that's when it calculates whether it's BST or GMT
[12:04] <dholbach> we don't associate vnues with teams.... hm
[12:04] <mhall119> dholbach: no,true
[12:04] <mhall119> we already have tz field for userprofile, I guess I can default it to the tz of the user
[12:05] <mhall119> people will rarely be creating venues outside of their  own timezone
[12:05] <dholbach> hum
[12:05] <dholbach> my concern is people travelling and changing timezones
[12:06] <nigelb> and people using different timezones to work around bugs in the wiki :/
[12:06] <nigelb> moinmoin to be exact.
[12:06] <mhall119> dholbach: how often will someone be creating venues when they travel?
[12:06] <mhall119> nigelb: do you use a different timezone in launchpad for that?
[12:07] <nigelb> mhall119: yep, or else I can't login to the wiki.
[12:07] <mhall119> dholbach: remember I'm just talking about defaults, they'll still be able to change it
[12:07] <dholbach> mhall119, do you want to make it a (overridable) preselection and get it from the browser?
[12:07] <mhall119> dholbach: you mean for the venue?
[12:07] <mhall119> or for userprofile?
[12:08] <dholbach> ok, you answered question 1
[12:08] <dholbach> do you want to get the users timezone from the browser?
[12:08] <mhall119> right now the venue.tz field defaults to "Africa/Abidjan" in the form when the field is not set
[12:09] <mhall119> can we get it from the browser?
[12:09] <mhall119> it there a javascript trick or something for that?
[12:09] <dholbach> I thought there was talk about it
[12:10] <dholbach> do you think it might make sense to bring the discussion on a wiki page?
[12:10] <dholbach> to me it seems like there's a lot of different problems/ideas/places involved
[12:11] <dholbach> so sometimes I'm not sure if we're talking about saving time in the current timezone of whoever creates the venue/event or displaying it for a user who might be in some other timezone somewhere
[12:11] <mhall119> dholbach: we can
[12:11] <dholbach> only if you think it makes sense
[12:11] <dholbach> you're putting all the work into it already
[12:11] <mhall119> I'd rather get these changes is now though, rather than wait on discussions about setting defaults
[12:12] <dholbach> sure
[12:30] <mhall119> I do have a question about migrating existing team event times
[12:31] <mhall119> right now they're stored in the DB at UTC, but we tell people to treat them a localtime
[12:32] <mhall119> initially, with my branch, venues say they are on UTC until a timezone is set, so it won't immediately break things
[12:32] <dholbach> mhall119, via management command we could convert them to something that makes sense as soon as a venue tz is set?
[12:32] <mhall119> but as teams set timezones for venues, it'll change the displayed time of any event using that venue
[12:33] <mhall119> hmm, I can add a hook to the venue's save method, so change times of any associated event when the venue's timezone is set for the first time
[12:34] <dholbach> it's tricky
[12:34] <dholbach> tricky tricky tricky
[12:34] <mhall119> how so?
[12:35] <dholbach> what do we do if somebody picks a wrong tz and wants to change afterwards?
[12:35] <mhall119> yeah, then they'll be stuck
[12:35] <czajkowski> aye
[12:35] <czajkowski> and trust me TZ is such a touchy subject with folks 
[12:36] <mhall119> we can do it every time venue.tz is changed
[12:36] <dholbach> but how do we know what the value in front of us is? :)
[12:36] <dholbach> (the timestamp)
[12:36] <mhall119> it'll happen when the venue is saved
[12:36] <mhall119> we'll do a db lookup for any event using that venue
[12:37] <mhall119> check what the offsets from UTC were from both old and new timezone on the date of the event
[12:37] <mhall119> and adjust the time by the difference in offset
[12:38] <dholbach> so we have to have a "if venue.tz was empty before" check in there, right?
[12:38] <mhall119> the intent would be to keep the local time the same, even when venue's timezone is changed
[12:38] <mhall119> dholbach: now I'm thinking we just do it every time a venue.tz changes
[12:38] <dholbach> right
[12:38] <mhall119> to cover the "oops, I set it to the wrong timezone" scenario
[12:39] <dholbach> but if it was empty before, we convert from "utc, but actually something else" to "utc + offset", no?
[12:39] <mhall119> right
[12:39] <dholbach> and if the tz is changed afterwards it's just the offset that's changed
[12:40] <mhall119> it'll change by the difference in offsets
[12:40] <dholbach> difference between what?
[12:41] <mhall119> so if you change a venue's timezone from Europe/London at UTC+0 to US/Eastern at UTC-400, then we change the event's time by -400
[12:42] <mhall119> if you change from US/Eastern at UTC-400 to US/Pacific at UTC-700, we change the event's time by -300
[12:42] <mhall119> so that the local time display is always the same
[12:43] <dholbach> ok
[12:43] <mhall119> does that make sense?
[12:43] <dholbach> I guess it does
[12:44] <mhall119> heh, I guess I'll try implementing it and see if it still makes sense in code
[12:44] <dholbach> it's just that datetime.datetime has a tzinfo field
[12:44] <dholbach> so I thought we'd just change the value there
[12:44] <mhall119> it's actually a class, and not implemented
[12:44] <dholbach> but I'm not sure any more
[13:04] <mhall119> ok, that works
[13:05] <mhall119> so now people can set venue timezones at their leisure, and they won't have to worry about changing event times
[13:36] <mhall119> dholbach: cjohnston: When you can: https://code.launchpad.net/~mhall119/loco-directory/team-events-localtime/+merge/41306
[13:38] <mhall119> dholbach: can you check if python-tz is installed on the production server?
[13:44] <dholbach> mhall119, it is
[13:46] <dholbach> mhall119, but we probably should document it in INSTALL
[13:46] <dholbach> and spit out an error message maybe?
[13:50] <mhall119> working on it
[13:54] <mhall119> I don't think we need an error message, we don't do that for any of the other package dependencies
[13:54] <mhall119> but I added it to the INSTALL
[14:29] <dscassel_> Thanks, mhall119. :D
[15:16] <mhall119> dscassel_: for what?
[15:31] <nigelb> mhall119: Hi, sorry.  I got up waaay later I should have yesterday :)
[15:34] <nigelb> mhall119: Anyway, I wanted to try and hack something toegether for team reports over the weekend with the foundations project
[15:34] <nigelb> Just wanted to touch base with you re:that
[15:35] <nigelb> Also, I was woundering if we could write a planet like app from scratch, I mean so we can re-theme it and it would be easier to set up feeds, etc
[15:44] <dscassel_> mhall119: For time zones. You have no idea the amount of grief I'm getting for trying to get people to use the LD without them.
[17:14] <mhall119> nigelb: dholbach already has a teamreports project, are you aware of this?
[17:15] <nigelb> mhall119: I am :)
[17:15] <mhall119> dscassel: I can imagine, it's been a major thorn in our side for a long time
[17:15] <nigelb> I think nathan started it
[17:15] <mhall119> nigelb: cool, right now there's no guarantees that the code in my branch even has valid syntax
[17:15] <mhall119> and it's subject to some pretty major changes
[17:16] <mhall119> but if you're okay with that, I'd appreciate the testing and feedback
[17:16] <nigelb> I'd love to try for the sake of learning and/or helping test your code :)
[17:17] <mhall119> cool, let me know when you get started and I'll try to be around more to provide help
[17:17] <nigelb> \o/
[17:18] <czajkowski> TEAM REPORTS 
[17:34] <mhall119> Florida didn't do anything in October, we just sat around
[17:36] <jledbetter> mhall119, I don't believe you
[17:36] <mhall119> okay, we maybe had a small party the last week of the month
[17:37] <jledbetter> Yeah, just a couple of people chillin' and eatin' pizza.
[17:37] <mhall119> yeah, just a couple
[17:37] <mhall119> ...hundred
[17:37] <jledbetter> Little shindig indeed.
[17:37] <mhall119> very low key
[17:38] <mhall119> I mean, the movie was only on like a 40 foot screen
[17:38] <mhall119> jledbetter: you really did miss out :(
[17:39] <mhall119> did you see the pictures?
[17:39] <jledbetter> Yes. Saw pictures. I'll be there next time it's in Orlando.
[17:39] <mhall119> awesome
[17:40] <mhall119> bring jtatum back with you
[17:40] <jledbetter> Hm... Well, ok ;)
[17:41] <mhall119> all this talk of pizza parties has made me hungry
[17:44] <jledbetter> Almost lunch time :)
[17:57]  * mhall119 just uploaded UDS party pics to flickr so they'll show on our team page in LD
[17:57] <mhall119> http://loco.ubuntu.com/teams/ubuntu-us-florida so nice :)
[19:24] <karthick87> Hi..!Can anyone help me in creating a loco team?
[19:27] <karthick87> Anyone..???
[19:29] <serfus> karthick87, you should contact one of the loco-council
[19:30] <karthick87> serfus: wanna contact whom?
[19:31] <czajkowski> serfus: what's up?
[19:31] <czajkowski> karthick87: what loco team are you looking to start up
[19:31] <serfus> :)
[19:32] <karthick87> czajkowski: I am from india.I would like to start a locoteam for my state
[19:33] <czajkowski> karthick87: there is already an indian team as far as I'm aware
[19:33] <czajkowski> karthick87: you should talk to http://loco.ubuntu.com/teams/indian-team
[19:35] <karthick87> czajkowski: Thank you :)
[19:36] <czajkowski> no problem 
[19:36] <czajkowski> time for dinner 
[19:36] <czajkowski> toodles
[19:36] <serfus> bon appetit 
[19:39] <CrazyLemon> hm..do you guys know to whom i must complain if RSS feed for Canonical's news & events doesnt work (meaning it returns 404 for every feed) ?
[19:39] <paultag> hey serfus 
[19:39] <paultag> hey karthick87 :)
[19:39] <karthick87> hiyas paultag :)
[19:40] <serfus> howdy paultag, what's up?
[19:40] <paultag> serfus, thanks for the redirect, you rock
[19:40] <paultag> karthick87, anything I can help with?
[19:40] <paultag> Oh wait, czajkowski already took care of you 
[19:40] <paultag> nevermind
[19:41] <karthick87> paultag: yeah sure
[19:42] <karthick87> paultag: I wanna contribute for ubuntu documentation.Can you guide me?
[19:42] <paultag> /join #ubuntu-doc
[19:42] <paultag> karthick87, ^
[19:43] <karthick87> oke :)
[19:43] <czajkowski> CrazyLemon: webmaster
[19:44] <CrazyLemon> czajkowski ok..tnx :)
[19:44] <czajkowski> no problem 
[19:45] <paultag> !lococouncil > paultag 
[19:45] <ubot4> paultag, please see my private message
[20:01] <paultag> !lococouncil > czajkowski 
[20:01] <ubot4> czajkowski, please see my private message
[20:58] <AlanBell> CrazyLemon: who you can sometimes find in #ubuntu-website
[21:00] <CrazyLemon> AlanBell thanks but i guess someone just took out blogs and other feeds from canonical.com/rss.xml  so now only canonical related feeds are on that RSS
[21:01] <AlanBell> I have no idea