**** Session 5 ~ Working with Ubuntu <-> GNOME QA (tips&tricks) ~ BEGIN AT Tue Sep 2 01:34:04 2008 Sep 01 22:04 < pedro_> Hello everybody my name is Pedro Villavicencio Garrido Sep 01 22:04 < pedro_> I'm currently living in Santiago de Chile, I'm the guy behind the Ubuntu Desktop Bugs and I work for Canonical since a little more than a year Sep 01 22:05 < pedro_> Today i will talk to you a bit about the Ubuntu+GNOME QA Sep 01 22:05 < pedro_> everybody knows what GNOME is ? Sep 01 22:05 < pedro_> alright! well for those who don't know it Sep 01 22:06 < pedro_> The GNOME project provides you of two things the GNOME Desktop environment an intuitive and attractive desktop (blink ;-)) for users and the GNOME development platform which is an extensive and rich framework for building applications that integrate with the rest of the Desktop Sep 01 22:06 < pedro_> And if you haven't noticed... it's the default desktop of Ubuntu ;-) Sep 01 22:07 < pedro_> The latest stable relase of GNOME is GNOME 2.22 and since it's the default desktop of Ubuntu , GNOME 2.22 is available in Hardy if you want to try it Sep 01 22:07 < pedro_> if you want to use the development release of GNOME which is GNOME 2.23.90 there's a few ways to do it Sep 01 22:07 < pedro_> The first one is to download Ubuntu Intrepid from http://www.ubuntu.com/testing/ , but for example if you're using Hardy and you don't want to upgrade to Intrepid but you really want to use GNOME what you can do is build GNOME from the source, there's two ways for doing this Sep 01 22:08 < pedro_> 1) Using GARNOME Sep 01 22:08 < pedro_> GARNOME is a build utility that allows you to build GNOME from latest tarballs, both the stable and unstable branch, it's pretty easy to use and actively maintained the only bad thing is that it doesn't support building from SVN... but we have another tool for that Sep 01 22:08 < pedro_> 2) Jhbuild Sep 01 22:09 < pedro_> if you're brave enough you can build GNOME with jhbuild which allows you to build the latest modules from GNOME the SVN, is way more flexible than GARNOME, you can build an specific branch like GNOME 2.18, 2.16, etc or use bleeding edge software (GNOME trunk), it's not really recommended for beginners but if you want to learn how GNOME is build it's perfect. Sep 01 22:09 < pedro_> I currently use Jhbuild for testing and if you're interested I've put my jhbuildrc file at http://www.gnome.org/~pvillavi/jhbuild/ Sep 01 22:10 < pedro_> you can also look to http://live.gnome.org/JhbuildOnUbuntu if want to see what you need to do in order to build your GNOME in Ubuntu with jhbuild Sep 01 22:10 < pedro_> and if you're having issues with it, there's a page of common issues when building: http://live.gnome.org/JhbuildIssues Sep 01 22:11 < pedro_> if your problem is not listed there, that's probably a bug and should be reported ;-) Sep 01 22:11 < pedro_> <emet> QUESTION: Do these build tools output packages? Sep 01 22:11 < pedro_> emet: no they don't do it Sep 01 22:12 < pedro_> <apachelogger> QUESTION: are there daily packages for ubuntu, or are there plans to get such a thing running? Sep 01 22:12 < pedro_> apachelogger: that might be difficult to do and not really necessary since there's no GNOME releases each day and also the desktop team is really good at packaging those in just a few hours Sep 01 22:13 < pedro_> but it would be a really good question for the desktop testing talk at Thursday ;-) Sep 01 22:13 < pedro_> alright, did you wondered how many space do you need to build? Sep 01 22:13 < pedro_> between sources, build and install Sep 01 22:13 < pedro_> you need ~10 gb for all Sep 01 22:14 < pedro_> if you like to build things there's a project at GNOME called the Build Brigade Sep 01 22:14 < pedro_> what they do is to automate discovery and reporting of GNOME build errors to make the testing of the development version easy for everyone, finding the build errors and regressions quickly Sep 01 22:14 < pedro_> if you have your browser open Sep 01 22:15 < pedro_> you can have a look to http://build.gnome.org Sep 01 22:15 < pedro_> where you can see a pretty nice resume about all the GNOME modules, the red ones are the ones that failed to build and the green ones represent the ones that the build was successful Sep 01 22:16 < pedro_> so if you have a spare machine and are interested on testing you can join them at #build-brigade in irc.gnome.org and yes you can also subscribe to their mailing list and ask things : http://mail.gnome.org/mailman/listinfo/build-brigade-list Sep 01 22:16 < pedro_> help is always needed and both projects will benefit of that ;-) Sep 01 22:17 < pedro_> is anybody familiar with the Ubuntu Bugsquad? Sep 01 22:17 < pedro_> you know those awesome people? Sep 01 22:17 < pedro_> well in GNOME we also have a GNOME Bugsquad Sep 01 22:17 < pedro_> The GNOME Bugsquad is the Quality Assurance team for GNOME, which basically keep track of the current bugs in GNOME and try to make sure that major bugs do not go unnoticed by developers Sep 01 22:17 < pedro_> the same mission as the Ubuntu Bugsquad ;-) Sep 01 22:18 < pedro_> Those bugs are being tracked in the GNOME Bugzilla which is located at bugzilla.gnome.org, everybody can help you only need to create an account also the Bugsquad hangs out in IRC at the #bugs channel on irc.gnome.org so if you have any questions regarding a report the best place to ask is there unless is something really technical in that case you can ask to the module maintainer Sep 01 22:19 < pedro_> but hey what about getting permission for triage, if you want to have it, you need to read the Triage Guide at http://live.gnome.org/Bugsquad and after that ask for the permissions at #bugs Sep 01 22:20 < pedro_> the general disclaimers are : 1) Use common sense and 2) If unsure, ask at the channel first Sep 01 22:20 < pedro_> nothing too complex as you can see Sep 01 22:20 < pedro_> When working with the GNOME Bugzilla you'll be winning some points Sep 01 22:20 < pedro_> and no you can't change them for t-shirts Sep 01 22:21 < pedro_> the more work you do the more points you'll have . same as karma at Launchpad Sep 01 22:21 < pedro_> In Ubuntu we also have a team that take care of the GNOME Bugs Sep 01 22:21 < pedro_> that team is called the Ubuntu Desktop Bugs Sep 01 22:22 < pedro_> the team is basically the awesome seb128, me and a few outstanding community members ;-) Sep 01 22:22 < pedro_> we always need help so if you like GNOME, Ubuntu and want to help us, you're more than welcome ;-) Sep 01 22:22 < pedro_> <apachelogger> QUESTION: can one merge the gnome bugzilla points and lp karma to become ubercool? Sep 01 22:23 < pedro_> apachelogger: haha no sadly you can't but hey submit a feature request :-P Sep 01 22:23 < pedro_> if you're wondering which packages we keep track well the list is located at: https://bugs.edge.launchpad.net/~desktop-bugs/+packagebugs as you can see they are ~110 packages which is a lot of work Sep 01 22:24 < pedro_> If we same some spare time we also do some triage at these products: https://wiki.ubuntu.com/Bugs/Upstream/GNOME/UniverseList If you want to adopt a package and do some triage work on it you're free to go ;-) Sep 01 22:25 < pedro_> the team hang out at #ubuntu-bugs so if you want to join the team just drop by and say hi ;-) Sep 01 22:25 < pedro_> the launchpad page is : https://edge.launchpad.net/~desktop-bugs Sep 01 22:26 < pedro_> and yeah while doing work with Launchpad you also win points but in launchpad they are called Karma Sep 01 22:26 < pedro_> One of our tasks is also forward bugs upstream Sep 01 22:27 < pedro_> since you're already know how to get help and briefly how to GNOME Bugsquad works, I'll introduce you to the forward Ubuntu GNOME related ones Sep 01 22:27 < pedro_> first steps well, you need a bugzilla account, if you don't have one http://bugzilla.gnome.org/createaccount.cgi Sep 01 22:28 < pedro_> you only need a valid email ;-) Sep 01 22:28 < pedro_> after that well you need to search the Bugzilla database in oder to see if the bug was already reported Sep 01 22:28 < pedro_> if you go to http://bugzilla.gnome.org/query.cgi Sep 01 22:29 < pedro_> you'll see the basic search functionality of bugzilla Sep 01 22:29 < pedro_> one of the common mistakes people do when searching is not searching for the closed bugs Sep 01 22:29 < pedro_> let's take for example a query with the string "i love ubuntu" Sep 01 22:30 < pedro_> if you search for it, bugzilla will return you "zarro boogs found" Sep 01 22:30 < pedro_> OMG nobody loves ubuntu :-( Sep 01 22:30 < pedro_> gnome people is so evil.... Sep 01 22:30 < pedro_> but hey let's try something else Sep 01 22:31 < pedro_> we made that mistake, we didn't searched for the closed ones Sep 01 22:31 < pedro_> so let's try this, let's search with this text: "i love ubuntu" meta-status:all Sep 01 22:31 < pedro_> meta-status:all means show me all the bugs containing "i love ubuntu" i don't care about the status , just please show me those Sep 01 22:32 < pedro_> now you'll get results!! Sep 01 Sep 01 22:32 < pedro_> woohoo people love us again! Sep 01 22:33 < pedro_> that was just a brief example if you want to read more about it you can take a look to http://bugzilla.gnome.org/page.cgi?id=boogle-help.html Sep 01 22:33 < pedro_> you can basically search by status, gnome-version, os, target, assignee, etc Sep 01 22:34 < pedro_> ok before sending our bug upstream is also good to have a look to the list of the more frequent reported bugs http://bugzilla.gnome.org/duplicates.cgi Sep 01 22:34 < pedro_> searching is a bit difficult if you don't really know how the software works and you can easily spend a few minutes on it Sep 01 22:35 < pedro_> for example searching for a stacktraces that matches one submitted at Ubuntu, the basic way is to go to the simple search and start copy & paste a few of the function names into it, which is not very optimal... Sep 01 22:35 < pedro_> and well the GNOME Bugzilla has a very cool feature called the "Simple Dup Finder" which allows you to of course find duplicates and if you used the gnome bugzilla before you probably saw it, on the reports there's a link at the top right which said "simple dup finder" if you click there it will show you the probably duplicates of that bug, but what if you want to search as said for a stacktrace what can you do? Sep 01 22:36 < pedro_> there's a cool trick for that too Sep 01 22:36 < pedro_> you can use the http://bugzilla.gnome.org/dupfinder/simple-dup-finder.cgi? simple dup finder page Sep 01 22:36 < pedro_> and copy and paste the stacktrace or bug description there Sep 01 22:37 < pedro_> <kevjava> QUESTION: Are there parts of GNOME that seem to consistently need more attention? Sep 01 22:37 < pedro_> the big products always needs more attention, like the Evolution one Sep 01 22:37 < pedro_> nautilus and so on Sep 01 22:37 < pedro_> <xander21c> Question: Is there mentoring fot Gnome QA Sep 01 22:38 < kevjava> pedro_: Cool, thanks :). Sep 01 22:38 < pedro_> xander21c: yes, the mentoring of the Ubuntu GNOME ones is provided at #ubuntu-bugs and the one for GNOME at #bugs in irc.gnome.org Sep 01 22:38 < pedro_> so if you interested just join the channels and ask ;-) Sep 01 22:39 < pedro_> If the bug was reported what you need to do is to link the report in launchpad (aka create a bug watch), more instructions about this at: https://wiki.ubuntu.com/Bugs/Watches Sep 01 22:39 < pedro_> i think that jorge mentioned that in his amazing talk Sep 01 22:39 < pedro_> so if you want to know more about it look at those logs ;-) Sep 01 22:40 < pedro_> but here's is one issue Sep 01 22:40 < pedro_> what if there's another report in launchpad linking to that report? Sep 01 Sep 01 22:40 < pedro_> how can you know it? Sep 01 22:40 < pedro_> we don't want to have 10 reports linking to the same one upstream Sep 01 22:40 < pedro_> those should be marked as duplicate and just have one master right? Sep 01 22:40 < pedro_> that's the right thing to do Sep 01 22:40 < pedro_> but ok how we can search for those? Sep 01 22:41 < pedro_> ok don't make too much noise i'll show you a secret... Sep 01 22:42 < pedro_> let's say we found the bug http://bugzilla.gnome.org/show_bug.cgi?id=506357 Sep 01 22:42 < pedro_> upstream Sep 01 22:42 < ubot5> Gnome bug 506357 in screenshot "crash in Take Screenshot: taking a screen shot" [Critical,Unconfirmed] Sep 01 22:42 < pedro_> what we are going to do is : go to https://bugs.launchpad.net/bugs/bugtrackers/gnome-bugs/#bugnumber Sep 01 22:42 < pedro_> and replace #bugnumber for the bug number of the upstream one Sep 01 22:43 < pedro_> you'll be redirected to the bug in launchpad that is linking to the upstream one Sep 01 22:43 < pedro_> see magic! Sep 01 22:44 < pedro_> <RoAkSoAx> QUESTION: how can we get more involved with Gnome development (more related to MOTU work). Are there any specific task list where we can get started Sep 01 22:44 < pedro_> RoAkSoAx: yeah there's always tasks to do, I'd recommend to go trough the list of bugs marked as gnome-love Sep 01 22:45 < pedro_> http://bugzilla.gnome.org/reports/gnome-love.cgi <- RoAkSoAx Sep 01 22:45 < pedro_> let's continue if the bug wasn't reported at all you can add a new one then Sep 01 22:45 < pedro_> for doing it you need to go to http://bugzilla.gnome.org/enter_bug.cgi and select the right product and component, sometimes it's hard to find the right component in big products like Evolution, but follow your common sense, if the bug describe issues with reading, writing emails well the component is Mailer, is the problem is with contacts, probably the right component is Contacts and so on Sep 01 22:46 < pedro_> most of the products have a list describing their components so taking the same example the list of components of the Evolution product is here: http://bugzilla.gnome.org/describecomponents.cgi?product=Evolution Sep 01 22:46 < pedro_> You also need to be carefully with reports from evince for example Sep 01 22:47 < pedro_> people tend to reports bugs about rendering in Evince which is in most of the cases wrong Sep 01 22:47 < pedro_> poppler is the rendering backend for evince and such bugs should be filled at their bug tracker Sep 01 22:47 < pedro_> so double check them before submit any of those at the GNOME Bugzilla Sep 01 22:49 < pedro_> one of the last considerations is to choose the right Keyword Sep 01 22:49 < pedro_> if you're submitting a bug with a good stacktrace, you need to add the STACKTRACE keyword to the report Sep 01 22:49 < pedro_> if is a bug about usability, well the usability keyword and so on Sep 01 22:50 < pedro_> the list of keywords can be found here: http://bugzilla.gnome.org/describekeywords.cgi Sep 01 22:50 < pedro_> be sure to use them and again if you're unsure just ask :-) Sep 01 22:52 < pedro_> after the bug was forwarded what you need to do is to create a bug watch linking to the bug you just submitted upstream, it'll be updated regularly and will reflect the status of the upstream bug report Sep 01 22:52 < pedro_> instructions at https://wiki.ubuntu.com/Bugs/Watches Sep 01 22:53 < pedro_> that's almost the whole process of forwarding a bug to the GNOME Bugzilla Sep 01 22:53 < pedro_> and linking it to launchpad also Sep 01 22:54 < pedro_> now it's up to the maintainers to have a look to it in order to fix it, or why not you if you're interested Sep 01 22:55 < pedro_> as said previously we have to deal with toons of bugs daily and we always need help so if you like GNOME and Ubuntu as we do Sep 01 22:56 < pedro_> feel free to join us and ask a lot of questions, asking is not bad so the more the best ;-) Sep 01 22:58 < pedro_> I think that's all if you have any questions later feel free to send an email to me or to the ubuntu bugsquad mailing list or why not ask it on the IRC channels, we are most of the time there and well there's always people willing to help new bugsquaders Sep 01 22:58 < pedro_> thanks everybody and hope to see you around soon ;-) **** Session 5 ~ Working with Ubuntu <-> GNOME QA (tips&tricks) ~ END AT Tue Sep 2 02:28:58 2008
This page was last modified on 2 September 2008, at 05:15. This page has been accessed 520 times.
