[00:19] cjohnston: how about my teams list speed improvements? [00:19] its already approved [00:19] just waiting on nigels bot [00:19] you didnt put in a commit message so its been sitting there all day [00:19] stupid NameField! [00:19] btw [00:20] yes, NameField sucks [00:20] btw, cranberry has South 0.7 [00:20] it does? [00:20] when did that happen [00:21] dunno, dholbach told me [00:21] hmm [00:21] 0.7.3 [00:21] so use manage.py schemamigration [00:22] I think there's code in there so that NameField will work without you having to do anything when you use 0.7 [00:22] i think thats what it is [00:22] and it blows [00:22] what blows? [00:22] namefield [00:24] like I said, it should "just work" with south 0.7 [00:24] mhall119: http://paste.ubuntu.com/642270/ [00:25] http://paste.ubuntu.com/642272/ [00:26] pastebin the actual migration script [00:26] why is it getting rid of the participants table? [00:27] http://paste.ubuntu.com/642273/ [00:27] i dunno [00:28] might be my fault [00:28] give me a couple [00:29] ok [00:40] mhall119: https://code.launchpad.net/~chrisjohnston/summit/tracklead [00:40] thats what is deleting [00:44] any thoughts mhall119 ? [00:53] one second [00:55] cjohnston: I have no idea what's causing the deletion [00:55] do you get that when you use South 0.6? [00:56] btw, I pushed a new version of my LD venues fix to add test cases [01:17] mhall119: when running 0.6 I get the NameField error [01:19] :( [01:19] did you try it? [01:19] I wonder if something wasnt properly migrated in the past [01:20] or if updaitng django f'ed it up [01:23] I have a whole bunch of MPs that need review [02:32] later, I'm tired and heading to bed [02:32] good night mhall119 [02:32] good morning nigelb [02:32] * nigelb is now 23 [02:33] nigelb, Happy birthday [02:33] jledbetter: Hey! THank you :) [02:35] nigelb: if you make it over tonight, I've got some scotch with your name on it [02:35] paultag: hah. There's always fedex :D [02:36] nigelb: well that's no fun unless we can share the toast [02:36] nigelb: Happy Birthday [02:36] paultag: Good Point! [02:36] paultag: he meant he can fedex himself [02:36] mhall119: Thanks :) [02:36] hahaha [02:36] mhall119: hahahaha [02:36] truth [02:36] dude today was ubuntu kung-fu loco day [02:37] I just kicked so much ass [02:37] safer than crossing the street [02:37] mhall119: my crushed belongings beg to differ [02:37] have you seen how they drive? [02:37] mhall119: fedex is a hazard to all mankind, we can all sleep at night knowing no human are handled by them [02:38] haha, its Tara's birthday too (Novacut) [02:38] * mhall119 can think of a few I'd like to ship without insurance [02:39] lol [02:39] mhall119: so, I've not pushed a single line of fixes against syn [02:39] I'm so bummed at this code I don't even want to touch it [02:39] paultag: If your friends didn't recognize Klingon, you shouldn't be friends with them any more :P [02:40] nigelb: dude, those were both ubunfriends [02:40] nigelb: I am shoked [02:40] shocked, better yet [02:40] heh === czajkows1i is now known as czajkowski === daker_ is now known as daker [12:33] paultag: make 2.0 a complete re-write in python [13:08] mhall119, can pls test this https://code.launchpad.net/~daker/loco-directory/fix.707614/+merge/65124 === yaili_ is now known as yaili [13:09] cjohnston's output is odd [13:35] daker: later I will [13:35] ok tyt === yaili_ is now known as yaili === daker is now known as daker_ [18:41] ping mhall119 [19:08] ronnie1: sorting events by approved teams? [19:08] cjohnston: yes (still keep the region sorting too) [19:08] cjohnston, i think like putting all approved teams first then the unapproved later under them [19:08] I disagree [19:08] coalwater: yes [19:08] I don't think we should segregate like that [19:09] cjohnston: why not? [19:09] I think the logo is good enough [19:09] I think it would be discouraging [19:11] cjohnston, i think the top box looks better, do u ? [19:12] * cjohnston goes to look [19:12] even easier to notice without scrolling all the way down [19:14] I don't like it being "attached" to the subnav.. i'm thinking it probably wouldnt be following the design guidelines either [19:14] ok, so u want it floating like the about page ? [19:15] thats my opinion, yes [19:15] do u have a design guidelines page? [19:15] Just my two cents. we need to look at our goals of loco directory. [19:15] Its about trying to make loco teams more accessible to new comers [19:16] If we seggregate, it makes that harder. [19:16] coalwater: design.ubuntu.com [19:16] design.canonical.com [19:16] sorry [19:16] If of course makes it easy to know which team is approved and which team is not, but that's not why loco directory was built. [19:16] +1 [19:16] s/was/is [19:19] i don't mind them being sorted or not, it's just i got little confused when i opened the teams list for the first time, had to ask on the irc here to understand why some loco teams are grayed and some are not [19:19] thats the point of the bug your working on coalwater [19:19] I believe you were working on a legend or footnote for that. Isn't there already a mouseover? [19:19] there is a mouseover [19:19] there is, but its not easly noticeable [19:19] easily [19:20] i think we might find a neat way we might also add a link on the guide of how to get ur team accepted [19:20] Would making it linkable and poping out a fancybox help make it easier? [19:20] s/fancybox/lightbox [19:21] if i were to click the image next to the team, i would expect it to go to the team [19:23] so http://dl.dropbox.com/u/14224314/Screenshot-1.png on the top ? [19:24] the size of -2 tho [19:24] -2 what [19:24] o ok [19:24] lol [19:24] got it [19:24] small and thin ? [19:24] si [19:25] i need to read more of python and django to be more helpful on the coding side, than just some templates :D [19:26] do all websites projects use python/django [19:26] not all.. [19:26] theres wordpress and drupal too [19:26] but most of what we do is django [19:28] is jledbetter around here often ? [19:28] haven't seen her in a while [19:29] she's usually busy i suppose [19:30] i might get her to help me with jdango [19:30] django* [19:30] Yeah, very busy, coalwater. You could try those classes I mentioned to you before. [19:31] coalwater, And a django one now: http://p2pu.org/en/groups/introduction-to-django/ [19:31] cjohnston, nigel: if you wont want to destinguish between approved and "yet to be approved" (sounds more positive than "not approved"), why use different icons? [19:31] how else would you want to differentiate [19:32] there needs to be something [19:32] propose better wording if you like [19:32] but they are approved and not approved.. yet to be approved doesnt suit a team that lost their approval [19:32] so then yet to be approved again? [19:32] cjohnston: true [19:33] ronnie1: I don't want to primarily just mention that. [19:34] If it can be mentioned, good with me. That's all [19:34] what i dont understand is that you do not want to sort them by approval, but still want to show approved/unapproved on the list page [19:34] I like it the way it is [19:34] others want it to be more clear [19:34] but seperating them makes them even more different than just a logo [19:35] i suggest using all the same icons (no differentiate between approved/unapproved) or sort by approved [19:35] as the bug describes, the logo's are confsing [19:35] thats why we are defining what the logos mean [19:35] when you understand the logo's you can differentiate between approved/unapproved very easily [19:36] i can mark it wont fix if you wish [19:36] i agre [19:36] agree [19:36] thats why i dont think anything more is needed [19:36] (than defining the logos) [19:36] which is already done [19:36] btw [19:37] whats the use of displaying the approved/unapproved in this list actually? [19:37] there arent any other lists [19:37] transparency [19:39] stupid question : why there should be a different display depending of this status of approved / not approved ? These teams are accepted to the "locoteams" group by an administrator. Yes we have to show users the team is or is not approved, but this information is for me only usefull on the team detail page. Opinions ? [19:40] YoBoY: only on the detail page is good for me. but maybe czajkowski want to have an overview of approved/unapproved teams [19:40] this overview exist on Launchpad no ? [19:40] the 'problem' i have with the current solution, is that the differentiating logo's are cluttering the nice clean design/view of the site [19:41] I'll pose this question then.. Why not? It is MORE work for us to change it. YoBoY your very own team doesnt use LP much.. we are trying to make LD a one stop shop for all needed info. [19:41] ronnie1: then leave it the way it is.. if they want to know what the logo means, mouseover it [19:43] cjohnston: and yes you are right, why not. I only think a user don't really search for that type of information in the first place. he search for events, support, users... and don't really care of the approved status of the eventual team he could find localy. [19:44] The LC can use it to quickly find out information [19:44] instead of having to click on the teams [19:44] cjohnston: with the 'current situation' i mean the current live version, without the bugfix. [19:44] ronnie1: how is it cluttering anything.. there is a logo (or bullet point) for each team [19:44] cjohnston: for the LC we can think of other solutions. normal users do not have to differentiate in my opinion [19:45] why make more work [19:45] and why duplicate efforts [19:45] there is already a team list, why make another [19:46] it was just a question, I also think it's great to be able to see how many teams are grown enought to be approved teams :) [19:46] so there is another reason for having it [19:47] because users an LC have different interests. Its not that 'it has to be the way i want', but i think it just looks better and raises less questions. I agree there are bugs that need more attention now [19:47] +1 [19:47] but the current design does not hinder the user [19:47] other than being curious [19:47] it's just an eyecandy bug for now [19:47] and if they are curious enough, they will figure out what it means [19:47] and then they know [19:48] and then they can look just like the lc and quickly see who is and isnt approved [19:48] seeing growth is not as easy if they are not sorted. I suggest coalwater makes the fix and we merge it. we maybe have a look later to improve it [19:48] im fine with that.. i disagree with sorting [21:14] mhall119, cjohnston where are you with the django package upgrade ? [21:16] django 1.1.1 sucks :/ [21:43] cjohnston, daker, coalwater: i just worked a bit on the event detail page. i redesigned the "attending" block. Feedback is welcome [21:43] http://img69.imageshack.us/img69/3192/event1z.png [21:44] http://img40.imageshack.us/img40/4746/event2pl.png [21:44] http://img580.imageshack.us/img580/7658/event3.png [21:45] imageshack doesn't work for me :/ [21:45] hmm, ill do ubuone then, moment [21:45] http://ubuntuone.com/p/14B7/ [21:46] http://ubuntuone.com/p/14B6/ [21:46] http://ubuntuone.com/p/14B3/ [21:47] nice!! [21:53] cairo :o [21:53] ronnie1, sorry what's the original links :D [21:54] coalwater: current live version: http://loco.ubuntu.com/events/egyptlocoteam/1055/detail/ [21:54] funny thing im egyptian but for some reason i don't believe in our loco team [21:58] oh the pyramid people :P [21:58] i like how compact it is [21:58] found a friend on the list lol [21:58] :D [22:00] coalwater: nice to see new fresh loco-directory developers :) [22:01] u mean me ? lol i still need much to be called a loco directory developer [22:02] any help is welcome, even small steps [22:04] im not as active anymore as i used to be. I want to do more, but have limited time :( [22:04] ronnie1, the label at the bottom right is too small [22:05] daker: which screenshot? [22:05] what label? [22:06] the lp username on the comments list [22:06] bottom left u mean [22:07] daker, thats a part of the screenshot i didnt change yet. also the irc channel is too small [22:07] ill work on that another time [22:07] i was just reporting it :) [22:08] daker: great! we have a buglist for these things ;) [22:08] ok [22:09] coalwater: that small label issue is maybe a great bug to start, coalwater [22:09] its only css/templates [22:10] report it and give me a link to bookmark [22:10] im working on this one right now, when i finish it i could switch to it [22:10] https://bugs.launchpad.net/loco-directory/+bug/783544 [22:10] Launchpad bug 783544 in loco-directory "Teams listing's small logos aren't informative enough (affects: 1) (heat: 5)" [Low,Confirmed] [22:11] i am going to report it [22:14] i want to get membership to lp's loco-dir-dev team :( lol [22:14] cjohnston, ask mhall119 or cjohnston [22:14] i mean coalwater [22:15] coalwater, bug 809597 [22:15] Launchpad bug 809597 in loco-directory "The lp username on the event's comment is too small (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/809597 [22:15] ok [22:16] what's your lp username ? [22:16] coalwater, [22:17] cjohnston: coalwater, i'm against segregating teams by approval status [22:17] daker, same name [22:18] done. [22:18] thanks [22:19] yw [22:26] sry was eating and trying to keep my keyboard clean [22:27] mhall119, excuse my poor english, but what does segregate mean [22:29] coalwater: separating them [22:30] hm well i wasn't gonna do any kind of sorting, that's up to u, im just working on the tiny ui change [22:31] we can attempt some basic sorting by country name [22:32] unfortunately the lack of standard naming convention means we can't sort by name [22:33] mhall119: on that note, I have no idea how hard it would be but just throwing the idea out there, there is already "State/Province/Region" and "City" fields in the team details, would it be difficult to add a "Country" so then you have all the data you need to sort with? [22:34] Hold on, there is already a countries list. [22:34] city without country? that's a bit weird [22:34] head_victim: we already have a field for country [22:34] Is there a way of sorting with that field? [22:35] Try to manufacture a "standard" naming using the edited fields for use purely to list teams. [22:35] I'm not sure on sorting, it's a many-to-many field [22:36] a team can have multiple countries [22:37] It does seem to get a bit more complex everytime I hear more about how varied the teams are. [22:37] yeah [22:39] are the countries entered by a text box ? or do we have auto complete/ drop down menu ? [22:39] o wait, a team has many countries? [22:39] It's a scrollable list [22:40] i think ill stick with css bugs untill i study the system more, instead of asking silly questions lol