[00:03] Is there some IRC I should turn to with questions regarding getting into "Getting started" [00:03] I have one regarding TestDrive [00:05] Wrong room sorry === AndrewMC is now known as SpockVulcan === Jamie is now known as Guest48124 === SpockVulcan is now known as AndrewMC [04:20] hi [05:21] anybody home? [05:22] Hey [05:22] Im from china [05:23] Cool, I'm in the US. :D [05:23] it's not the time to discuss? [05:23] I'm pool in english [05:24] i just got here [05:24] me too [05:26] Well, it's a bit early, I don't think that the next class starts any time soon. [05:29] yeh, difference of time [05:30] let's have a look the class list. [05:38] while waiting Full Circle Magazine: http://fullcirclemagazine.org/issue-46/ [05:38] Direct: http://dl.fullcirclemagazine.org/issue46_en.pdf === msnsachin12 is now known as msnsachin [07:43] good morning [08:09] It's time to say "good night" in our country ~ hehe === msnsachin12 is now known as msnsachin === qwebirc86266 is now known as geco2 [09:11] Any Discussions? [09:19] sriram, if you mean the classes they do not start for another 7 hours [09:20] tdelv, schedule please? [09:22] !schedule [09:22] To view the upcoming Ubuntu Classroom schedule, visit the Learning Events Calendar at http://people.ubuntu.com/~nhandler/classroom.html === msnsachin12 is now known as msnsachin === nmsnsachi is now known as msnsachin [14:39] hey what time the today session is starting ? I am from India... [14:40] ranjan: 2130 IST === andreserl is now known as RoAkSoAx_ [14:40] nigelb, thanks :P) === RoAkSoAx_ is now known as RoAkSoAx [14:43] can anybody give me the link of yesterdays' session log ? [14:43] zeitgeist's log [14:43] all on https://wiki.ubuntu.com/UbuntuDeveloperWeek [14:44] dholbach, thanks :) [14:45] i am new to IRC [14:45] can say ubuntu participation on GSOC? [15:32] hey guys .. can you tell me why i cannot install with "sudo apt-get install openssh-server" in ubunto 10.04 Lucid? [15:33] !support [15:33] For general questions or support, please use our support channel, #ubuntu [15:33] You should probably ask in #ubuntu which is the support channel [15:33] ok thanks! [15:53] what is this sesion like ? "test drive " ?? [15:53] are we going to learn testing ? [15:54] techbreak, yes [15:54] acarpine, testing of what ? [15:54] I think we are going to learn testdrive tool [15:54] acarpine, what is that tool for ? tool like ? [15:54] hey folks, keep chat to #ubuntu-classroom-chat, sessions will be happening here :) [15:55] ops right... [15:58] HELLO MY FRIENDS! IT'S DAY 3 of UBUNTU DEVELOPER WEEK! WELCOME! :) [15:58] if you need any information about the event at all, check out https://wiki.ubuntu.com/UbuntuDeveloperWeek [15:58] !caps | dholbach [15:58] dholbach: PLEASE DON'T SHOUT! We can read lowercase too. [15:58] :P [15:58] also, please make sure you join #ubuntu-classroom-chat [15:58] because that's where all the chatter goes [15:59] and questions too - please make sure you prefix your questions with QUESTION: [15:59] ie: QUESTION: RoAkSoAx: was Pisco invented in Peru or in Chile? [15:59] dholbach, Peru of course! [15:59] :) [16:00] today we'll start of the day with RoAkSoAx aka. Andres Rodriguez who will introduce you to TestDrive and how to run virtual machines (including the Ubuntu development release) in a sane manner [16:00] RoAkSoAx, the stage is yours [16:00] enjoy! [16:00] thanks dholbach [16:00] Good Morning Everybody! My name is Andres Rodriguez (as dholbach already saud) and I'm the upstream developer of TestDrive. [16:01] So Who is here for the TestDrive Session? === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: Ubuntu Developer Week - Current Session: TestDrive - Instructors: RoAkSoAx [16:01] raise your hands in #u-c-chat [16:01] Logs for this session will be available at http://irclogs.ubuntu.com/2011/03/02/%23ubuntu-classroom.html following the conclusion of the session. [16:01] Perfect then. [16:01] This session is divided as follows: [16:01] 1. Introduction [16:01] 2. How to use TestDrive (its different uses)! [16:01] 3. Do you want to help TestDrive become better? - Development Opportunities! [16:01] 4. Questions/Comments/Suggestions? [16:02] == Introduction == [16:02] TestDrive was originally created by Dustin Kirkland to test the Ubuntu Daily ISO's of the development release. It was originally a command line application, a shell script, that was later rewritten to python. At this point, it was only a command line application. Nowdadays we have a GTK UI as well. The GTK was my Google Summer of Project with the objective of not only be able to test the Daily ISO Image of the Development release, but to be [16:02] able to test other ISO's in a simple way. I believe that the original objectives were achieved and there's also the opportunity to do more cool stuff. [16:04] So the initial sole purpose of TestDrive was to be able to test Ubuntu Daily ISO's, to help with the Testing when new Ubuntu pre-releases were available and others, such as start a VM in a quick manner with no configuration based in any Ubuntu Daily ISO Available. These daily ISOs were only the Ubuntu development release [16:05] So now you may wonder... what else can I do with TestDrive? [16:06] TestDrive can be used for the following: [16:06] * Test Ubuntu Development Releases - Daily ISO's [16:06] * Test Older Ubuntu Releases [16:06] * Test flavors(Kubuntu/Xubuntu/Edubuntu/Mythbuntu/Ubuntu Studio) [16:06] * Test any *other* ISO from any Other Distribution [16:06] * Test Ubuntu Cloud Daily Images [16:06] * Test qcow2 disk images. [16:06] * Ubuntu ISO Download Manager :) [16:06] * And of course, test if any of our packages is fixed in any release. [16:07] So at this point I'm assuming everybody is running TestDrive (and for those who are running natty, you'll notice a notification a few seconds right after you start TestDrive and I'll get to that in a bit) [16:07] If you are not running it yet, please go ahead [16:08] let me know when you all have TestDrive ready :) [16:09] !question [16:09] !q [16:09] !y [16:09] techbreak asked: how to get testdrive ready ? [16:10] monish001 asked: how to start testdrive? [16:10] sorry my bad [16:10] From the command line: sudo apt-get install testdrive [16:10] that comman will install both, TestDrive GTK and the command line application [16:10] Or you guys can go to Software Center and search for TestDrive and Install it [16:11] Then (for those running gnome Maverick + Applications > System Tools > TestDrive an Ubuntu ISO [16:12] monish001 asked: terminal says - You will have to enable the component called 'universe' [16:13] monish001, yes you need to enable though by default it should be.You can also do it from Gnome but I can't seem to recall what to launch :) [16:13] If you are running Maverick I believe it is in System > Preferences > Software Sources [16:14] If you are running Ubuntu Software Center > Edit > Software Sources [16:14] monish001, ^^ [16:15] (sorry I don't really use much Ubuntu Software Center) [16:16] So anyways, let's move on otherwise time might run out [16:16] So how can we Test Ubuntu Development Releases? It is easy. When you launch TestDrive, by default it will provide all the available ISO's of the current development release. In this case, Natty. The testing procedure is even easier. Simply 1. Select, 2. Sync, 3. Launch. So we can select either 1 or more ISO's. Sync means that It will download the ISO's form the repository automatically. And once an ISO is synced completely we can Launch it. [16:16] dholbach has setup a nice wikipage that show's this behavior: https://wiki.ubuntu.com/UsingDevelopmentReleases/ [16:17] techbreak_, Please do so :) [16:18] Now, I understand not everybody has the same hardware as I do, and not everybody has the same virtualization techonlogy [16:18] TestDrive Fully supports 2 virtualization technologies (In the latest release included in Natty, or in Maverick PPA) [16:19] So for those who are running maverick do this in the command line: [16:19] sudo apt-get install python-software-properties [16:19] sudo add-apt-repository ppa:testdrive/ppa [16:19] sudo apt-get update [16:19] sudo apt-get install testdrive [16:19] with that all in maverick/natty should have the latest release [16:20] now, if you are using KVM as your virtualization technology or your CPU supports KVM, when you installed TestDrive everything should be ready to launch [16:21] if you use virtualbox , you'll first have to install it: sudo apt-get install virtualbox-ose [16:21] so anyways, how can I choose what virtualization technology to use: Simple TestDrive > Edit > Preferences > Virtualization > Hypervisor (and select the hypervisor of your preference and click SAVE) [16:22] So by now I'm assuming you guys are downloading the ISO. Now we know how to change the Hypervisor. Please all take a look to https://wiki.ubuntu.com/UsingDevelopmentReleases/ [16:22] you'll see the nice screenshots [16:23] so while the ISO downloads, I;ll continue to explain what other things we can do with TestDrive, so let's just leave TestDrive to do the work for a while [16:24] So, what else can I do with TestDrive besides testing the Ubuntu Development releases.... We can test *Older* Ubuntu releases. So, how can we do it? It is also simple. Edit > Preferences > Ubuntu Releases. If you notice, there's two things to consider. The Repository and the Release itself. The repository can either be http://cdimage.ubuntu.com or http://releases.ubuntu.com and the releases would be the available releases for each reposito [16:24] ry. You just select the desired Repository and the desired release in the repository, and click save. [16:24] darkdevil75 asked: if i have already downloaded the iso, how do i point to the location? [16:25] darkdevil75, I'll get to that in a bit [16:26] So how we select older Development Releases in the command line? Somthing like this: testdrive -p cdimage -r maverick [16:26] we specify the desired repository and the desired release [16:26] if you only run "testdrive" in the command line, it will default to "cdimage" and "ubuntu development release (in this case, natty)" [16:28] So, another thing we can do with TestDrive, is to also test different Ubuntu flavors, from both a previous release or the current development release. So now, how can we test different them? By default Ubuntu/Kubuntu/Xubuntu/Other are the flavors enabled. We can also test Edubuntu/Mythbuntu/UbuntuStudio. For that we go to Edit > Preferences > Distributions > (Select the desired ones). Then we save and the available flavors in the selected [16:28] repository/release will be appear. [16:29] from the command line we do something like: "testdrive -p releases -r maverick -l kubuntu" [16:29] or "testdrive -l kubuntu" -> For Kubuntu Natty [16:30] stefwal54 asked: is there a way to solve the problem that the virtual machine crashed [16:30] Steap, not with testdrive :( [16:31] stefwal54, not with testdrive :( [16:31] testdrive in the case of KVM only uses kvm command to launch the ISO's [16:31] chilicuil asked: what if I pause downloading an iso, testdrive will continue downloading where I leave it?, what if I want to test the ubuntu dev version iso everyday, will it download all the iso again, or it will do a diff between the 2 isos? [16:31] chilicuil, TestDrive will only download the diff and not the whole iso. However the progress will always go from 0 to 100 [16:32] Fpor all of those concerned, TestDrive to download all Ubuntu ISO's will use rsync [16:34] Now, TestDrive Also allows us to to download and launch ISO's that might not be Ubuntu ISOs or are located in other repositories/servers/or Even the local machine. So how can we do this? Simple. In the GTK main interface you'll notice that there's the"Other". Once the "Other" tab is selected, the "Add ISO" button will become enabled. Then we enter a simple description, the URL where the ISO is located, and the protocol to use, which is eith [16:34] er rzync, or zsync. If you notice there's also a file procotol. This can be used when the ISO is in our machine, and to be able to add it, we need to provide the absolute path of the ISO as URL. [16:35] So, "Add Other ISO" will launch another dialog to be able to add the ISO [16:37] In this case, we could use the URL of any ISO there, let's say a Fedora ISO, select zsync or rsync (if the server of the URL supports it), then click on "Add" and then "Save" [16:37] this will make available the ISO under the "Other" tab, and we can select it, click Sync, and once it finished download, we can just click Launch [16:37] easy huh? [16:38] but wait, did you just mention we can also add ISO's already downloaded??? Yes you can ( darkdevil75 ). There's a few ways to do this [16:39] fisch246 asked: "Unable to validate Virtualization Method [virtualbox]" i have virtualbox installed... anyway i can fix this? [16:39] fisch246, We'll hold that question for the end :) [16:40] So anyways, how can be run with TestDrive ISO's that I already downloaded [16:40] simple: With the GTK we can use TestDrive > File > Open [16:40] TestDrive > File > New [16:40] and notice that TestDrive > File > New is the same as "Add Other ISO" [16:41] so as URL we just give the full path of the ISO [16:41] however, we can also do this from the command line [16:41] testdrive -u rzync://www.youriso.com/download.iso [16:42] or testdrive -u /path/to/iso/ubuntu.iso [16:42] chadadavis asked: 3D driver support? [16:42] chadadavis, that's hypervisor side of things, not TestDrive's :( [16:43] so anyways, what else can we do with TestDrive? [16:44] we can also Test Ubuntu Cloud Images [16:44] wait what? Cloud Images?? Yes, cloud images that run in the cloud can be tested in the local machine [16:44] unfortunately for now it will just work for daily images and it only works in testdrive command line [16:45] techbreak asked: what is cloud image ? image of cloud ubuntu OS ? [16:46] techbreak_, the Cloud Image is the Ubuntu Image used in cloud computing for either Eucalyptus Cloud or Amazon EC2. In other words, whenever you launch Ubuntu in the Cloud it uses a cloud image (i.e. a disk file with some other components that have Ubuntu pre-loaded) [16:46] Now, to be able to test Ubuntu Cloud Daily Images we will need to use the command line application. So, we can open a command line and just do the following to obtain the latest Daily UEC/Cloud Images available: [16:46] testdrive -p uec-daily -l uec-server [16:46] We can also specify the release (i.e. Maverick) [16:46] testdrive -p uec-daily -l uec-server -r maverick [16:47] Now, a cool feature that was added lately is to be able to launch the Cloud Image in the local terminal/console. But what does this mean? Instead of launching the image in a separate KVM window it will display it in the terminal from where you are launching testdrive. The command is as follows: [16:47] testdrive -p uec-daily -l uec-server --curses [16:47] NOTE: Running cloud images only work with KVM [16:48] * RoAkSoAx running out of time [16:48] as I mentioned before we can also run images located in the machine [16:48] Now we can also launch images that are located in the machine. With TestDrive GTK you can do it by using the "Other" tab - "Add ISO" (Equivalent to File > New) or simply File > Open. The local images that can be launched can be either ISO Images, Disk Images (QCOW2) and Cloud Images. We can also do this from the command line as follows: [16:48] testdrive -u /local/path/to/image.iso [16:48] testdrive -u /local/path/to/image.img [16:48] testdrive -u /local/path/to/uec-image.tar.gz [16:48] testdrive -u /local/path/to/uec-image.tar.gz --curses [16:49] last but not least, for those running Natty, we have recently added an Indicator Applet (if you notice) that will appear and notify the user whenever there are available pre-release candidate ISO's available for testing. These ISOs are the ISOs that are being tested towards the next Ubuntu release. (i.e. ISO's for Tomorrow's Alpha3). [16:49] the idea behind that was to make aware people who were using TestDrive that there's an Ubuntu pre-release available for testing [16:49] == How to Contribute == [16:49] Now, we've given an overview of the things we can do with TestDrive. What about if you want to contribute to TestDrive and make it better. Well it is simple, you can either contribute with ideas, fixing bugs or implementing new features. Though if you have an idea and can submit a patch, that's more desirable :). Some of the new reported feature requests are: [16:49] "Re-run this program with TestDrive" https://bugs.launchpad.net/testdrive/+bug/704675 [16:49] "Quicklist and progressbar support" https://bugs.launchpad.net/testdrive/+bug/711915 [16:49] "GUI Option for zsync" https://bugs.launchpad.net/testdrive/+bug/701818 [16:49] "Support VMWare" https://bugs.launchpad.net/testdrive/+bug/527161 [16:50] == Questions/Comments/Suggestions? == [16:50] Since I only have 10 mins left [16:51] lets do questions/comments/suggestions and try to get up a machine up and running [16:51] There are 10 minutes remaining in the current session. [16:51] techbreak asked: ok if I am not funny what is this kvm ? [16:51] techbreak, indeed KVM is one of the varios methods to create Virtual Machines [16:51] and the one pre-ferred in Ubuntu [16:52] acarpine asked: why i should run a cloud image? [16:53] acarpine, you don't have to, but if you would like to test it, you are more than welcome to do so!! :). Adding the support to TestDrive was a feature requested to be able to easily test Cloud Images by the Developer [16:53] stefwal asked: is there a difference between a second machine and testdrive? If some one has a second machine of course! [16:54] stefwal: Of course, TestDrive uses a Vritualization Technology to run an ISO image (mainly) in a Virtual Machine [16:54] you could also burn that ISO in a USB Stick and then test it in real HW [16:54] techbreak asked: what are we supposed do after testing ? what if we found some error or bug or something ? where to submit ? how ? [16:54] techbreak_, if you found a error/bug with Ubuntu, just file the bug http://launchpad.net/ubuntu [16:55] if you found a bug in TestDrive file a bug in launchpad.net/testdrive [16:55] Vikash asked: I have one que. I may be off the topic because i have just come to the session... Which OS is better Ubuntu or Ubuntu-derivative [16:55] Vikash, you can test that yourself with TestDrive :) [16:55] and use whichever you like better [16:56] There are 5 minutes remaining in the current session. [16:56] So anyways, anyone has anything else for the last 5 minutes of the session? [16:57] stefwal asked: any good ways to test? [16:57] stefwal, refer to https://wiki.ubuntu.com/UsingDevelopmentReleases/ for the steps on how to test techbreak_ shows how to run the download ISO [16:58] stefwal, but that's the point, testing involves trying to do things [16:58] you can always follow ISO testing if you would like to contribute [16:58] and it will show step by step on how to do it and you can use TestDrive for that [16:58] stefwal, refer to iso.qa.ubuntu.com [16:59] techbreak asked: what after i finish downloading ? any link if get stuck ? [16:59] techbreak asked: can I burn cd /dvd from the downloaded image from testrive ? [17:00] techbreak_, yes: Slect the Image you'd like to burn and click on "Create USB disk" [17:00] which will launch USB creator [17:00] to finish please for more help you cn find me in channel #testdrive [17:00] I believe my time is over. Thank you all for attending [17:00] Project website: launchpad.net/testdrive IRC Channel: #testdrive === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: Ubuntu Developer Week - Current Session: LoCo Directory Hacking - Instructors: mhall119, cjohnston [17:01] Logs for this session will be available at http://irclogs.ubuntu.com/2011/03/02/%23ubuntu-classroom.html following the conclusion of the session. [17:02] Hello everyone [17:02] my name is Michael Hall, and I'm one of the developers of the Ubuntu LoCo Directory [17:03] I hope you've all been to http://loco.ubuntu.com already, but does anybody not know what it is? [17:04] alright, quick overview then [17:05] the loco directory is a community-driven project, meaning decisions and implementation are determined by the community, not Canonical [17:05] techbreak asked: mhall119, idk what is this sessoin about ? loco directory ??? [17:05] techbreak_: http://loco.ubuntu.com [17:05] this session is going to get you ready to start hacking and contributing to it [17:06] the loco-directory is written in Python, and uses the Django web framework [17:06] you will need at least working knowledge of python, and some basic understanding of Django to work on LD [17:07] if you don't currently have Django knowledge, don't worry, it's very easy and I'll go over some of it this hour [17:07] the main developers of LD are myself, cjohnston, dholbach, Ronnie and daker [17:07] we all hang out in #ubuntu-locoteams, and that's usually where we discuss LD development [17:08] since loco.ubuntu.com is hosted on one of Canonical's servers running Ubuntu 10.04, we're restricted to the versions software in those repositories [17:09] specifically python 2.6, Django 1.1, jQuery 1.3 and jQuery-ui 1.7 [17:09] if you're running Lucid, you're all set [17:09] if you're running Maverick or Natty, you'll need to grab those versions manually [17:11] < YoBoY> QUESTION : we can't develop with earlier versions of python, django, ... or [17:11] it's just recomended ? [17:12] since we develop on 2.6, and it'll be running 2.6 in production, it's generally a good idea for you to use 2.6 [17:12] I can't say for sure that it won't work with 2.4, but it's likely [17:13] I'm assuming you have all been introduced to the basics of bzr by now, but if not just ask about it as I go [17:13] alright, lets get the code! [17:13] cd to where you want it to live [17:13] then run: bzr branch lp:loco-directory [17:13] that'll get you a copy of the latest trunk [17:14] trunk is almost always stable [17:14] RawChid asked: IS there a manual or webpage which describes how to do this? [17:14] not that I know if, but ask us in #ubuntu-locoteams (after this session) and we can help you with it === cmagina is now known as cmagina-lunch [17:15] okay, by now you should all have a local branch of loco-directory [17:15] so cd loco-directory and let's take a look [17:16] quick Django info: [17:16] Django projects are divided between the root 'project' folder, and sub 'application' folders [17:17] in the root of the branch, 'loco_directory' is the django project folder [17:17] so cd loco_directory [17:17] under there you'll see 'common', 'events', 'meetings', 'services', 'teams', 'userprofiles' and 'venues' [17:18] those are all of the Django applications that make up LD [17:18] 'common' is just what it sounds like, it's for things that don't fit elsewhere [17:19] 'teams' contains all the code for LoCo Team records [17:19] ls ./teams/ [17:19] a Django app typically has several standard files [17:20] models.py is where you define your data models, Django will automatically turn these into SQL tables for you (you'll see that later) [17:20] views.py is where you write the code that is responsible for responding to an HTTP request [17:21] and urls.py maps a URL pattern to a view [17:21] any questions so far? [17:21] ok, moving on [17:22] the 'events' and 'venues' are the apps that handle LD's event tracker, if you've used LD before you'll know what they do [17:22] they have the same basic structure as 'teams', with models.py, views.py and urls.py [17:23] same for 'meetings' and 'userprofiles' [17:23] now, Django has a built-in templating system that we use. Our views.py code will usually make use of one or more templates in rendering an HTTP response [17:24] templates live under the 'templates' directory in the project folder [17:24] if you ls ./templates/ you'll see that they're separated out by app as well [17:24] so, to recap [17:25] if you want to change data structures, it'll likely be in a models.py [17:25] if you want to change the logic behind a display, it'll likely be in a views.py [17:25] and if you want to change the interface (html), it'll likely be in the templates [17:25] everybody with me so far? [17:26] alright, let's get you guys setup with a working instance of LD [17:27] first things first, lets look at settings.py in the project folder [17:27] there's a lot of stuff in here, but the key piece is down around line 116: INSTALLED_APPS [17:27] this is a list of apps that Django will use for this project [17:28] monish001 asked: does Django works on MVC (model view controller framework)? [17:28] yes, though they call it Model-View-Template, and things are slighting shifted [17:29] specifically, the typical 'controller' logic is in the view, and most of the display stuff is in the templates [17:29] okay, lets loot at INSTALLED_APPS [17:29] the first 4 are the standard Django apps, auth gives us User and Group models, plus permissions [17:30] contenttypes is really internal stuff you won't likely ever need to worry about [17:30] sessions gives us automatic session tracking, just like any good web framework should [17:30] admin is the best of them all, it'll give you a fully functional interface to manage the data in your database for all your defined models [17:31] if you look in most of the application folders, you'll see amdin.py, which tells the admin app how to present your models [17:31] the next 6 items in INSTALLED_APPS are the LD apps we've already gone over [17:32] django_openid_auth is what let's us tie our users and groups to the Ubuntu Single Signon === Mkaysi is now known as OmgBot [17:32] south is a special Django app, by default Django will create DB tables based on your models, but it won't change existing tables, which means once you create them you have to make any future changes manually === OmgBot is now known as Guest83509 [17:33] south lets you track your model structure, and will provide migration scripts whenever you make changes to them [17:33] we make good use of south in the loco directory === Guest83509 is now known as Mkaysi [17:33] if you look under most of the application folders, you'll see a 'migrations' folder, these are the south scripts [17:33] ok, that's all for settings.py [17:34] next step, copy local_settings.py.sample to local_settings.py [17:34] we use local_settings.py for settings that are specific to a running instance of LD, they aren't checked into bzr [17:35] there's not really anything you need to do with it right now, except make the copy [17:35] everyone with me still? The next part is setting it all up [17:36] alright, lets get our database [17:36] from the project folder, run "./manage.py syncdb" [17:36] it will ask you for a superuser, select yes and give it a username, email and password [17:37] syncdb is the Django command that created your initial database tables [17:37] by default, LD will use a local sqlite3 file for it's database [17:37] in production, it runs against postgres [17:38] you're also free to use MySQL [17:38] when syncdb finishes, you'll see a message about some apps not being synced because they're under south's migration control [17:38] so after syncdb, run: ./manage.py migrate [17:39] this will cause South to run through all of it's migration scripts [17:39] which will leave you with the proper table structures [17:39] if you're using sqlite, you'll see some warnings because it doesn't support some contraints, don't worry about those [17:40] finally, we'll need to initialize your setup, so run: ./manage.py init-ld [17:41] init-ld does several things, it'll setup a group in your database for the LoCo Council, it will create necessary symlinks for jquery, and finally it'll grab a copy of lp:ubuntu-website/light-django-theme [17:41] that last bit is important [17:41] light-django-theme provides the base templates and CSS for several Django powered Ubuntu sites [17:42] loco.ubuntu.com (of course), but also summit.ubuntu.com and 10.cloud.ubuntu.com [17:42] everybody run all of those steps okay? [17:42] * mhall119 looks at the clock [17:44] okay, typically the next step is to either refresh your database with data from Launchpad,or refresh it with data from loco.ubuntu.com [17:44] but, both of those take a while to run, so we're going to skip them and I'll just have you download a copy of loco_directory.db [17:44] http://ubuntuone.com/p/fn1/ [17:44] put that into your project folder (over-writing the one you made with syncdb) [17:45] for reference, "./manage.py lpupdate" will refresh teams and some users from Launchpad, but won't get events, venues or meetings [17:45] "./manage.py import-live-data" will use LD's REST/Json services to download data from loco.ubuntu.com [17:46] once you have the database file, run: ./manage.py runserver [17:46] this will run django's built in webserver on localhost:8000 [17:47] which you can then visit in your browser to see your local instance running [17:48] oh yes, Ronnie brings up a point that I missed [17:48] INSTALL file in the root of the branch has instructions for getting things setup [17:48] one of the lines is a long apt-get install, which will get you all the dependencies [17:49] okay, hopefully I've gotten you guys a working (or mostly working) isntance of the LD code [17:50] the next step is to find a bug at https://bugs.launchpad.net/loco-directory to work on [17:50] if you need help figuring out what needs to be done, just ask us in #ubuntu-locoteams [17:51] There are 10 minutes remaining in the current session. [17:51] but remember, data=models.py, logic=views.py, UI=templates [17:51] that'll get you to the right place 90% of the time [17:51] after you make the fix, test it locally first [17:51] once you're happy with it, run: bzr commit -m "You message" --fixes lp:12345 [17:51] where 12345 is the bug number you're working on [17:52] that'll help launchpad associate your code with that bug [17:52] then: bzr push lp:~you/loco-directory/fixes-12345 [17:52] agian, I hope you've all been introduced to bzr and distributed development, so this should be familiar [17:53] then go to https://code.launchpad.net/loco-directory, select your branch, and click the "Propose for merging" link [17:54] then one of the main developers will review your code (when we have time, we all have actual jobs too) [17:54] < chadadavis> QUESTION, doe the push statement make a new branch as well, or just [17:54] upload the current branch? [17:55] it will create a new branch in Launchpad, based off the lp:loco-directory branch [17:55] these are very lightweight in launchpad, so don't hesitate to push stuff [17:55] we typically have one branch per fix or feature [17:56] There are 5 minutes remaining in the current session. [17:56] once your code bases a review, we will merge it into lp:loco-directory [17:56] from there it will get translated and wait for the next release of LD [17:56] anything that lands in trunk will be in the next release [17:57] we don't have a fixed release schedule though, so it's hard to say if it'll take days or weeks to get it out [17:57] < YoBoY> QUESTION : can you point us some easy bugs to start working on ? [17:58] we try to mark small/easy fixes as 'bitesize' in launchpad, you can get a list of them from https://bugs.launchpad.net/loco-directory/+bugs?field.tag=bitesize [17:58] if you get stuck or have other questions, come find one of us in #ubuntu-locoteams [17:58] and happy hacking! === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: Ubuntu Developer Week - Current Session: Ubuntu ARM and the OMAP4 images - Instructors: ogra [18:01] Logs for this session will be available at http://irclogs.ubuntu.com/2011/03/02/%23ubuntu-classroom.html following the conclusion of the session. [18:02] hey hey [18:03] so i will give a short insight into Ubuntu ARM, the team and the images we care for, i dont expect this to take much time so there should be plenty of time for questions (if there are any) [18:04] the ubuntu arm team (as the name suggests) cares for the arm port in ubuntu [18:04] we build images for different types of arm hardware [18:04] target audience for these images are endusers [18:05] and we try to make them an identical experience to any other ubuntu architecture, so you can expect identical functionallity as in any other ubuntu install [18:06] initially the ubuntu arm team consisted of 8 developers that cared for the whole archive [18:06] all builds (and their failures) as well as all images had to be maintained by this small bunch of people === daker is now known as Ghost_of_daker [18:07] recently ARM recognized how important ubuntu was for them, so they started linaro ... [18:07] linaro is a consortium of companies taking care of improving arm and the arm experience [18:08] i.e. nowadays if you get an arm board you will need a linux kernel from the vendor, a so called BSP [18:08] usually that has tons of incompatible changes so the kernel couldnt be merged upstream in linus tree [18:08] and you will also not run a kernel for board A on board B [18:09] linaros mission is to fix such issues [18:09] so that at some point you have someting like the linux-generic package that runs on all arm hardware [18:09] they also care about the toolchain and compiler to get the best optimization out of them [18:10] and they help a lot with failures to build from source [18:10] so since linaro is around, the work of the ubuntu-arm team got a lot easier, we stand on their sholders now [18:10] ... [18:11] over the recent releases we built images for a variety of boards ... starting with freescales imx51 babbage board, marvells dove board (which is known from the press as armada board nowadays) and the very popular beagleboard from TI === cmagina-lunch is now known as cmagina [18:12] with maverick we started to work closely with TI to make ubuntu the reference platform for their OMAP4 pandaboard [18:12] this was released in 10.10 and gets improved in 11.04 now [18:12] as architectures come and go the babbage and dove architectures vanished from our list of ports, omap 3 and 4 persist [18:13] if you want to help out with arm development i would highly suggest to take a look at the pandaboard on http://pandaboard.org [18:13] its is available for $175 and has all HW you can imagine [18:14] with the ubuntu install and the TI addons it is fully capable of playing 1080p video [18:14] so if you are intrested in arm development on ubuntu a beagleboard (see beagleboard.org) or a panda is the way to go [18:15] for people that cant afford hardware we also worked out cross ways of building and testing arm packages, the qemu-kvm-extras-static package brings all you need to run an arm chroot on your x86 boax [18:15] for testing and devevlopment thats a good start [18:16] for the highly embedded thinking people linaro offers a cross toolchain and the xdeb packages that makes it possible to cross build packages for arm on an x86 host [18:17] if you are intrested in tryinf out our images you can find install instructions and download links at https://wiki.ubuntu.com/ARM/OMAP it sill always list links to the different release centric instructions [18:17] ok, enough of me babbling i think :) [18:18] there are some questions [18:18] darkdevil75 asked: arm? [18:19] yes :) [18:19] monish001 asked: arm port means arm hardware architecture platform? [18:19] right, it means the CPU you carry in your mobile phone, tablet or (rarely) in your netbook [18:19] monish001 asked: why is arm hardware important? [18:20] heh, well, as you see above it runs very transparently in many devices ... you can find arm in your dishwasher as well as in your mobile phone or the ipad [18:20] even in TVs [18:21]