=== Alan_ is now known as Guest67250 === cyrex is now known as luisalvarado [06:05] I will miss the Ubu Dev Week meetings on here. Will they be posted somewhere (esp. the part of setting everything up and looking through code)? [06:06] cc11rocks: everything in this channel is logged, so you'll find the complete log on irclogs.ubuntu.com [06:06] Okay, thanks [06:07] Will the meeting be very detailed or more of an overview? [06:10] at a guess, I'd say more of an overview, but there'll likely be pointers to more information on the web etc [06:15] Alrightly, thank you [06:16] no problem :) === davlefou_ is now known as davlefou === mat_benjut is now known as bukan_mamat === bukan_mamat is now known as quixotden === quixotden is now known as quixotedon_shema === quixotedon_shema is now known as quixotedon_cute === quixotedon_cute is now known as quixotedon_macho === Madmike is now known as PJaros === raj is now known as virtuaposta [10:45] hey [11:00] #diaspora [11:04] Hi... [11:07] less than 4 hours left :) [11:13] watz the starting time in GMT?? [11:15] shabiitd: 15:00 [12:55] hello === D is now known as Guest19467 === JW is now known as Guest66570 === tho is now known as Guest10955 === chb is now known as Guest30755 [14:35] when it starts? [14:35] 25 min more [14:35] yes [14:52] Hi all! [14:52] hi PaoloRotolo [14:53] hi [14:53] sssh... settle in your seat, it will be starting soon :) [14:55] Any way how to turn off notifications for logging in and out users? [14:55] Or nice IRC client for doing that? [14:55] Xchat [14:55] hi everyone :)) [14:55] XChat [14:55] arvislacis1: /ignore #ubuntu-classroom CRAP NOTICES SNOTES CTCPS JOINS PARTS QUITS KICKS MODES WALLOPS NICKS DCC DCCMSGS CLIENTNOTICES CLIENTCRAP CLIENTERRORS HILIGHTS === Madmike is now known as PJaros [14:56] dholbach: Thanks [14:56] anytime [14:56] hola gente [14:56] /ignore #ubuntu-classroom CRAP NOTICES SNOTES CTCPS JOINS PARTS QUITS KICKS MODES WALLOPS NICKS DCC DCCMSGS CLIENTNOTICES CLIENTCRAP CLIENTERRORS HILIGHTS [14:56] I'm excited open Linux Classroom! [14:56] hello averybody [14:56] arvislacis1, without the leading space [14:56] Sit back and enjoy:) [14:58] dholbach: how do you "unignore" or does it just reset when you leave and rejoin? [14:58] neoteric, I guess it resets [14:58] It doesn't work [14:58] some clients might not support it [14:58] What client are you using? [14:59] xchat-gnome [14:59] it's time [14:59] Smuxi :) [14:59] Xchat, right click on #ubuntu-classroom (left menu), Settings, mark Hide Join/Part Messages [15:00] H E L L O M Y F R I E N D S ! [15:00] Hi [15:00] Welcome to another Ubuntu Developer Week! [15:00] dholbach, o/ [15:00] hi [15:00] Thanks nohtype! [15:00] wait, isn't it moderated? [15:00] Was just about to ask. [15:00] \o/ === 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: Introduction to Ubuntu development - Instructors: dholbach [15:00] Here we go! [15:01] Before we start off, here just a few pointers which should generally help you through the event. [15:01] First of all: make sure you also join #ubuntu-classroom-chat [15:01] #ubuntu-classroom is just for the session itself, all the chat, discussion and questions happen in #ubuntu-classroom-chat [15:01] if you have a question you want to be answered in the session, please prefix it with QUESTION: [15:02] ie, QUESTION: Can you recommend any good music for a late-night hacking session? [15:02] also have a look at https://wiki.ubuntu.com/UbuntuDeveloperWeek because all the session information is on there [15:02] Two questions which come up frequently are: will there be logs? [15:03] yes, we will also put them up on https://wiki.ubuntu.com/UbuntuDeveloperWeek/ [15:03] and the second one is "how can I ignore all the joins/parts of people?" [15:03] you can do that by typing "/ignore #ubuntu-classroom CRAP NOTICES SNOTES CTCPS JOINS PARTS QUITS KICKS MODES WALLOPS NICKS DCC DCCMSGS CLIENTNOTICES CLIENTCRAP CLIENTERRORS HILIGHTS" into the channel window [15:03] without the " obviously [15:04] some IRC clients might not support this though [15:04] alright - that's everything organisational from me for now [15:04] Let's start the first session! === zen is now known as Guest54747 [15:04] My name is Daniel Holbach, I've been working on Ubuntu for almost all of its life and always loved our Developer community [15:05] for a years I've been working for Canonical now, first working on the Desktop, then moving on to work with our Developer community === prashanthsunder9 is now known as prashanth [15:05] in this first session I want to give you an overview over how Ubuntu development generally works [15:06] there are lots of people, lots of moving parts and it can all seem very confusing, but it's actually fine and quite easy to learn :) [15:06] in this first session I just want to give you a broad overview, so you at least heard all the most important things once [15:06] and to answer as many questions as we possibly can :) [15:07] If I'm too fast or don't make sense, please speak up. :) [15:07] Ubuntu is made up of thousands of different components, written in many different programming languages. Every component - be it a software library, a tool or a graphical application - is available as a source package. [15:07] Source packages in most cases consist of two parts: the actual source code and metadata. Metadata includes the dependencies of the package, copyright and licensing information, and instructions on how to build the package. [15:08] Once this source package is compiled, the build process provides binary packages, which are the .deb files users can install. [15:08] Every time a new version of an application is released, or when someone makes a change to the source code that goes into Ubuntu, the source package must be uploaded to Launchpad’s build machines to be compiled. [15:09] The resulting binary packages then are distributed to the archive and its mirrors in different countries. The URLs in /etc/apt/sources.list point to an archive or mirror. [15:09] very day CD images are built for a selection of different Ubuntu flavours. Ubuntu Desktop, Ubuntu Server, Kubuntu and others specify a list of required packages that get on the CD. These CD images are then used for installation tests and provide the feedback for further release planning. [15:11] Also should I note that in the last 2-3 cycles we have been putting together a huge QA lab where tests on all kinds of packages are run, which obviously also help with the release planning. :) [15:11] Ubuntu’s development is very much dependent on the current stage of the release cycle. [15:11] We release a new version of Ubuntu every six months, which is only possible because we have established strict freeze dates. [15:11] With every freeze date that is reached developers are expected to make fewer, less intrusive changes. [15:12] If you have a look at https://wiki.ubuntu.com/QuantalQuetzal/ReleaseSchedule you can see the release schedule for the current 12.10 release. [15:12] You can see that we just went past Feature Freeze. [15:12] Feature Freeze is the first big freeze date after the first half of the cycle has passed. At this stage features must be largely implemented. [15:12] The rest of the cycle is supposed to be focused on fixing bugs. === jeff_ is now known as Guest22207 [15:13] After that the user interface, then the documentation, the kernel, etc. are frozen, then the beta release is put out which receives a lot of testing because many deem it stable enough to play around with it. [15:13] From the beta release onwards, only critical bugs get fixed and a release candidate release is made and if it does not contain any serious problems, it becomes the final release. [15:13] Any questions so far? [15:13] Come on, don't be shy. :) [15:14] marcos asked: QA in this context is Question and Answer? [15:15] marcos, sorry, I could have made it clearer - no, QA in the sentence above meant "Quality Assurance" [15:15] everything that goes from pro-active testing (test suites run automatically and manual testing) to work on bug reports, testing CD images, etc. [15:16] QA is what makes Ubuntu not good, but great :) [15:16] conner_bw asked: What is the criteria for " it does not contain any serious problems" [15:17] conner_bw, that's not always a clear-cut decision, but data-loss, critical program crashes and things like that certainly count as show-stoppers [15:17] agmenor_ asked: As an app developer, which version should I be running ? When ? [15:17] ClassBot, as an app developer it might be good enough to run the latest stable, which is 12.04, but as somebody who works on Ubuntu itself, it's necessary to run 12.10 - and if only in a virtual machine [15:18] you need to be able to test the changes you want to introduce into Ubuntu in a live environment [15:18] paulo_gomes asked: say an application releases a new version of its software after the freeze in ubuntu do we have to wait for the next release? [15:18] ClassBot, that depends - if it's early in the cycle it can go in without problems - if it's a bug fix release you can still get it in after the freeze [15:18] but the later in the cycle, the harder it will be to get it past the release team [15:19] but for a good reason: we need to have time to test things [15:19] (I'll talk more about this later on.) [15:19] conner_bw asked: What is the criteria for " it does not contain any serious problems", like i'm using 12.04 and am subscribed to a few bugs which were clearly released anyway (Libre Office Launcher Integration, for example) === nick is now known as Guest24273 [15:20] conner_bw, sometimes a decision must be made to keep the release rolling out on the right day - it's not always easy [15:20] Liverpudlian asked: Is developing apps different when it comes to LTS versions? === arvislacis is now known as Guest35542 [15:21] Liverpudlian, LTS versions are of course interesting because many decide to stay on that particular version. So there is more interest of app authors to get their app on the LTS. [15:21] obounaim asked: What is the URL of QA? [15:21] obounaim, https://wiki.ubuntu.com/QATeam/ might work as a good introduction into everything the team does. [15:21] dsp__ asked: how to stop all these logs, i just wanna see your chat msgs.... its confusing [15:22] dsp__, type "/ignore #ubuntu-classroom CRAP NOTICES SNOTES CTCPS JOINS PARTS QUITS KICKS MODES WALLOPS NICKS DCC DCCMSGS CLIENTNOTICES CLIENTCRAP CLIENTERRORS HILIGHTS" into the chat window, but without the " [15:22] C1sM0 asked: Are .deb files created automatically once the source code has been send up? [15:23] C1sM0, yes, they land in the queue because we don't have an infinite amount of build machines, but if the queue is largely empty you can expect your package to be built and ready in the archive within an hour [15:23] nja asked: Why does the Work Item Iteration on the Quantal Release Schedule show A-2 at the top instead of A-1? [15:24] nja, I assume you are talking about http://status.ubuntu.com/ubuntu-quantal/? I'm not quite sure about this to be honest. [15:24] Maybe because Alpha 2 was the last milestone? [15:24] Sorry, don't know. [15:24] marcos asked: App Showdown accept closed source and pay applications too? [15:24] marcos, not as far as I know, no === piro is now known as Guest22304 [15:25] maybe we can try to direct our focus away from apps for a little bit - in this session I will try to talk a bit more about the development of Ubuntu itself - although large parts apply for app development and packaging as well [15:25] _et asked: Builds done using which C-I tool? [15:25] _et, I don't know C-I tool - all our packages are built on Launchpad, which is an Open Source platform built with Zope and Python - the build process itself uses sbuild [15:26] ziviani asked: who defines the requirements for each GA release? what if some features are no able to be developed until the freezing date? [15:26] ziviani, if features can't get done in the cycle, they are dropped and left for next cycle to be implemented. [15:26] The decision is made by the release team and the respective team leads. [15:26] nja asked: Why does Lernid have a "Terminal" tab? [15:27] nja, when we get to a live demo part you can try out what the presenter is saying live on your system [15:27] smartboyhw asked: Then what about software packaging? [15:28] smartboyhw, I'm not quite sure I understand your question. Ubuntu Development is a lot about Software Packaging and its integration with each other. Maybe you can ask another question? [15:28] marcos asked: Update releases (like 12.04.1) accept new features? [15:28] marcos, no, it will largely "just" include security and stability fixes, updated translations and the like [15:29] it's just impossible to direct your attention to developing two releases (12.04 and 12.10 for example) at the same time [15:29] Henrich asked: how many buildds are there? can we see the list? [15:29] Henrich, yes - it's available here: https://launchpad.net/builders/ [15:30] Alright - that was a true avalanche of questions - thanks everyone! :) [15:30] My fingers are aching, but not bleeding yet, so let's keep going. [15:30] Thousands of source packages, billions of lines of code, hundreds of contributors require a lot of communication and planning to maintain high standards of quality. [15:30] At the beginning of each release cycle we have the Ubuntu Developer Summit where developers and contributors come together to plan the features of the next releases. [15:31] Every feature is discussed by its stakeholders and a specification is written that contains detailed information about its assumptions, implementation, the necessary changes in other places, how to test it and so on. [15:31] This is all done in an open and transparent fashion, so even if you can not attend the event in person, you can participate remotely and listen to a streamcast, chat with attendants and subscribe to changes of specifications, so you are always up to date. [15:31] As you can see on https://uds.ubuntu.com/ the next UDS is going to be in Copenhagen - if you're there, make sure you drop by. [15:32] Not every single change can be discussed in a meeting though, particularly because Ubuntu relies on changes that are done in other projects. === Zubozrout is now known as zubozrout [15:32] That is why contributors to Ubuntu constantly stay in touch. Most teams or projects use dedicated mailing lists to avoid too much unrelated noise. [15:32] For more immediate coordination, developers and contributors use Internet Relay Chat (IRC). All discussions are open and public. [15:33] Another important tool regarding communication is bug reports. Whenever a defect is found in a package or piece of infrastructure, a bug report is filed in Launchpad. [15:33] All information is collected in that report and its importance, status and assignee updated when necessary. This makes it an effective tool to stay on top of bugs in a package or project and organise the workload. [15:33] Most of the software available through Ubuntu is not written by Ubuntu developers themselves. Most of it is written by developers of other Open Source projects and then integrated into Ubuntu. [15:33] These projects are called “Upstreams”, because their source code flows into Ubuntu, where we “just” integrate it. [15:34] The relationship to Upstreams is critically important to Ubuntu. It is not just code that Ubuntu gets from Upstreams, but it is also that Upstreams get users, bug reports and patches from Ubuntu (and other distributions). [15:34] The most important Upstream for Ubuntu is Debian. Debian is the distribution that Ubuntu is based on and many of the design decisions regarding the packaging infrastructure are made there. [15:34] Traditionally, Debian has always had dedicated maintainers for every single package or dedicated maintenance teams. In Ubuntu there are teams that have an interest in a subset of packages too, and naturally every developer has a special area of expertise, but participation (and upload rights) generally is open to everyone who demonstrates ability and willingness. [15:34] average_drifter asked: I just forked someone's repo of HTOP 1.0.1 from github, and made a patch, the person merged my patch. how can make sure that this patch gets into the Ubuntu repository together with all the stuff he added ? (he added support for thread monitoring). I'm sure a lot of people know what HTOP is.. it's a pretty good utilitary for monitoring processes(kind of like top) [15:35] average_drifter, Great. Just what I wanted to talk about next. :) [15:35] NickE asked: Does Launchpad host everything to do with a given project (unless it is upstream)? [15:36] NickE, if you decide to use Launchpad to host your project, you can put all the code branches, the bug reports, translations, the specifications, the releases and support tracker into Launchpad [15:36] and if a project decides to not use Launchpad, you can easily set up a code mirror [15:36] and daily builds and the like [15:36] raju asked: Whats the ground work have to do , to join in a current running project as one of its the developer ? [15:37] raju, I would always recommend to have a look out (and ask for) some simple bugs you can start working on. [15:37] Luckily this week we'll have a session about fixing small bugs in Ubuntu and what to do about them. [15:37] Tomorrow, 17:00 UTC. [15:38] Alright, since there's so much interest in fixing bugs and getting stuff into Ubuntu, let's talk a bit about it. [15:38] Getting a change into Ubuntu as a new contributor is not as daunting as it seems and can be a very rewarding experience. It is not only about learning something new and exciting, but also about sharing the solution and solving a problem for millions of users out there. [15:38] Open Source Development happens in a distributed world with different goals and different areas of focus. [15:38] For example there might be the case that a particular Upstream is interested in working on a new big feature while Ubuntu, because of the tight release schedule, is interested in shipping a solid version with just an additional bug fix. [15:39] hat is why we make use of “Distributed Development”, where code is being worked on in various branches that are merged with each other after code reviews and sufficient discussion. [15:39] In the example I just mentioned it would make sense to ship Ubuntu with the existing version of the project, add the bugfix, get it into Upstream for their next release and ship that (if suitable) in the next Ubuntu release. It would be the best possible compromise and a situation where everybody wins. [15:40] More specifically: To fix a bug in Ubuntu, you would first get the source code for the package, then work on the fix, document it so it is easy to understand for other developers and users, then build the package to test it. [15:40] After you have tested it, you can easily propose the change to be included in the current Ubuntu development release. A developer with upload rights will review it for you and then get it integrated into Ubuntu. [15:41] If that makes you curious, that's great - I'll give you some links to docs later on. The mechanics of fixing a bug are always the same and you learn the tools pretty quickly. It's sometimes just that you have a particularly tricky bug in front of you. But there's always people who can help you out. :) [15:41] raju asked: Sorry if its sounds like silly doubt but i want to ask it . how a starting user can estimate the Bug strength as simple one or complex one ? [15:42] raju, it's sometimes not easy to estimate. It's quite common to think "hah, this one is going to be easy" and then you spend hours on fixing it. [15:42] It happens to me all the time. :) [15:42] The good thing is though that we picked a bunch of easy to fix tasks, which Stefano will talk about in his session tomorrow [15:42] and which are mentioned in the docs I'll point out later on [15:43] When trying to find a solution it is usually a good idea to check with Upstream and see if the problem (or a possible solution) is known already and, if not, do your best to make the solution a concerted effort. [15:43] prashanth asked: Where do you usually get the source code? [15:44] prashanth: it's all in Launchpad - a quick "apt-get source " or "bzr branch ubuntu:" will get the source for you - but more on that specifically later on :) [15:44] When fixing bugs additional steps might involve getting the change backported to an older, still supported version of Ubuntu and forwarding it to Upstream. [15:44] The most important requirements for success in Ubuntu development are: having a knack for “making things work again,” not being afraid to read documentation and ask questions, being a team player and enjoying some detective work. [15:45] More questions? :) [15:45] prashanth asked: where can we get a list of Upstreams? [15:46] prashanth: Good question. To get a page with all info about a package in Ubuntu, you can for example go to https://launchpad.net/ubuntu/+source/gedit [15:47] If you go to https://launchpad.net/gedit though (note the missing "ubuntu/+source"), you get the information about Upstream [15:47] geekette86 asked: i wanna know more about apport-retrace [15:48] apport-retrace is a very nice tool - what it does for us is that if a program crashes and it saves a core dump with the current state of the program's used memory, apport-retrace can get us a human-readable output of the crash stacktrace, so the functions which were called in which part of the code, which line, which variables and so on [15:49] https://wiki.ubuntu.com/DebuggingProgramCrash has more info about this generally [15:49] Henrich asked: If you find same problem in upstream (e.g. Debian), do you report it to upstream bug tracker? if not, why? [15:49] Henrich, yes, you do that if you can be reasonably sure that the problem happens there as well and not because Ubuntu has a modified version of it [15:49] neoteric asked: If source can be mirrored into Launchpad would it then be possible that someone fixes a bug in the LaunchPad version that is not fixed in an Upstream package? If so, what then? [15:50] neoteric, Unfortunately Launchpad can't push code to the Upstream project, so we need to forward patches 'manually'. [15:50] raju asked: please explain more about this " a good idea to check with Upstream and see if the problem (or a possible solution) is known already and, if not, do your best to make the solution a concerted effort" [15:50] There are 10 minutes remaining in the current session. [15:50] Ok, let's say you find a problem in gedit. It crashes for some reason. [15:51] First you might want to check if there's a new release available which fixes the issue, if not you could try to check the upstream commits if a recent change fixed the issue. [15:51] If that's not the case, you could have a look at upstream's bug tracker and see if somebody reported the issue already and if a fix is in progress. [15:51] In that case you can then help out to test the fix and give valuable feedback. [15:52] If the problem is not know, you'd report it with all the relevant info you have and try to help out as best as you can. [15:52] eklok asked: whats the difference between the package management and how windows does it? i never got that right. And why would it be better to wrap stuff up in packages [15:53] The good thing with package management in a distro is that we have control over what gets in. If something is unstable we don't have to put it in or we can roll back to an old version. Also can we more easily integrate things with each other because we have all the source code. [15:53] On top of that we can more easily find security issues by scanning the entire archive or rebuilding all packages with new security features, etc. [15:53] Also is it easier for our users. They get all their updates from one place and don't have to update 64325823 programs individually. [15:53] If you ask me, it's best thing since sliced bread. [15:54] ziviani asked: What are the next Ubuntu goals? Based on the huge efforts with Unity for a better user experience I believe Ubuntu is more focused in UX right now. Is it the focused area where developers could give the special attention? [15:55] A lot of attention indeed goes into UX, but there are many other teams, who for instance work on the server or make sure that everything works on all kinds of devices, etc. https://wiki.ubuntu.com/Teams might help you find something you're interested in. [15:55] exodus asked: Daniel, have you and the Ubuntu Developers Team thought about doing a session in Google Hangout or a similar type of streaming? [15:55] There are 5 minutes remaining in the current session. [15:55] exodus, yes - we've done a few of them and I plan to put on a few sessions soon again. If you follow @ubuntudev on Twitter, Identi.ca, Google+ or Facebook you should get a note. :) [15:56] nja asked: Why are you not streaming this in a G+ hangout? [15:56] In the next session there will be more instructions which you can easily copy/paste from IRC, but not from a Google+ Hangout. Maybe in the future we'll have more video casts. [15:56] Another point of interest might be people who are at work and can't watch videos, but can easily read up an IRC logs. [15:56] Also an IRC log is searchable. [15:57] That said, I know that videos can be a bit more inviting and more personal than a text-based session. [15:57] luisalvarado asked: what tools do you recommend to start working on a bug fix? [15:57] luisalvarado, more on that in the next session and Stefano's session tomorrow. [15:58] Let's take 3 minutes break so we can all get another glass of water, a cup of tea or something else. [15:58] Thanks everyone and see you in 3. :) === 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: Getting set up for Ubuntu development - Instructors: dholbach [16:00] Logs for this session will be available at http://irclogs.ubuntu.com/2012/08/28/%23ubuntu-classroom.html following the conclusion of the session. === cyrex_ is now known as luisalvarado [16:01] Excellent - welcome back to session number two at https://wiki.ubuntu.com/UbuntuDeveloperWeek :) [16:01] for those of you who joined in late, please also make sure you're in #ubuntu-classroom-chat so you can ask your questions there [16:02] and please prefix them with QUESTION: so the bot will pick them up [16:02] In this session we will set up our development environment, configure the tools and everything, so you're ready for the upcoming sessions and for getting involved [16:03] if we get through everything quick enough we can even have a look at a package and what to do with it [16:03] this session will be practical, so you might want to open a terminal already [16:03] There are a number of things you need to do to get started developing for Ubuntu. [16:03] We'll get your computer set up so that you can start working with packages, and upload your packages to Ubuntu’s hosting platform, Launchpad. [16:03] Here’s what we’ll do: [16:04] - Installing packaging-related software. This includes: Ubuntu-specific packaging utilities, Encryption software so your work can be verified as being done by you, Additional encryption software so you can securely transfer files. [16:04] - Cover the creation and configuring of your account on Launchpad [16:04] - Setting up your development environment to help you do local builds of packages, interact with other developers, and propose your changes on Launchpad. === qwerty is now known as Guest18258 [16:04] It is advisable to do packaging work using the current development version of Ubuntu. Doing so will allow you to test changes in the same environment where those changes will actually be applied and used. [16:05] This means that you will need to run Ubuntu Quantal (12.10) in some form. [16:05] Don't despair - you can run it in a chroot or virtual machine if that suits you for testing, or in a separate partition, or something along those lines. [16:05] Still it's very important to test your fixes in a live environment. [16:05] https://wiki.ubuntu.com/UsingDevelopmentReleases explains how to do it safely. [16:06] If you are now on 12.04, you're fine - you can still go through the instructions and repeat them later on. [16:06] There are a number of tools that will make your life as an Ubuntu developer much easier. You will encounter these tools later on. To install most of the tools you will need run this command: [16:06] sudo apt-get install packaging-dev [16:07] This will take a while, so just keep it running. [16:07] This command will install the following software: [16:07] - gnupg – GNU Privacy Guard contains tools you will need to create a cryptographic key with which you will sign files you want to upload to Launchpad. [16:07] - pbuilder – a tool to do a reproducible builds of a package in a clean and isolated environment. [16:07] - ubuntu-dev-tools (and devscripts, a direct dependency) – a collection of tools that make many packaging tasks easier. [16:07] - bzr-builddeb (and bzr, a dependency) – distributed version control with Bazaar, a new way of working with packages for Ubuntu that will make it easy for many developers to collaborate and work on the same code while keeping it trivial to merge each others work. [16:07] - apt-file provides an easy way to find the binary package that contains a given file. [16:08] ... and obviously many many many other good things we won't cover in this tutorial. :) [16:08] Any questions so far? [16:08] NickE asked: What VM does TestDrive use? [16:09] NickE, I think it uses kvm. [16:09] nja asked: Is it usual to get "apt-file update needed" after installing those packages? [16:09] nja, not for now, I don't think [16:09] conner_bw asked: Is bzr etched in stone? Will git be supported someday? [16:10] conner_bw, I don't know - you could try to ask in #launchpad though [16:10] personally I love bzr because it's quite easy to learn, but I know others prefer git or some other version control system [16:10] the good thing is that Launchpad can import git branches and others as well, so you can work on them natively with bzr [16:11] Ok, let's crack on. [16:11] The Debian/Ubuntu packaging tools need to learn about you . So please simply open your ~/.bashrc in a text editor and add something like this to the bottom of it: [16:11] export DEBFULLNAME="Bob Dobbs" [16:12] export DEBEMAIL="subgenius@example.com" [16:12] Please use YOUR email address and YOUR name. :) [16:12] Now save the file and either restart your terminal or run: [16:13] source ~/.bashrc [16:13] (If you do not use the default shell, which is bash, please edit the configuration file for that shell accordingly.) [16:13] Now that this is done, the packaging tools will always use your name and email address by default. [16:14] nja asked: Is bash the shell integrated in Lernid? [16:14] nja, yes, lernid uses whatever shell you normally use - the default is bash [16:14] Now that this is done, let's create GPG key. [16:14] If you have a key already, you're fine - you don't need another. [16:15] GPG stands for GNU Privacy Guard and it implements the OpenPGP standard which allows you to sign and encrypt messages and files. This is useful for a number of purposes. [16:15] In our case it is important that you can sign files with your key so they can be identified as something that you worked on. If you upload a source package to Launchpad, it will only accept the package if it can absolutely determine who uploaded the package. [16:15] To generate a new GPG key, run: [16:15] gpg --gen-key [16:15] GPG will first ask you which kind of key you want to generate. Choosing the default (RSA and DSA) is fine. Next it will ask you about the keysize. The default (currently 2048) is fine, but 4096 is more secure. [16:15] Afterwards, it will ask you if you want it to expire the key at some stage. It is safe to say “0”, which means the key will never expire. === patrick is now known as Guest90143 [16:16] The last questions will be about your name and email address. Just pick the ones you are going to use for Ubuntu development here, you can add additional email addresses later on. [16:16] Adding a comment is not necessary. Then you will have to set a passphrase, choose a safe one (a passphrase is just a password which is allowed to include spaces). [16:16] Now GPG will create a key for you, which can take a little bit of time; it needs random bytes, so if you give the system some work to do it will be just fine. === raiden is now known as Guest47874 [16:16] Maybe we will just let it sit there for a bit and do its thing, while we take care of other business. [16:17] Let's create our SSH key next. [16:17] SSH stands for Secure Shell, and it is a protocol that allows you to exchange data in a secure way over a network. It is common to use SSH to access and open a shell on another computer, and to use it to securely transfer files. For our purposes, we will mainly be using SSH to securely push changes to Launchpad. [16:17] To generate an SSH key, enter: [16:17] ssh-keygen -t rsa [16:18] The default file name usually makes sense, so you can just leave it as it is. For security purposes, it is recommended that you use a passphrase. [16:19] nja asked: Can the passphrase be changed later? [16:19] nja, yes [16:19] Next, let's set up pbuilder. [16:19] pbuilder allows you to build packages locally on your machine. It serves a couple of purposes: [16:19] - The build will be done in a minimal and clean environment. This helps you make sure your builds succeed in a reproducible way, but without modifying your local system. [16:20] - There is no need to install all necessary build dependencies locally [16:20] - You can set up multiple instances for various Ubuntu and Debian releases. [16:20] Setting pbuilder up is very easy, simply run: [16:20] pbuilder-dist create [16:20] So for quantal, you'd run: [16:20] pbuilder-dist quantal create [16:21] You can install multiple pbuilders, for each release of Ubuntu, or in the case of Debian maybe sid. This will take a while as it will download all the necessary packages for a “minimal installation”. These will be cached though. [16:21] Are there any questions up until now? [16:22] jsjgruber-l82-p asked: Why might you need a .pbuilderrc file? [16:22] in .pbuilderrc you could specify a lot of things: for example using additional mirrors, installing packages into the chroots by default, etc. [16:22] pbuilder's manpage should give you a good idea of what you might want to use. In the most cases you don't need it though. [16:23] exodus asked: Lets say I'm building a complicated package, which depends on various packages which are not already in a pbuilder slate. PackageA depends on PackageB & PackageC. After I build B & C, does pbuilder know B & C as a dependency for A. Is there a special set-up for the packages installed in pbuilder environment? [16:24] exodus, Good questions. Sometimes you might want to build a couple of packages in a certain sequence, for instance you want to transition 10 packages from libsomething1 to libsomething 2 [16:25] in this case you can teach pbuilder to re-use packages you already built and to add them to its sources [16:25] lengau asked: Why does pbuilder require root permissions? [16:25] lengau, because it uses chroot internally to create a completely separate minimal system in which it performs the build [16:26] TheLordOfTime asked: How do you teach pbuilder to use the already-built packages, in the hypothetical exodus presented? [16:26] TheLordOfTime, https://wiki.ubuntu.com/PbuilderHowto is one I know about. [16:27] If it's outdated, I'd recommend to ask in #ubuntu-motu [16:27] Ok. I assume GPG finished creating the key for you already. Let's move on with the key then. :) [16:27] You might have gotten a message similar to this one: [16:27] pub 4096R/43CDE61D 2010-12-06 [16:27] Key fingerprint = 5C28 0144 FB08 91C0 2CF3 37AC 6F0B F90F 43CD E61D [16:27] uid Daniel Holbach [16:27] sub 4096R/51FBE68C 2010-12-06 [16:27] In this case 43CDE61D is the key ID. [16:28] Next, you need to upload the public part of your key to a keyserver so the world can identify messages and files as yours. To do so, enter: [16:28] gpg --send-keys [16:28] This will send your key to one keyserver, but a network of keyservers will automatically sync the key between themselves. Once this syncing is complete, your signed public key will be ready to verify your contributions around the world. [16:28] nja asked: What are all these generated keys for? [16:29] nja, if you upload a package to Launchpad (for instance to your personal package archive), it will check if the package was really done by you [16:29] the GPG key is used to sign a package and make sure it wasn't tampered with and that it originates from you [16:30] the SSH key is used for Bazaar, which I'll talk a bit more in a minute - it basically pushes your changes to LP using a secure connection [16:30] With a basic local configuration in place, your next step will be to configure your system to work with Launchpad. [16:30] Launchpad is the central piece of infrastructure we use in Ubuntu. It not only stores our packages and our code, but also things like translations, bug reports, and information about the people who work on Ubuntu and their team memberships. You will also use Launchpad to publish your proposed fixes, and get other Ubuntu developers to review and sponsor them. [16:31] Sponsoring basically means "upload a package for somebody else". This is what needs to be done if you want to get a fix into Ubuntu and you don't have upload rights yet. [16:31] You will need to register with Launchpad and provide a minimal amount of information. This will allow you to download and upload code, submit bug reports, and more. [16:32] Besides hosting Ubuntu, Launchpad can host any Free Software project. https://help.launchpad.net/ has more information if you should generally get stuck somewhere. [16:32] If you don’t already have a Launchpad account, you can easily create one (https://launchpad.net/+login). If you have a Launchpad account but cannot remember your Launchpad id, you can find this out by going to https://launchpad.net/~ and looking for the part after the ~ in the URL. [16:32] TheLordOfTime asked: I've seen this thing about the Ubuntu Code of Conduct. Do I need to sign that to develop for Ubuntu? [16:33] TheLordOfTime, yes - if you want to become part of the team, become an Ubuntu member (get voting rights, an @ubuntu.com address and be generally recognised for your work), you will have to sign it [16:33] there's no hidden clauses or anything crazy in there - you won't sign up for a washing machine you'll have to pay [16:33] the code of conduct basically says to us all: be excellent to each other [16:34] and that's generally a good thing to comply with :) [16:34] man_let asked: can less intelligent people contribute? [16:34] man_let, We have enough tasks for everyone in Ubuntu. No matter what your interest, ability or preference might be. [16:35] nja asked: HELP! My LaunchPad password reset won't arrive! [16:35] nja, I think somebody mentioned it in the chat window already, but you can ask in #launchpad for help. [16:35] and you can follow the instructions from the log or the documentation later on [16:36] Launchpad’s registration process will ask you to choose a display name. It is encouraged for you to use your real name here so that your Ubuntu developer colleagues will be able to get to know you better. [16:36] When you register a new account, Launchpad will send you an email with a link you need to open in your browser in order to verify your email address. If you don’t receive it, check in your spam folder. [16:36] The new account help page (https://help.launchpad.net/YourAccount/NewAccount) on Launchpad has more information about the process and additional settings you can change. [16:37] You need to tell Launchpad about GPG key, so to find about your GPG fingerprint, please run: [16:37] gpg --fingerprint [16:37] and it will print out something like: [16:37] pub 4096R/43CDE61D 2010-12-06 [16:37] Key fingerprint = 5C28 0144 FB08 91C0 2CF3 37AC 6F0B F90F 43CD E61D [16:37] uid Daniel Holbach [16:37] sub 4096R/51FBE68C 2010-12-06 [16:37] Head to https://launchpad.net/~/+editpgpkeys and copy the “Key fingerprint” into the text box. In the case above this would be 5C28 0144 FB08 91C0 2CF3 37AC 6F0B F90F 43CD E61D. Now click on “Import Key”. [16:37] Launchpad will use the fingerprint to check the Ubuntu key server for your key and, if successful, send you an encrypted email asking you to confirm the key import. Check your email account and read the email that Launchpad sent you. [16:37] If your email client supports OpenPGP encryption, it will prompt you for the password you chose for the key when GPG generated it. Enter the password, then click the link to confirm that the key is yours. [16:38] Back on the Launchpad website, use the Confirm button and Launchpad will complete the import of your OpenPGP key. [16:38] Find more information at https://help.launchpad.net/YourAccount/ImportingYourPGPKey [16:38] And then you can do the same with your SSH key. [16:38] Open https://launchpad.net/~/+editsshkeys in a web browser, also open ~/.ssh/id_rsa.pub in a text editor. [16:39] Make sure it's ~/.ssh/id_rsa.pub (public part) and not ~/.ssh/id_rsa (secret part) [16:39] :) [16:39] This is the public part of your SSH key, so it is safe to share it with Launchpad. Copy the contents of the file and paste them into the text box on the web page that says “Add an SSH key”. Now click “Import Public Key”. [16:39] For more information on this process, visit the creating an SSH keypair page on Launchpad: https://help.launchpad.net/YourAccount/CreatingAnSSHKeyPair [16:39] thotp asked: might the GPG key changes when i re-install the operating system? [16:40] thotp: it might be worth backing up the ~/.gnupg directory [16:40] you should be able to just copy it back [16:40] The last thing I wanted to mention briefly - I know we rushed through a lot, so I want to make some time for more questions - is setting up Bazaar, which should be pretty quick. [16:40] Bazaar is the tool we use to store code changes in a logical way, to exchange proposed changes and merge them, even if development is done concurrently. It is used for the new Ubuntu Distributed Development method of working with Ubuntu packages. [16:41] o tell Bazaar who you are, simply run: [16:41] bzr whoami "Bob Dobbs " [16:41] bzr launchpad-login subgenius [16:41] whoami will tell Bazaar which name and email address it should use for your commit messages. With launchpad-login you set your Launchpad ID. This way code that you publish in Launchpad will be associated with you. [16:41] Again: If you can not remember the ID, go to https://launchpad.net/~ and see where it redirects you. The part after the “~” in the URL is your Launchpad ID.) [16:42] And that should be pretty much it. [16:42] One thing you also might want to do is open the "software properties" and make sure the "Sources" part is checked. This will let you download sources from all packages in Ubuntu easily. [16:43] or just make sure you have deb-src lines in /etc/apt/sources.list [16:43] eklok asked: what keeps you motivated to programm/debug? isnt it exhausting to deal with this every day. I want to motivate myself but i always fail [16:43] eklok, the people and the feeling that if a bug is fixed, it's not just fixed for me but for many millions of users out there [16:43] also do I learn something new all the time, which is great [16:44] of course it can be hard to solve a problem, but you can always ask for help [16:44] man_let asked: what if 2 ppl have the same public key? [16:44] man_let, there have been collisions of gpg keys already, but they are very rare - can somebody dig out a link about this? [16:44] nja asked: What can I do if I have 2 subkeys. How do I know which one to delete? [16:45] I hope http://www.gnupg.org/gph/en/manual.html#AEN282 can help you with it [16:45] Any more questions? :) [16:46] nja asked: Can I not see what one was created most recently? [16:46] If you mean GPG, I'm afraid I don't have the answer right now. Maybe somebody in #ubuntu-classroom-chat or #ubuntu-motu can help. [16:46] Sorry [16:47] If you followed all the instructions, the following example should work: [16:47] Please run: [16:47] bzr branch ubuntu:hello [16:47] This will give you a Bazaar branch of the "hello world" package in Ubuntu and all its revisions in Ubuntu. [16:47] then please: [16:47]