| trinikrono1 | i agree with you AlanBell i have also wondered why it would redirect there | 00:21 |
|---|---|---|
| elky | AlanBell, should be checking by referrer at minimum, you'd think | 00:32 |
| bkerensa | Any council members stirring? | 02:47 |
| paultag | hey bkerensa | 02:47 |
| bkerensa | Hey paultag can I PM | 02:47 |
| bkerensa | or better yet can you join #ubuntu-or-us | 02:48 |
| bkerensa | #ubuntu-us-or even :) | 02:48 |
| paultag | sure | 02:50 |
| Neo31 | Hello, are there some ubuntu packagers here? I may need some assistance to make the first packaging participation in UGJ for my loco team. | 06:50 |
| AlanBell | Neo31: perhaps try #ubuntu-motu | 07:17 |
| elky | he did. | 07:17 |
| AlanBell | jolly good | 07:18 |
| Neo31 | I already got there AlanBell :) thanks | 07:18 |
| czajkowski | AlanBell: opinion on what ? | 07:47 |
| AlanBell | in the loco directory if you are on an event such as http://loco.ubuntu.com/events/ubuntu-ie/1211/detail/ is the "Back to Events List" first subnav option ever useful? | 07:49 |
| czajkowski | me sits up and tries to focus | 07:49 |
| AlanBell | because it does exactly the same as the top nav option a few pixels above | 07:50 |
| AlanBell | I am thinking of changing it to *always* go back to the team | 07:50 |
| AlanBell | so to http://loco.ubuntu.com/teams/ubuntu-ie | 07:50 |
| czajkowski | no I like it namely if I tweet that link url | 07:50 |
| czajkowski | the going back button brings em to a list of events tis kinda nice | 07:50 |
| czajkowski | but thats me | 07:51 |
| AlanBell | but it does the same as the big events button at the very top | 07:58 |
| AlanBell | so for me if I saw a tweet about something in a hackerspace in Galway I might think, OK, can't make that, click Back and see stuff in Venezuela and have no easy way to get back to the -ie page and see there is an event in Dublin and Limerick which I might be able to get to | 08:00 |
| AlanBell | and if I start here http://loco.ubuntu.com/teams/ubuntu-ie and want to read about all the events it is too hard to get back to the team page | 08:02 |
| AlanBell | the link *is* there, but burried 3/4 of the way down the details | 08:02 |
| AlanBell | and the thing in the top that starts with "Back . . ." takes me to the bewildering global list and I have to hunt through it to find my way back to the team I want | 08:03 |
| AlanBell | "Back to Teams List" on a team object makes perfect sense | 08:04 |
| AlanBell | but on an Event or Meeting I find it highly improbable that the user came from the global list, or if they did, that the global list is where they want to go back to | 08:05 |
| AlanBell | I am not just complaining about it, I am proposing that I fix it, but I am asking first to see if anyone disagrees with the change | 08:06 |
| nigelb | AlanBell++ | 08:08 |
| nigelb | AlanBell: I agree. For a majority of the use cases, this fits. | 08:09 |
| AlanBell | I think my primary frustration with the LoCo directory is that I am constantly accidentally escaping from the microsite for the team | 08:09 |
| AlanBell | are there any events with a large number of organising teams? | 08:16 |
| AlanBell | I don't mean the global event object, real events | 08:17 |
| nigelb | I don't think we have that use case yet. | 08:17 |
| AlanBell | yeah, I don't think you can do it in the UI | 08:17 |
| AlanBell | fine, I will code it as a loop so it would support two teams organising an event if one day that can be done, if a large number of teams organise one event it will run out of button space | 08:19 |
| AlanBell | but that can't happen | 08:19 |
| AlanBell | code done, will test and merge request later | 08:22 |
| czajkowski | AlanBell: coolio :) | 08:22 |
| AlanBell | I should just do the merge request and get it live really http://tinyurl.com/whenitest | 08:25 |
| AlanBell | bug 802508 | 08:47 |
| === Quintasan_ is now known as Quintasan | ||
| mhall119 | AlanBell: we've only had one event with multiple teams as a test, we don't have a UI to do it yet | 11:46 |
| AlanBell | cool, if I can get loco directory to actually run I will test and merge | 11:51 |
| AlanBell | ImportError: No module named django.core.management | 11:51 |
| AlanBell | not sure how to install what it wants to do a "make live" and import the test data | 11:52 |
| mhall119 | did you run make init? | 11:53 |
| AlanBell | same error | 11:55 |
| AlanBell | did sudo make depends | 11:56 |
| mhall119 | do make clean, then make init again | 11:59 |
| mhall119 | what version of Ubuntu are you using? | 11:59 |
| AlanBell | 11.04 | 12:00 |
| AlanBell | No distributions at all found for python-feedparser (from -r requirements.txt (line 21)) | 12:02 |
| AlanBell | but I have python-feedparser | 12:02 |
| mhall119 | in pip, it's just "feedparser" | 12:02 |
| mhall119 | take the python- out of that line in requirements.txt, then make clean; make init again | 12:02 |
| nigelb | Was the make file a bad idea? | 12:02 |
| mhall119 | no :P | 12:02 |
| nigelb | I think its complicated things for people who do help us. | 12:03 |
| nigelb | (personally) | 12:03 |
| AlanBell | hmm, I have python-feedparser from the repos, so now I have that and something else somewhere | 12:04 |
| AlanBell | so these tar.gz things it is downloading from somewhere, it is just putting them in this source tree right? | 12:05 |
| mhall119 | AlanBell: it gives a clean separation, so your loco-directory development requirements don't force the rest of your system to have things installed | 12:05 |
| mhall119 | AlanBell: it's putting them in the 'env' directory | 12:06 |
| AlanBell | ok, so not screwing up my system altogether then :) | 12:06 |
| nigelb | We're trying to make sure it doesn't screw up your system :P | 12:06 |
| mhall119 | no, it creates a separated python environment | 12:06 |
| mhall119 | make depends is the only one with system-wide impact | 12:06 |
| AlanBell | ok, that is fine. Mixing packaged python and pip egg stuff scares me | 12:07 |
| AlanBell | the easy_install stuff looks like a recipe for pain | 12:08 |
| AlanBell | this is now doing promising looking stuff | 12:09 |
| AlanBell | so that requirements.txt thing was a bug right/ | 12:09 |
| nigelb | yeah, it was | 12:09 |
| nigelb | please propose an MP | 12:09 |
| AlanBell | um, I can fold it into the MP I am doing | 12:10 |
| AlanBell | really wish I hadn't gone for the live option | 13:04 |
| mhall119 | it's slow, yeah | 13:13 |
| AlanBell | https://code.launchpad.net/~alanbell/loco-directory/backbutton/+merge/73526 | 13:25 |
| nigelb | AlanBell: would you mind writing tests? :) | 13:27 |
| AlanBell | how? | 13:27 |
| nigelb | There should already be a few tests in the test folder . | 13:27 |
| nigelb | mhall119 is the expert to ask in case you're stuck. | 13:28 |
| AlanBell | I can't see a test folder and I don't really understand what structured test could be done | 13:30 |
| AlanBell | you run it, open an event or meeting and observe that the nav no longer contains a pointless back to global list option and contains a back to team option | 13:32 |
| nigelb | AlanBell: YOu could do this | 13:32 |
| nigelb | create a team | 13:32 |
| nigelb | create an event | 13:32 |
| nigelb | go to the event page | 13:33 |
| nigelb | make sure the back is pointing to the team's page | 13:33 |
| AlanBell | hmm, I see events/tests.py but I don't understand how to use it | 13:35 |
| mhall119 | AlanBell: each django app directory can have a tests.py | 13:53 |
| mhall119 | there should already be some in /teams/ | 13:53 |
| AlanBell | there is a tests.py there | 13:53 |
| AlanBell | but I don't know what to assert | 13:54 |
| mhall119 | I did a class on this a while back, I'll see if I can find the logs | 13:54 |
| mhall119 | nigelb: do you remember what day that was? | 13:54 |
| nigelb | mhall119: No, I can check though | 13:55 |
| AlanBell | so does everything need a test now? | 13:56 |
| mhall119 | it's preferred | 13:56 |
| * AlanBell sees a two line patch turning into a big old test | 13:56 | |
| nigelb | yes | 13:56 |
| AlanBell | what runs the tests? some firefox plugin? | 13:57 |
| mhall119 | AlanBell: ideally we would have already had a test case for that link, and you'd just have to update it, but we don't, so one has to be made | 13:57 |
| nigelb | AlanBell: ./manage.py test | 13:57 |
| mhall119 | no, just django's built-in test runner | 13:57 |
| AlanBell | I don't think I can write a test for it based on the tests that are already there | 14:01 |
| AlanBell | even if I managed to get the test to create a team and an event and a meeting | 14:02 |
| AlanBell | if I did assertContains(response, "test team") that would be meaningless as it is on the page anyway | 14:03 |
| AlanBell | it would need some kind of xpath statement to assert the link was in the right place, had the right target and name | 14:03 |
| nigelb | AlanBell: You need to assert the full <a href=...> | 14:03 |
| nigelb | or we could use pyquery | 14:04 |
| AlanBell | I certainly can't make a test for the requirements.txt change | 14:09 |
| mhall119 | no, but for the Back link you can | 14:10 |
| mhall119 | if you want to make the requirements.txt change a separate MP, I'll approve it right away | 14:10 |
| AlanBell | I don't know how | 14:11 |
| mhall119 | how to do which? | 14:11 |
| AlanBell | I am not making a separate whole instance of loco directory just to split out a one line patch | 14:11 |
| nigelb | You don't have to | 14:11 |
| mhall119 | you shouldn't need to do that | 14:11 |
| nigelb | Just commit one change, propose a merge | 14:11 |
| nigelb | Also, you should have branches setup. | 14:12 |
| mhall119 | nigelb: would you like to write up a doc for doing an init-repo, branch and lightweight checkout specifically for loco-directory? I think that would help | 14:12 |
| AlanBell | so do I have to roll back to the start and do them as two commits? | 14:12 |
| AlanBell | I have three copies of loco directory already | 14:13 |
| AlanBell | I tried bzr pull in one of the others but that didn't work so I branched a new one | 14:14 |
| nigelb | I think I need to give clear documentation on using branches | 14:15 |
| nigelb | and how to use co-located branches in bzr so that you can share envs | 14:15 |
| mhall119 | AlanBell: this is the workflow most of us use now for loco-directory, summit, etc: http://micknelson.wordpress.com/2011/05/19/sharing-your-development-environment-across-branches/ | 14:21 |
| AlanBell | ok | 14:24 |
| nigelb | I use something slightly different, but probably slightly harder as well. | 14:25 |
| === kinoucho` is now known as kinouchou | ||
| === jpds_ is now known as jpds | ||
| Ronnie | jono: do you have time to answer some question about the trademark name Ubuntu | 19:53 |
| paultag | Ronnie: 99.999% of inqueries come down to: "Is it about or exactly pertaining to Ubuntu?". If the answer is "Yes", in general, it's OK. LoCos are included in that official stuff | 19:58 |
| paultag | common sense seems to be right right(tm) thing | 19:58 |
| bkerensa | paultag: unless its a domain name right? | 20:01 |
| Ronnie | paultag: a while ago Michelle Surtees-Myers send me this message: """We want to support you in establishing your foundation, however, a special license is required for this, and we are currently working on this. We will need to have some further discussions in this regard. If you need any more information, please contact our Community Manager, Jono Bacon (cc'd here).""" | 20:03 |
| Ronnie | were almost at the point of officially creating the foundation, and therefore we want to know if its 'safe' to use that 'Ubuntu' in the name of the foundation | 20:04 |
| jono | Ronnie, is this the NL thing? | 20:04 |
| Ronnie | jono: yes | 20:04 |
| jono | Ronnie, I thought Michelle followed back up | 20:05 |
| jono | let me check into it and see what is going on | 20:05 |
| paultag | bkerensa: domain names are fine | 20:33 |
| paultag | bkerensa: providing it's the loco it's self | 20:33 |
| paultag | there's a bit more then that, but that's basically it | 20:33 |
| paultag | brb | 20:33 |
| AlanBell | Ronnie: you are creating a legal entity for the LoCo? | 20:53 |
| AlanBell | well seeing as ./manage.py test returns errors already I am not sure adding my tests to it is a good idea http://paste.ubuntu.com/679228/ | 21:17 |
| cjohnston | AlanBell: ya.. the tests need to be updated if you are talking about LD | 21:20 |
| bkerensa | paultag: How do certain commercial blogs get to use the ubuntu name in their domain like OMG Ubuntu? I couldnt figure out that one | 21:37 |
| AlanBell | bkerensa: they ask for permission | 21:38 |
| AlanBell | sometimes retrospectively | 21:38 |
| AlanBell | have a look in the bottom right of their footer | 21:38 |
| AlanBell | http://www.ubuntu.com/aboutus/trademarkpolicy | 21:39 |
| bkerensa | ok... well I was gonna do a Ubuntu/FOSS podcast personally but I decided to not use the Ubuntu name and used a Linux varient domain name because I didnt wanna deal with TM issues | 21:39 |
| AlanBell | really not a big deal | 21:40 |
| AlanBell | if you are doing community advocacy of any kind the answer will be yes | 21:41 |
| JanC | OTOH, using a more general name makes it easier to stray from the pure Ubuntu stuff in that podcast... ;) | 21:41 |
| AlanBell | and there is a whole class of things where you don't need to ask permission | 21:42 |
| AlanBell | yup, plenty of reasons to build your own brand identity | 21:42 |
| Ronnie | AlanBell: yes we are creating a legal entity (and yes we are aware of the concequences of being a legal entity in our country) | 21:58 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!