=== ssweeny_ is now known as ssweeny === txwikinger is now known as txwikinger_work === txwikinger_work is now known as txwikinger === txwikinger is now known as txwikinger3 === txwikinger3 is now known as txwikinger_work === txwikinger_work is now known as txwikinger [06:38] date -u === Gonzofox_ is now known as Gonzofox === croppa_ is now known as croppa === bluesmoke_ is now known as bluesmoke === asac_ is now known as asac [10:45] Hello everybody [10:46] hello johane [10:47] Hi guys [10:47] You are Ubuntu developers? [10:50] johane: No [10:50] Ok [10:50] Johane: just someone who's trying to be more integrated in ubuntu & linux life cycle [10:51] Good job and keep up the good work [10:51] I'm using ubuntu too [10:52] I'm helping myself with bits and tights [10:54] johane: good thing, i encourage you [10:56] somaunn:Thankyou [10:56] I'm also learning programing [10:57] johane: programming ? good thing to do with linux === KennethP_ is now known as KennethP [10:58] johane: i'm watching a video concerning notifications in jaunty (Ubuntu 9.04) [10:58] johane: telling you that thing is crazy [10:59] johane: i mean hot and different than what i've seen in linux before [10:59] Can you give me the link? [11:01] johane: http://www.markshuttleworth.com/wp-content/uploads/2008/12/jaunty904_notifications_example1_web_092.swf [11:03] Holy got :Looks very nice [11:03] More info on notifications: http://www.markshuttleworth.com/archives/253 [11:03] Y can't wait for it tobe released [11:05] Vista and WinShit 7 are babies next to the upcomming Ubuntu [11:07] johane: :D right [11:08] if someone have links containing the same video please don't hesitate [11:08] to send it [11:11] somaunn:Where you from? [11:12] johane: from congo, but actually in south africa [11:12] somaun: Is it hot there? [11:14] johane: yeah, i mean sometimes [11:14] johane: but it's a nice place [11:15] Where i live i have only 5*C maximin [11:16] *Maximim [11:16] Is winter here in Romania [11:16] You heard of Romania? [11:21] johane: yeah [11:22] johane: was there long time ago for studies [11:26] Wow-Can you remember the city? [11:29] And what studies you made there? [11:33] johane: it wasn't me, but my father [11:33] johane: and he was in sovata if remenber [12:46] hola, hay alguien por aqui? [12:51] ... [13:24] hi all! === ursula_ is now known as Ursinha === jyeager is now known as duanedesign === Obama is now known as Guest2079 [14:10] hello guys ... [14:12] get a question right here [14:12] can someone help me ? [14:13] somaunn: #ubuntu for help with ubuntu === sdx24 is now known as sdx23 [15:30] hey [15:31] hey [15:31] how are you doing today? [15:54] hey seb128 [15:54] hi Arc [15:54] Hi everyone [15:55] HELLO EVERYBODY! [15:55] WELCOME TO DAY 3 OF UBUNTU DEVELOPER WEEK! [15:55] morning dholbach! [15:55] ... also known as the Week of Awesome! [15:55] How are you all doing? [15:55] Who's excited for another day of UDW? [15:55] groggy with green tea in hand :-P [15:55] Me, me [15:56] but ready :-) [15:56] /brewing a coffe [15:56] who else? don't be shy :) [15:56] Ok... there's a bunch of names I spotted in here that look familiar, for everybody who's new: [15:56] Me, yeah!!!!! [15:57] please... don't be shy! If you have questions, please ask! [15:57] but please.... ask in #ubuntu-classroom-chat and prefix them with QUESTION: [15:57] * directhex is excited for day 4. day 4 is more awesome [15:57] ie: QUESTION: seb128: are you really German? [15:57] lol [15:57] no [15:57] ;-) [15:57] and I'm not from Alsace [15:57] * dholbach hugs seb128 [15:57] * seb128 hugs dholbach [15:57] * dholbach hugs seb128 back [15:58] we still have 3 minutes left until seb128 takes over, so grab a coffee, tea or any other drink and enjoy it [15:58] Sebastien Bacher will talk about a topic he's very familiar with: Pushing out GNOME releases to millions of users [15:58] ROCK ON! :) [15:59] Still 30 seconds.. [15:59] no join in #ubuntu-classroom-chat ?? [16:01] ok, good ;-) [16:01] good morning, afternoon, evening to everybody! [16:02] I'll do a presentation of what the ubuntu desktop team is doing first [16:02] and then we can do questions-answers [16:02] so [16:02] The Ubuntu Desktop Team is the team working on most of the Ubuntu GNOME desktop applications. [16:03] The team is a mix of people working full time for canonical and rocking contributors [16:03] we have some contributors around I see ;-) [16:03] hey crevette, pochu (and probably others) ;-) [16:03] * Where we are [16:03] - #ubuntu-desktop on irc.ubuntu.com [16:03] - ubuntu-desktop@lists.ubuntu.com [16:04] - launchpad: desktop-bugs and ubuntu-desktop teams [16:04] * What we do [16:04] - work on the desktop packages, the rough list is on https://launchpad.net/~desktop-bugs/+packagebugs [16:04] - update the desktop packages when new versions are available [16:04] - work on the corresponding bugs lists, triage the bugs and work with upstream to get those resolved [16:05] * How we work: [16:05] - most of the packages are coming from the debian pkg-gnome team [16:05] - we try to keep those packages in sync as much as possible and send their our changes to them [16:05] - we do package unstable version earlier and carry ubuntu specific changes though [16:06] - the packaging is mostly done using cdbs [16:06] - we mostly updates packages when GNOME roll new tarballs and backport upstream fixes [16:06] [16:06] * How we do updates: [16:07] - we current have somebody looking at the new upstream tarballs and noting what upgrade we need to do in ubuntu [16:07] - tasks are usually splitted on IRC (ie, upgrade are assigned to people there) [16:08] - people are free to claim tarballs they want to work on [16:08] - contributors use bugs on launchpad to get their work reviewed [16:08] usually it's easy to get review since the team is quite active [16:09] and you often find people to help on IRC [16:09] [16:10] the current workflow has some limitation and we will try to improve it [16:10] some packages are moving to bzr for the packaging work and we will probably try to standardize that [16:10] didrocks started some documentation on the topic and you can find details on the ubuntu desktop wiki: https://wiki.ubuntu.com/DesktopTeam [16:11] we also want a system which allow to set a todolist and let people claim work directly there rather than using IRC [16:11] some people started to work on a website listing all the versions available in ubuntu, debian and upstream for the team packages [16:12] we will probably try to continue this way and have a website which allow people to claim work they are doing [16:12] on a technical side upgrades are usually standard version updates [16:13] some are easy enough for beginner so if you want to get started that's no issue [16:13] some other are tricker (soname changes, change to build system, new binaries added) [16:13] the things we usually check for updates [16:13] - the configure requirement and if they changed [16:14] if they changed the (build-)depends need to be updated to reflect that [16:14] - that the update builds and work correctly [16:14] - the bugs closed in the upgrade [16:15] library are also checked for abi changes (in which case the soname should be updated if the new abi is not compatible, or the shlibs updated if there is new functions but the abi is still compatible) [16:15] [16:15] ok [16:15] that was it for the summary of what the team is doing on how [16:15] we also discuss desktop changes, new components to install by default or not, configuration changes, etc [16:16] [16:16] we can do questions and answers now ;-) [16:16] can't join #ubuntu-classroom-chat [16:16] why? [16:16] good question [16:16] QUESTION: Off-topic: Can someone work remotely for Canonical? [16:17] DasEi: /msg me and I'll try to help you [16:17] pochu: can you write the nickname of whoever asked too maybe? [16:17] sure, sorry [16:17] creek23> QUESTION: Off-topic: Can someone work remotely for Canonical? :-/ [16:17] creek23: most of the people working on Ubuntu for canonical are working remotely [16:17] so yes it's possible [16:18] the job offers are on the website and that's specified in the descriptions [16:18] [16:18] next [16:18] fta> QUESTION: seb128: you said "somebody looking at the new upstream tarballs", d'oh! manually? how often? why somebody and not some script? [16:19] fta: GNOME has a mailing list which gets mails about all the tarballs uploaded so that's easy to keep track ... why not a script because nobody wrote one yet ... interested? ;-) [16:19] probably [16:19] in fact somebody started working on a website listing ubuntu, debian and upstream version as said before [16:19] would be good to continue this work [16:19] QUESTION:seb128: I'm not ready for doing development, but could help translating to german, where to go ? [16:19] that would show what is to update [16:20] DasEi: please write questions in #ubuntu-classroom-chat [16:20] DasEi: questions on #ubuntu-classroom-chat [16:20] pochu: NEXT [16:20] directhex> QUESTION: how often does the desktop team reassess which app is used to accomplish a given task (e.g. pidgin vs empathy), and what are the criteria for a change? [16:20] seb128, ok (a pointer would be nice). Thanks [16:21] fta: there is a discussion about it on the ubuntu-desktop@lists.ubuntu.com started some months ago if you want to check the archives [16:21] directhex: good question, that's not a periodic tasks, we do look at suggestions though so that's whenever somebody do one [16:21] you can do a suggestion on the mailing list or during the weekly meetings [16:22] the team has weekly IRC meeting on #ubuntu-desktop, they are at 16:30utc on tuesday [16:22] pochu: NEXT [16:22] hggdh> QUESTION: we are based on Debian. But every so often a Debian package is found to be older than a new requirement. What is the procedure? [16:23] fta: btw, the page is this: http://norsetto.890m.com/desktop_packages.php [16:23] hggdh: we try to get work done there so we don't block on Debian [16:23] pinging the debian maintainer before starting on an update can be a good idea [16:23] usually we don't block on a reply as said though [16:23] sending the debdiff back to the debian pts is good practice too [16:24] or at least a bug there request for the update and pointing to the ubuntu work [16:24] if they do the update and we can sync we lower the ubuntu-debian delta which means less work for everybody [16:24] pochu: NEXT [16:24] Arc> QUESTION: whats the future for the default XMPP client look like? [16:25] this cycle is focussed on stabilization since we have quite some users annoying but how much rewrittes or GNOME changes have been breaking in previous cycle so we will not likely change that, it should still be pidgin [16:25] we will probably look again at empathy next cycle [16:25] pochu: NEXT [16:25] DasEi> QUESTION:seb128: I'm not ready for doing development, but could help translating to german, where to go ? [16:26] (urg should read what I type [16:26] annoying but how -> annoyed by how [16:26] yes, I suggest contacting the german translation team for that though [16:26] ubuntu-l10n-de on launchpad, they probably have a mailing list too [16:27] translations are made on launchpad or directly upstream, check with your locale team to know the details [16:27] pochu: NEXT [16:27] creek23> QUESTION: Who makes the Ubuntu theme? Wallpaper? etc? [16:27] the ubuntu artwork team [16:27] they have their own channel and I don't know how they decide on changes exactly [16:28] pochu: NEXT [16:29] I think we are running out of questions [16:29] creek23> QUESTION: Lots of opening from China, Taiwan? Why no Philippines? [16:29] (relating to job offers) [16:30] pochu: yeah, replying to those on the other channel ;-) [16:30] fta> QUESTION: what about daily builds, or builds for each commit (i refer to the last UDS opening from Mark) [16:31] (i meant "each upstream commit") [16:31] fta: that's out of the scope of the current #ubuntu-desktop ressources to do that I think but it's possible that some other team is wanting to put ressources on that, I don't know about it though, that's being discussed for some years but nobody got to do it yet [16:31] fair enough :) [16:31] that would be a good thing, a bit tricky to get right though [16:32] creek23> QUESTION: Why is "Windows key" (from the keyboard) not supported as it does in KDE? [16:32] creek23: that's a bug, what you expect to do? open the menu? or use it in shortcut [16:32] there is a gnome-control-center about it not working in shortcuts [16:33] +bug [16:33] NEXT [16:33] pochu> QUESTION: there has been a opening position for a desktop developer in terms of packaging for some time. Did you find anyone yet? [16:33] pochu: it would not still be open if we did ;-) [16:34] (hmm, so it is a bug.) [16:34] we are still interviewing candidates [16:34] if you keep it open for a few more time, I may apply :) [16:34] we didn't had some many matches for the job until now and some of those who were good decided to take a job somewhere else [16:35] thanks [16:35] Arc> QUESTION: is there any specific programming tasks open that would help gnome integration with Ubuntu? [16:35] pochu: you have the good profile so feel free to apply when you are done with universtity ;-) [16:35] :) [16:35] hum, good question [16:35] what sort of integration you are looking at exactly? [16:35] the next canonical dx team is going to work in those area [16:36] otherwise they is a lot of open bugs and request on launchpad [16:36] there is no specific list though [16:37] NEXT [16:37] creek23> QUESTION: How many exactly are the developers in the Desktop Team? [16:37] hum, good question [16:38] the ubuntu desktop team has probably around 7-8 regular contributors [16:38] and around the same number of people hanging around and doing some work every now and then [16:38] whoah! just 8?!?... o_O [16:39] so let's 7-8 people doing active work (some of them being full time canonical employees) and double the number if you count people helping on bug triage, etc [16:39] bug triage being active work too ;-) [16:39] NEXT [16:39] pochu> QUESTION: regarding the move to bzr for packaging, one of my reservations is that there will be a branch per package instead of one repository for all the desktop packages (as with pkg-gnome). Do you think this will be an advantage or a drawback? [16:40] that's something we already discussed, I don't think that makes a real different [16:40] there is some wrappers around to bzr get everything for a team [16:41] which would give you a full checkout [16:41] and that let you the option to just get and work on one component [16:41] ah, makes sense [16:41] NEXT [16:41] creek23> QUESTION: Ubuntu Netbook Remix out, is there a chance for Ubuntu Mobile Remix with GNOME in it? [16:41] I don't know enough about remix to reply to that I think [16:41] they do use GNOME applications now? [16:42] the purpose of the remix edition is that GNOME doesn't really fit on those screen [16:42] you need different interfaces on different devices [16:42] oh, I thought GNOME was used in it. [16:42] I think they modified some apps (e.g. liferea) for them [16:42] ie, the user experience is different on a notebook or tablet than on a desktop [16:43] the netbook remix uses gnome, albeit with some hacks here & there to fill more of the screen. mobile ed is something else [16:43] not the same input device, screen space, etc [16:43] NEXT? [16:43] SUGGESTION: it would attract more programmers to help with Ubuntu desktop if there was a "wishlist" for applets or specific added features, vs mixing them with "bugs" [16:43] (not really a question (: ) [16:44] that's a good remark though [16:44] the wiki has a todo and we try to tag some bugs [16:44] we could do a better job to make lists, it's not easy to classify by tasks and how easy they are though [16:45] NEXT [16:45] looks like there are no more questions [16:45] the todolist thing [16:46] you can send emails to the list if you have suggestions [16:46] or look at specs for the current cycle [16:46] those are usually tasks the team is working on [16:47] ji [16:47] hi* [16:47] no other question? [16:48] let me summarize what we need help on maybe then ;-) [16:48] - doing regular desktop updates and package new components [16:48] - triage bugs, send those upstream when they are upstream issue and get them resolved [16:50] what does he mean by "triage"? [16:50] - organize the workflow: documentation, create activity on the mailing list to encourage people to join, switch to bzr, tools to automate verifications done on every updates for example, work on the website to summarize work to get done, etc [16:50] ah [16:50] ok, so we push software to users, ie you [16:51] the users happily update to new version and notice that things stopped working the way they did [16:51] or they have request to had a feature [16:51] they open bugs on launchpad [16:51] our work is to review those bugs to decide on what is important to fix and what can wait [16:51] we don't have the resources to work on everything [16:52] and lot of those issues are in code ubuntu is not writing [16:52] ie if you get a bug in gedit it's likely in the GNOME gedit code and it should be sent to bugzilla.gnome.org so the people who are writting the code know about the issue [16:53] (there are a few questions now) [16:53] NEXT ;-) [16:53] ia> QUESTION: if you've heard about gnome-macmenu-panel, then could you tell, please, does gnome or ubuntu-desktop team plan include it "right-in-box", so user right after installation could select, which type of menu he would like to use - global(one, at top panel, for all windows) or not(traditional usage, when each window has its own menu bar) [16:53] no, first time I read about this name [16:54] feel free to discuss it on #ubuntu-desktop or mail the ubuntu-desktop mailing list to suggest that we look at it [16:54] next [16:54] Ape3000> QUESTION: So how can we help in triaging in practice? [16:54] dholbach: do you have a pointer on how to start on bug triage? ;-) [16:55] https://wiki.ubuntu.com/Bugs [16:55] https://wiki.ubuntu.com/DesktopTeam/Bugs [16:55] too [16:55] ... and https://wiki.ubuntu.com/Bugs/HowToTriage too [16:55] perhaps https://wiki.ubuntu.com/Bugs/Triaging [16:55] :-) [16:55] next? [16:56] basically pick an application you use and know and look on launchpad to bugs which are not Confirmed or Triaged [16:56] ask for details if required, etc [16:56] #ubuntu-bugs is a good place to start [16:56] pochu: NEXT ;-) [16:56] DasEi> QUESTION/idea :though not hard for me to figure out, I think it'll be nice for new users to see the files (and maybe harddrives/dev's) on their desks, as they are used from other [16:57] we decided back in warty to have a clean desktop because that's usually where people have the files they use, their background image they like to look at, etc [16:57] there is enough way to access those drivers, the computer location, the places menu, etc [16:57] I don't think we want to change the default setting but that's just a gconf setting to switch if you want to do that [16:57] NEXT [16:58] that was the last question :) [16:58] ok, thanks everybody! [16:58] thanks seb! [16:58] seb128: in ibex first even files created on desk didn't show up, is what I meant [16:58] thanks seb128! [16:58] * creek23 claps! :D [16:59] thanks!!! [16:59] thanks a lot seb128 [16:59] nice [16:59] cheers [16:59] applause [16:59] thanks [16:59] cheers [17:00] excellent - I hope you guys are going to help out seb128 in #ubuntu-desktop soon! :) [17:00] so who's here for fixing Ubuntu bugs? who's excited? :-))) [17:00] yeah!! [17:00] * Flimm waves hand [17:00] \0/ [17:00] who else? :) [17:00] You told me on Packaging 101 to come and listen here for the answer to my question, so here I am [17:00] sorry not at this point :-P [17:01] * creek23 is. [17:01] yep, partly excited because i've got a steak though too :) [17:01] dholbach: do you know when pitti will run his gdb/crash session btw? the one that didnt happen yesterday? [17:01] * charlie-tca waves [17:01] :-) [17:01] * porthose waves [17:01] mnemo: it'll be announced broadly - no worries :) [17:01] ok my friends - let's talk about fixing bugs [17:02] it's really not difficult to be part of the revolution, to help out and make Ubuntu better [17:02] especially with helpful people in #ubuntu-bugs and #ubuntu-motu [17:02] again let me point you to https://wiki.ubuntu.com/MOTU/GettingStarted as it links to all the important stuff [17:03] the important skill you need to have or develop is what I like to refer to as 'detective skills' [17:03] it sometimes takes some searching on the web, some reading of docs, some talking to people [17:04] and checking out what happened in the upstream revision control system, etc. to find a fix that's ready already or find a way to develop a simple fix [17:04] because that's what it's all about: make Ubuntu better, be part of an awesome team :) [17:04] OK, enough hand-waving - let's get to work and fix a few open bugs :) [17:05] we have myriads of lists of open bugs, lists with CD building problems, lists of packages that don't build anymore and so on and so forth [17:05] a bunch of them are linked from the MOTU/GettingStarted page [17:05] I put some efforts into agreggating those lists in Harvest [17:05] http://daniel.holba.ch/harvest [17:06] it's a tool that pulls information about various 'opportunities' from various lists and displays them per package [17:06] dholbach: how do you" check out what happened in the upstream control system?" [17:06] duanedesign: we'll get to that in a bit in one of the examples [17:06] duanedesign: can you ask the next questions in #ubuntu-classroom-chat prefixed with QUESTION: please? :) === KennethP_ is now known as KennethP [17:06] I picked a few easy ones from harvest and hope we'll get through them in time [17:07] let's start off with empathy [17:07] http://daniel.holba.ch/harvest/handler.py?pkg=empathy [17:08] it displays opportunities from various lists - not very nice, but it does its job - if you want to help out making harvest better, let me know - the code is in Launchpad [17:08] let's click on the 291533 link [17:08] it'll take us to one of the bugs that is on the "resolved-upstream" list [17:08] which means: fixed upstream, broken in Ubuntu [17:09] you can see the bug is about intrepid, version 2.24.1 all tabs having the same name [17:09] now let's click on the "gnome-bugs #535042" link [17:09] (if I'm too quick or anything is not clear, let me know in #ubuntu-classroom-chat please) === bluesmoke is now known as Amaranth [17:10] so the upstream developer says on 2008-11-24 this is fixed already and that we should check if it really is [17:10] intrepid will still have the same version, but let's check if we have a newer version in jaunty to play with [17:11] click on the 'overview' link on the launchpad bug, it'll take you to https://launchpad.net/ubuntu/+source/empathy [17:11] jaunty has 2.25.4-1ubuntu1 [17:11] and if you check ftp://ftp.gnome.org/pub/GNOME/sources/empathy/2.25/ (where new GNOME releases end up at), you'll see that 2.25.4 was released at 06.01.2009 [17:12] which is way after 2008-11-24 [17:12] this means: the bug can theoretically be closed in Ubuntu [17:12] what's important now? [17:12] _____ _____ ____ _____ ___ _ _ ____ _ [17:12] |_ _| ____/ ___|_ _|_ _| \ | |/ ___| | [17:12] | | | _| \___ \ | | | || \| | | _| | [17:12] | | | |___ ___) || | | || |\ | |_| |_| [17:12] |_| |_____|____/ |_| |___|_| \_|\____(_) [17:12] [17:12] sorry for the bold letters and stuff, I thought I'd point it out clearly :) [17:13] who here runs jaunty? [17:13] * dholbach does [17:13] * mnemo too [17:13] * fta does too [17:13] * charlie-tca too [17:13] * seb128 does [17:13] * creek23 uses Intrepid :( [17:13] if nobody else does that's fine... here's how you can still SAFELY test jaunty: [17:13] https://wiki.ubuntu.com/UbuntuDevelopment/UsingDevelopmentReleases [17:13] me too [17:14] it will tell you how to make use of virtual machines, separate partitions or whatnot to safely run and test the development release [17:14] so going back to our nice empathy bug [17:14] we're <-> this close to closing it and having another bug fixed [17:14] we just need to test it :) [17:15] this was a very cheesy example, but you see what it took to get to the point of "ah, this should be fixed already" [17:15] just a bit of digging and checking some other sites [17:15] and that's what it's all about :) [17:15] QUESTION: Will VirtualBox run Jaunty on WUBI? o.O [17:15] creek23: I'm sorry, I'm the wrong person to ask that, I did not use WUBI yet - you could try it :) [17:16] alright... let's move on to the next example ;-) [17:16] http://daniel.holba.ch/harvest/handler.py?pkg=gtksourceview [17:16] gtksourceview is the piece of code that does syntax highlighting in places like gedit and stuff [17:16] let's click on the 242920 link [17:17] another one on the list of resolved-upstream bugs [17:17] Question: Don't you close the bug now? [17:17] benste: did you test if it was really fixed? :) [17:17] closing on hearsay does not count :) [17:17] thought someone else did it here :-) [17:17] _____ _____ ____ _____ ___ _ _ ____ _ [17:17] |_ _| ____/ ___|_ _|_ _| \ | |/ ___| | [17:17] | | | _| \___ \ | | | || \| | | _| | [17:17] | | | |___ ___) || | | || |\ | |_| |_| [17:17] |_| |_____|____/ |_| |___|_| \_|\____(_) [17:17] [17:17] :-) [17:17] QUESTION: how do you "close" a bug? [17:18] duanedesign: you click on the dropdown thingie next to "empathy" on the launchpad page (in the yellow bar) [17:18] it'll open a menu where you can change the status to "fix released" [17:18] alright, let's crack on with the gtksourceview bug [17:19] again it's supposed to be fixed upstream, so let's take a look at the upstream bug [17:19] "gnome-bugs #139968" [17:19] http://bugzilla.gnome.org/show_bug.cgi?id=139968 [17:19]