[05:10] mornin [06:47] good morning [06:48] someone can ping me before the classroom on the LD today ? :p [07:44] good morning [10:55] what time is the classroom session today? [10:58] trinikrono, via #ubuntu-classroom==>set topic: the fridge [10:58] i'll take a look [10:58] for example its 7am for me [10:58] Upcoming Schedule: http://is.gd/8rtIi [11:04] trinikrono, is your question answered? [11:04] is the schecule in utc? [11:05] wo 2. mrt 16:00 – 17:00 GMT [11:05] first class [11:06] leoquant: gmt and utc is the same? [11:07] sorry telephone).... [11:07] ... [11:08] ok i think i have it now [11:08] it would be 11am-12pm for me [11:09] will just leave it to idle then thanks leoquant [12:20] Ronnie, dholbach mhall119 cjohnston nigelb http://isdjango1.3releasedyet.com/ [12:20] daker: lol [12:20] haha, neat website [12:21] in 1.3 are coming a few very nice features :D [12:21] hahaha [12:21] also lol @ the url :D [12:22] like this one http://ismubarakstillpresident.com/ [12:50] daker: did you make that django one? [12:51] no, someone post it on #django-fr [12:51] ah [12:51] I'm not sure what's big about 1.3 besides class-based views [12:52] o/ [12:52] morning mhall119 [12:52] do you have time these next few days to do some summit reviews? [12:53] not today, unfortunately [12:54] nigelb: what are you doing April 1st? [12:54] mhall119: nothing much I suppose, why? [12:54] http://loco.ubuntu.com/events/team/729/detail/ [12:54] UGJ? [12:54] cjohnston and I will be summit hacking [12:54] if you can participate remotely [12:55] YESSIR! [12:55] register on LD [12:55] cjohnston: you haven't registered on LD yet either [12:56] I've now registered :D [12:57] Only 2 hours? Pfffft :p [12:57] \o/ [12:57] nigelb: we both have kids who will be getting out of school [12:58] oh, right. 2 hours is a big thing. [12:58] Actually, we could skype up and jus talk instead of IRC [13:04] that can probably be arranged [13:04] \o/ [13:04] * nigelb does happy dance === daker_ is now known as daker [13:34] mornin === daker_ is now known as daker [13:53] morning cjohnston === daker_ is now known as daker [14:06] daker, :) [14:06] :) [14:54] morning cjohnston dholbach daker [15:33] hi mhall119 [15:36] https://wiki.ubuntu.com/UbuntuDeveloperWeek Day 3 starting in 25 minutes in #ubuntu-classroom [15:45] \o/ [16:53] haha LD session in a few minutes :) [16:54] good luck with that guys :) === ianto is now known as Guest70369 === Guest70369 is now known as ianto [17:33] Ronnie: I have an error on the manage.py init-ld >> django.db.utils.DatabaseError: no such table: auth_group [17:34] YoBoY: have you executed: ./manage.py syncdb [17:34] and ./manage.py migrate ? [17:34] ha nop :p [17:34] going too fast :D [17:36] great that's fine now [17:59] that is a lot to cover in an hour [18:00] yes [18:03] if only I had time to work on LD :'] === daker is now known as Ghost_of_daker [18:08] oh no, Ghost_of_daker ! ;0 [18:08] :D [18:08] è_é [18:11] mhall119: nice session.. :) ... [18:11] mhall119: but m stuckd somewhere :( [18:12] where aakshay__ ? [18:13] YoBoY: here [18:13] YoBoY: ./manage.py syncdb You will need to run ./manage.py init-ld to make the LoCo Team Directory fully work. You will need to run ./manage.py init-ld to make the LoCo Team Directory fully work. Error: No module named south [18:14] YoBoY: Error: No module named south [18:14] install python-django-south [18:14] make sure you install all the packages in the INSTALL file [18:15] aakshay__: read the INSTALL file you have a sudo apt-get install .... line in it [18:15] cjohnston: nopes.. :( ......let me check all the packages [18:15] cjohnston: thanks.... :) .. [18:15] YoBoY: thanks.. :) [18:15] aakshay__: what version of ubuntu are you running? [18:16] cjohnston: maverick lynx [18:17] cjohnston: 10.04 [18:17] that's lucid lynx [18:17] aakshay__: you have all of those packages installed? [18:17] cjohnston: in progress.. :) [18:17] ok [18:17] let me know when you finish [18:18] Ronnie: the links top-nav are relative to my install not absolute links (example : http://127.0.0.1:8000/teams/ubuntu-fr/wiki.ubuntu.com ) it's normal ? [18:19] YoBoY: thats sounds like a bug [18:19] cjohnston: yes... :) [18:19] Ronnie: LD or upstream ? ^^" [18:19] ill have a look [18:20] thanks [18:23] cjohnston: yippii... its working... [18:23] cjohnston: i run syncdb [18:23] its upstream, ill provide a patch [18:23] then migrate' [18:24] cjohnston: then what to do? [18:24] :) [18:25] Next you will run the migrate [18:25] Ronnie: great :) [18:25] you should be able to continue on as was taught in the classroom aakshay__ [18:26] cjohnston: yes. if i get stuck somewhere then will come back to ask .. :) [18:38] YoBoY: Fixed, mhall119 needs to approve it tough [18:39] great :) [18:39] and the "user" links to the left, this should be functionnal soon ? [18:40] there is a merge proposal for that one [18:40] so it mostly depends on cjohnston and mhall119 [18:49] cjohnston: done with settings.. now i want to start with bugs.. :) [18:51] good aakshay_ [18:52] cjohnston: thanks.. gud nite.. see ya [18:52] aakshay_: maybe this is a good bug to work on https://bugs.launchpad.net/loco-directory/+bug/608289 [18:52] Launchpad bug 608289 in loco-directory "Add continent field to venue (affects: 1)" [Low,Triaged] [18:52] Ronnie: ok.. let me start on it now itself [18:53] ubot4: ok.. let me start now itself [18:53] aakshay_: Error: I am only a bot, please don't think I'm intelligent :) [18:53] :) [18:53] ubot4: :) ... may be you are... :D [18:53] aakshay_: Error: I am only a bot, please don't think I'm intelligent :) [18:54] cjohnston: no gud nite.. sry...i am giving a try to fix bugs now.. :) [18:54] lol [18:54] cjohnston: :D [18:58] aakshay_: have you any experience with django? [18:58] Ronnie: no.. :( [18:59] Ronnie: where to start with it? [18:59] oke, if you have some questions about that bug, feel free to ask... [18:59] first you need to add an extra field to the venue model [18:59] which lives in venues/models.py [19:00] that field should be linked to the teams/models.py:Country model [19:00] Ronnie: ok.. [19:00] http://docs.djangoproject.com/en/dev/ref/models/fields/#django.db.models.ForeignKey [19:01] Ronnie: ok.. let me check [19:08] Ronnie: thanks for fixing the top-nav [19:08] LD's init-ld just grabs the latest trunk of ubuntu_website, I need to upgrade it to use bzr-apps so we can specify a version [19:09] mhall119: there is already a merge for the integration of top-nav, so fixing ubuntu_website is not needed atm [19:09] Ronnie: i think i need to learn django first because i dont know how to add an extra field to venue model.. :) [19:09] Ronnie: a merge in ubuntu_website or in LD? [19:09] LD [19:09] aakshay_: http://docs.djangoproject.com/en/dev/intro/tutorial01/ [19:09] that'll get you going on Django [19:10] Ronnie: who added top-nav to LD? [19:10] mhall119: thanks.. the session was very informative.. do i need to learn python as well? [19:10] the continent is almost a copy of the country field "country = models.ForeignKey(Country, null=True)" [19:10] aakshay_: yes, python is a must [19:11] but python is easy, especially if you have previous programming knowledge [19:11] mhall119: https://code.launchpad.net/~ronnie.vd.c/loco-directory/top-nav/+merge/51459 [19:11] mhall119: i am good at programming. so let me start learning python and django.. [19:12] Ronnie: ok.. let me try to edit [19:13] Ronnie: ah, using the stuff in ubuntu_website, awesome [19:13] you rock [19:13] mhall119: yes, there is also a part for the upcoming "my_teams" page [19:14] cool, how's that coming? [19:14] i needed to fix a few other bugs (see twidentica and rss branched) [19:15] the my teams page is almost ready, it need some small tweaks [19:56] Ronnie: i added in venues/models.py then its showing an error in database :(.... means v need to edit the other files as well. [19:56] aakshay_: you need to update the database by executing south, let me explain [19:57] go to the loco_directory folder (cd in terminal) and type (without quotes) "./manage.py schemamigration Venue" [19:57] ./manage.py schemamigration Venue --auto [19:58] Make sure you have the correct version of south === Ghost_of_daker is now known as angeldaker [20:01] this command tells south the make a migration file with the difference in the database structure [20:01] next we need to apply it on the database [20:02] ./manage.py migrate [20:11] aakshay_: did it work? [20:23] Ronnie: Sorry.. net was not working.. i am working with the above commands. [20:23] aakshay: take your time, its not a race competition ;) [20:24] Ronnie: :) ... [20:33] aakshay: how its going? [20:34] Ronnie: it is showing "Nothing ti Migrate" in all [20:34] *to [20:34] and with this command: ./manage.py schemamigration Venue --auto [20:35] i actually run this command only [20:35] should i try with the previous one? [20:35] oops, my bad, got some typo's [20:35] ./manage.py schemamigration venues --auto [20:36] Ronnie: :-).. okiez.. let me try [20:36] it should tell that a 0007 file has been created, if executed correctly [20:37] Ronnie: yipii.. worked... [20:37] Ronnie: " Migrating forwards to 0007_auto__add_field_venue_continent. > venues:0007_auto__add_field_venue_continent - Loading initial data for venues. " [20:37] oke great [20:37] now execute: ./manage.py migrate venues [20:37] Ronnie: ok.. yes [20:38] that should make changes to the database [20:38] Ronnie: it showed nothin to migrate [20:39] aakshay: hmm, thats strange [20:39] and the command: ./manage.py migrate [20:39] Ronnie: i think because i run this already with "./manage.py schemamigration venues --auto" [20:39] without venues [20:39] Ronnie: so no need to worry [20:40] Ronnie: i run this without "venues" [20:40] probably the same result [20:40] Ronnie: yes... ;-).. [20:40] Ronnie: what to do next? [20:40] oke, i guess its good [20:40] next we need to check forms.py [20:41] this file translates a model into a form [20:41] here you can exclude, include fields, do some validation and save the changes to the database [20:41] if the form is very standard, this file should be almost empty [20:42] Ronnie: "standard" refers to??? [20:42] Ronnie: means what does "very standard " mean here [20:42] no additional checks, no extra fields (which are not defined in model.py) [20:42] Ronnie: ok [20:43] Ronnie: where to access this file [20:43] ? [20:43] venues/forms.py [20:43] got it [20:44] Venue looks like a very standard form. it does one add one validation for the venue.name, and it includes some extra css and js to the page [20:44] - first "one" [20:44] nothing fancy [20:44] yes [20:44] it is [20:44] where you have to look is the Meta class [20:45] it defines model=Venue (which reffers to the Venue model in models.py) [20:45] Ronnie: yes.. it is defining [20:46] sometime the Meta class has a property exclude = ('some_db_field') or it contains fields = ('some_db_field1', 'another_field') [20:47] Ronnie: okiez [20:47] if meta contained the fields param, you needed to add the new field in there, but if fields is not defined, django automaticcally uses all fields in the model, so were good to ge [20:47] ge = go [20:47] Ronnie: Meta is not showing any fields [20:47] its showing only single line "metta = venue" [20:48] *meta [20:48] yes, so forms.py is complete (we do not want to add extra checks to the continent field, and django automatically saves it on submit) [20:49] the last step is to check the HTML [20:49] ok.. [20:49] but this one is probably good already [20:49] therefore we go to templates/venues/ folder [20:49] yes [20:50] the only template that uses the form we just checked is the file venue_update.html [20:50] there is no "folder" in this [20:51] yes venue_update is tehre [20:51] *there [20:51] try to understand the template [20:51] ok [20:51] and try to think if you need to add something [20:53] i think in this line "html_addr: $("#id_country, #id_spr, #id_city, #id_address")," we need to add continent field???? [20:53] aakshay: you have a sharp eye, very good [20:54] Ronnie: :D..... [20:54] so can i add "#id_continent" [20:54] ? [20:54] yes [20:55] done [20:56] new line is " html_addr: $("#id_country, #id_spr, #id_city, #id_address,#id_continent ")," [20:56] then your ready to test (for the sake of readability, you can add an extra space after #id_address [20:56] okiez.. [20:57] do you still remember how to start the site [20:57] ya [20:58] let me start again [20:58] :) [20:58] yippii.. seems as if worked [20:58] :) [20:59] django can be that easy [20:59] yay [20:59] push it up, and it will be reviewed... [21:00] fwiw, a review may take a while [21:01] done [21:01] :) [21:01] :) [21:01] its showing teh continents [21:01] *the [21:01] cjohnston: o/.... [21:01] Ronnie: what to do next?..... :) [21:02] aakshay: you want to commit the changes [21:02] you can commit the changes, and push to your own lp profile [21:02] bzr commit -m "text about what you did" --fixes lp:12345 [21:02] ok [21:02] need to run in loco_directory? [21:03] then bzr push lp:~username/loco-directory/12345 [21:03] cjohnston: need to run in loco_directory? [21:03] I run it in the base direcotry.. i dont know if it matters [21:03] so the directory that has the INSTALL file [21:04] means in loco-directory? [21:04] yes [21:04] okiez.. let me commit [21:04] usually when you branch files, you execute the command bzr branch lp:loco-directory foldername [21:05] the foldername can be anything you like, so choose a descriptive name for the bug you trying to fix [21:05] yes [21:06] my projects folder contains atm 16 different branches of loco-directory, so with a good name you can easiliy find which folder belongs to what fix [21:07] okiez.. thats the best way :) [21:08] my folder hirarchy is usually /projects// [21:08] or bugnr_name-of-fix [21:09]

is the is the bug number [21:09] ? [21:10] if you only use the bugnumber, its hard to find the right folder, because you have too lookup the number in LP to know which bug, therefore i add an extra descriptive tekst [21:10] yes thats easy way then [21:10] :) [21:10] and i pushed the changes [21:10] :) [21:11] what to do next? [21:11] i see, now you need to tell that the code is ready to be merged into the main brnach [21:11] https://code.launchpad.net/~akshaytayal/loco-directory/608289 [21:11] this is the link of your created branch [21:11] there is a button "Propose for merging" [21:11] yes [21:12] click that one, and add a desription of the change you made [21:13] now propose merge? [21:13] yes [21:13] clicked it [21:14] showing the status "Pending" [21:14] :) [21:14] yes, now you have to lean back, and wait for response [21:14] yeee!!!!..... :) ...... [21:14] Ronnie: stop teaching people to spam s! [21:14] s! [21:14] us! [21:14] \o/ [21:15] if the code is OK, it will be merged, if not we will provide some feedback about the changes that you need to make [21:16] when the branch is merged into trunk, then you can delete the folder on your pc [21:16] ok....but now you gave all the directions what to do next.. how will i do the bug correction myself? [21:16] okiez [21:16] ok....but now you gave all the directions what to do next.. how will i do the bug correction myself? [21:17] what do you mean [21:17] you just fixed a bug [21:17] if you want to di it yourself, you need to learn django. if you know its structure, you can fix bugs yourself [21:17] so just do the same thing [21:18] ok then i will start learning django by today itself... because i dint know while file to visit next for the correction [21:18] what about pyhton? [21:18] I just learn stuff as I go [21:19] you you have experience with other languages, i think you can start directly with the django manual [21:19] python is not that hard, i think you can learn both at the same time [21:19] ya i am perfect with c++ coding... okiez.. so i start with django [21:19] :) [21:20] if you need help, there is a #python and #django channel, LD specific questions can you ask here [21:20] I'm in both python and django [21:20] ok.. and i will also learn stuff as i go [21:20] :) [21:20] if you are nice, they will help you [21:20] indeed [21:20] and since our code is open source, you can show them the actual code and they will be able to help you easier [21:20] * Ronnie is still learning too. for each bug i need the django documentation [21:21] :D [21:21] cjohnston: okiez.. n yes we can show the code too :) [21:21] any suggestions which bug should i take next? [21:21] :) [21:22] aakshay: https://bugs.launchpad.net/loco-directory/+bug/723845 [21:22] Launchpad bug 723845 in loco-directory "Change order on Event and Meeting pages (affects: 1) (heat: 6)" [Low,Confirmed] [21:22] thats an easy one [21:22] i was gonna do it, but feel free aakshay [21:22] altough this is more a html thing than django [21:23] ok .. so i will start with this by today itself [21:23] but i may take time.. :( [21:23] aakshay: that one is a cut and paste [21:23] ok then its very easy... :) [21:24] i will do it today only then [21:24] *will try :D [21:24] Ronnie: im settin up to merge in the code you approved, then ill try to do a couple reviews [21:25] cjohnston: great :D [21:27] aakshay: a more django bug is this one: https://bugs.launchpad.net/loco-directory/+bug/616383 [21:27] Launchpad bug 616383 in loco-directory "Needs ability to directly link to a comment (affects: 1)" [Wishlist,Triaged] [21:27] or this https://bugs.launchpad.net/loco-directory/+bug/616547 [21:27] Launchpad bug 616547 in loco-directory "Edit/Delete Comments (affects: 1)" [Wishlist,Triaged] [21:27] Ronnie: okiez.. but you need to help me with these [21:28] today i got one hour left [21:28] no problem..i will ask you tommorrow.. [21:29] here also its 3 AM ..:D [21:29] and i hav college in morning....;) [21:29] where do you come from? [21:30] m in India [21:30] :) [21:30] nigelb: ^ [21:30] Tricky comes from india too (but he is not online now) [21:30] which part of india [21:31] m in Delhi [21:31] :) [21:31] where do you come from? [21:32] im from The Netherlands (a very small country in west europe) [21:32] next to germany [21:32] okiez.. :)... [21:33] * cjohnston and mhall119 are from Florida (US) [21:33] i have heard about it before.. :) ... [21:33] :D [21:34] aakshay: I commented on your merge proposal [21:34] Ronnie or cjohnston, could you walk him through making a south migration script? [21:34] I've about to leave for home [21:34] mhall119: more the "brz add" command ;) [21:34] I thought Ronnie did [21:35] mhall119: ok.. checking... [21:35] bzr add sounds better [21:35] aakshay: [21:35] go back to loco-directory [21:35] ok [21:35] m in [21:35] oh, did he just not add it? [21:36] Ronnie: bzr add loco_directory/venues/migrations/ ? [21:36] you guys rock [21:36] mhall119: I believe so [21:36] cjohnston: next... :) [21:36] aakshay: trying to make sure I give you the correct thing [21:36] just bzr add in the top directory [21:36] aakshay: did bzr add say it added a file? [21:37] aakshay: "bzr add *" [21:37] i dint do "add" [21:37] i run "commit" and "push".. :) [21:38] you have to bzr add $file [21:38] right.. do the add now, then the commit, then the push [21:38]