From conrads at cox.net Sun Feb 1 23:05:02 2009 From: conrads at cox.net (Conrad J. Sabatier) Date: Sun, 1 Feb 2009 17:05:02 -0600 Subject: Compcache breaks build in 2.6.7.2 Message-ID: <20090201170502.0b2f05a4@serene.no-ip.org> Linux serene.no-ip.org 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009 x86_64 GNU/Linux CC ubuntu/compcache/compcache.o ubuntu/compcache/compcache.c: In function ‘compcache_size_setup’: ubuntu/compcache/compcache.c:465: error: implicit declaration of function ‘strtoul’ make[2]: *** [ubuntu/compcache/compcache.o] Error 1 make[1]: *** [ubuntu/compcache] Error 2 make: *** [ubuntu] Error 2 I seem to have resolved my earlier problem with the "debug" re-definition, by the way, simply by going thgouh my .config file and hand-editing out all the places where *DEBUG*=y was enabled. -- Conrad J. Sabatier From conrads at cox.net Mon Feb 2 00:07:26 2009 From: conrads at cox.net (Conrad J. Sabatier) Date: Sun, 1 Feb 2009 18:07:26 -0600 Subject: Compcache breaks build in 2.6.7.2 In-Reply-To: <20090201170502.0b2f05a4@serene.no-ip.org> References: <20090201170502.0b2f05a4@serene.no-ip.org> Message-ID: <20090201180726.004b8b85@serene.no-ip.org> On Sun, 1 Feb 2009 17:05:02 -0600 "Conrad J. Sabatier" wrote: > I seem to have resolved my earlier problem with the "debug" > re-definition, by the way, simply by going thgouh my .config file and > hand-editing out all the places where *DEBUG*=y was enabled. Seems I spoke too soon here. Apparently, the compcache=generated errors just happened to occur before the previously mentioned debug errors. -- Conrad J. Sabatier From vicedar at gmail.com Mon Feb 2 03:33:25 2009 From: vicedar at gmail.com (Savvas Radevic) Date: Mon, 2 Feb 2009 04:33:25 +0100 Subject: bugjam logo svg? Message-ID: Is there an SVG source of the global bug jam logo? Link please? And license of course :) From thekorn at gmx.de Mon Feb 2 08:48:36 2009 From: thekorn at gmx.de (markus korn) Date: Mon, 2 Feb 2009 09:48:36 +0100 Subject: New version of hugday tools! Message-ID: <7533d3600902020048k42e49a6bx219d29023872bb03@mail.gmail.com> Hello Hug-Day lovers! I spend some time during the last week to completely rewrite the hugday tool [1]. You can use this commandline tool to * get a list of ubuntu hugdays * get a list of tasks for a hugday * mark tasks as DONE If you would like to use this tool or start hacking on the tool you can get it from my PPA at [2] or get the branch from lp:hugday-tools. How to use this tool? * get url of latest hugday: $ hugday current * get list of all task for current hugday: $ hugday list $ hugday list --filter open (get list of all open tasks) So far the hugday tool did not change any content of a wiki page, to be able to do so, the tool needs the users MOIN ID, run $ hugday init --user USERNAME --cookie PATH/TO/MOZILLA/COOKIE Where USERNAME is the name which will be shown in the 'triager' column after marking a task as DONE and COOKIE is the cookie.sql or cookie.txt of your mozilla browser profile. If you are not using a mozilla based browser you can also search for the MOIN_ID or MOIN_SESSION in the cookie file of your browser and run $ hugday init --user USERNAME --wiki-id (MOIN_ID or MOIN_SESSION) Now marking tasks as DONE by you is as simple as running: $ hugday close 123456 23456 3456 456 For more information see hugday --help, read the README or just ask me ;) I hope this tool helps and makes participating on ubuntu hugdays even more fun! For ideas, patches, bugs etc. please use the bug tracker at [1] Markus [1] https://edge.launchpad.net/hugday-tools [2] https://edge.launchpad.net/~thekorn/+archive/ppa From pochu at ubuntu.com Mon Feb 2 11:19:04 2009 From: pochu at ubuntu.com (Emilio Pozuelo Monfort) Date: Mon, 02 Feb 2009 12:19:04 +0100 Subject: New version of hugday tools! In-Reply-To: <7533d3600902020048k42e49a6bx219d29023872bb03@mail.gmail.com> References: <7533d3600902020048k42e49a6bx219d29023872bb03@mail.gmail.com> Message-ID: <4986D6A8.2000300@ubuntu.com> markus korn wrote: > Hello Hug-Day lovers! > I spend some time during the last week to completely rewrite the > hugday tool [1]. You can use this commandline tool to > * get a list of ubuntu hugdays > * get a list of tasks for a hugday > * mark tasks as DONE > > If you would like to use this tool or start hacking on the tool you > can get it from my PPA at [2] or get the branch from lp:hugday-tools. Hi Markus! Wouldn't it make sense to include this in the new ubuntu-qa-tools package? Cheers, Emilio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: OpenPGP digital signature URL: From pablog.ubuntu at gmail.com Mon Feb 2 14:12:54 2009 From: pablog.ubuntu at gmail.com (Pablo Castellano) Date: Mon, 02 Feb 2009 15:12:54 +0100 Subject: New version of hugday tools! In-Reply-To: <7533d3600902020048k42e49a6bx219d29023872bb03@mail.gmail.com> References: <7533d3600902020048k42e49a6bx219d29023872bb03@mail.gmail.com> Message-ID: <4986FF66.9050904@gmail.com> markus korn wrote: > Hello Hug-Day lovers! > I spend some time during the last week to completely rewrite the > hugday tool [1]. You can use this commandline tool to > * get a list of ubuntu hugdays > * get a list of tasks for a hugday > * mark tasks as DONE > > If you would like to use this tool or start hacking on the tool you > can get it from my PPA at [2] or get the branch from lp:hugday-tools. > > How to use this tool? > * get url of latest hugday: > $ hugday current > * get list of all task for current hugday: > $ hugday list > $ hugday list --filter open (get list of all open tasks) > So far the hugday tool did not change any content of a wiki page, to > be able to do so, the tool needs the users MOIN ID, run > $ hugday init --user USERNAME --cookie PATH/TO/MOZILLA/COOKIE > Where USERNAME is the name which will be shown in the 'triager' column > after marking a task as DONE and COOKIE is the cookie.sql or > cookie.txt of your mozilla browser profile. If you are not using a > mozilla based browser you can also search for the MOIN_ID or > MOIN_SESSION in the cookie file of your browser and run > $ hugday init --user USERNAME --wiki-id (MOIN_ID or MOIN_SESSION) > Now marking tasks as DONE by you is as simple as running: > $ hugday close 123456 23456 3456 456 > For more information see hugday --help, read the README or just ask me ;) > > I hope this tool helps and makes participating on ubuntu hugdays even more fun! > For ideas, patches, bugs etc. please use the bug tracker at [1] > > Markus > > [1] https://edge.launchpad.net/hugday-tools > [2] https://edge.launchpad.net/~thekorn/+archive/ppa > Good work! Could you release a version for Intrepid too? :) -- Regards, Pablo. From thekorn at gmx.de Mon Feb 2 23:47:51 2009 From: thekorn at gmx.de (markus korn) Date: Tue, 3 Feb 2009 00:47:51 +0100 Subject: New version of hugday tools! In-Reply-To: <4986D6A8.2000300@ubuntu.com> References: <7533d3600902020048k42e49a6bx219d29023872bb03@mail.gmail.com> <4986D6A8.2000300@ubuntu.com> Message-ID: <7533d3600902021547w2b7e70c1haae150e8716b4fc4@mail.gmail.com> On Mon, Feb 2, 2009 at 12:19 PM, Emilio Pozuelo Monfort wrote: > > Hi Markus! Wouldn't it make sense to include this in the new ubuntu-qa-tools > package? > Hi Emilio, I've no strict opinion on this, this can of course be part of ubuntu-qa-tools, what does everyone else think? If we decide to include it into u-qa-tools we should think about renaming the config file, currently it's ~/.hugday_config, maybe something like ~/.ubuntu-qa-tools/hugday.conf or ~/.config/ubuntu-qa-tools/hugday.conf (just in case other scripts in this package also have config files) Markus From thekorn at gmx.de Mon Feb 2 23:49:57 2009 From: thekorn at gmx.de (markus korn) Date: Tue, 3 Feb 2009 00:49:57 +0100 Subject: New version of hugday tools! In-Reply-To: <4986FF66.9050904@gmail.com> References: <7533d3600902020048k42e49a6bx219d29023872bb03@mail.gmail.com> <4986FF66.9050904@gmail.com> Message-ID: <7533d3600902021549m7768c522g28072449c9ef98af@mail.gmail.com> On Mon, Feb 2, 2009 at 3:12 PM, Pablo Castellano wrote: > Could you release a version for Intrepid too? :) good point, I updated my PPA with packages for intrepid and jaunty today From pedro at ubuntu.com Tue Feb 3 08:58:29 2009 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Tue, 03 Feb 2009 09:58:29 +0100 Subject: New version of hugday tools! In-Reply-To: <7533d3600902020048k42e49a6bx219d29023872bb03@mail.gmail.com> References: <7533d3600902020048k42e49a6bx219d29023872bb03@mail.gmail.com> Message-ID: <1233651509.4717.16.camel@thylacine> Hello, On Mon, 2009-02-02 at 09:48 +0100, markus korn wrote: > Hello Hug-Day lovers! > I spend some time during the last week to completely rewrite the > hugday tool [1]. You can use this commandline tool to > * get a list of ubuntu hugdays > * get a list of tasks for a hugday > * mark tasks as DONE > I hope this tool helps and makes participating on ubuntu hugdays even more fun! > For ideas, patches, bugs etc. please use the bug tracker at [1] > Thanks for the tool Markus!, I've added the instructions to UbuntuBugDay/Tools and also edited the TaskTemplate for the Bug Days to include a link to that documentation. Best Regards, pedro. From martinmai1024 at web.de Tue Feb 3 15:25:09 2009 From: martinmai1024 at web.de (Martin Mai) Date: Tue, 03 Feb 2009 16:25:09 +0100 Subject: Announcing the Next Ubuntu Hug Day! - 2009-02-05 Message-ID: <1233674709.5524.61.camel@martin-desktop> Fellow Ubuntu Triagers! This week's HugDay target is *drum roll please* update-manager! * 60 New bugs need a hug * 107 Incomplete bugs need a status check * 125 Confirmed bugs need a review Bookmark it, add it to your calendars, turn over those egg-timers! * 2009-02-05 * http://wiki.ubuntu.com/UbuntuBugDay/20090205 Can't stress it enough: everyone can help! Have some time? Triage boogz! I won't be upset if you get a headstart~ ;) Have a blog? Blog about Hugday! Have some screen space? Open #ubuntu-bugs and keep an eye out for newcomers in need. Have minions? Teach THEM to triage for you! :) Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! Make a difference; we will be in #ubuntu-bugs (FreeNode) all day and night, and will be ready to answer your questions about how to help. If you're new to all this, head to http://wiki.ubuntu.com/HelpingWithBugs Have a nice day, Martin Mai [From the BugSquad] -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From andres.mujica at seaq.com.co Mon Feb 9 03:07:41 2009 From: andres.mujica at seaq.com.co (=?ISO-8859-1?Q?Andr=E9s?= Mauricio Mujica Zalamea) Date: Sun, 08 Feb 2009 22:07:41 -0500 Subject: ubuntu-co Prep GBJ Session Message-ID: <1234148861.30482.9.camel@localhost> Hello team, just to let you know that we held a great preparation session for the GBJ with the Colombian Team https://wiki.ubuntu.com/ColombianTeam/GlobalBugJam/Report Also we've translated to Spanish and updated the GBJ Flyer with the February 09 session. We hope to put the spanish subtitles on the screencast, by the way anyone knows how can be those subtitles added?? Andrés Mauricio Mujica Zalamea andres.mujica at ubuntu.com Ubuntu Member Ubuntu BugSquad -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Ubuntu.png Type: image/png Size: 10571 bytes Desc: not available URL: From macoafi at gmail.com Mon Feb 9 03:20:09 2009 From: macoafi at gmail.com (Mackenzie Morgan) Date: Sun, 08 Feb 2009 22:20:09 -0500 Subject: ubuntu-co Prep GBJ Session In-Reply-To: <1234148861.30482.9.camel@localhost> References: <1234148861.30482.9.camel@localhost> Message-ID: <1234149609.8368.11.camel@betty> On Sun, 2009-02-08 at 22:07 -0500, Andrés Mauricio Mujica Zalamea wrote: > We hope to put the spanish subtitles on the screencast, by the way > anyone knows how can be those subtitles added?? Just saw this the other day: http://www.makeuseof.com/tag/how-to-add-subtitles-to-a-movie-or-television-series/ There are Linux directions using VLC. -- Mackenzie Morgan http://ubuntulinuxtipstricks.blogspot.com apt-get moo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From ara at ubuntu.com Mon Feb 9 14:53:53 2009 From: ara at ubuntu.com (Ara Pulido) Date: Mon, 09 Feb 2009 15:53:53 +0100 Subject: New package: ubuntu-qa-tools Message-ID: <49904381.5020402@ubuntu.com> Hello all, In Jaunty there is a new package available: ubuntu-qa-tools This package contains some of the tools available in the LP project, ubuntu-qa-tools [1] If you want your tool to be include in the package, please, branch the packaging branch and push a new one with a merge proposal with your changes (or send me an email). I will review it and repackage before feature freeze. bzr branch lp:~ubuntu-bugcontrol/ubuntu-qa-tools/packaging Please, remember that we are reaching feature freeze (Feb 19th), and if you want your script or application to be included in the package, you will need to rush. Cheers, Ara. [1] https://launchpad.net/ubuntu-qa-tools ---------------------------------------------------- Package: ubuntu-qa-tools Priority: optional Section: universe/devel Installed-Size: 168 Maintainer: Ubuntu MOTU Developers Architecture: all Version: 0.1 Depends: python (>= 2.5), python-central (>= 0.6.7), python-soappy, devscripts, genisoimage, python-launchpad-bugs (>= 0.2.25), python-launchpadlib, dctrl-tools Filename: pool/universe/u/ubuntu-qa-tools/ubuntu-qa-tools_0.1_all.deb Size: 19394 MD5sum: 30e8b132cf56ab086817131cec0f5311 SHA1: 7c2ab8de19980fb8a934f5df7d3564477590515d SHA256: 826859d9ff9c1ee59a98fcf54a353cd9e7bd23c2eab33d0d859c3aa5c9801bf9 Description: useful tools for Ubuntu testers and bug triagers This is a collection of useful tools that Ubuntu QA team uses to make their daily work a lot easier. . Such tools can include bug filing, bug reporting, scripts to download ISO images, etc. . Available scripts are: . * check-needs-packaging - checks for bugs that require new packaging * body-searching - search bugs with a particular text * count-senders - quantity of messages sent by individuals to the bug mailinglist * tagged-bugs - search for tagged bugs in Launchpad * triager-query - search for actions of a particular triager * dl-ubuntu-test-iso - downloads ISOs for testing using rsync * iso-ripper - rips debs out of downloaded isos * debian-bug-search - searches the Debian bug tracking system Homepage: https://launchpad.net/ubuntu-qa-tools/ Python-Version: >= 2.5 Bugs: mailto:ubuntu-users at lists.ubuntu.com Origin: Ubuntu From panbalag1 at gmail.com Tue Feb 10 14:09:21 2009 From: panbalag1 at gmail.com (Prasanth Anbalagan) Date: Tue, 10 Feb 2009 09:09:21 -0500 Subject: Identifying the Ubuntu release in a bug Message-ID: <7f75fcac0902100609t59b966bo85e3976688650703@mail.gmail.com> Hi all, I'm trying to identify the ubuntu release against which the bug were actually reported in https://bugs.launchpad.net/ubuntu/ For example, the following bug does not have the info. https://bugs.launchpad.net/ubuntu/+bug/7261 Could someone help me how to identify the ubuntu release in such cases. Aren't there standard fields that identify the releases? I tried using the links for individual releases ( eg: https://launchpad.net/ubuntu/warty/). But when I sum up the bug count from such individual releases, they don't seem to match up against the one obtained by using " https://bugs.launchpad.net/ubuntu/". Any information regarding the same would be of great help. Regards Prasanth -------------- next part -------------- An HTML attachment was scrubbed... URL: From martinmai1024 at web.de Tue Feb 10 14:32:21 2009 From: martinmai1024 at web.de (Martin Mai) Date: Tue, 10 Feb 2009 15:32:21 +0100 Subject: Announcing the Next Ubuntu Hug Day! - 12th of February, 2009 Message-ID: <1234276341.5524.1.camel@martin-desktop> This week's HugDay target is *drum roll please* bugs without a package! Bookmark it, add it to your calendars, turn over those egg-timers! * 12th of February, 2009 * http://wiki.ubuntu.com/UbuntuBugDay/20090212 Can't stress it enough: everyone can help! Have some time? Triage boogz! I won't be upset if you get a headstart~ ;) Have a blog? Blog about Hugday! Have some screen space? Open #ubuntu-bugs and keep an eye out for newcomers in need. Have minions? Teach THEM to triage for you! :) Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! Make a difference; we will be in #ubuntu-bugs (FreeNode) all day and night, and will be ready to answer your questions about how to help. If you're new to all this, head to http://wiki.ubuntu.com/HelpingWithBugs Have a nice day, Martin Mai [From the BugSquad] -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From glgxg at sbcglobal.net Tue Feb 10 16:28:33 2009 From: glgxg at sbcglobal.net (NoOp) Date: Tue, 10 Feb 2009 08:28:33 -0800 Subject: Announcing the Next Ubuntu Hug Day! - 12th of February, 2009 In-Reply-To: <1234276341.5524.1.camel@martin-desktop> References: <1234276341.5524.1.camel@martin-desktop> Message-ID: On 02/10/2009 06:32 AM, Martin Mai wrote: > This week's HugDay target is *drum roll please* bugs without a package! > You should probably also add this link for this particular HugDay: https://wiki.ubuntu.com/Bugs/FindRightPackage From pedro at ubuntu.com Tue Feb 10 17:39:51 2009 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Tue, 10 Feb 2009 14:39:51 -0300 Subject: Announcing the Next Ubuntu Hug Day! - 12th of February, 2009 In-Reply-To: References: <1234276341.5524.1.camel@martin-desktop> Message-ID: <1234287591.4520.16.camel@thylacine> Hello, On Tue, 2009-02-10 at 08:28 -0800, NoOp wrote: > On 02/10/2009 06:32 AM, Martin Mai wrote: > > This week's HugDay target is *drum roll please* bugs without a package! > > > > You should probably also add this link for this particular HugDay: > > https://wiki.ubuntu.com/Bugs/FindRightPackage > that's already linked on the wiki page of the hug day : https://wiki.ubuntu.com/UbuntuBugDay/20090212#Guidance Regards, pedro. From macoafi at gmail.com Tue Feb 10 17:57:05 2009 From: macoafi at gmail.com (Mackenzie Morgan) Date: Tue, 10 Feb 2009 12:57:05 -0500 Subject: Identifying the Ubuntu release in a bug In-Reply-To: <7f75fcac0902100609t59b966bo85e3976688650703@mail.gmail.com> References: <7f75fcac0902100609t59b966bo85e3976688650703@mail.gmail.com> Message-ID: <1234288625.15217.0.camel@betty> On Tue, 2009-02-10 at 09:09 -0500, Prasanth Anbalagan wrote: > Could someone help me how to identify the ubuntu release in such > cases. If the user included the package version, you can do: rmadison and look for that package version to see which release it's in. -- Mackenzie Morgan http://ubuntulinuxtipstricks.blogspot.com apt-get moo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From brian at ubuntu.com Tue Feb 10 18:08:08 2009 From: brian at ubuntu.com (Brian Murray) Date: Tue, 10 Feb 2009 10:08:08 -0800 Subject: Identifying the Ubuntu release in a bug In-Reply-To: <1234288625.15217.0.camel@betty> References: <7f75fcac0902100609t59b966bo85e3976688650703@mail.gmail.com> <1234288625.15217.0.camel@betty> Message-ID: <20090210180808.GB3025@murraytwins.com> On Tue, Feb 10, 2009 at 12:57:05PM -0500, Mackenzie Morgan wrote: > On Tue, 2009-02-10 at 09:09 -0500, Prasanth Anbalagan wrote: > > Could someone help me how to identify the ubuntu release in such > > cases. > > If the user included the package version, you can do: > rmadison > and look for that package version to see which release it's in. This will only return information about releases available via the archive so will not include unsupported releases. Additionally, if a package version was superceded, like during the development of a release, that package version will not be returned by rmadison. However, rmadison and the package version can give you a rough guess as to which release the bug was found in. -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From brian at ubuntu.com Tue Feb 10 16:38:53 2009 From: brian at ubuntu.com (Brian Murray) Date: Tue, 10 Feb 2009 08:38:53 -0800 Subject: Identifying the Ubuntu release in a bug In-Reply-To: <7f75fcac0902100609t59b966bo85e3976688650703@mail.gmail.com> References: <7f75fcac0902100609t59b966bo85e3976688650703@mail.gmail.com> Message-ID: <20090210163853.GA3025@murraytwins.com> On Tue, Feb 10, 2009 at 09:09:21AM -0500, Prasanth Anbalagan wrote: > Hi all, > > I'm trying to identify the ubuntu release against which the bug were > actually reported in > > https://bugs.launchpad.net/ubuntu/ > > For example, the following bug does not have the info. > > https://bugs.launchpad.net/ubuntu/+bug/7261 > > Could someone help me how to identify the ubuntu release in such cases. > Aren't there standard fields that identify the releases? I tried using the > links for individual releases ( eg: https://launchpad.net/ubuntu/warty/). > But when I sum up the bug count from such individual releases, they don't > seem to match up against the one obtained by using " > https://bugs.launchpad.net/ubuntu/". Any information regarding the same > would be of great help. When a bug is reported about Ubuntu it is considered to affect the latest version of Ubuntu unless specified otherwise. In your particular case we can look at the date the bug was reported, 2004-08, and guess that it affects 4.10. With regards to https://launchpad.net/ubuntu/warty/ - this is a list of bugs that were targeted to the Warty release. A bug that has a release task will have sub-entries indicating the name of the release. If you look at bug 274714 you can see it has an Intrepid release task - meaning that it was targeted for fixing in Intrepid. Another thing to note is that bugs reported using apport (Help - Report a Problem, ubuntu-bug, or an apport crash) automatically gather the version of Ubuntu that the bug is being reported from. This information then is available in the bug's description in the DistroRelease portion. -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From thekorn at gmx.de Wed Feb 11 11:15:16 2009 From: thekorn at gmx.de (markus korn) Date: Wed, 11 Feb 2009 12:15:16 +0100 Subject: New version of hugday tools! In-Reply-To: <7533d3600902020048k42e49a6bx219d29023872bb03@mail.gmail.com> References: <7533d3600902020048k42e49a6bx219d29023872bb03@mail.gmail.com> Message-ID: <7533d3600902110315r7a8571eft728fe25e37b6753d@mail.gmail.com> Just a quick update, the hugday tool is now part of ubuntu-qa-tools (0.1.1) Thanks to everyone who make that happen, Markus From martinmai1024 at web.de Tue Feb 17 15:58:42 2009 From: martinmai1024 at web.de (Martin Mai) Date: Tue, 17 Feb 2009 16:58:42 +0100 Subject: Announcing the Next Ubuntu Hug Day! - 19th of February, 2009 Message-ID: <1234886322.6879.12.camel@martin-desktop> Fellow Ubuntu Triagers! This week's HugDay target is *drum roll please* network-manager-applet! * #88 New bugs need a hug * #23 Incomplete bugs need a status check * #25 Confirmed bugs need a review Bookmark it, add it to your calendars, turn over those egg-timers! * 19th of February, 2009 * http://wiki.ubuntu.com/UbuntuBugDay/20090219 Can't stress it enough: everyone can help! Have some time? Triage boogz! I won't be upset if you get a headstart~ ;) Have a blog? Blog about Hugday! Have some screen space? Open #ubuntu-bugs and keep an eye out for newcomers in need. Have minions? Teach THEM to triage for you! :) Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! Make a difference; we will be in #ubuntu-bugs (FreeNode) all day and night, and will be ready to answer your questions about how to help. If you're new to all this, head to http://wiki.ubuntu.com/HelpingWithBugs Have a nice day, Martin Mai [From the BugSquad] -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From ara at ubuntu.com Wed Feb 18 08:38:17 2009 From: ara at ubuntu.com (Ara Pulido) Date: Wed, 18 Feb 2009 09:38:17 +0100 Subject: Jaunty's new features testing day! Message-ID: <1234946297.7802.14.camel@sushirider> Hey all! We are pleased to announce the next Ubuntu Testing Day that will be next Monday, February 22nd. This time we are going to test new features in the next Ubuntu release (Jaunty Jackalope, future 9.04). This Thursday we are reaching Feature Freeze, meaning that all the new features, new software and all the new things that are not bug fixes should be in the archive that day. We are going to test three new features, depending on the flavor you're testing. This is all new stuff, so it can be fun to play around finding bugs nobody else have found before! If you don't want to upgrade to Jaunty yet, you can install it in a virtual machine and test from there. New features to be tested: * Screen Profiles * New UNR USB images * Improved Guided LVM partitioner Bookmark it, add it to your calendars, turn over those egg-timers! * 22nd of February, 2009 * https://wiki.ubuntu.com/Testing/UbuntuTestingDay/20090222 Who can join the Testing Day? Everyone. You don't need to be a developer. You don't need to know how to code. Everyone is welcome. If you don't know how to help, then just stop on by and we'll explain everything to you. In fact, one of the objectives of the Testing Day is to help people willing to start testing Ubuntu to make it better. Where to join the Testing Day? Come to #ubuntu-testing on freenode IRC. We will be there day and night resolving your testing questions you might have. Normal testing activity takes place in #ubuntu-testing at other times also. Please, join us next Monday and help to make Ubuntu even better! Cheers, Ara. From ara at ubuntu.com Wed Feb 18 14:22:20 2009 From: ara at ubuntu.com (Ara Pulido) Date: Wed, 18 Feb 2009 15:22:20 +0100 Subject: Jaunty's new features testing day! In-Reply-To: <1234946297.7802.14.camel@sushirider> References: <1234946297.7802.14.camel@sushirider> Message-ID: <1234966940.7802.66.camel@sushirider> Of course this is Monday, February 23rd. Sorry! On Wed, 2009-02-18 at 09:38 +0100, Ara Pulido wrote: > Hey all! > > We are pleased to announce the next Ubuntu Testing Day that will be next > Monday, February 22nd. > > This time we are going to test new features in the next Ubuntu release > (Jaunty Jackalope, future 9.04). This Thursday we are reaching Feature > Freeze, meaning that all the new features, new software and all the new > things that are not bug fixes should be in the archive that day. > > We are going to test three new features, depending on the flavor you're > testing. This is all new stuff, so it can be fun to play around finding > bugs nobody else have found before! If you don't want to upgrade to > Jaunty yet, you can install it in a virtual machine and test from there. > > New features to be tested: > * Screen Profiles > * New UNR USB images > * Improved Guided LVM partitioner > > Bookmark it, add it to your calendars, turn over those egg-timers! > * 22nd of February, 2009 > * https://wiki.ubuntu.com/Testing/UbuntuTestingDay/20090222 > > > Who can join the Testing Day? > Everyone. You don't need to be a developer. You don't need to know how > to code. Everyone is welcome. If you don't know how to help, then just > stop on by and we'll explain everything to you. In fact, one of the > objectives of the Testing Day is to help people willing to start testing > Ubuntu to make it better. > > Where to join the Testing Day? > Come to #ubuntu-testing on freenode IRC. We will be there day and night > resolving your testing questions you might have. Normal testing activity > takes place in #ubuntu-testing at other times also. > > Please, join us next Monday and help to make Ubuntu even better! > > Cheers, > Ara. > > > From jorge at ubuntu.com Wed Feb 18 20:51:04 2009 From: jorge at ubuntu.com (Jorge O. Castro) Date: Wed, 18 Feb 2009 15:51:04 -0500 Subject: New tool for opening upstream tasks Message-ID: At UDS I went over the upstream report[1] and pointed out how we do a good job of linking Ubuntu bugs to upstream bugs when we know it's an upstream bug but we generally don't do a decent job of marking bugs as affecting upstream in the first place. After the session I asked around and asked why people weren't linking bugs. The overwhelming response was that it was an extra step in the process and that it took so long, so unless it was a serious bug they didn't bother. So now that LP has an API for manipulating bugs I asked Graham Binns to make a script that will make "bulk opening of upstream tasks" possible. The script is called upstream-packagebugs[2]. Here's an example: ./upstream-packagebugs tomboy --debug You'll want the --debug to see exactly which bugs it's pulling. The script will open a new tab and ask you to auth with launchpad (you only have to do this once). Then it will grab all the Tomboy bugs that are TRIAGED and do NOT have an open upstream task and return those one at a time asking you to open an upstream bug task. You then answer yes or no to each bug, and then it goes and opens the blank upstream task for that package. As I envision the workflow, you basically do your bugwork for the day, then when you're ready to close out the day, you run the script and pick the bugs you've triaged for the day that affect upstream and then you're done. I've opened two bugs[3] that I think would make this tool more useful to bulk-open tasks, anyone can feel free to fix them/add information! Some things you might want to know: a) It can be slow. It'll definitely be slow the first time, since it's snagging all the bugs. The script does caching after you say Y or N to it, so it does get faster as you use it. The nice thing this provides over say, using the web interface is that while you do wait, you can do bulk opening after it's done. You can also fire up multiple instances on multiple projects for the win. b) This is an experiment to see how we can improve opening more upstream tasks. It's not going to magically find upstream bugs and link them or anything like that (yet). IMO that's a separate problem handled separately, the purpose of this tool is to allow developers and triagers to open blank upstream tasks easily, since we're not doing that very well. c) Some people have told me that with their specific projects the default action should be to open a blank upstream task and have declining that be the option instead of the way it is now. I am interested in feedback on this. So please try this, kick the tires, and start opening blank upstream tasks, especially those of you with terrible upstream linkage percentages. As the numbers of open tasks grow we can then help focus triaging efforts on those to get those bugs filed upstream and linked. [1] https://edge.launchpad.net/ubuntu/+upstreamreport [2] https://launchpad.net/lp-upstream-tools (you can grab it via "bzr branch lp:lp-upstream-tools") [3] https://bugs.launchpad.net/lp-upstream-tools/+bugs -- Jorge Castro jorge (at) ubuntu.com External Project Developer Relations Canonical Ltd. From mrooney at gmail.com Wed Feb 18 22:01:02 2009 From: mrooney at gmail.com (Mike Rooney) Date: Wed, 18 Feb 2009 14:01:02 -0800 Subject: New tool for opening upstream tasks In-Reply-To: References: Message-ID: <4f4806ee0902181401k7aabeda2qcb0e377c52a6cbe2@mail.gmail.com> On Wed, Feb 18, 2009 at 12:51 PM, Jorge O. Castro wrote: > > c) Some people have told me that with their specific projects the > default action should be to open a blank upstream task and have > declining that be the option instead of the way it is now. I am > interested in feedback on this. So please try this, kick the tires, > and start opening blank upstream tasks, especially those of you with > terrible upstream linkage percentages. As the numbers of open tasks > grow we can then help focus triaging efforts on those to get those > bugs filed upstream and linked. > This would be very useful I think. Launchpad already allows you to link an Ubuntu package to an upstream one, so it would be nice if, as the owner/maintainer of the associated upstream, I could tell Launchpad to automatically mark the task as affecting upstream as well and let me invalidate them as appropriate. Especially for packages with minor or non-existent differences from upstream (or upstream projects which explicitly support Ubuntu, which seem to be growing in number), it is likely the bug is an upstream issue. -- Michael Rooney mrooney at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.holbach at ubuntu.com Thu Feb 19 05:35:48 2009 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Thu, 19 Feb 2009 06:35:48 +0100 Subject: New tool for opening upstream tasks In-Reply-To: References: Message-ID: <499CEFB4.3040108@ubuntu.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jorge O. Castro schrieb: > So now > that LP has an API for manipulating bugs I asked Graham Binns to make > a script that will make "bulk opening of upstream tasks" possible. The > script is called upstream-packagebugs[2]. Here's an example: > > ./upstream-packagebugs tomboy --debug Do you think it would make sense to put it into ~ubuntu-bugcontrol/ubuntu-qa-tools/master ? It's even packaged and in the distro. Have a great day, Daniel - -- https://wiki.ubuntu.com/GlobalBugJam - 20-22 February 2009 Join in on the fun with YOUR team! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmc77QACgkQRjrlnQWd1eslrQCcCDzrIb02iQj86bhb3v6an6Gd wP0An36vpAgqQwYcOQ9tGy2u3IkW9Xs8 =Wtyt -----END PGP SIGNATURE----- From jorge at ubuntu.com Thu Feb 19 15:02:00 2009 From: jorge at ubuntu.com (Jorge O. Castro) Date: Thu, 19 Feb 2009 10:02:00 -0500 Subject: New tool for opening upstream tasks In-Reply-To: <499CEFB4.3040108@ubuntu.com> References: <499CEFB4.3040108@ubuntu.com> Message-ID: On Thu, Feb 19, 2009 at 12:35 AM, Daniel Holbach wrote: > Do you think it would make sense to put it into > ~ubuntu-bugcontrol/ubuntu-qa-tools/master ? It's even packaged and in > the distro. I think eventually this will be the right place for it, I guess if people really start to use it and we get in some more features to make it more useful then I think that's a good idea. -- Jorge Castro jorge (at) ubuntu.com External Project Developer Relations Canonical Ltd. From chuckfrain at pobox.com Thu Feb 19 16:29:28 2009 From: chuckfrain at pobox.com (Chuck Frain) Date: Thu, 19 Feb 2009 11:29:28 -0500 Subject: New tool for opening upstream tasks In-Reply-To: References: Message-ID: Out of curiosity (I've not found an answer yet), what is the best way to tell if a bug is an upstream issue vs an Ubuntu specific issue? If there is a page out there that explains it please feel free to point me in the appropriate direction. Thanks! Chuck On Wed, Feb 18, 2009 at 3:51 PM, Jorge O. Castro wrote: > At UDS I went over the upstream report[1] and pointed out how we do a > good job of linking Ubuntu bugs to upstream bugs when we know it's an > upstream bug but we generally don't do a decent job of marking bugs as > affecting upstream in the first place. After the session I asked > around and asked why people weren't linking bugs. The overwhelming > response was that it was an extra step in the process and that it took > so long, so unless it was a serious bug they didn't bother. So now > that LP has an API for manipulating bugs I asked Graham Binns to make > a script that will make "bulk opening of upstream tasks" possible. The > script is called upstream-packagebugs[2]. Here's an example: -------------- next part -------------- An HTML attachment was scrubbed... URL: From jorge at ubuntu.com Thu Feb 19 19:13:34 2009 From: jorge at ubuntu.com (Jorge O. Castro) Date: Thu, 19 Feb 2009 14:13:34 -0500 Subject: New tool for opening upstream tasks In-Reply-To: References: Message-ID: On Thu, Feb 19, 2009 at 11:29 AM, Chuck Frain wrote: > Out of curiosity (I've not found an answer yet), what is the best way to > tell if a bug is an upstream issue vs an Ubuntu specific issue? If there is > a page out there that explains it please feel free to point me in the > appropriate direction. I tend to look in debian/patches or see how many patches with have vs. debian on patches.ubuntu.com. I tend to lean on "this is probably upstream" if a package is in universe and more obscure, but that's just me. -- Jorge Castro jorge (at) ubuntu.com External Project Developer Relations Canonical Ltd. From daniel.holbach at ubuntu.com Sat Feb 21 13:28:34 2009 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Sat, 21 Feb 2009 14:28:34 +0100 Subject: 5-a-day changes Message-ID: <49A00182.6020409@ubuntu.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everybody, I announced it at http://daniel.holba.ch/blog/?p=366 already: the 5-a-day initiative is going to change. Let's face it - the 5-a-day tool and applet were too complicated. Now it's enough to click on https://launchpad.net/~5-a-day-participants/+join and join the team. If you're at a Bug Jam, add yourself to https://wiki.ubuntu.com/Bugs/Events too and your bugs will get counted as well. No 5-a-day-applet, no 5-a-day client necessary any more. Statistics will be up ASAP and announced. :-) https://wiki.ubuntu.com/5-A-Day Have a great day, jam on! Daniel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmgAYEACgkQRjrlnQWd1esVugCdFGhMlAYwR6celKZIrMPbgKzG ViwAn2zjLoULeo0MQmi7VtPiirz5oCb+ =/ln/ -----END PGP SIGNATURE----- From dantrevino at gmail.com Sat Feb 21 13:37:50 2009 From: dantrevino at gmail.com (dan) Date: Sat, 21 Feb 2009 08:37:50 -0500 Subject: 5-a-day changes In-Reply-To: <49A00182.6020409@ubuntu.com> References: <49A00182.6020409@ubuntu.com> Message-ID: How is team or tag participation managed? On Feb 21, 2009 8:32 AM, "Daniel Holbach" wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everybody, I announced it at http://daniel.holba.ch/blog/?p=366 already: the 5-a-day initiative is going to change. Let's face it - the 5-a-day tool and applet were too complicated. Now it's enough to click on https://launchpad.net/~5-a-day-participants/+join and join the team. If you're at a Bug Jam, add yourself to https://wiki.ubuntu.com/Bugs/Events too and your bugs will get counted as well. No 5-a-day-applet, no 5-a-day client necessary any more. Statistics will be up ASAP and announced. :-) https://wiki.ubuntu.com/5-A-Day Have a great day, jam on! Daniel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmgAYEACgkQRjrlnQWd1esVugCdFGhMlAYwR6celKZIrMPbgKzG ViwAn2zjLoULeo0MQmi7VtPiirz5oCb+ =/ln/ -----END PGP SIGNATURE----- -- Ubuntu-bugsquad mailing list Ubuntu-bugsquad at lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.holbach at ubuntu.com Sat Feb 21 15:33:47 2009 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Sat, 21 Feb 2009 16:33:47 +0100 Subject: 5-a-day changes In-Reply-To: References: <49A00182.6020409@ubuntu.com> Message-ID: <49A01EDB.3010804@ubuntu.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 dan schrieb: > How is team or tag participation managed? Team participation is not there yet, but will come soon. The good thing about the new system is: no data is lost, but will be added to the stats retroactively, because we get the data from Launchpad. Tags were "replaced" by Bug Jams and Hug days which are "managed" through https://wiki.ubuntu.com/Bugs/Events - the Hug days stats will be added soon as well. Have a great day, Daniel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmgHtsACgkQRjrlnQWd1etJNgCcCBrWPdi9GZkgj3JnOMyw88kI uR4An1kMJCwmYB4l8vx3y+vCp92hA+iy =7897 -----END PGP SIGNATURE----- From daniel.holbach at ubuntu.com Mon Feb 23 15:54:19 2009 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Mon, 23 Feb 2009 16:54:19 +0100 Subject: After the Global Bug Jam Message-ID: <49A2C6AB.80000@ubuntu.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everybody, the second Global Bug Jam was a huge success. I've been very happy with all I've heard and what happened in Berlin. :-) A few stories about the Global Bug Jam were posted at https://wiki.ubuntu.com/GlobalBugJam/Stories - it'd be great if you could add yours and maybe also add a few words about what you did, how it all went, etc. I would like to propose that we do the next Global Bug Jam around the same time of the release cycle of Karmic Koala again. What do you think we should do better next time? Have a great day, Daniel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmixqsACgkQRjrlnQWd1euJdgCcD3w0l3Tm95eUwUafp7H6M1Bd auIAn1/7LjE3FdYO98kC4HJ69iCcKIK1 =fHGm -----END PGP SIGNATURE----- From greg.grossmeier at gmail.com Mon Feb 23 20:16:17 2009 From: greg.grossmeier at gmail.com (Greg Grossmeier) Date: Mon, 23 Feb 2009 15:16:17 -0500 Subject: After the Global Bug Jam In-Reply-To: References: <49A2C6AB.80000@ubuntu.com> Message-ID: On Mon, Feb 23, 2009 at 12:19 PM, Jim Campbell wrote: > As for suggestions, the five-a-day and bug squad wiki pages are good > info resources, but it would be great to have a one-page bug-link > cheat sheet, too. Our bug jam brought out a bunch of people who had > never triaged bugs before, and we had a lot of quick questions that > are answered on the wiki, but it can take time to track them down if > you aren't familiar with the bug team wiki pages. (I'm not faulting > the layout of the bug team wiki pages, it's just that there's a lot of > content out there). We put together a *very* spare bugs link page on > the Chicago Team wiki ( https://wiki.ubuntu.com/ChicagoTeam/Links - > it's, um, very spare . . . ), but having a comprehensive one-pager > could help us work through things more quickly as we scurry to fix > bugs. I like that idea. Kinda like the playbooks we have for packaging and 5-a-day now. The one for 5-a-day currently doesn't have specific instructions on how to sign up/report your bugs/etc which means that A) it is still ok to use and B) isn't really something we can hand out to get people started easily. Maybe we could write something up in a similar fashion for specific instructions. Have it use the same kind of logos/format so it looks really nice when printed in color. We (Michigan) handed these out at our event at Penguicon last year for the packaging jam and they were a big hit! greg From daniel.holbach at ubuntu.com Tue Feb 24 07:21:02 2009 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Tue, 24 Feb 2009 08:21:02 +0100 Subject: After the Global Bug Jam In-Reply-To: References: <49A2C6AB.80000@ubuntu.com> Message-ID: <49A39FDE.8030805@ubuntu.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greg Grossmeier schrieb: > I like that idea. Kinda like the playbooks we have for packaging and > 5-a-day now. The one for 5-a-day currently doesn't have specific > instructions on how to sign up/report your bugs/etc which means that > A) it is still ok to use and B) isn't really something we can hand out > to get people started easily. Check out https://wiki.ubuntu.com/GlobalBugJam?action=AttachFile - what do you think about GlobalBugJam.pdf? Also do you think https://wiki.ubuntu.com/Bugs/HowToTriage/Charts is helpful? Anything we need to add to https://wiki.ubuntu.com/RunningBugJam#Material ? Have a great day, Daniel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmjn94ACgkQRjrlnQWd1esO/gCfb+DFKgizK4CGiNwhPQz7VgkM sEoAn38QptSotAW77UL1aM/eb/0o/p7g =6UH5 -----END PGP SIGNATURE----- From martinmai1024 at web.de Tue Feb 24 11:20:06 2009 From: martinmai1024 at web.de (Martin Mai) Date: Tue, 24 Feb 2009 12:20:06 +0100 Subject: Announcing the Next Ubuntu Hug Day! - 26th of February, 2009 Message-ID: <1235474406.5590.5.camel@martin-desktop> Fellow Ubuntu Triagers! This week's HugDay target is *drum roll please* Apport bugs with failed traces! * #193 Apport bugs need to be checked Bookmark it, add it to your calendars, turn over those egg-timers! * 26th of February, 2009 * http://wiki.ubuntu.com/UbuntuBugDay/20090226 Can't stress it enough: everyone can help! Have some time? Triage boogz! I won't be upset if you get a headstart~ ;) Have a blog? Blog about Hugday! Have some screen space? Open #ubuntu-bugs and keep an eye out for newcomers in need. Have minions? Teach THEM to triage for you! :) Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! Make a difference; we will be in #ubuntu-bugs (FreeNode) all day and night, and will be ready to answer your questions about how to help. If you're new to all this, head to http://wiki.ubuntu.com/HelpingWithBugs Have a nice day, Martin Mai [From the BugSquad] -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From brian at ubuntu.com Tue Feb 24 22:27:04 2009 From: brian at ubuntu.com (Brian Murray) Date: Tue, 24 Feb 2009 14:27:04 -0800 Subject: Greasemonkey Stock Replies Update Message-ID: <20090224222704.GQ6766@murraytwins.com> I blogged[0] about this the other day but think it is useful enough that an e-mail is in order too. Kees and I have updated the Launchpad Greasemonkey standard reply script[1] so that common standard replies are pulled in from a central location[2] on a regular basis. I've added the majority of the responses from the wiki[3], however if your favorite one is missing file a bug about the Launchpad Greasemonkey Scripts project[4] and I'll get it added. I hope this makes triaging bugs a bit easier! [0] http://www.murraytwins.com/blog/?p=34 [1] http://bazaar.launchpad.net/~gm-dev-launchpad/launchpad-gm-scripts/master/files [2] http://people.ubuntu.com/~brian/greasemonkey/bugsquad-replies.xml [3] https://wiki.ubuntu.com/Bugs/Responses [4] https://launchpad.net/launchpad-gm-scripts/+filebug -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From ara at ubuntu.com Wed Feb 25 12:03:17 2009 From: ara at ubuntu.com (Ara Pulido) Date: Wed, 25 Feb 2009 13:03:17 +0100 Subject: 5-a-day changes In-Reply-To: <49A01EDB.3010804@ubuntu.com> References: <49A00182.6020409@ubuntu.com> <49A01EDB.3010804@ubuntu.com> Message-ID: <1235563397.22181.0.camel@sushirider> Hello Daniel, Is it possible to add also Testing Days data? Thanks, Ara. On Sat, 2009-02-21 at 16:33 +0100, Daniel Holbach wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > dan schrieb: > > How is team or tag participation managed? > > Team participation is not there yet, but will come soon. The good thing > about the new system is: no data is lost, but will be added to the stats > retroactively, because we get the data from Launchpad. > > Tags were "replaced" by Bug Jams and Hug days which are "managed" > through https://wiki.ubuntu.com/Bugs/Events - the Hug days stats will be > added soon as well. > > Have a great day, > Daniel > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkmgHtsACgkQRjrlnQWd1etJNgCcCBrWPdi9GZkgj3JnOMyw88kI > uR4An1kMJCwmYB4l8vx3y+vCp92hA+iy > =7897 > -----END PGP SIGNATURE----- > From azimout at gmail.com Wed Feb 25 12:51:47 2009 From: azimout at gmail.com (Dimitris Symeonidis) Date: Wed, 25 Feb 2009 13:51:47 +0100 Subject: Greasemonkey Stock Replies Update Message-ID: <36265bc20902250451k6608fa4bu94f43f1b41e6223@mail.gmail.com> Brian, you might want to also update the README file to reflect these changes... Thanx for all your work Dimitris Symeonidis "If you think you're too small to make a difference, try sleeping with a mosquito!" - Amnesty International From daniel.holbach at ubuntu.com Wed Feb 25 13:12:46 2009 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Wed, 25 Feb 2009 14:12:46 +0100 Subject: 5-a-day changes In-Reply-To: <1235563397.22181.0.camel@sushirider> References: <49A00182.6020409@ubuntu.com> <49A01EDB.3010804@ubuntu.com> <1235563397.22181.0.camel@sushirider> Message-ID: <49A543CE.7080001@ubuntu.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ara Pulido schrieb: > Is it possible to add also Testing Days data? How would that work? What kind of data would be involved there? Have a great day, Daniel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEUEARECAAYFAkmlQ84ACgkQRjrlnQWd1euTjwCffh6jNl5GL3o3zRIfMnLaEfks jxIAliFlkA7lG8FzFO6bZ0cmwphqqPM= =5Gxx -----END PGP SIGNATURE----- From ara at ubuntu.com Wed Feb 25 15:04:03 2009 From: ara at ubuntu.com (Ara Pulido) Date: Wed, 25 Feb 2009 16:04:03 +0100 Subject: 5-a-day changes In-Reply-To: <49A543CE.7080001@ubuntu.com> References: <49A00182.6020409@ubuntu.com> <49A01EDB.3010804@ubuntu.com> <1235563397.22181.0.camel@sushirider> <49A543CE.7080001@ubuntu.com> Message-ID: <49A55DE3.5090501@ubuntu.com> Same thing, bugs filed or touched while testing. Daniel Holbach wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Ara Pulido schrieb: >> Is it possible to add also Testing Days data? > > How would that work? What kind of data would be involved there? > > Have a great day, > Daniel > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEUEARECAAYFAkmlQ84ACgkQRjrlnQWd1euTjwCffh6jNl5GL3o3zRIfMnLaEfks > jxIAliFlkA7lG8FzFO6bZ0cmwphqqPM= > =5Gxx > -----END PGP SIGNATURE----- > From mrooney at gmail.com Wed Feb 25 18:17:50 2009 From: mrooney at gmail.com (Mike Rooney) Date: Wed, 25 Feb 2009 10:17:50 -0800 Subject: Greasemonkey Stock Replies Update In-Reply-To: <20090224222704.GQ6766@murraytwins.com> References: <20090224222704.GQ6766@murraytwins.com> Message-ID: <4f4806ee0902251017u1bc27dedhe7cc3884a0efdcd@mail.gmail.com> On Tue, Feb 24, 2009 at 2:27 PM, Brian Murray wrote: > I blogged[0] about this the other day but think it is useful enough that > an e-mail is in order too. > > Kees and I have updated the Launchpad Greasemonkey standard reply > script[1] so that common standard replies are pulled in from a central > location[2] on a regular basis. > > I've added the majority of the responses from the wiki[3], however if > your favorite one is missing file a bug about the Launchpad Greasemonkey > Scripts project[4] and I'll get it added. > > I hope this makes triaging bugs a bit easier! > > Thanks, this is an excellent usability improvement! Two questions: - Is there any plan to consolidate a lot of the popular scripts (such as this, karma, button tags, patches) into an extension which could be installed via a package, and included in qa-tools or something? Having multiple computers, and fresh installs of release+1 alphas/betas and such, often means I forget to install these or have them out of sync with the latest in VC. - It would be neat to have variables such as %n that would automatically change to the persons LP username, to create more personal messages so they don't seem so impersonal. I change all my messages to include the persons name but having this included could be cool as well. Does anyone else do this? And, and a third question :) If I change a message, will it get overwritten on the next XML update? -- Michael Rooney mrooney at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian at ubuntu.com Wed Feb 25 18:40:02 2009 From: brian at ubuntu.com (Brian Murray) Date: Wed, 25 Feb 2009 10:40:02 -0800 Subject: Greasemonkey Stock Replies Update In-Reply-To: <4f4806ee0902251017u1bc27dedhe7cc3884a0efdcd@mail.gmail.com> References: <20090224222704.GQ6766@murraytwins.com> <4f4806ee0902251017u1bc27dedhe7cc3884a0efdcd@mail.gmail.com> Message-ID: <20090225184001.GV6766@murraytwins.com> On Wed, Feb 25, 2009 at 10:17:50AM -0800, Mike Rooney wrote: > On Tue, Feb 24, 2009 at 2:27 PM, Brian Murray wrote: > > > I blogged[0] about this the other day but think it is useful enough that > > an e-mail is in order too. > > > > Kees and I have updated the Launchpad Greasemonkey standard reply > > script[1] so that common standard replies are pulled in from a central > > location[2] on a regular basis. > > > > I've added the majority of the responses from the wiki[3], however if > > your favorite one is missing file a bug about the Launchpad Greasemonkey > > Scripts project[4] and I'll get it added. > > > > I hope this makes triaging bugs a bit easier! > > > > > Thanks, this is an excellent usability improvement! Great, I'm glad to hear it! > Two questions: > > - Is there any plan to consolidate a lot of the popular scripts (such as > this, karma, button tags, patches) into an extension which could be > installed via a package, and included in qa-tools or something? Having > multiple computers, and fresh installs of release+1 alphas/betas and such, > often means I forget to install these or have them out of sync with the > latest in VC. I personally don't know anything about writing Firefox extensions so don't have any plans to do it, additionally I believe a fair bit of work is need to convert a greasemonkey script into an extension. However, maybe we could get them into the ubuntu-qa-tools package and have the scripts installed somehow. > - It would be neat to have variables such as %n that would automatically > change to the persons LP username, to create more personal messages so they > don't seem so impersonal. I change all my messages to include the persons > name but having this included could be cool as well. Does anyone else do > this? I'd really like to rewrite the greasemonkey scripts to use the javascript version of the Launchpad API but haven't made any headway here. If they were updated to use this API I imagine it'd be easier to grab the reporter's name and have it inserted via a variable. > And, and a third question :) If I change a message, will it get overwritten > on the next XML update? If you locally modify a standard reply that exists in the XML file and then pull the standard replies it seems (I had to test it myself) that your modification will get overwritten. This might be the right thing to do since if you are making changes to a standard reply it should probably exist in the XML file - right? However, there should probably be a way to distinguish between the replies that are from the XML file and those that are not. -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From brian at ubuntu.com Wed Feb 25 19:45:27 2009 From: brian at ubuntu.com (Brian Murray) Date: Wed, 25 Feb 2009 11:45:27 -0800 Subject: Greasemonkey Stock Replies Update In-Reply-To: <20090225184001.GV6766@murraytwins.com> References: <20090224222704.GQ6766@murraytwins.com> <4f4806ee0902251017u1bc27dedhe7cc3884a0efdcd@mail.gmail.com> <20090225184001.GV6766@murraytwins.com> Message-ID: <20090225194527.GW6766@murraytwins.com> On Wed, Feb 25, 2009 at 10:40:02AM -0800, Brian Murray wrote: > On Wed, Feb 25, 2009 at 10:17:50AM -0800, Mike Rooney wrote: > > On Tue, Feb 24, 2009 at 2:27 PM, Brian Murray wrote: > > > > > I blogged[0] about this the other day but think it is useful enough that > > > an e-mail is in order too. > > > > > > Kees and I have updated the Launchpad Greasemonkey standard reply > > > script[1] so that common standard replies are pulled in from a central > > > location[2] on a regular basis. > > > > > > I've added the majority of the responses from the wiki[3], however if > > > your favorite one is missing file a bug about the Launchpad Greasemonkey > > > Scripts project[4] and I'll get it added. > > > > > > I hope this makes triaging bugs a bit easier! > > > > > > > > Thanks, this is an excellent usability improvement! > > Great, I'm glad to hear it! > > > Two questions: > > > > - Is there any plan to consolidate a lot of the popular scripts (such as > > this, karma, button tags, patches) into an extension which could be > > installed via a package, and included in qa-tools or something? Having > > multiple computers, and fresh installs of release+1 alphas/betas and such, > > often means I forget to install these or have them out of sync with the > > latest in VC. > > I personally don't know anything about writing Firefox extensions so > don't have any plans to do it, additionally I believe a fair bit of work > is need to convert a greasemonkey script into an extension. However, > maybe we could get them into the ubuntu-qa-tools package and have the > scripts installed somehow. > > > - It would be neat to have variables such as %n that would automatically > > change to the persons LP username, to create more personal messages so they > > don't seem so impersonal. I change all my messages to include the persons > > name but having this included could be cool as well. Does anyone else do > > this? > > I'd really like to rewrite the greasemonkey scripts to use the > javascript version of the Launchpad API but haven't made any headway > here. If they were updated to use this API I imagine it'd be easier to > grab the reporter's name and have it inserted via a variable. > > > And, and a third question :) If I change a message, will it get overwritten > > on the next XML update? > > If you locally modify a standard reply that exists in the XML file and > then pull the standard replies it seems (I had to test it myself) that > your modification will get overwritten. This might be the right thing > to do since if you are making changes to a standard reply it should > probably exist in the XML file - right? Oops, I take that back. I now have a 2nd response with the same name, since I didn't change it, but with different content than the one in the XML file. Clearly this is the part Kees worked on! -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From mrooney at gmail.com Wed Feb 25 21:07:33 2009 From: mrooney at gmail.com (Mike Rooney) Date: Wed, 25 Feb 2009 13:07:33 -0800 Subject: Greasemonkey Stock Replies Update In-Reply-To: <20090225194527.GW6766@murraytwins.com> References: <20090224222704.GQ6766@murraytwins.com> <4f4806ee0902251017u1bc27dedhe7cc3884a0efdcd@mail.gmail.com> <20090225184001.GV6766@murraytwins.com> <20090225194527.GW6766@murraytwins.com> Message-ID: <4f4806ee0902251307k35429110q4ad45112987f2598@mail.gmail.com> On Wed, Feb 25, 2009 at 11:45 AM, Brian Murray wrote: > On Wed, Feb 25, 2009 at 10:40:02AM -0800, Brian Murray wrote: > > On Wed, Feb 25, 2009 at 10:17:50AM -0800, Mike Rooney wrote: > > > On Tue, Feb 24, 2009 at 2:27 PM, Brian Murray > wrote: > > > > > > > I blogged[0] about this the other day but think it is useful enough > that > > > > an e-mail is in order too. > > > > > > > > Kees and I have updated the Launchpad Greasemonkey standard reply > > > > script[1] so that common standard replies are pulled in from a > central > > > > location[2] on a regular basis. > > > > > > > > I've added the majority of the responses from the wiki[3], however if > > > > your favorite one is missing file a bug about the Launchpad > Greasemonkey > > > > Scripts project[4] and I'll get it added. > > > > > > > > I hope this makes triaging bugs a bit easier! > > > > > > > > > > > Thanks, this is an excellent usability improvement! > > > > Great, I'm glad to hear it! > > > > > Two questions: > > > > > > - Is there any plan to consolidate a lot of the popular scripts (such > as > > > this, karma, button tags, patches) into an extension which could be > > > installed via a package, and included in qa-tools or something? Having > > > multiple computers, and fresh installs of release+1 alphas/betas and > such, > > > often means I forget to install these or have them out of sync with the > > > latest in VC. > > > > I personally don't know anything about writing Firefox extensions so > > don't have any plans to do it, additionally I believe a fair bit of work > > is need to convert a greasemonkey script into an extension. However, > > maybe we could get them into the ubuntu-qa-tools package and have the > > scripts installed somehow. > It is actually pretty trivial as I understand it: http://lifehacker.com/software/greasemonkey/turn-your-greasemonkey-scripts-into-firefox-extensions-164741.php And I think there are already ubuntu packages which install a firefox extension, so it should be fairly straightforward. I can take a look at this if you like and think it would be worthwhile, and level up my packaging skills. > > > > > > - It would be neat to have variables such as %n that would > automatically > > > change to the persons LP username, to create more personal messages so > they > > > don't seem so impersonal. I change all my messages to include the > persons > > > name but having this included could be cool as well. Does anyone else > do > > > this? > > > > I'd really like to rewrite the greasemonkey scripts to use the > > javascript version of the Launchpad API but haven't made any headway > > here. If they were updated to use this API I imagine it'd be easier to > > grab the reporter's name and have it inserted via a variable. > > > > > And, and a third question :) If I change a message, will it get > overwritten > > > on the next XML update? > > > > If you locally modify a standard reply that exists in the XML file and > > then pull the standard replies it seems (I had to test it myself) that > > your modification will get overwritten. This might be the right thing > > to do since if you are making changes to a standard reply it should > > probably exist in the XML file - right? > > Oops, I take that back. I now have a 2nd response with the same name, > since I didn't change it, but with different content than the one in the > XML file. Clearly this is the part Kees worked on! Okay, so that is nice and would allow people to customize them with more personalization if desired, cool! Of course then you have to check to make sure yours is up to date with the latest changes and merge. -- Michael Rooney mrooney at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From vicedar at gmail.com Thu Feb 26 08:03:04 2009 From: vicedar at gmail.com (Savvas Radevic) Date: Thu, 26 Feb 2009 09:03:04 +0100 Subject: Why is needs-upstream-report tag kubuntu-specific? Message-ID: I was wondering if someone could explain why is the needs-upstream-report tag kubuntu-specific? This could be very well used for ubuntu packages as well, that need to be sent upstream and linked to launchpad. Such a tag would help to distinguish them from others. From vicedar at gmail.com Thu Feb 26 08:15:44 2009 From: vicedar at gmail.com (Savvas Radevic) Date: Thu, 26 Feb 2009 09:15:44 +0100 Subject: Why is needs-upstream-report tag kubuntu-specific? In-Reply-To: References: Message-ID: dholbach has just explained why: 09:07:42 < dholbach> savvas: I don't see why the tag should be used at all - we can simply open en empty upstream task 09:08:14 < dholbach> savvas: and can query it from the advanced bug page 09:10:23 < dholbach> savvas: on the advanced bug page it's "Show bugs that need to be forwarded to an upstream bug tracker So it's easy to find: https://bugs.launchpad.net/ubuntu/+bugs?field.status_upstream-empty-marker=1 We simply open an empty upstream task by clicking on "Also affects project" on the bug page! From gary_inman at hotmail.com Thu Feb 26 13:47:02 2009 From: gary_inman at hotmail.com (Gary Inman) Date: Thu, 26 Feb 2009 07:47:02 -0600 Subject: remove Message-ID: -------------- next part -------------- An HTML attachment was scrubbed... URL: From mok at bioxray.au.dk Fri Feb 27 08:19:28 2009 From: mok at bioxray.au.dk (Morten Kjeldgaard) Date: Fri, 27 Feb 2009 09:19:28 +0100 Subject: Please drop the please... please? Message-ID: <40A73538-9168-4374-8834-E65710777605@bioxray.au.dk> Hi, When I browsed the content of my mailbox folder with new bugmail this morning, I became mildly annoyed at the overly polite subjects "Please..." this or "Please..." that. Isn't it overdoing the (wonderful) Ubuntu politeness a bit? The result of all this verbiage in the mail subject is that the _interesting_ part of the subject is moved further to the right in the message listing where it is often truncated by the next column. So, couldn't we accept the technically exact "Sync foo" and "Backport foo" instead of "Please sync foo" and "Please backport foo"?? The "Please" can be put in the wording of the message, if politeness is required. Please? :-) Cheers, Morten -- Morten Kjeldgaard Ubuntu MOTU Developer GPG Key ID: 404825E7 From jonathan at ubuntu.com Fri Feb 27 13:37:58 2009 From: jonathan at ubuntu.com (Jonathan Carter (highvoltage)) Date: Fri, 27 Feb 2009 15:37:58 +0200 Subject: Please drop the please... please? In-Reply-To: <40A73538-9168-4374-8834-E65710777605@bioxray.au.dk> References: <40A73538-9168-4374-8834-E65710777605@bioxray.au.dk> Message-ID: <49A7ECB6.20903@ubuntu.com> Hi Morten Morten Kjeldgaard wrote: > So, couldn't we accept the technically exact "Sync foo" and "Backport > foo" instead of "Please sync foo" and "Please backport foo"?? The > "Please" can be put in the wording of the message, if politeness is > required. I agree, the "please" also sounds somewhat passive aggressive. Not sure if that's just me though :) -Jonathan From hggdh2 at gmail.com Fri Feb 27 14:16:16 2009 From: hggdh2 at gmail.com (hggdh) Date: Fri, 27 Feb 2009 08:16:16 -0600 Subject: Please drop the please... please? In-Reply-To: <40A73538-9168-4374-8834-E65710777605@bioxray.au.dk> References: <40A73538-9168-4374-8834-E65710777605@bioxray.au.dk> Message-ID: <20090227081616.1baac1e4@xango2> On Fri, 27 Feb 2009 09:19:28 +0100 Morten Kjeldgaard wrote: (snip) > So, couldn't we accept the technically exact "Sync foo" and > "Backport foo" instead of "Please sync foo" and "Please backport > foo"?? The "Please" can be put in the wording of the message, if > politeness is required. Well... I was against it, since when we open a (say) sync or merge *request* we are asking somebody else to do something that we either cannot do, or do not have the time, or whatever. So, politeness is absolutely required (as it always should be, BTW). On the other hand, a nicely worded request should be as good as a "please (sync|whatever) ...". After all, a bug subject should be as succinct as possible, and still carry enough information to nail the issue. So technical correctness would trump politeness on the subject, as you pointed out. I am not sure about the loss of real space on the subject, since we are talking about just 7 characters-worth of used space. Anyway, albeit reluctantly, I agree with your position (and actually had a bit of fun reading the subject). Nevertheless, we should keep in mind that politeness is an acquired, ah, skill, needs continuous honing, and can get lost easily, as shown on many flame wars. > Please? :-) It would be my pleasure ;-) So: +1. Cheers, ..hggdh.. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From vicedar at gmail.com Fri Feb 27 14:32:39 2009 From: vicedar at gmail.com (Savvas Radevic) Date: Fri, 27 Feb 2009 15:32:39 +0100 Subject: Please drop the please... please? In-Reply-To: <20090227081616.1baac1e4@xango2> References: <40A73538-9168-4374-8834-E65710777605@bioxray.au.dk> <20090227081616.1baac1e4@xango2> Message-ID: > Well... I was against it, since when we open a (say) sync or merge > *request* we are asking somebody else to do something that we either > cannot do, or do not have the time, or whatever. So, politeness is > absolutely required (as it always should be, BTW). Then why is a needs-packaging request filed as "[needs-packaging] program-here"? :) From laserjock at ubuntu.com Fri Feb 27 15:51:49 2009 From: laserjock at ubuntu.com (Jordan Mantha) Date: Fri, 27 Feb 2009 07:51:49 -0800 Subject: Please drop the please... please? In-Reply-To: <20090227081616.1baac1e4@xango2> References: <40A73538-9168-4374-8834-E65710777605@bioxray.au.dk> <20090227081616.1baac1e4@xango2> Message-ID: <82926f0e0902270751qabc74d3s4fd8d54c7b0ae17@mail.gmail.com> On Fri, Feb 27, 2009 at 6:16 AM, hggdh wrote: > On Fri, 27 Feb 2009 09:19:28 +0100 > Morten Kjeldgaard wrote: > > (snip) > >> So, couldn't we accept the technically exact  "Sync foo" and >> "Backport foo" instead of "Please sync foo" and  "Please backport >> foo"?? The "Please" can be put in the wording of the message, if >> politeness is required. > > Well... I was against it, since when we open a (say) sync or merge > *request* we are asking somebody else to do something that we either > cannot do, or do not have the time, or whatever. So, politeness is > absolutely required (as it always should be, BTW). One can simply "shift" the politeness to the text of the bug report. Using a bug title of "Sync: from Debian (main) to Universe" and a report text that starts out with "Please sync from Debian (main) to Universe." fulfills both the politeness and brevity requirements, IMO. -Jordan From briancurtis.wx at gmail.com Fri Feb 27 16:00:14 2009 From: briancurtis.wx at gmail.com (Brian Curtis) Date: Fri, 27 Feb 2009 11:00:14 -0500 Subject: Please drop the please... please? In-Reply-To: <82926f0e0902270751qabc74d3s4fd8d54c7b0ae17@mail.gmail.com> References: <40A73538-9168-4374-8834-E65710777605@bioxray.au.dk> <20090227081616.1baac1e4@xango2> <82926f0e0902270751qabc74d3s4fd8d54c7b0ae17@mail.gmail.com> Message-ID: Hi all, I don't feel that this is such a big issue as we are making it out to be. There is nothing wrong about being polite saying please in the title or text of a bug report, and theres nothing wrong about not saying please in the title or text of a bug report. Bugs are a professional matter, and we know that those type of requests are typical and frequent. I appreciate all the politeness that users give devs/triagers in their bug reports, and in my opinion is a very awesome thing to do in bug reports. Just my $0.02 ~Brian Research is what I'm doing when I don't know what I'm doing. --Wernher Von Braun "The second law of thermodynamics: If you think things are in a mess now, JUST WAIT!!" On Fri, Feb 27, 2009 at 10:51 AM, Jordan Mantha wrote: > On Fri, Feb 27, 2009 at 6:16 AM, hggdh wrote: > > On Fri, 27 Feb 2009 09:19:28 +0100 > > Morten Kjeldgaard wrote: > > > > (snip) > > > >> So, couldn't we accept the technically exact "Sync foo" and > >> "Backport foo" instead of "Please sync foo" and "Please backport > >> foo"?? The "Please" can be put in the wording of the message, if > >> politeness is required. > > > > Well... I was against it, since when we open a (say) sync or merge > > *request* we are asking somebody else to do something that we either > > cannot do, or do not have the time, or whatever. So, politeness is > > absolutely required (as it always should be, BTW). > > One can simply "shift" the politeness to the text of the bug report. > Using a bug title of "Sync: from Debian (main) to > Universe" and a report text that starts out with "Please sync > from Debian (main) to Universe." fulfills both the > politeness and brevity requirements, IMO. > > -Jordan > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian at ubuntu.com Fri Feb 27 16:21:40 2009 From: brian at ubuntu.com (Brian Murray) Date: Fri, 27 Feb 2009 08:21:40 -0800 Subject: Please drop the please... please? In-Reply-To: References: <40A73538-9168-4374-8834-E65710777605@bioxray.au.dk> <20090227081616.1baac1e4@xango2> Message-ID: <20090227162140.GB7788@murraytwins.com> On Fri, Feb 27, 2009 at 03:32:39PM +0100, Savvas Radevic wrote: > > Well... I was against it, since when we open a (say) sync or merge > > *request* we are asking somebody else to do something that we either > > cannot do, or do not have the time, or whatever. So, politeness is > > absolutely required (as it always should be, BTW). > > Then why is a needs-packaging request filed as "[needs-packaging] > program-here"? :) This allows them to be visually distinguishable, from other bug reports without a package, when you look at a bug list in Launchpad. If "Please" were dropped from "sync request" you'd still have "sync" which is not the case with '[needs-packaging]' gpicsync'. -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From jmarsden at fastmail.fm Fri Feb 27 18:08:59 2009 From: jmarsden at fastmail.fm (Jonathan Marsden) Date: Fri, 27 Feb 2009 10:08:59 -0800 Subject: Encoding things in the bug title (was: Re: Please drop the please... please?) In-Reply-To: <20090227162140.GB7788@murraytwins.com> References: <40A73538-9168-4374-8834-E65710777605@bioxray.au.dk> <20090227081616.1baac1e4@xango2> <20090227162140.GB7788@murraytwins.com> Message-ID: <49A82C3B.8020303@fastmail.fm> Brian Murray wrote: > This allows them to be visually distinguishable, from other bug reports > without a package, when you look at a bug list in Launchpad. If > "Please" were dropped from "sync request" you'd still have "sync" which > is not the case with '[needs-packaging]' gpicsync'. Stepping back a little: if we are going to formally encode various items of request-type information into the bug title field, perhaps it would be best to do so in a more standardized way? So (for example) if we use [needs-packaging], we should also use [sync], and more generally should use [tag] for any given tag. That way anyone writing scripts to process these has an easier job. Further, when LP is (at some hypothetical future date) enhanced so we don't need to abuse the title field in this way, because it has easy to use capabilities for storing and displaying request types (sync, needs-packaging, bug, etc.), then an automated sweep could easily find all bugs with encoded [tag]s in their titles and set the appropriate type field(s). The "visually distinguishable" part suggests to me that an enhancement request to make bugs with these tags be displayed in a distinctive way in the displayed list (different colour? Symbol next to them? Whatever UI people feel makes sense) might be appropriate. In other words, IMO the creation of informal and inconsistent pseudo-standards for encoding information into the title field should be regarded as a sign that the system as a whole could and probably should deal with this information differently and more directly. If that is impractical, or can only happen in the distant future, let's at least make the way we encode info in there be somewhat consistent. Final thought: [needs-packaging] and [sync] are not really bugs, so much as requests for action. Is naming this entire section of LP "Bugs" really the most appropriate way to go, since it is being used for things that are not really bugs, as well as for things that are indeed bugs? Jonathan