[03:59] <zkriesse> MootBot: hi
[03:59] <zkriesse> Does anyone here know if I could possibly get mootbot in my channel?
[03:59] <zkriesse> !MootBot
[08:17] <Rhonda> soren: Thanks for the hint. Am repoening the bug now and leaving the TZ hint :)
[13:14] <thorwil> godbyk-android: in fact we really should do that
[13:15] <thorwil> godbyk-android: meeting opened. nobody besides us to is here, so: meeting closed :)
[13:15] <godbyk-android> Sure. Guess I souls get in front if my computer then. :-)
[13:15] <godbyk-android> ha!
[13:15] <godbyk-android> So easy.
[13:16] <thorwil> really worth getting up early, isn't it?
[13:16] <godbyk-android> It's pretty sad if I'm the only one showing up.
[13:16] <godbyk-android> Yeah, I need to adjust my availability for this meeting. Move it to a more sensible time or something.
[13:16] <thorwil> godbyk-android: mpt is on holiday last and this week
[13:17] <godbyk-android> Aha
[13:17] <godbyk-android> 7 am sucks. :-)
[13:18] <thorwil> that on top of this running on the side with everyone having enough on their hands, anyway ...
[13:18] <godbyk-android> (especially since I usually have to be at another meeting an  hour or two later)
[13:19] <thorwil> godbyk-android: mpt mentioned a book project you talked about?
[13:20] <godbyk-android> Yeah, I think we should have a usability principles/design book for open source developers
[13:21] <thorwil> i agree in so far as there should be a central resource
[13:22] <godbyk-android> Something that's  a  bit more general than the HIGs.
[13:23] <thorwil> godbyk-android: sure. including sections on common misconceptions regarding the value of options, expert-modes and such
[13:24] <godbyk> Basically something that would help OSS developers develop more usable software at the start and also explain  how to go about testing their software (for usability).
[13:24] <godbyk> right
[13:25] <godbyk> giving concrete examples to illustrate bad designers and how to make them better (and *why* the better designs are better).
[13:25] <godbyk> as it stands now, I think the usability thing is kind of a mystery to most developers.
[13:25] <godbyk> and they're not too inclined to buy expensive books to read.
[13:26] <godbyk> so we toss together a free book (ala the Ubuntu manual), web site, etc., etc.
[13:26] <godbyk> something that can be linked to during discussions (in email lists, irc chats, etc.)
[13:29] <thorwil> godbyk: i have been thinking all the same and even vaguely mentioned it when sabdfl offered me to apply for a job. well, that did not happen
[13:29] <godbyk> bummer
[15:00] <dholbach> #startmeeting
[15:00] <MootBot> Meeting started at 09:00. The chair is dholbach.
[15:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:00] <dholbach> WELCOME EVERYBODY!
[15:00] <dholbach> Who's all here for the LoCo Directory meeting?
[15:00] <mhall119> o/
[15:00] <rick_h_> +1
[15:01] <dholbach> Who else? Come on, don't be shy :-)
[15:01] <Ddorda> i'm here
[15:01] <jasonjang> +1
[15:01] <Ddorda> still playing Lego though
[15:02] <cjohnston> o/
[15:02] <Daviey> \o
[15:02] <dholbach> awesome - if anybody of you comes in late, please let us know you're there :)
[15:02] <dholbach> I talked to mhall119 about this meeting and we thought it'd make sense to introduce the project first, talk about how things are done right now and answer all the questions, then proceed to review the open bugs and see if we need to reprioritise
[15:03] <dholbach> [TOPIC] Introduction
[15:03] <MootBot> New Topic:  Introduction
[15:03] <dholbach> So we're talking about http://loco.ubuntu.com/ which first aimed to replace the giant list of loco teams
[15:03] <rww> o/
[15:03] <dholbach> (does anybody have a link for that?)
[15:03] <dholbach> so basically just a big list of teams, who's admin of those teams, where their websites are, if they're approved etc.
[15:04] <cjohnston> https://wiki.ubuntu.com/LoCoTeamList
[15:04] <dholbach> thanks cjohnston - you can see that list here http://loco.ubuntu.com/teams/
[15:04] <dholbach> we get most of the information from Launchpad through launchpadlib
[15:04] <dholbach> the next step was that we added information about events that teams are holding
[15:05] <dholbach> so if you head to http://loco.ubuntu.com/events/ you get an idea of what's currently going on
[15:05] <dholbach> we distinguish between global events (like release parties or the ubuntu global jam)
[15:05] <dholbach> and local events, like real-life meetings those teams are holding
[15:05] <dholbach> folks can confirm their attendance for those events and add comments, etc.
[15:06] <dholbach> we partly integrated maps and country/continent information, but that's still in flux
[15:06] <dholbach> please: if you have any questions or things are not clear, please do ask
[15:06] <dholbach> any questions right now? :)
[15:06] <Daviey> dholbach, Does it rock?
[15:06] <mongolito404> Is there any other format available for the list of events (iCal, RSS, etc/)  ?
[15:06] <dholbach> Daviey: it doesn't rock - it ROCKs
[15:07] <Daviey> dholbach, Ah good! :)
[15:07] <dholbach> mongolito404: yes, there's ICal information about events
[15:07] <mongolito404> And is there a list of events per LoCo team ?
[15:07] <mhall119> there's also RSS feeds for events
[15:07] <dholbach> there you go :)
[15:07] <Ddorda> dholbach: it will be possible in the future to make a "one time meeting place"? since now we have meetings in different places, and making a new place for the list everytime is annoying
[15:07] <cjohnston> mongolito404: yes... if you click on the loco team from the teams page
[15:07] <mhall119> mongolito404: yes, if you go to the teams's page, there's a link
[15:07] <dholbach> Ddorda: you mean that you can re-use existing venues?
[15:08] <mhall119> also, there is a REST/JSON interface to all of the information in the loco-directory, so you can write mashups or feed data into another website/app: https://wiki.ubuntu.com/LoCoDirectory/API
[15:08] <Ddorda> dholbach: i mean, if it is possible to make a "one time venue"
[15:08]  * dholbach hugs mhall119
[15:08] <dholbach> Ddorda: so that the venue does not appear ever again?
[15:08] <Ddorda> indeed
[15:08] <mongolito404> I don't see an iCal feed for a team events page. I'm missing something ?
[15:08] <dholbach> Ddorda: no, that functionality is not there yet - can you file a bug about it, so we can see how best to implement it and what others think?
[15:08] <mhall119> mongolito404: the ical is global only right now, but there are per-team RSS feeds of events
[15:09] <Ddorda> dholbach: will do.
[15:09] <dholbach> thanks Ddorda
[15:09] <Ddorda> another question: my friend has the directory interface in Hebrew for some reason, any way to change it back to English?
[15:09] <dholbach> http://loco.ubuntu.com/events/team/ubuntu-pk/rss/ ŌåÉ for example
[15:09] <MootBot> LINK received:  http://loco.ubuntu.com/events/team/ubuntu-pk/rss/ É for example
[15:09] <rww> Ddorda: can you subscribe ~robertwall to it when you do? I'd been meaning to ask for one-time venues.
[15:10] <Ddorda> rww: sure thing :)
[15:10] <dholbach> Ddorda: there's a bug about it, you need to change browser's language atm
[15:10] <Ddorda> dholbach: okay, thanks :)
[15:11] <dholbach> bug 570638
[15:11] <dholbach> any more immediate questions?
[15:11] <Ddorda> oh! another thing: is it possible to choose other organizer to the meeting, instead of having the LoCo as an organizer?
[15:11] <dholbach> Ddorda: no, not yet, we don't have an event organiser role
[15:11] <dholbach> it might make sense to have a contact for an event
[15:11] <Ddorda> since there are some meetings that our LoCo takes part in, but not the organizer
[15:11] <mhall119> I think there is a bug for that
[15:12] <Ddorda> dholbach: no need for a role
[15:12] <mhall119> Ddorda: you can still leave the LoCo as the organizer in the LD
[15:12] <Ddorda> hwo about some kind of category, like the venues..
[15:12] <mhall119> it's really to specify which loco is involved, not the loco's role in the event
[15:12] <dholbach> I think it'd be good to select a member or two as contacts for an event if there's any queries
[15:13] <dholbach> oh, maybe I misunderstood
[15:13] <moshe742> i think he means if the organizers are another group for open source
[15:13] <dholbach> Ddorda: can you clarify?
[15:13] <moshe742> he= Ddorda
[15:13] <Ddorda> dholbach: ..?
[15:14] <moshe742> you mean about august pinguin, right?
[15:14] <Ddorda> moshe742: indeed
[15:14] <Ddorda> we don't organize August penguin event, but we do take part in it
[15:14] <Ddorda> but in the LoCo directory it says that we organize it
[15:14] <dholbach> maybe we can have a separate discussion on the loco-contacts or ubuntu-event-planners mailing lists?
[15:14] <mhall119> The organizing team means which team has organized to participate in the event
[15:14] <mhall119> not necessarily who is running the event
[15:15] <Ddorda> mhall119: i see, so it's about 'the right word' :)
[15:15] <mhall119> right
[15:15] <dholbach> ok, let's make that a separate discussion :)
[15:15] <dholbach> or file a bug and we fix the description :)
[15:15] <Ddorda> will do
[15:15] <dholbach> whatever seems right :)
[15:15] <dholbach> thanks
[15:15] <mongolito404> viewer may be confused as "Organizing" will usually implies that the team is organizing the event, not its own participation at the event.
[15:16] <Ddorda> 2 bug reports from one coversation, nice :)
[15:16] <dholbach> mongolito404: ok, I see what you mean
[15:16] <dholbach> alright, if there's no other immediate questions (please just keep them coming), we can talk about how the LD is developed and how we work together
[15:16]  * Daviey suggests if there is doubt, it's at the very least a usability issue.. Therefore raise a bug and be as descriptive as possible
[15:16] <moshe742> what is LD?
[15:16] <mhall119> Ddorda: I suspect they won't be the last
[15:16] <dholbach> moshe742: sorry, the LoCo Directory
[15:17] <moshe742> thanks:)
[15:17] <Ddorda> LaunchDad :D
[15:17] <dholbach> haha
[15:17] <dholbach> [TOPIC] LoCo Directory Development
[15:17] <MootBot> New Topic:  LoCo Directory Development
[15:17] <mhall119> we use LP and LD a lot, sometimes I've had to re-read
[15:17] <dholbach> alright, so we have a bunch of people in here who helped develop the LoCo Directory and who put a lot of effort into making it rock
[15:18] <dholbach> getting the source code is trivial,    bzr branch lp:loco-directory    will give you all you need
[15:18] <dholbach> it even comes with an INSTALL file that tells you how to set it up and make it run locally
[15:18] <Daviey> dholbach, Do we still suggest postgres for local?!
[15:18] <dholbach> it's written in python and uses the Django framework
[15:18] <dholbach> Daviey: no, it's optional
[15:19] <mhall119> Daviey: I think we default local_settings.py to sqlite
[15:19] <dholbach> mhall119 will give a session at https://wiki.ubuntu.com/UbuntuDeveloperWeek next week about Django and how to work with it, if you're interested
[15:20] <mhall119> the class will be generic Django, not LD specific, but I will hit on most of what is used in LD
[15:20] <dholbach> the basics are: you define what kind of data you work with in models, define an url structure, set up views on that data (what do I want on a specific page), then put stuff into templates which contain bits of HTML and some very simple "programming language" to shoehorn the data into the page
[15:21] <dholbach> particularly because the data used in the LD is very clear and immediate (you have teams, team.contact, venues and venue.city, etc.) it's such a fun and interesting project to work on
[15:21] <dholbach> we use launchpadlib to get data from Launchpad, but that's basically all the code bases we use
[15:22] <dholbach> on the web front we use just html and jquery for some nice animations and to make the interface nicer
[15:22] <dholbach> are there questions about the "platform"?
[15:23] <dholbach> if you have questions later on, just ask :)
[15:23] <dholbach> so how do we work together?
[15:23] <moshe742> well, i am new here so where can i get the basics on all of this?
[15:23] <dholbach> moshe742: do you have any specific questions?
[15:23] <mhall119> moshe742: will you be able to attend my classes on the 16th?
[15:23] <Ddorda> may i ask the annoying question "why not drupal" ?
[15:23] <moshe742> when will it be?
[15:24] <dholbach> Ddorda: we all liked django and python and it's what the project was started in
[15:24] <mhall119> moshe742: 16:00UTC->18:00
[15:24] <mhall119> Ddorda: Django, being an app framework rather an a CMS, was more suited to what we were doing
[15:24] <moshe742> will it be in the irc?
[15:24] <dholbach> moshe742: yes in #ubuntu-classroom
[15:24] <mhall119> moshe742: yes, in #ubuntu-classroom
[15:24] <Ddorda> dholbach: and i like Drupal! let's make an 0.9 revolution like Compiz
[15:24] <moshe742> ok, i will be there
[15:24] <dholbach> just check out https://wiki.ubuntu.com/UbuntuDeveloperWeek - it has all the details
[15:24] <Ddorda> joking :P
[15:25] <dholbach> if you have played around with python a bit and checked out the source code I guess a lot of it will make sense if you look at it a bit
[15:25] <dholbach> if not, talk to us on #ubuntu-locoteams
[15:26] <dholbach> I'm sure that Daviey, mhall119, toabctl, cjohnston, myself or others will be happy to help you get started
[15:26] <Daviey> o/
[15:26] <dholbach> so the way we work is something like this:
[15:26] <dholbach>  - we get a bug report or file a bug ourselves
[15:27] <Ddorda> dholbach: i was joking... don't take me seriously :P
[15:27] <dholbach>  - somebody decides to work on it, so they branch lp:loco-directory and work on a separate branch for that fix
[15:27] <dholbach>  - we use merge proposals and peer-review everything
[15:27] <dholbach>  - that gets merged, the bug gets milestoned with whatever is the current milestone
[15:27] <dholbach>  - once we have a bunch of interesting bugs fixed, we merge new translations from launchpad in
[15:28] <dholbach>  - we release it and ask the Canonical IS team to get the new code on loco.ubuntu.com
[15:28] <dholbach>  - DONE :)
[15:28] <dholbach> if you need help with bzr or merge proposals we can help with that too
[15:28] <mhall119> it's very easy once you get into it
[15:28] <cjohnston> ground control is a great tool for starting too
[15:28] <dholbach> the idea is that we try to work on separate things, get them reviewed by the team and merge them in and release when it feels right
[15:29] <rww> Do you release on a set schedule, or just when there's a good collection of changes?
[15:29] <dholbach> rww: the latter
[15:29] <dholbach> rww: if there's something important we fixed or it feels like it's substantial we release
[15:29] <mhall119> and don't be offended if your merge proposal gets marked as "Needs Fixing", most of them do, even the ones the main developers submit
[15:29] <dholbach> ie: https://launchpad.net/loco-directory/0.2.x/0.2.4
[15:29] <dholbach> https://launchpad.net/loco-directory/0.2.x/0.2.5
[15:30] <dholbach> those were smaller releases which fixed just a couple of bugs
[15:30] <Ddorda> i reported both bugs, can i write them down here so people will see, or it will be too much spam?
[15:30] <mhall119> Ddorda: we're going to review open bugs in a bit
[15:30] <dholbach> Ddorda: we'll go through bugs later on, if that's OK
[15:30] <Ddorda> sure, sorry :)
[15:30] <dholbach> awesome
[15:31] <mhall119> since you got them in so quickly, we can go over them too
[15:31] <dholbach> just a few words about bugs now
[15:31] <dholbach> we use tags to indicate where those bugs are happening or what they affect
[15:31] <dholbach> check out https://bugs.launchpad.net/loco-directory/+bugs
[15:31] <dholbach> on the right hand side you can see a list of tags
[15:31] <dholbach> so "events", "teams", "venues", "maps" should be obvious
[15:32] <dholbach> "stats" is about statistics we'll probably introduce one day
[15:32] <dholbach> "mainpage" is about making the landing page more useful, "ui" is well, about UI
[15:32] <dholbach> but we also have some special tags like "bitesize" which are small bugs suitable for newcomers
[15:32] <dholbach> or "needs-decision" where we identified a problem and don't know yet how to fix it, the LoCo Council helped us in the past with those
[15:33] <dholbach> "schema-change" means that something in the data structure has changed
[15:33] <dholbach> everything else is pretty straight-forward:
[15:33] <dholbach>  - Triaged once the bug is full-well understood
[15:33] <mhall119> bitesize bugs are good for people who are learning python and django, they are usually one or two line fixes, we save them for newcomers to encourage people to get involved
[15:33] <dholbach>  - In Progress (plus assigned to someone) if someone is working on it
[15:34] <dholbach>  - "Fix Committed" once the fix has been merged into lp:loco-directory (but is not deployed on loco.ubuntu.com yet)
[15:34] <dholbach>  - Fix Released once it was released
[15:34] <dholbach> also once a fix is in trunk (lp:loco-directory), we milestone it, so we have some kind of "changelog" for the release
[15:34] <dholbach> note that the bottom of http://loco.ubuntu.com/ shows the current release
[15:35] <dholbach> are there any more questions about the LD and how it's developed?
[15:35] <dholbach> I know that it might be a bit much information all at once :)
[15:36] <mhall119> we also use blueprints for planning major changes and features
[15:36] <mongolito404> Any automatic testing ?
[15:36]  * Daviey adds, even if you are unsure of your fix - push it to launchpad via bzr anyway and propose for merging.  Then it'll be either accepted, or a discussion on how to imporve it - to then get it landed
[15:36] <Daviey> it's really not as scary as it sounds!
[15:36] <Daviey> mongolito404, Our automatic testing framework is currently community based :)
[15:37] <dholbach> Daviey adds a good point - most of the development discussion happens in blueprints and even hackers who landed lots of fixes sometimes have to rework their fixes a couple of times to get it right
[15:37] <dholbach> it's important that we as a team can say: ok, yes, we like it the way it is because we'll maintain the page
[15:37] <dholbach> mongolito404: not as much as we'd like
[15:37] <Daviey> Oh, and dholbach is the offical gatekeeper of code. :)
[15:38] <dholbach> mongolito404: we had a couple of test cases, but no, not much, unfortunately
[15:38] <mhall119> bzr branches on launchpad are cheap, so make and push whatever work you do so it's available to others
[15:38] <Daviey> (but ideally keep the changes small and easy to read)
[15:38] <dholbach> can the IRC Council please kick Daviey from the thannel (reason: I'm NOT the offical gatekeeper!)
[15:38] <dholbach> s/thannel/channel
[15:38] <Daviey> :)
[15:38] <cjohnston> yes you are
[15:38] <cjohnston> :-
[15:38] <cjohnston> :-P
[15:38] <mhall119> s/official/de facto/
[15:39] <dholbach> no, I'm not - I'm really just a team member like everybody else :)
[15:39] <dholbach> we have no hierarchy :)
[15:39] <mhall119> he's our community-appointed benevolent dictator
[15:39] <Daviey> It really helps if you commit often.  So even changing a few lines to do X, commit it to bzr with a readable changelog
[15:39] <dholbach> it's all bit chaotic, but in a good way :)
[15:39] <dholbach> Daviey++
[15:39] <cjohnston> cabdfn  = community-appointed benevolent dictator... for now
[15:39] <cjohnston> hehe
[15:39] <Daviey> committing a massive change in one commit isn't groovy. ;)
[15:39] <mhall119> +1
[15:40] <dholbach> but as we said before: it's all easy, not too hard, whatever you want to contribute is appreciate and we'll mentor you if you too think this is an exciting and important project
[15:40] <cjohnston> Daviey: https://edge.launchpad.net/~loco-directory-dev   dholbach looks like the owner to me.. hehe
[15:40] <mhall119> we're also very laid back and informal, it's not hard to get a contribution merged into the loco-directory
[15:41] <dholbach> any more questions?
[15:41] <dholbach> did we bore everybody to sleep already? :)
[15:41] <elky> Is it friday yet?
[15:41] <mhall119> cjohnston: ~loco-directory-dev/loco-directory/0.2/ is trunk
[15:41] <jasonjang> THX, i've no question, dholbach
[15:41] <dholbach> elky: you're nearer to it than most of us others :)
[15:42] <dholbach> alright, let's proceed to bugs then :)
[15:42] <dholbach> [TOPIC] Bug Review of the LD
[15:42] <MootBot> New Topic:  Bug Review of the LD
[15:42] <dholbach> I'd like to put some attention to https://blueprints.launchpad.net/ubuntu/+spec/community-m-loco-directory-plans
[15:42] <dholbach> it's what we discussed at UDS and is stuff we'd like to get done in the maverick cycle if possible
[15:43] <dholbach> if you look at the work items area, there's a couple of bugs that were all marked as "High importance"
[15:43] <dholbach> so they'll turn up at https://bugs.launchpad.net/loco-directory/+bugs at the top
[15:43] <dholbach> most of them revolve around making teams and events more easily findable because the lists get very long very easily
[15:44] <dholbach> also to indicate team contacts, etc.
[15:44] <Ddorda> so.. now i can show my bug reports? :D
[15:44] <dholbach> do we still think they all make sense?
[15:44] <dholbach> Ddorda: in a bit
[15:44] <mhall119> dholbach: can we triage new bugs at the end?
[15:44] <dholbach> sure
[15:44] <mhall119> that'll cover Ddorda's
[15:45] <dholbach> (also please note the [dholbach] in the Whiteboard section is just a preliminary measure to get them on the radar for the blueprint tracking)
[15:45] <dholbach> :-)
[15:45] <dholbach> so, let have a look at the "High" importance bugs first - do they still all make sense there?
[15:45] <cjohnston> in other words, he wants you to take his tasks.. lol
[15:46] <dholbach> cjohnston: get to work! :)
[15:46] <cjohnston> they are all beyond me.
[15:46] <mhall119> dholbach: I think some of them are more wishlist than high
[15:46] <dholbach> mhall119: for example?
[15:47] <mhall119> I usually consider high bugs to mean something isn't working
[15:47] <dholbach> ah ok
[15:47] <dholbach> maybe we should use critical for them?
[15:47] <mhall119> like, showing descriptive team names
[15:47] <Daviey> well IMo wishlist does indicate new feature
[15:47] <dholbach> 601679 could be Critical for example
[15:47] <Daviey> High is a current feature not working, or a non-critical regression
[15:47] <cjohnston> I think we decided to prioritise things as we would like their importance in this cycle
[15:48]  * Daviey missed that memo cjohnston 
[15:48] <mhall119> dholbach: I agree with that, don't want spammers farming emails from LD
[15:48] <cjohnston> Daviey: that seemed to be how it was from uds
[15:48] <YoBoY> dholbach: +1 the mails are not visible by everyone in a majority of applications
[15:48] <dholbach> so let's use Critical for stuff that doesn't work in the future
[15:48]  * dholbach will readjust that bug
[15:48] <dholbach> we don't use critical very often any way
[15:48] <YoBoY> hi ^^"
[15:48] <mhall119> we rarely have critical problems ;)
[15:48] <Daviey> well a crticial bug is normally already on our radar.
[15:49] <dholbach> I used High for the stuff that we put in the blueprint - hope that's ok
[15:49] <mhall119> dholbach: there's nothing wrong with it, as long as we're all on the same page as to what that means
[15:49] <cjohnston> I think they can have both meanings
[15:49] <cjohnston> a feature thats high and a problem thats high
[15:49] <dholbach> maybe somebody wants to document that on https://wiki.ubuntu.com/LoCoDirectory? we don't use that page as much as we could :)
[15:50] <dholbach> just 2-3 sentences
[15:50] <dholbach> ok, nobody volunteers, I'll do it
[15:51] <mhall119> dholbach: I'm already on it ;)
[15:51] <dholbach> oh wow
[15:51] <dholbach> mhall119 is unstoppable
[15:51]  * dholbach hugs mhall119
[15:51] <dholbach> (hugs are an important ingredient in the LoCo Directory as you can see)
[15:52] <dholbach> mhall119, Daviey: do you want to go through the bugs one by one or should we look at them in groups?
[15:52] <dholbach> (not sure how much time you all have)
[15:52] <mhall119> nobody's listed on the schedule after us
[15:53] <dholbach> ok, let's zip through them quickly - can you, if you think the importance should change, or tags are missing or something else is not clear please speak up, also if you intend to work on it?
[15:54] <dholbach> from top to bottom on https://bugs.launchpad.net/loco-directory/+bugs
[15:54] <dholbach> bug 601679
[15:54]  * dholbach added teams, data
[15:54] <dholbach> any takers?
[15:55] <Ddorda> dholbach: sorry, i'm drupalian
[15:55] <mhall119> ui
[15:55]  * YoBoY only know how to open bugs T_T
[15:55] <dholbach> ok, added
[15:55] <mhall119> dholbach: will we only display the email for logged in users, or are we going to implement a contact form for anyone to use?
[15:56] <dholbach> mhall119: LP has a contact form already - we can just link to that
[15:56] <mhall119> right now, LD doesn't send out emails, but we've discussed that in the past
[15:56] <dholbach> which requires log in there
[15:56] <mhall119> ah, even better
[15:56] <dholbach> yeah
[15:56] <YoBoY> you choose, the mail is in clear for loged in users in LP, so...
[15:56] <dholbach> should be a trivial change - I'll take it
[15:56] <dholbach> next: bug 495046
[15:57] <dholbach> looks alright to me, if you think it's a good idea to work on it just say "I'll take bug XYZ"
[15:58] <dholbach> so we can go through them more quickly :)
[15:58] <mhall119> is this for users?
[15:58] <mhall119> display a user's real name
[15:58] <dholbach> atm just for adding the real name, but it'd be a preparation for future user stuff
[15:58] <dholbach> once we have that model it'll be trivial to add more
[15:58] <mhall119> do we have real name info coming from LP right now?
[15:59] <dholbach> no
[15:59] <dholbach> we need schema-change for that
[15:59] <mhall119> Django's user table has a space for first and last name, we just need to get them from LP (if they're there)
[15:59] <dholbach> it's not crazy amounts of work, but substantial because templates need to change too, etc
[16:00] <dholbach> I wouldn't want to split up a display_name string from LP into first and last name programmatically
[16:00] <dholbach> it invites too much problems
[16:00] <YoBoY> not every one put a first and last name on LP
[16:01] <mhall119> so, launchpad and ui tags for that one
[16:01] <dholbach> think of Spanish names like Pedro Villavivencio Garrido, yes and what YoBoY said
[16:01] <mhall119> who's our launchpadlib guru?
[16:01] <dholbach> I'm not a guru, but I know that it just has .display_name as one string
[16:01] <dholbach> it doesn't have first and last name
[16:01] <mhall119> dholbach: we can just dump the entire display name into Django's Firstname field, and treat that like a display name
[16:02] <dholbach> let's make that a separate discussion - I personally don't know if it should be the django user or if it should be something else because we might add other stuff in the future
[16:02] <mhall119> okay, future discussion
[16:02] <dholbach> rock on
[16:02] <dholbach> next: bug 496250
[16:03] <dholbach> should be easy to do
[16:03] <dholbach> requires a schema-change too
[16:03] <dholbach> next: bug 570613 effie_jayx seems to be on it - does anybody know of any progress there?
[16:03] <mhall119> yeah, and team members to update the info, because LP has no concept of a team contact
[16:04] <dholbach> mhall119: yep
[16:04] <mhall119> dholbach: I'll take 496250
[16:04] <dholbach> thanks mhall119 - can you assign to yourself?
[16:05] <dholbach> I'll send a mail to effie-jayx about it and also ask toabctl and huats to have a look because they worked with map stuff in the past a lot I think
[16:05] <mhall119> done
[16:05] <dholbach> next: bug 579833
[16:05] <czajkowski> aloha
[16:05] <dholbach> should be VERY interesting, I don't know how easy or complicated it is
[16:05] <dholbach> it'd certainly add more life to the LD :)
[16:06] <mhall119> I think this can be considered as "Medium", and it's not a necessary feature addition, but still something desirable
[16:06] <mhall119> along with the twitter/identica feeds
[16:06] <dholbach> mhall119: ok, I made it High because it was discussed at UDS
[16:06] <dholbach> I set the importance to medium
[16:06] <dholbach> if anybody's interested in working on that, speak up
[16:07] <dholbach> next: bug 582354
[16:07] <dholbach> seems to b ea bit more work, but something we really should fix soon
[16:07] <mhall119> yeah, the big question is how to allow the transition without dumping all the old data
[16:07] <dholbach> we answered  that question
[16:07] <dholbach> comment 6
[16:08] <mhall119> right
[16:08] <mhall119> does LP provide any kind of internal id that doesn't change?
[16:09] <dholbach> no idea
[16:09] <dholbach> might be worth finding out
[16:09] <mhall119> yeah, then we could avoid having to do anything for this in the future
[16:09]  * dholbach nods
[16:09] <dholbach> can you add the thought to the bug?
[16:09] <dholbach> next up is a double pack of bugs: bug 596823 and bug 596826
[16:10] <dholbach> it'd be FANTASTIC to fix them and as far as I can see it wouldn't be complicated as we have all that data already :)
[16:10] <mhall119> venues is already grouped by country
[16:11] <mhall119> would grouping it further by continent add anything?
[16:11] <dholbach> I think it'd be nice
[16:11] <dholbach> especially it we do the same thing for teams
[16:12] <mhall119> ok, that'd be pretty simple for venues, just an additional regrouping
[16:12] <dholbach> the list will get longer and longer, so maybe something like adding anchors at the top would help
[16:12] <dholbach> and make the whole LD much more useful
[16:12] <dholbach> especially with 100 release parties coming up :-P
[16:12] <mhall119> the search function works pretty well for usability
[16:13] <dholbach> I guess it helps if you make several offers to find something ;-=
[16:13] <dholbach> ;-)
[16:13] <dholbach> alright, that's all for the High importance bugs :-)
[16:14] <dholbach> it'd be nice if we could get them sorted out in the Maverick time frame
[16:14] <mhall119> commented on the venues bug
[16:14] <dholbach> thanks mhall119
[16:14] <dholbach> medium bugs
[16:14] <mhall119> do we want to group teams by country, when most of the time there will be one per country?
[16:14] <mhall119> or will by continent be enough
[16:14] <dholbach> we should try continent first and then see how it goes
[16:15] <dholbach> for the US it'd make sense to have country :)
[16:15] <mhall119> ok
[16:15] <mongolito404> mhall119: Ubuntu-fr is the LoCo for French speaking... while Ubuntu-be is a pure country based LoCo with no specific language (we use French, Dutch, German and English)
[16:15] <dholbach> might be interesting to see how we deal with countries that span various continents
[16:15] <dholbach> we should probably list them twice just to make sure
[16:15] <mhall119> for the US, the list will only be 50 long, it's browsable
[16:15] <dholbach> :)
[16:15] <mhall119> mongolito404: that's a whole other issue, YoBoY brought it up a couple days ago
[16:16] <YoBoY> yep
[16:16] <dholbach> yeah and we have a bug report for that
[16:16] <dholbach> so we'll get to it
[16:16] <mhall119> you French guys are always complicating things ;)
[16:16] <dholbach> haha
[16:16] <dholbach> yeah, want all their colonies listed and everything ;-)
[16:16] <YoBoY> mhall119: it's why we rocks ;)
[16:16]  * YoBoY hugs mhall119 
[16:16] <mhall119> :P
[16:16] <dholbach> alright, let's get to those bugs in a bit
[16:16] <mongolito404> Yes but this highlight the fact there there is some multi-countries LoCos
[16:17] <dholbach> mongolito404: yes, we're aware of that and we hope to solve it in a careful but pragmatic way
[16:17] <dholbach> the most important thing to me is that users find teams and events easily
[16:17] <mhall119> mongolito404: some yes, but that's a matter for the loco-council to figure out i think
[16:17] <mhall119> we can implement it either way
[16:17] <dholbach> alright, let's crack on
[16:18] <dholbach> bug 523497
[16:18] <mhall119> I think I fixed that with the new theme
[16:18] <dholbach> mhall119: can you close it? toabctl can reopen if necessary
[16:18] <dholbach> bug 528829
[16:19] <mhall119> now only logged in LC members see links for managing global events
[16:19] <dholbach> would definitely be nice
[16:19] <mhall119> yes
[16:19] <dholbach> afaik django even has the list of us states somewhere
[16:19] <mhall119> this I would consider "High", actually
[16:19] <dholbach> maybe we can factor that in somewhere
[16:19] <dholbach> ok, done
[16:19] <dholbach> takers?
[16:19] <mhall119> adding it to Venue would be good too
[16:19] <mongolito404> About "states", I've seen many implementation in the Druapl world that doesn't fit real world cases.
[16:20] <mhall119> mongolito404: can you elaborate on that?
[16:20] <mongolito404> In Belgium we have very special (and ihmo, stupid, but that's another question) country subdivisons.
[16:21] <dholbach> we could think about special casing this just for huge teams like the US team
[16:21] <mongolito404> The traditional subdivision used for "states" field in address are Provinces. But the country is so small that they have nearly no meaning for most users.
[16:21] <mhall119> not just US, but even large countries with a single loco (for venues)
[16:21] <mongolito404> Plus, and that's the trick, there is some place in Belgium that are not part of any Provinces.
[16:22] <dholbach> it sounds to me like it should be an optional field
[16:22] <mhall119> dholbach: for teams yes
[16:22] <mongolito404> And I'm sure Belgium is no the only country with country subdivisions that don't map to the "clean" US-style "sates" concept.
[16:23] <dholbach> ok, we have like 20 bugs left, maybe we should just limit ourselves to bug importance, missing tags and if we have takers for the bug? otherwise I'm afraid we'll be here even longer
[16:23] <mhall119> mongolito404: if we give you a way to provide some for of sub-country identifier for a Venue, would you be able to use it as such?
[16:23] <dholbach> particularly all the timezone/country/continent/state discussions take ages
[16:23] <mhall119> dholbach: fine by me, we can continue in #ubuntu-locoteams for more indepth discussion
[16:23] <YoBoY> geopolitical matters always take ages
[16:24] <YoBoY> ^^
[16:24] <dholbach> we don't want to get political at all
[16:24] <mongolito404> http://www.geonames.org/ is a nice source for information about country subdivisons (as a web service)  but if used, the system must be ready to accept custom code for special cases (like Belgium).
[16:24] <MootBot> LINK received:  http://www.geonames.org/ is a nice source for information about country subdivisons (as a web service)  but if used, the system must be ready to accept custom code for special cases (like Belgium).
[16:24] <dholbach> but stay pragmatic and do the majority of our users a service :)
[16:25] <mhall119> next bug
[16:25] <dholbach> I think it's important that we briefly highlight bugs and if some of us find out they're interested in a bug, please just go and subscribe and have your say
[16:25] <dholbach> and we can further discuss in #ubuntu-locoteams in the next hours and days
[16:25] <dholbach> bug 540532
[16:25] <mhall119> that's one we need to ask the launchpad folks about I think
[16:26] <mhall119> or the openid folks
[16:26] <dholbach> yeah, I think there was a separate bug about that
[16:26] <dholbach> can you tag "launchpad"?
[16:26] <dholbach> so we have stuff we can pester the lp folks about
[16:26] <mhall119> your fix will work in 99% of situations though, and i think that's enough to implment it
[16:26] <dholbach> bug 552762
[16:27] <mhall119> I'm still not sure about this
[16:27] <dholbach> me neither
[16:27] <dholbach> needs-decision?
[16:27] <mhall119> as described by czajkowski, I think having multiple events would be more appropriate
[16:27] <mhall119> yeah, needs-decision
[16:27] <dholbach> ok
[16:27] <dholbach> next: bug 579828
[16:28] <dholbach> I have no idea how to do that - can we do that with crazy django decorators? :-D
[16:28] <mhall119> that's where we want to add a popup on the add-event form to add a venue without leaving the event form
[16:28] <mhall119> I've done it in the past, using a hack with the admin widgets, but it'll need some reworking to fit into LD
[16:28] <dholbach> I'd be fine if form 1 ŌåÆ form 2 if the popup is too complicated
[16:28] <mhall119> I'll take the assignment, but it'll take a while
[16:29]  * dholbach hugs mhall119
[16:29] <mhall119> I need to add that functionality to my work app anyway
[16:29] <dholbach> we should do a renewed call for help, maybe have a LD bug of the month :)
[16:29] <mhall119> so it's a good excuse
[16:29] <dholbach> nice
[16:29] <dholbach> next: bug 579841
[16:29] <dholbach> larger piece of work, but probably nice to have at some stage
[16:29] <dholbach> tagged with 'user' as all the other models.user ideas
[16:30] <dholbach> next: bug 585306
[16:30] <dholbach> should be easy to do, just a bit of confirmation here and there
[16:30] <dholbach> I'll add bitesize
[16:30] <mhall119> dholbach: I'm tagging the profile as needs-decision also, I think we should discuss it more on -contacts and -council
[16:30] <dholbach> thanks mhall119, yes
[16:31] <dholbach> next: bug 590091
[16:31] <mhall119> dholbach: that one may also be resolved in the new theme, I'll have to check
[16:31] <mhall119> 585306 that is
[16:31] <dholbach> mhall119: awesome
[16:31] <dholbach> 590091 should be easy to do too
[16:31] <rww> I'll take 590091
[16:31] <dholbach> rww: thanks - can you assign to yourself?
[16:31] <dholbach> if you need help, shout :)
[16:32] <mhall119> rww: make sure it's not already working, I thought I submitted a fix for that a while back
[16:32] <rww> mhall119: k
[16:32] <dholbach> thanks guys
[16:32] <dholbach> next: bug 599831
[16:32] <dholbach> would be very nice, our current mainpage is not useful at all
[16:33] <mhall119> agreed, it shouldn't be difficult either, but not quite bitesize
[16:33] <dholbach> yep
[16:33] <mhall119> a good one for cjohnston ;)
[16:33] <dholbach> next: bug 600134
[16:33] <mhall119> I'm not sure it's all that difficult
[16:33] <dholbach> yep, agreed
[16:33] <ebel> I submitted that one
[16:33] <rww> I'll grab 600134 too, it looks doable
[16:34] <dholbach> use login decorator, change a few strings
[16:34] <dholbach> :)
[16:34]  * dholbach hugs rww
[16:34] <dholbach> awesome
[16:34] <mhall119> ebel: can we discuss it later in -locoteams?
[16:34] <ebel> mhall119: sure
[16:34] <dholbach> next: bug 601081
[16:35] <mhall119> sounds like something that should be updated in launchpad
[16:35] <dholbach> I have no idea what this bug is about
[16:36] <mhall119> I think launchpad currently lists teams and up for reapproval, but LC is only re-evaluating a subset of them
[16:36] <dholbach> can you add that thought to the bug?
[16:36] <dholbach> I think it'd be good to link to the reapproval page and explain what the page is about on the LD page
[16:36] <dholbach> which should be easy to do
[16:36] <dholbach> ok, next up
[16:36] <dholbach> next bug: 601838
[16:36] <dholbach> very easy to do
[16:37] <dholbach> and we're done with medium bugs
[16:37] <dholbach> let's try to do the rest in the next 23m - 2 hours is enough for this meeting :)
[16:37] <mhall119> dholbach: I commented on it, but should it be marked as won't fix?
[16:37] <dholbach> I'll leave that to you
[16:38] <dholbach> next: bug 503939
[16:38] <dholbach> for somebody good with web ui stuff
[16:38] <mhall119> I'll leave it open to add a link and explanation on the reapprovals pae
[16:38] <dholbach> next: bug 510328
[16:38] <dholbach> can we confirm we use the same in the whole LD and close the bug?
[16:39] <mhall119> the bug specifically wants them sorted a different way, which I disagree with
[16:39] <dholbach> that's fine
[16:39] <dholbach> let's just make sure we use a similar style across the app and be done with it
[16:39] <dholbach> next: bug 510572
[16:40] <dholbach> somebody good with rss and data could fix the bug easily
[16:40]  * dholbach adds bitesize
[16:40] <rww> which page are those RSS feeds on?
[16:40] <mhall119> the team pages
[16:40] <dholbach> rww: if you go to a team's event page, it'll have the rss info in the header
[16:40] <dholbach> or in the team page itself
[16:41] <dholbach> it's not well-advertised
[16:41] <dholbach> that should be fixed too
[16:41] <dholbach> can somebody file a bug about that so we can discuss how we can do that?
[16:41] <dholbach> next: bug 582571
[16:41] <dholbach> ah yes, that's still an issue, I think
[16:42] <rww> Oh, I see. I'll take 510572 and file one for advertising RSS.
[16:42] <dholbach> in the "None" section at the bottom of http://loco.ubuntu.com/venues/
[16:42] <dholbach> rww: you're a rockstar!
[16:42] <mhall119> dholbach: the venue doesn't have a name, that's a database fix
[16:42] <dholbach> mhall119: oh ok, can you add that info to the bug? happy to "fix it" :-D
[16:42]  * dholbach assigns
[16:43] <mhall119> we currently have a "none" section for venues without a country, but if it has no name, it has no link text
[16:43] <dholbach> also make the venue name mandatory
[16:43] <dholbach> and I'll rename "None" too
[16:43] <dholbach> can you add that to the bug too?
[16:43] <dholbach> I'd fix them in the same go, or if you want can you file a separate bug?
[16:43] <dholbach> I'll load up the next bugs then :)
[16:44] <mhall119> sure
[16:44] <dholbach> thanks muchly
[16:44] <dholbach> ha, bug 582573 is fixed
[16:44] <dholbach> next: bug 599640
[16:45] <dholbach> would be nice to have to pre-populate a form and have a "duplicate event" link
[16:45] <dholbach> it's a bit of work, but not too much I guess
[16:45] <dholbach> next: bug 599708
[16:45] <mhall119> I think 582573 is fixed
[16:46] <dholbach> I have no idea how to do that, and which API we'd use (remember we have to get IS to approve the installation of new packages and stuff) and if we can access it easily from the loco.ubuntu.com host (might have to get a hole poked in the firewall)
[16:46] <mhall119> oh, I fail reading
[16:46]  * dholbach hugs mhall119 :)
[16:46] <mhall119> dholbach: not much work, I'll take it
[16:46] <dholbach> but maybe we can just use raw HTTP/RSS and get it over a data center proxy
[16:46] <ebel> dholbach: it might be possible to include a javascript widget for it? ie processing happens on the browser side?
[16:46] <dholbach> erm instead of raw HTTP I meant "not use some crazy library"
[16:47] <mhall119> 599640 that is
[16:47] <dholbach> mhall119: awesome
[16:47] <ebel> but then you have to pick one service (twitter or identica), which is a flaw...
[16:47] <dholbach> ebel: that'd be a possibility too - can you add info about that to the bug report?
[16:47] <dholbach> ebel: then we can decide it later on
[16:47] <mhall119> dholbach: I was looking into a feed parsing library that will let us aggregate twitter and identica feeds for that
[16:48] <dholbach> ok, if you can all add that info, I'd appreciate it
[16:48] <dholbach> next: bug 600552
[16:48] <dholbach> definitely a needs-decision one, as it'd add various links and icons for all the tags to the page
[16:48] <dholbach> I'm not too fussed over how we do it
[16:49] <dholbach> next: bug 601928
[16:49] <dholbach> another bitesize one
[16:49] <dholbach> and we're done with low prio bugs
[16:49] <dholbach> only just a few left
[16:50] <dholbach> next: bug 526800
[16:50] <dholbach> a lot more work, I think right now we're doing quite fine with the model we use, so wishlist is appropriate methinks
[16:50] <mhall119> I think that needs to be elevated above wishlist now
[16:50] <mhall119> we keep getting requests
[16:50] <dholbach> mhall119: because of abuse?
[16:51] <mhall119> hmm, no, just people wanting it that way
[16:51] <mhall119> maybe we should send out an inquiry to loco-contacts to see if it's necessary
[16:51] <dholbach> they can implement it that way, if they like :-P
[16:51] <dholbach> "patches are welcome" ;-)
[16:51] <dholbach> no, I can see why a more careful member would like to have it
[16:52] <dholbach> but as I said, I think it's a bit more work to get it in, schema-change, more LP checks, couple of views and templates need changing
[16:52] <dholbach> so changes across the board
[16:52] <dholbach> if you want to raise the importance, please go ahead
[16:52] <mhall119> yeah, we'll need to pull sub-team info from launchpad too
[16:52] <dholbach> yeah
[16:52] <mhall119> I had some initial code for this, but the launchpad part was slow
[16:52] <dholbach> bug 538177 definitely needs decision - it'd be nice to have, but we need to spec out very clearly, 1) what should be sent and 2) to whom, 3) how to configure it
[16:53] <dholbach> and that it's properly spec'ed out is not my requirement but that of IS
[16:53] <mhall119> we need to make sure IS is okay with us sending out emails too
[16:53] <dholbach> they want opt-out and a very obvious reasons for getting mail
[16:53] <mhall119> I'm going to add sending tweets/dents to that one too
[16:54] <dholbach> next: bug 539512
[16:54] <dholbach> it'd be nice if country/state info for teams could be used to pick venues :)
[16:55] <dholbach> very nice
[16:55] <mhall119> I like it, it would require some schema-changes and extra javascript/ajax magic on the front end
[16:55] <dholbach> why js/ajax?
[16:55] <mhall119> so we can display just associated venues by default, but allow for expanding the list
[16:55] <dholbach> I thought that could be solved in the query in the view
[16:55] <dholbach> ahhh gotcha
[16:55] <dholbach> shall we add an ajax or javascript tag?
[16:55] <dholbach> not sure if that helps any
[16:56] <mhall119> by the time someone gets to the venue field in the events form, they won't want to refresh to get all venues
[16:56] <mhall119> just ui
[16:56] <dholbach> yeah
[16:56] <dholbach> sounds great
[16:56] <mhall119> fortunately, with the new JSON API, it should be much easier to implement now
[16:56] <dholbach> next: bug 540384 - would be very nice
[16:56] <dholbach> Daviey: ^ :)
[16:56] <Daviey> o/
[16:56] <Daviey> Sorry, i had to take a conf call.
[16:56] <dholbach> next: bug 559228 - would be nice too and a good mainpage candidate too
[16:57] <dholbach> Daviey: that was your bug, just saying ;-)
[16:57] <mhall119> cjohnston might like it, he was doing counts for events already
[16:57] <dholbach> the stats bug probably needs some spec'ing out too
[16:57] <dholbach> cjohnston, Daviey: maybe you can have a chat about 540384
[16:57] <mhall119> yeah, with a mind towards what akgraner needs for UWN
[16:57] <Daviey> cjohnston, That should be a good bug to tackle
[16:57] <Daviey> sorry it fell off my radar
[16:57] <dholbach> no worries
[16:58] <dholbach> and we're done with Wishlist bugs
[16:58] <dholbach> there's just untriaged or undecided bugs left
[16:58] <dholbach> from top to bottom
[16:58] <dholbach> next: bug 570638
[16:58] <dholbach> personally I have no idea how to do that
[16:58] <dholbach> shall we mark it Low?
[16:59] <mhall119> for now, yeah
[16:59] <dholbach> ok
[16:59] <dholbach> I'll mark it Triaged too as the problem is well-understood
[16:59] <Daviey> hmm
[16:59] <Daviey> it needs an implementable suggestion
[16:59] <Daviey> Ie, cookie or flags at the top?
[16:59] <mhall119> ideally we'd do it the way other pages do it
[17:00] <mhall119> I'm just not sure how that is
[17:00] <dholbach> ok, either I'll mark it confirmed or add a "research" tag?
[17:00] <Daviey> hmm
[17:00] <mhall119> hmmmm
[17:00] <dholbach> I'd like research because it'd make a list of fun things to look at in the sparetime :)
[17:00] <Daviey> I wonder if our friendly translations coordinator has a suggestion? :)
[17:00] <dholbach> and new things :)
[17:00] <dholbach> he's on holidays
[17:00] <Daviey> bah
[17:00] <dholbach> ok, research it is
[17:00] <mhall119> okay, i'm okay with research
[17:00] <dholbach> next: bug 571644
[17:01] <Daviey> Hmm
[17:01] <mhall119> I say we just fix the French language
[17:01] <dholbach> haha
[17:01] <dholbach> ok, I'll just ask back if it's still a problem in the newest version
[17:01] <Daviey> mhall119, It seems French is not a registered LP project? :/
[17:01] <dholbach> maybe we can wrap
[17:01] <mhall119> or maybe just as for a more concise translation?
[17:02] <dholbach> can you follow up with those questions? concise? still a problem?
[17:02] <dholbach> and mark it incomplete?
[17:02] <Daviey> dholbach, it needs re-confirmation with the new UI
[17:02] <mhall119> YoBoY: mongolito404: can that translation be made shorter?
[17:02] <Daviey> "I have submited a shorter translation : "├Ć propos de l'annuaire"" <-- mhall119
[17:02] <dholbach> ok, let's ask for reconfirmation and crack on
[17:02] <dholbach> can somebody update the bug?
[17:02] <mhall119> ok
[17:02] <YoBoY> mhall119: i already make a proposal, but with the new theme i don't have this bug anymore, the "about" is not translated
[17:02] <mongolito404> Yep, "├Ć propos de l'annuaire" is ok
[17:03] <Daviey> YoBoY, bug fixed \o/
[17:03] <dholbach> next: bug 574049
[17:03] <YoBoY> ;) i open back if it's appear again
[17:03] <mhall119> that's the launchpad/openid issue we need to talk to someone about
[17:03] <dholbach> yeah
[17:03] <dholbach> it sucks
[17:03] <mhall119> a good candidate for "research"
[17:03] <dholbach> yeah
[17:03] <dholbach> I added a brief discussion I had with the lads
[17:03] <mhall119> what importance?
[17:04] <dholbach> but I'll just add research for now and mark Medium?
[17:04] <Daviey> yeah
[17:04] <mhall119> right now, we've only had one instance of it pop up
[17:04] <mhall119> but it's potential is much more severe
[17:04] <Daviey> well that is because all the other users have LP accounts, not just Ubuntu SSO -right?
[17:04] <mhall119> I think Medium will do for now
[17:04] <mhall119> Daviey: yes
[17:04] <rww> yup. I don't think it's a common condition, and that's the only time I've seen it
[17:05] <mhall119> we assume that a successful openid auth means they also have a launchpad profile, and that's evidently not always true
[17:05] <dholbach> I'll add research
[17:05] <Daviey> yeah.. had the rug pulled out on us slightly there :(
[17:06] <dholbach> next: bug 597592
[17:06]  * mhall119 blames statik 
[17:06] <Ddorda> what's the bug # for the problem of changing language for the interface?
[17:06] <mhall119> importing data is going to require a lot of spec-ing
[17:06] <YoBoY> Ddorda: 570638
[17:06] <Ddorda> rww: btw, i've subscribed you to the bug, as you asked
[17:06] <rww> Ddorda: thanks
[17:06] <Ddorda> YoBoY: thanks
[17:07] <dholbach> mhall119: I'll mark it wishlist for now
[17:07] <mhall119> tag it as research too
[17:07] <mongolito404> mhall119: Whay a lot of spec ?
[17:07] <dholbach> and events please
[17:07] <mongolito404> s/Whay/Why ?
[17:07] <dholbach> mongolito404: because when you import data it's always a security problem, etc.
[17:07] <dholbach> mongolito404: hard to get right
[17:08] <mhall119> mongolito404: automatically importing data opens us up to other concerns
[17:08] <mhall119> what he said
[17:08] <mongolito404> Importing from iCal should be pretty straigforward
[17:08] <mhall119> as long as it's a good feed
[17:08] <Daviey> Yeah, even LP for certain stuff review it before it's authorized
[17:09] <mhall119> though there are differences between ical's capabilities and LD's capabilities
[17:09] <Daviey> So it would need acking first, and tieing to a particular team
[17:09] <dholbach> next: bug 600161
[17:10] <ebel> oh, mine again
[17:10] <mhall119> Timezone is a known issue we've been avoiding, but I don't think displaying the date twice is all that bad
[17:10] <Daviey> cjohnston, We had a discusion about this when you first started with the project, didn't we?
[17:10] <dholbach> needs-decision, low prio
[17:10] <Daviey> wishlist
[17:10] <ebel> dates aren't localized either, i should file a bug...
[17:10] <dholbach> next: bug 601683
[17:10] <mhall119> ebel: yes, that's a known issue, we haven't figured out a good way of handling that
[17:11] <mhall119> why?
[17:11] <mhall119> oh right, France again
[17:11] <ebel> mhall119: accept lang http header (if it exists?)
[17:11] <mhall119> the idea of a local-community with a global footprint breaks a lot of our assumptions
[17:11] <dholbach> I think with bug 601947 we should close 601683
[17:11] <mhall119> ebel: lang header for timezone?
[17:12] <ebel> mhall119: oh I meant the date localization. Timezone data is in launchpad.
[17:12] <YoBoY> mhall119: yes France again ^^
[17:12] <mhall119> dholbach: they seem different to me
[17:13] <mhall119> 601683 is because ubuntu-fr is something the France loco, and sometimes the Francophone loco
[17:13] <dholbach> I think it addresses the main concern from a user perspective (which is the only thing I care about): that you can easily find teams of your country and events in your language :)
[17:13] <mhall119> though, again, "francophone local community" is an oxymoron to me
[17:13] <dholbach> mhall119: agreed
[17:13] <dholbach> I'm happy to bump the language bug up to high and make sure we spec out language / online events for maverick+1
[17:13] <Daviey> Well Chrome(ium) supports "requesting location", if that fails we could drop back to geoip :)
[17:14] <dholbach> and won't fix the other bug
[17:14] <YoBoY> not only, the bug 602438 is another effect of this mandatory choice, i can't choose realy France if i have to ignore the overseas french department
[17:14] <dholbach> let's talk about that in a bit
[17:14] <YoBoY> ok, it's the bot :p
[17:15] <dholbach> I'd really like us to focus on the user and how they find stuff
[17:15] <mhall119> I think we need the LC's input on how to treat ubuntu-fr
[17:15] <mhall119> dholbach: +1
[17:15] <mhall119> I'm okay to closes 601683 if it was mainly about listing location
[17:15] <dholbach> I'll take bug 601947 and bump that to high
[17:16] <dholbach> and make sure we make use of it in maverick+1
[17:16] <dholbach> with that I think a lot of other "problems" can be dropped to low prio
[17:16] <mhall119> ok
[17:16] <Ddorda> looks like an Important feature
[17:16] <YoBoY> mhall119: you can close it, it was opened more to port this problem to your attention
[17:16] <Ddorda> IMHO anyway
[17:17] <dholbach> ok, so what about 601683?
[17:17] <mhall119> close it
[17:17] <dholbach> ok, thanks
[17:17] <Ddorda> never been in such a long session, trying to keep an eye on what's going on
[17:17] <dholbach> next: bug 601944
[17:18] <dholbach> Ddorda: we#re almost done
[17:18] <mhall119> the screenshot doesn't look bad to me
[17:18] <dholbach> ok, I'll add "teams ui", not sure what the problem is though :)
[17:18] <mhall119> YoBoY: how would you want that displayed?
[17:19] <YoBoY> open a team page : http://loco.ubuntu.com/teams/ubuntu-fr if you don't see a difference... ;)
[17:19] <mhall119> I just see "France" ;)
[17:20] <YoBoY> the labels are no more on one line
[17:20] <dholbach> yeah, one line is too much then
[17:20]  * mhall119 is still confused
[17:20] <dholbach> it could be more tight, with less space between the lines of listed countries
[17:20] <dholbach> but that's all I see
[17:20] <mhall119> oh, ok, I get it now
[17:20] <dholbach> ok, please add that info to the bug
[17:21] <mhall119> I thought that was just a chrome vs. firefox difference in the screenshot
[17:21] <dholbach> next: bug 602438
[17:21] <mhall119> sounds like a matter for the UN
[17:21] <Ddorda> like what?
[17:21] <Ddorda> Russia?
[17:21] <mhall119> France again
[17:21] <dholbach> Ddorda: countries with more than one continent is a problem already solved
[17:21] <YoBoY> lol
[17:22] <Ddorda> YoBoY: you're our problem! :D
[17:22] <YoBoY> sorry ^^
[17:22] <rww> perhaps there should be a 'france' tag ;P
[17:22] <mhall119> dholbach: Russia team currently lists a dozen neighboring countries as part of it's team
[17:22] <mhall119> rww: +1
[17:22] <Ddorda> YoBoY: i'll accept that after i'll finish with your script for the CDs
[17:22] <Ddorda> takes me too much time :S
[17:23] <YoBoY> :p
[17:23] <dholbach> ok, what is this bug about
[17:23] <dholbach> that we should have a different or additional data source for our "countries"?
[17:23] <YoBoY> it's about some countries have different territories around the world, in the country list this appear like countries if they have an iso code
[17:24] <mhall119> I'm not sure, we already allow multiple countries
[17:24] <dholbach> there must be an official list of countries, like something that everybody else (amazon, ebay, etc.) use
[17:24] <YoBoY> i already pointed in the bug report a data source who fix this
[17:24] <dholbach> YoBoY: how much entries does this give us?
[17:25] <YoBoY> don't understand
[17:25] <dholbach> you suggest that we use a new list for our list of countries
[17:25] <dholbach> or list "territories" instead of countries
[17:25] <dholbach> how much more entries would that be?
[17:26] <mhall119> dholbach: I think currently those "territories" of France are listed as separate "countries" in LD
[17:26] <YoBoY> no list countries, but real countries, actually your listing is based on iso_3166.xml and it's shoud be based on iso_3166_2
[17:26] <Ddorda> mhall119: you can do something like "france: territory #1"
[17:27] <mhall119> YoBoY: not necessarily, if a territory is geographically displaced, it might have it's own LoCo team
[17:27] <Ddorda> YoBoY: sorry for numbering you, i just don;t know the nmames :P
[17:27] <dholbach> ok, I'll mark it research and triaged for now
[17:27] <dholbach> I realise that right now some people might fall through the cracks and that's something we should fix
[17:27] <YoBoY> mhall119: yes should be great also to have teams on this overseas departement
[17:28] <dholbach> BUT: I wouldn't like everybody to have to go through a list of every island or borrough in the world
[17:28] <YoBoY> but it's not the case ^^
[17:28] <dholbach> so, research
[17:28] <dholbach> next: bug 603188
[17:28] <mhall119> YoBoY: could you detail an implementation on that?
[17:28] <mhall119> in the bug comments
[17:28] <mhall119> the whole point of having venue records was so they could be kept and reused if desired
[17:29] <YoBoY> hum... i can try
[17:29] <dholbach> I'll mark it needs-decision and wishlist for now
[17:29] <dholbach> next: bug 603189
[17:29] <Ddorda> yo that's mine :P
[17:29] <mhall119> maybe just add an option to delete venues?
[17:29] <mhall119> 603189 bitesize ui
[17:30] <mhall119> Ddorda can implement it
[17:30] <dholbach> :)
[17:30] <dholbach> next: bug 603223
[17:30] <dholbach> Medium, ui teams bitesize
[17:30] <mhall119> agreed
[17:31] <dholbach> and with that we're done
[17:31] <Daviey> \o/
[17:31] <dholbach> 2,5h of loco-directory action
[17:31] <mhall119> but a very very productive 2.5 hours
[17:31] <Daviey> crieky o'reily
[17:31] <dholbach> thanks so much everybody - this will give us all a lot of food for thought
[17:31] <rww> I'll grab 603223 as well, since I'm doing the other RSS thing
[17:31]  * dholbach hugs rww
[17:31] <dholbach> rww: you're awesome
[17:31] <mhall119> yes, thanks to everyone who participated
[17:31] <dholbach> thanks a lot everybody
[17:31] <Daviey> thanks gatekeeper
[17:31] <rww> dholbach: can you tell I found some free time recently ;)?
[17:32] <dholbach> join us in #ubuntu-locoteams, grab a bug you like, talk to us, we'll help you get started
[17:32] <dholbach> rww: it occurred to me :)
[17:32] <dholbach> #endmeeting
[17:32] <MootBot> Meeting finished at 11:32.
[17:32]  * dholbach hugs you all
[17:32] <dholbach> time to take the dog for a walk
[17:32] <dholbach> see you guys :)
[17:32] <Daviey> dholbach, o/
[17:32] <YoBoY> thanks dholbach :)
[22:27] <MichealH_> How long until the forum council meeting?
[22:28] <MichealH_> Is it in 30 mins?
[22:30] <jacob> heh heh, just happened to check my mail and saw that it was today
[22:31] <MichealH_> Good job I reminded you!
[22:31] <jacob> indeed :D
[22:31] <jacob> I believe it is 30 mins. 2200 UTC = 6pm EDT here
[22:32] <MichealH_> 22:00 =23:00 here :P
[22:32] <jacob> :o
[22:32] <MichealH_> heh...Daylight savings...
[22:42] <MichealH_> has just had problems with SSL :/
[22:52] <MichealH_> 7 mins everyone
[23:00] <MichealH_> It's time
[23:01] <MichealH_> http://ubuntuforums.org/member.php?u=883491
[23:01] <MichealH_> wron link
[23:01] <MichealH_> *wrong
[23:02] <MichealH_> https://wiki.ubuntu.com/ForumCouncilAgenda
[23:02] <jacob> might want to wait a few minutes, then we can start pinging people
[23:02] <MichealH_> Is anyone here?
[23:02] <dmizer> Yup.
[23:03] <dmizer> Meeting often starts a bit late.
[23:03] <MichealH_> \o/
[23:03] <MichealH_> Ahh... First time at these meetings ;)
[23:04]  * jacob wonders what became of the idea of having the meetings in a forum thread
[23:04] <MichealH_> Jacob: not in real time chat?
[23:05] <MichealH_> waits
[23:05] <jacob> MichealH_: the problem is that most of the time it's difficult to get everyone to show up at the same time (for anything on IRC, really). threads are easy to follow and easier to discuss
[23:06] <MichealH_> Ahhh yes so it is...
[23:06] <MichealH_> Is it usually this late?
[23:06]  * dmizer thinks that forum thread meetings would be nightmarish to chair.
[23:07] <jacob> dmizer: yeah, maybe so.
[23:07] <jacob> ping Technoviking
[23:08] <MichealH_> Jacob what about cariboo907
[23:08] <cariboo907> I'm not an admin
[23:08] <MichealH_> Ahhhh
[23:09] <MichealH_> So mods = NO
[23:09] <jacob> aye
[23:09] <MichealH_> Admins = YES
[23:10] <MichealH_> Is it always this late?
[23:10] <dmizer> heh ... have patience.
[23:10] <dmizer> ;)
[23:10] <jacob> MichealH_: the scheduled time? depends. when everyone gets here..... echo dmizer :P
[23:11] <MichealH_> has none
[23:11] <MichealH_> Mind you it did say subject to change....
[23:12] <MichealH_> It is 11PM here... trying not to fall asleep lol
[23:13] <cariboo907> it's only 15:12 here :)
[23:13] <dmizer> you got it easy ... i had to wake up 4 hours early.
[23:13] <MichealH_> And you usually wake up at...
[23:13] <dmizer> 4 hours later than this.
[23:13] <dmizer> ;)
[23:14] <MichealH_> 3 AM?
[23:14] <dmizer> i'm in japan.
[23:14] <MichealH_> calculates
[23:14] <jacob> /grin
[23:14] <MichealH_> ... It passes the time
[23:15] <MichealH_> although I would like it served with garlic ;)
[23:15] <MichealH_> heh
[23:16] <MichealH_> Do you think it's postponed for another hour?
[23:17] <jacob> we'd likely hear about it
[23:18] <MichealH_> So it's a no?
[23:18]  * dmizer waves the patience flag again ;)
[23:18] <jacob> I mean, it's possible, but unlikely
[23:18] <MichealH_> heh Patience is a virtue young grasshopper
[23:20] <jacob> MichealH_: if this turns out to be a no-show, you can always mail your ideas to the FC list on https://wiki.ubuntu.com/ForumCouncil (I _think_ that address is correct)
[23:21] <MichealH_> Okay
[23:36] <Technoviking> sorry was in my datacenter
[23:36] <dmizer> hey hey!
[23:40] <jpds> Technoviking: It has no connectivity?
[23:41] <Technoviking> jpds: it does, but I was working
[23:42] <Technoviking> I miss that the meeting moved to this week
[23:49] <dmizer> Technoviking: it appears that you were not alone ;)
[23:53] <MichealH> Still no showup?
[23:54] <dmizer> nothing happening yet.
[23:55] <MichealH> Hmmmm...
[23:55] <dmizer> hey bodhi!
[23:57] <bodhi_zazen> 'lo dmizer , how goes ?
[23:57] <dmizer> not bad. still rubbing the sleep out of my eyes ... heh.
[23:58] <MichealH> Are we starting soon?
[23:59] <bodhi_zazen> starting what ? Do we have enough people ?
[23:59] <dmizer> don't think so. only you and Technoviking here atm.
[23:59] <MichealH> I don't know but it is midnight here!