=== pgraner-afk is now known as pgraner [01:23] hello ... does anyone know if there is a program or api that i can use to structure plain text? [01:24] like if i have a tree like structure that i want to lay out in plain text, but dont want to bother with the spacing and placement of the edges and nodes [01:24] is there something that would take care of that? [01:48] what do you want the output to look like and what does your input look like? === abhi_nav_ is now known as abhi_nav === Ddorda1 is now known as Ddorda === abhi_nav_ is now known as abhi_nav === yofel_ is now known as yofel [09:29] hi === abhi_nav is now known as abhijit === abhijit is now known as abhijit_ === abhijit_ is now known as abhijit__ === abhijit__ is now known as abhijit === abhijit is now known as abhi_nav === abhi_nav is now known as Guest16004 === Guest16004 is now known as abhi_nav_ === abhi_nav_ is now known as abhijit === abhijit is now known as abhi_nav === abhi_nav is now known as abhijit === abhijit is now known as abhijit_ === abhijit_ is now known as abhijit === abhijit is now known as abhijit__ === abhijit__ is now known as abhijit === eminor2 is now known as eminor === mohi1 is now known as Mohan_chml === pjarnahomzz is now known as pjarnahom === gamerchick02 is now known as gamerchick02-awa === gamerchick02-awa is now known as gamerchick02 [16:55] alright my friends - are you ready for day 4 of Ubuntu Developer Week? [16:55] if you're here today for the very first time, please also join #ubuntu-classroom-chat (yes, lernid does that for you automatically) [16:55] it's the best place to ask questions and chat to other people while the session is going on [16:56] and please prefix your questions with QUESTION: so the host of the session can pick them up easily [16:56] https://wiki.ubuntu.com/UbuntuDeveloperWeek has the schedule of today and I promise you a lot of fun with the great speakers we have here [16:57] first up is didrocks [16:57] Monsieur Roche, comment ça va? [16:57] ça va très bien daniel :) [16:57] so, as requested by Mr Holbach, the session will be in French [16:57] kidding :) [16:57] haha === abhijit_ is now known as abhijit [16:57] lol [16:58] that was the obvious answer of a member of the French mafia :) [16:58] * didrocks is eager to see #ubuntu-devel in french :) [16:58] next jump will be UDS! [16:58] you still have 2 minutes to get a cold or hot beverage - enjoy day 4 of UDW :) [17:00] didrocks: the stage is yours :) === 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: Create An Application For Ubuntu With Quickly - Instructor: didrocks [17:00] great! thanks dholbach [17:01] so, some quick words of presentation first [17:01] my name is Didier Roche, I'm working in the ubuntu desktop team on updating GNOME and UNE (Ubuntu Netbook Edition) [17:01] also, as a spare time project with Rick Spencer, I'm hacking on Quickly [17:02] first question will be from me :) who knows about Quickly? (please answer on -chat) [17:02] good, the session will be useful so :) [17:02] a lot of people having no idea what is it [17:02] So, few words about it [17:03] Quickly is to bring back fun in development [17:03] Rick, the person who created the Quickly idea, call it, among other things, an "Application Templating System" [17:03] the essence of the project is to provide you boiler plate for the kind of program you want to write [17:03] so the code that you would have to write for every program of a certain type gets generated for you [17:04] that part is called the "boiler plate" [17:04] we have different boiler plates right now: [17:04] ubuntu-application, ubuntu-cli and ubuntu-pygame in lucid [17:04] but Quickly is also a set of commands [17:05] the commands are designed to integrate with the Ubuntu Application infrastructure [17:05] thinks like bzr, launchpad, PPAs, etc.. [17:05] and the commands are what make all that work [17:05] The moto of Quickly is "Easy and Fun" [17:05] while I'll answer to the first set of questions, you can install it (not mandatory to follow the session): sudo apt-get install quickly [17:06] QUESTION: Is quickly and IDE? [17:06] no, it's not, it's a Command Line tools, that brings a lot of love [17:06] the core of Quickly brings advanced shell completion, it will suggest you everytime what to do [17:06] there is a Quickly API, (in trunk only right now), so if people want to integrate if with any IDE, go go go :) [17:07] QUESTION: Is it a code generator or is it more like a To-do list? [17:07] it's generate a boiler plate of code [17:07] but then, don't touch it [17:07] let me find a screenshot of what the ubuntu-application template generates for you [17:08] http://blog.didrocks.fr/public/projects/quickly/.Capture-Myproject_m.jpg [17:08] this is what you get after the first "create" command [17:08] you can then modify it to a wide range of applications, there is no more action on the code itself [17:09] QUESTION: Quickly will be ported to other distros??? [17:09] applications created with Quickly should work with any distros [17:09] there is no dependency on Quickly itself (it's not a framework) [17:09] Quickly itself is being packaged in fedora and gento [17:09] gentoo [17:09] we are waiting for templates for them so :) [17:10] QUESTION: Will quickly create MeeGo/Maemo buildable programs? [17:10] see above, you just need a template for that :) [17:10] QUESTION: How does Quickly differ from Acire/python- nippets? [17:10] well, acire is writtent with Quickly :) [17:10] written* [17:10] also, some of you may use Lernid [17:10] this is another Quickly app [17:11] so, you can see that Quickly can enables you to create a lot of different apps for different purpose [17:11] QUESTION: is quickly a ubuntu project or third party project? [17:12] as of today, the Quickly devs (mostly me, Rick making awesome work on Quickly-Widgets I'll talk about later), uses ubuntu [17:12] so, we develop templates for ubuntu first [17:12] but, the project is really template oriented [17:12] that means, you have no requirement to use python, or ubuntu [17:12] I'll go on and answer remaining questions then :) [17:13] so, as some of you have seen, Quickly brings a lot of tools, so downloading can take a while [17:13] Note that the current version is 0.4.3 on lucid [17:13] 0.4 brings a lot of news over 0.2, you can see that in previous ubuntu devweek sessions [17:14] the rest of the class will be in 4 parts: [17:14] Creating your app [17:14] Editing the UI [17:14] Writing Code [17:14] Packaging and PPAs [17:14] (so, to answer a question, yes, Quickly creates packages) [17:15] so, creating an app [17:15] this is a single command, $ quickly create ubuntu-application [17:15] (for ubuntu-cli, replace ubuntu-application by ubuntu-cli, for ubuntu-pygame, … you understand :)) [17:16] we support hyphen, spaces and a lot of fun in project_name [17:16] you can see that Quickly run the application for you [17:16] so, you already have a complete application ready ! [17:16] not really fancy, but you have preferences integrations, menus, about box, easter eggs :) [17:16] all what an application need! [17:17] (of course, wait for Quickly to be installed to run the command) [17:17] so, Quickly created a folder for you [17:17] you can cd into it [17:17] there, if you use tabulation, you should see that you have access to a lot of commands now [17:18] I won't enter and details all of them [17:18] the most important is… testing! [17:18] quickly run will launch your application [17:18] then, edit the code: [17:18] quickly edit [17:19] this will launch gedit and open all your development files there [17:19] there, you can remove what you want (like the preferences code), and tweak from the default [17:19] so, Quickly is opinionated choices [17:19] those choices are made by the template [17:19] for instance, in the ubuntu-application template, you have: [17:19] - python as a language to develop in [17:19] - glade for editing the GUI [17:20] - gedit as default editor (you can override this by exporting the EDITOR variable) [17:20] - pygtk for the toolkit [17:20] - desktopcouch for storing persistent data [17:20] - launchpad integration [17:20] all is chosen for helping you starting with your app [17:21] then, if you are confident enough and know what you need, you can remove each block you don't want and replace by yours [17:21] or create your own template even! [17:21] alucardni | didrocks: you missed bzr for version control ;-) [17:21] of course bzr :) [17:21] thanks! [17:22] the idea is really to drive development and help opportunistic developer to know "where to start" [17:22] rather than beeing lost in choices [17:22] for helping starting development too, we have a tutorial: [17:22] quickly tutorial [17:23] that will fire up yelp to have a step by step app to develop [17:23] and I heard that an "ubuntu developer manual" is on the way [17:23] let's move on, I see some questions, but nothing related to that :) [17:23] so, editing the UI. [17:24] as told previously, we use glade for that in the ubuntu-application template [17:24] to fire it up, just use quickly design [17:24] glade is really awesome for editing a GUI graphically [17:24] and really integrates in a easy way with python too [17:24] QUESTION: what is glade? a short intro about it, please? [17:25] glade is a tool for building gtk-based UI [17:25] let me find a screenshot [17:25] http://glade.gnome.org/images/glade-main-page.png [17:25] you choose your components and draw them on the application area [17:25] the quickly tutorial explains the basic of this [17:26] in fact, Glade is a UI editing tool, that creates the XML you need to describe your windows and widgets [17:26] don't worry because the quickly template totally handles keeping the code and the XML hooked up [17:26] if others templates, like kubuntu comes, we assume it won't use glade, obviously :) [17:27] hence the "design" command to launch it [17:27] so here are some tips for using Glade if you are new to Glade [17:27] first, adding widgets works like a fill tool [17:27] you click the widget you want in the toolbox, and then click where you want it to be on the window [17:27] the widgets will then fill the space alloted to it [17:27] to layout the form, you use HBoxes and VBoxes [17:28] an HBox handles Horizontal layout, and a VBox handles vertical [17:28] so you will find yourself putting lots of boxes within boxes [17:28] when you add a widget to a window, you can select it in the "inspector" tree if it is hard to select in the window itself' [17:28] boxes can be hard to select in the window, for example [17:28] if a widget is in a box, use the position property in the "Property editor" window in the "packing" tab to change the order [17:29] you can also set the pack type to start or end to change the order [17:29] Fill and Expand control sizing [17:29] while Border and Padding control spacing [17:29] whenever possible, you should use "Stock" widgets [17:29] they get translated, the right icons, etc... automatically [17:29] finally, if you want to add a dialog to your project: [17:29] 1. close glade [17:30] 2. run: quickly add dialog [17:30] 3. quickly glade [17:30] ooops [17:30] quickly design :) [17:30] quickly glade was in previous version of Quickly [17:30] this way, Quickly helps you to ship all files to get access to the new window [17:31] of course, your code can have bugs [17:31] what's best for debugging than a debugging tool where you can see variable values and such, step by step? [17:31] Quickly uses winpdb for that. Just run "quickly debug" and you can add breakpoints and such [17:32] ok, let's say you are happy with your project [17:32] now, you want to share with someone, or even release? [17:32] let's say you want to release your first version [17:33] it's pretty easy, just: [17:33] $ quickly release [17:33] this will version your release to YY.MM (the ubuntu way of marking an ubuntu version) === dark is now known as Guest88529 [17:33] you will be asked to bind with a Launchpad project you created [17:34] it will licence all your files (default is GPLV3 if you didn't run quickly licence by hand before) [17:34] it will tag your release, change evertything for your, drop the COPYING files to get a well licensed project [17:34] push your code to launchpad [17:34] also, the about box will contain the version of the current release, the credit, the copyright, the url to the project [17:35] (http://blog.didrocks.fr/public/projects/quickly/Capture-A_propos_de_Slip_Cover.png [17:35] for instance [17:35] and all that for free! No need to maintain it manually [17:35] in addition to that, it will create an ubuntu package [17:35] detecting all dependencies for you [17:36] will collect all your "quicky save" messages (quickly save is to take snapshot of your code. For those you know, it triggers a bzr commit) [17:36] it will upload your package to launchpad, in a ppa for people trying our your application [17:37] it will also upload your upstream tarball, sign it, push it to launchpad, and make an annoucement with your changes annoucement [17:37] dotblank | QUESTION: Does quickly walk you through steps with gpg? [17:37] if you don't have a gpg key already, Quickly will help you to create one [17:37] (same for ssh) [17:37] it won't upload it to launchpad yet, we are working with Launchpad guys to get that integrated nicely [17:38] in any case, it will tell you before uploading if something got wrong :) [17:38] QUESTION: is it possible to change the way of versioning e.g. to 0.0.1 as fist build? [17:38] just run quickly release 0.0.1 [17:38] then, you have to specify manually at each release the version number [17:39] but YY.MM is really the short approach and avoid a lot of collision :) [17:39] so, in a nutshell, in two commands: [17:39] quickly create ubuntu-application foo [17:39] quickly release [17:39] I have a licenced project, pushed to launchpad, with tarballs, announces and ubuntu package to share to the world! [17:40] sometimes, you maybe want to get some testing [17:40] and not release really to get people testing this [17:40] for local testing, you can use: [17:40] quickly package [17:40] this will create a package in your directory that you can install [17:40] for sharing in a ppa, use instead: quickly share [17:41] this won't change anything, won't licence your project, won't upload tarball [17:41] but at least, you can get some testing :) [17:41] QUESTION: does quickly package (version here) also work in order to force a version? [17:41] of course, but think that you can't upload to your ppa a version with a lower version than previous upload [17:42] you will see that there are a lot of other commands to manipulate your project [17:42] like quickly configure to configure the ppa you want to upload, the bzr branch where you want to push/pull, additional dependencies that you want to add… [17:43] if you use shell completion on license, you will see that we support a wide range of licence too. Adding a new one (or a custom is really easy) [17:43] last part I want to discuss is Quickly widgets before taking the bunch of pending questions :) [17:43] so, quickly widgets are widgets that help you to make your life easy [17:44] contrary to Quickly, this is for python only [17:44] in one line of code, you can show a dialog asking for a question and get the answer [17:44] this is generally taking 6-8 lines of codes [17:44] in 5 lines, you can get a CouchGrid [17:45] you can imagine that as a tabular, where you can store persistent information, synchronised between your use (using couchdb) [17:45] hosts* [17:45] it will detect for you the type of your column, you can add a filter in two lines, and such [17:46] this is really really great stuff and avoiding copying 50-60 lines from random websites [17:46] quickly-widgets come with a lot of widget [17:46] QUESTION: Where can we find information about Quiqly-widgets (couch-grid etc)? [17:46] as Rick is the main developer, you can find a lot of fun videos over the web [17:47] http://theravingrick.blogspot.com/ is your central info place [17:47] ok, taking questions now :) [17:47] let me a second to take them one by one [17:48] QUESTION: Say I don't need the preferences dialog in my project can I delete it from the project? [17:48] exactly, as told previously, you can remove any part of the code you don't want really easily [17:48] this is mainly for the preferences dialog removing a file and call to it [17:48] QUESTION: Is template creation difficult? [17:48] not at all, I've even written a tutorial on that [17:48] one sec [17:49] http://blog.didrocks.fr/index.php/post/Build-your-application-quickly-with-Quickly%3A-Inside-Quickly-part-6 [17:50] in general this set of 9 blog posts give you everything you need to know about Quickly http://blog.didrocks.fr/index.php/post/Build-your-application-quickly-with-Quickly%3A-part1 [17:50] but this was about Quickly 0.2, we have 0.4.X now [17:50] so I wrote some updates: http://blog.didrocks.fr/index.php/post/Quickly-0.4-available-in-lucid%21 [17:50] if you want to build a template upon an existing template [17:50] There are are 10 minutes remaining in the current session. [17:50] like ubuntu-cli sharing a lot in common with ubuntu-application [17:50] your can import commands between template [17:51] templates* [17:51] for instance, ubuntu-cli is really 0 line of code! [17:51] I just import every commands I need from ubuntu-application template [17:51] (apart from design which makes no sense for a command line application), and add dialog [17:51] so, it's really easy to create a template :) [17:52] you can even wrote you template in perl with some C boiler plate if you want some fun [17:52] Quickly is language agnostic [17:52] that comes to the question: [17:52] QUESTION: what is the difference between gambas and quickly? [17:52] gambas is (AFAIK), really binded with python [17:52] Quickly is written in python but template can be whatever you want [17:53] also gambas doesn't handle packaging and such [17:53] Quickly is really "helping your developping your project from start to the end" [17:53] QUESTION: Can quickly use existing source code? [17:53] sure, bughugger, another quickly project wasn't written for Quickly first [17:54] but migrate it to Quickly took half an hour approximately [17:54] it's just moving files in the right folder and add some glue [17:54] you won't get automatically launchpad integration for instance [17:54] (when you release your project with Quickly, project get integration like "Help on/Report a bug" in the help menu) [17:55] but you will get all the rest for free, which is already a lot :) [17:55] QUESTION: How hard is it to remove the couchdb support from the template? [17:55] hmm [17:55] I would say it's basically removing the preferences dialog [17:55] There are are 5 minutes remaining in the current session. [17:55] so, not hard at all :) [17:55] QUESTION: we CAN create templates for templates then? [17:56] sure, I don't see the point as quickly quickly already help you to create subtemplates [17:56] it's copying to ~/quickly-templates all what you need [17:56] I think that's it for question. If I forget some, yell [17:57] in the remaining times, some links: [17:57] - so, the blog post I posted before http://blog.didrocks.fr/index.php/post/Build-your-application-quickly-with-Quickly%3A-part1 and http://blog.didrocks.fr/index.php/post/Quickly-0.4-available-in-lucid%21) [17:57] - https://launchpad.net/quickly of course [17:57] - #quickly on freenode for support and development on Quickly [17:58] also, some reviews on 0.2 version: [17:58] - http://lwn.net/Articles/351522/ [17:58] - http://arstechnica.com/open-source/news/2009/08/quickly-new-rails-like-rapid-development-tools-for-ubuntu.ars [17:58] - http://www.maximumpc.com/article/news/canonical_releases_quickly_framework_speed_linux_app_development [17:58] we got some good contributions and I want to thank everyone helping to make Quickly better [17:58] (approximately 10 different people have contributed to the code so far, it's already a lot!) [17:59] hope that you can join, we don't bite and share the fun developping :) [17:59] I guess now, it's vish's who will explain you how to help Ubuntu in a night! [17:59] thanks didrocks! [17:59] take it away vish :) [18:00] Hope everyone enjoyed the Quickly session from the always amazing didrocks! [18:00] Never an easy task following didrocks! ;-) [18:00] vish: don't say that :-) === 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: Improving Ubuntu In An Evening - Instructor: vish [18:01] Hi everyone, I'm Vishnoo and I'm here to talk about how to improve Ubuntu in an evening . [18:01] I hope you are enjoying UDW and learning a lot. [18:01] Often when we introduce Ubuntu to someone and they are developers, they are surprised by Ubuntu being a community project and that they can get involved ! [18:02] One of the first things a new Ubuntu developer wants to know is how they can help and make a difference in Ubuntu OS. [18:02] Often the quickest, easiest way to do this is Hundred Papercuts Project [18:02] I will begin by giving a little bit of background information about the HundredPapercuts project, and why you should know + care about this project. :) [18:03] as always , please feel free to ask questions as you see fit , if you have questions as we go, ask on #ubuntu-classroom-chat by prefacing them with QUESTION: [18:03] So... for Karmic, the Ayatana Project together with the Canonical Design Team focused on identifying some of the “paper cuts” affecting user experience within Ubuntu. [18:04] Which we continued for Lucid and are doing it again for Maverick! [18:05] You maybe wondering what a papercut bug is? [18:05] Briefly put, A papercut is: [18:05] "a bug that will improve user experience if fixed, [18:05] is small enough for users to become habituated to it, [18:05] and is trivial to fix." [18:06] abhijit asked: can be do papercut for my lucid or I need to do it only for next proposed release? [18:06] abhijit: we usually fix for the next development release [18:06] the changes are string changes or UI changes which we cannot do after a UIF [18:06] !UIF [18:07] abhijit: UIF == User Interface Freeze [18:07] ok.. carrying on.. ;) [18:08] A paper cut is a bug that the average user would encounter on his/her first day of using a brand new installation of Ubuntu Desktop Edition (and Kubuntu too!). [18:08] You can find a more detailed definition at: https://wiki.ubuntu.com/PaperCut [18:08] Traditionally the goal is fixing 100 bugs per cycle! [18:08] [which includes 10 Kubuntu bugs , why 10 for Kubuntu? Well , it has a smaller team and as kubuntu folks like to put it, "KDE's already awesome!" ;p ] [18:09] The ayatana project convenes in #ayatana, so if you stop by there, you'll likely be able to jump right into a papercut discussion. [18:09] Now for a few examples which have been fixed in the past year: [18:09] Have a look at : http://img441.imageshack.us/img441/2964/compiz.jpg [18:09] What do you see wrong about that image? [18:10] any guesses? [18:10] matttbe: getting closer.. [18:11] matttbe: right! [18:11] * vish throws virtual candy to matttbe :) [18:11] Now have a look at : http://img22.imageshack.us/img22/3686/metacitycompositor.jpg [18:11] can everyone spot the difference , now? [18:12] Sc10: exactly! these are things users often dont notice [18:12] When you are working on something, the active window has to be on top and not the panel. When the window is on top it should not have a shadow on it! [18:12] That was fixed as part of the papercuts. [18:13] Another example: https://bugs.launchpad.net/hundredpapercuts/+bug/388949 [18:13] This fix will be released for Maverick [18:13] On the desktop if you right click , you will see an option 'Clean Up by Name' [18:14] If you were/are a windows user you'd probably recall an option "Desktop Clean Up wizard" ? [18:14] Now since the names are too similar a new user will often confuse the functions. [18:14] It has now been re-named to "Organize Desktop by Name" [18:15] That was a simple bug right? all it needed was a renaming of an existing function! [18:15] want more examples? ;) [18:16] moving on.. [18:16] saji89: yes simple changes [18:16] Now, why should you care about these trivial bugs? [18:17] If you are new to Ubuntu and eager to start working on Ubuntu , [18:17] this is the best way to get started! [18:17] the bugs are simple changes [18:18] helps you get familiar with the coding practices followed and gets you ready for handling bigger bugs in the packages. [18:18] it takes you just a day to make the impact! [18:18] And the change you make will be in the *default* install of the next release! [18:18] This is a very rare opportunity for a new member , to make changes in a default install. [18:19] asked : So, how do we know where the specific change is to be made? [18:20] saji89: the bugs will be filed in the applications , you need to dig into the source and just change it [18:20] Now , not that this is only for new members . ;) [18:20] Anyone can fix a papercut , all one needs to think is "what can I improve in Ubuntu today?" Head over to the triaged list of papercuts and submit fixes! [18:21] Sounds simple right? [18:21] Now let's getting into how to fix these bugs: [18:22] asked : So, This digging into source invloves BZR, and such things isn't it? [18:23] saji89: if its an Ubuntu specific bug , then yes , you need to bzr branch the Ubuntu branch and submit a merge [18:23] saji89: if its an upstream Gnome-bug then patches for the git code would be the best way [18:24] saji89: similarly debian == submit patch to debian :) [18:25] Now let's getting into how to fix these bugs: [18:25] This is the schedule for maverick https://launchpad.net/hundredpapercuts/maverick [18:25] The 100 paper cuts planned for Maverick are split into 10 milestones or "rounds" as we have been calling them, [18:25] or even "themes" [18:25] these milestones are like themes so that it is easier for a developer , who is say.. interested in Nautilus to find those related bugs and fix them. [18:26] has everyone seen the scheduled list ? [18:27] Now, the milestones are not hard deadlines, so don't worry that all of the bugs are not fixed yet. [18:27] Well, maybe worry a little bit ;) [18:28] And head over to the list of triaged bugs: https://bugs.launchpad.net/hundredpapercuts/+bugs?field.status%3Alist=TRIAGED [18:28] asked: so we take a bug and hope, that it is easy to fix? [18:29] mythos: there is not a question of hoping here , the bugs are usually trivial.. [18:29] as i showed examples earlier , the changes are trivial [18:30] often in the rush for new features , developers for the little things [18:30] mythos: We have what is called the GNOME Human Interface Guidelines : [18:30] http://library.gnome.org/devel/hig-book/stable/intro.html.en [18:30] Often there are certain areas in an application which dont follow those guidelines, ex: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/592661 [18:31] as you can see in that bug , the menu item "File" should not exist [18:31] since it is a photo manager , it should be a Photo menu [18:31] mythos: so , there is no hoping.. are we clear on that .. the fixes are trivial :) [18:32] well , most of the time.. ;) [18:32] if it turns out to be too large a problem we have often closed bugs.. [18:33] alrighty.. continuing from the triaged list: https://bugs.launchpad.net/hundredpapercuts/+bugs?field.status%3Alist=TRIAGED [18:34] as you can see there are a hundred odd bugs still waiting. [18:34] See any bug that interests you? [18:35] If you are truly committed to fixing it, you can assign it to yourself . [18:35] After assigning it to yourself, read the launchpad bug report and any upstream reports. [18:35] Then ask yourself, what does this paper cut need before it can be considered fixed? [18:36] Make a list, then start addressing those work items. [18:36] dont forget to Mark the bug as "In Progress" [18:36] asked : so, does it really matter to use bzr?, or can I just upload a debdiff? [18:37] chilicuil: as i mentioned earlier , if the bug is Ubuntu specific , then a branch will do. else debdiff [18:37] asked: So, when we are in need of some help, ehich irc channel shall we contact? === pjarnahom is now known as pjarnahomzz [18:38] saji89: #ubuntu-bugs, #ubuntu-motu, #ubuntu-desktop on IRC. Or just add a comment on the bug. That works too. [18:38] saji89: thats if you need assistance in fixing the bugs.. [18:39] also , a [18:39] #ayatana of course [18:40] saji89: the Ayatana Mailing list might be used as well , you you want to discuss the suggested design solution [18:41] now , if you look at : https://launchpad.net/hundredpapercuts/+milestone/maverick-round-9-sc-metadata [18:42] you can see the bugs there are just about updating the descriptions [18:42] mythos: thats simple right? :) [18:43] we just need to make a patch to fix these bugs once they have patches with the appropriate description , these have to be sent upstream to debian as well [18:44] since it is easier for the debian maintainers when we have the patches with an appropriate description [18:44]