From brian at ubuntu.com  Thu Aug  2 00:58:33 2007
From: brian at ubuntu.com (Brian Murray)
Date: Wed, 1 Aug 2007 17:58:33 -0700
Subject: More Bug Statistic Graphs
Message-ID: <20070802005833.GF22547@murraytwins.com>

Kees Cook's reimplementation[0] of Carthik's bug graphs prompted me to
start graphing too.  In addition to the total Ubuntu bug's graph[1], 
with a new 365 day view, in the "test" graphs area[2] you can find 
graphs of packages with more than 100 bugs, one of desktop team bugs and
one of new bugs without a package.

[0]
https://lists.ubuntu.com/archives/ubuntu-bugsquad/2007-July/000601.html
[1] http://people.ubuntu.com/~brian/graphs/
[2] http://people.ubuntu.com/~brian/testing_graphs/ 

-- 
Brian Murray                                                 @ubuntu.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20070801/52ab7f77/attachment.sig>

From carthik at gmail.com  Thu Aug  2 18:46:45 2007
From: carthik at gmail.com (Carthik Sharma)
Date: Thu, 2 Aug 2007 14:46:45 -0400
Subject: More Bug Statistic Graphs
In-Reply-To: <20070802005833.GF22547@murraytwins.com>
References: <20070802005833.GF22547@murraytwins.com>
Message-ID: <80f75db0708021146pb0e93f9y1be47e8cc673dcb4@mail.gmail.com>

On 8/1/07, Brian Murray <brian at ubuntu.com> wrote:
> Kees Cook's reimplementation[0] of Carthik's bug graphs prompted me to
> start graphing too.  In addition to the total Ubuntu bug's graph[1],
> with a new 365 day view, in the "test" graphs area[2] you can find
> graphs of packages with more than 100 bugs, one of desktop team bugs and
> one of new bugs without a package.

Cool! Glad to see someone taking it a step further :)

Carthik.--
Ph.D. Candidate
University of Central Florida
Homepage: http://carthik.net



From dufresnep at fastmail.fm  Sat Aug  4 20:05:04 2007
From: dufresnep at fastmail.fm (Paul Dufresne)
Date: Sat, 04 Aug 2007 16:05:04 -0400
Subject: Propose to make the need to have importance set on Triaged bugs rather
	than on Confirmed bugs for kernel bug policy
Message-ID: <1186257904.29997.1203750345@webmail.messagingengine.com>

As a member of BugSquad (not QA) team, I sometimes have to ask on IRC
for a member of QA team to 'at least' set the importance of a kernel
bug that I am to the point of confirming. This is because of the rule
in:
https://wiki.ubuntu.com/KernelTeamBugPolicies that says that 'Confirmed
bugs should have importance set'.

I think it would not change much if the rule was rather: 'Triaged bugs
should have importance set'.
Then I could easily confirm bugs on kernel, without asking help.


-- 
http://www.fastmail.fm - Same, same, but different





From brian at ubuntu.com  Mon Aug  6 17:35:04 2007
From: brian at ubuntu.com (Brian Murray)
Date: Mon, 6 Aug 2007 10:35:04 -0700
Subject: Propose to make the need to have importance set on Triaged bugs
	rather than on Confirmed bugs for kernel bug policy
In-Reply-To: <1186257904.29997.1203750345@webmail.messagingengine.com>
References: <1186257904.29997.1203750345@webmail.messagingengine.com>
Message-ID: <20070806173504.GB353@murraytwins.com>

On Sat, Aug 04, 2007 at 04:05:04PM -0400, Paul Dufresne wrote:
> As a member of BugSquad (not QA) team, I sometimes have to ask on IRC
> for a member of QA team to 'at least' set the importance of a kernel
> bug that I am to the point of confirming. This is because of the rule
> in:
> https://wiki.ubuntu.com/KernelTeamBugPolicies that says that 'Confirmed
> bugs should have importance set'.
> 
> I think it would not change much if the rule was rather: 'Triaged bugs
> should have importance set'.
> Then I could easily confirm bugs on kernel, without asking help.

This makes a lot of sense and I have updated the Kernel Team Bug Policy 
to reflect your idea.  Thank you for bringing it to everyone's attention.

-- 
Brian Murray                                                 @ubuntu.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20070806/f9d3d5bb/attachment.sig>

From brian at ubuntu.com  Mon Aug  6 21:39:43 2007
From: brian at ubuntu.com (Brian Murray)
Date: Mon, 6 Aug 2007 14:39:43 -0700
Subject: Hug Day - 8 Aug 2007
Message-ID: <20070806213943.GE353@murraytwins.com>

I'm happy to announce our next Hug Day on Wednesday, August 8th.  We
will be focusing on bug reports regarding the development release of
Ubuntu, Gutsy Gibbon, in particular.  Additionally, this will be Pedro
Villavicencio's first Hug Day.  He recently started at Canonical as a
Desktop QA Engineer - so ask him about your favorite desktop bug!  The 
list of targeted bugs will be posted at:

  https://wiki.ubuntu.com/UbuntuBugDay/20070808

This list will be finalized shortly before the start of the 8th to
ensure that all the bugs on it still need attention.  Our goal is to 
deal with all of the bugs on that list.

So on 8 August 2007, in all timezones, we'll be meeting in #ubuntu-bugs
on irc.freenode.net for another Ubuntu Hug Day.

  https://wiki.ubuntu.com/UbuntuBugDay

While you are welcome to apply to join the Ubuntu Quality Assurance team
anytime, Hug Day is a great day to join!

  https://wiki.ubuntu.com/UbuntuQA

If you're interested in helping make the next release of Ubuntu better, 
please stop by.  And feel free to ask bdmurray, pedro and the rest of 
the team for ways to help out.  We hope to see you there and your name 
on the list of bug triagers!

-- 
Brian Murray                                                 @ubuntu.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20070806/f7340d3a/attachment.sig>

From aoudia.madjid at gmail.com  Tue Aug  7 07:58:14 2007
From: aoudia.madjid at gmail.com (Madjid AOUDIA)
Date: Tue, 7 Aug 2007 09:58:14 +0200
Subject: Hug Day - 8 Aug 2007
In-Reply-To: <20070806213943.GE353@murraytwins.com>
References: <20070806213943.GE353@murraytwins.com>
Message-ID: <21211b1f0708070058ua2b13dcoe466e12ed391d88c@mail.gmail.com>

Hi ! I am  new here.
Can somebody tell me what a hug day is ?

Oh and how can i start working on bugs ? The latest item on the list i can
see right now is a month old ...

Thx,

Madjid.

On 8/6/07, Brian Murray <brian at ubuntu.com> wrote:
>
> I'm happy to announce our next Hug Day on Wednesday, August 8th.  We
> will be focusing on bug reports regarding the development release of
> Ubuntu, Gutsy Gibbon, in particular.  Additionally, this will be Pedro
> Villavicencio's first Hug Day.  He recently started at Canonical as a
> Desktop QA Engineer - so ask him about your favorite desktop bug!  The
> list of targeted bugs will be posted at:
>
>   https://wiki.ubuntu.com/UbuntuBugDay/20070808
>
> This list will be finalized shortly before the start of the 8th to
> ensure that all the bugs on it still need attention.  Our goal is to
> deal with all of the bugs on that list.
>
> So on 8 August 2007, in all timezones, we'll be meeting in #ubuntu-bugs
> on irc.freenode.net for another Ubuntu Hug Day.
>
>   https://wiki.ubuntu.com/UbuntuBugDay
>
> While you are welcome to apply to join the Ubuntu Quality Assurance team
> anytime, Hug Day is a great day to join!
>
>   https://wiki.ubuntu.com/UbuntuQA
>
> If you're interested in helping make the next release of Ubuntu better,
> please stop by.  And feel free to ask bdmurray, pedro and the rest of
> the team for ways to help out.  We hope to see you there and your name
> on the list of bug triagers!
>
> --
> Brian Murray                                                 @ubuntu.com
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFGt5UfDTAwc5ER+zURAoEPAKDWC6YEhipuhy1lShTViYvHo27FKACgsE4K
> 3Vlvzi3M/xRnYzrfl2A279s=
> =OXaC
> -----END PGP SIGNATURE-----
>
> --
> Ubuntu-bugsquad mailing list
> Ubuntu-bugsquad at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad
>
>


-- 
Madjid Aoudia
92, rue d'Alesia 75014 Paris
Tel. + 33 6 11 96 35 60
Pro: + 33 1 40 99 33 28
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20070807/a88e5269/attachment.html>

From brian at ubuntu.com  Tue Aug  7 15:54:30 2007
From: brian at ubuntu.com (Brian Murray)
Date: Tue, 7 Aug 2007 08:54:30 -0700
Subject: Hug Day - 8 Aug 2007
In-Reply-To: <21211b1f0708070058ua2b13dcoe466e12ed391d88c@mail.gmail.com>
References: <20070806213943.GE353@murraytwins.com>
	<21211b1f0708070058ua2b13dcoe466e12ed391d88c@mail.gmail.com>
Message-ID: <20070807155430.GJ353@murraytwins.com>

On Tue, Aug 07, 2007 at 09:58:14AM +0200, Madjid AOUDIA wrote:
> Hi ! I am  new here.
> Can somebody tell me what a hug day is ?

A Hug Day is where we collectively work on making bug reports more
complete, triaging and even fixing them.  It is called Hug Day because
every bug worked on is worth a hug!  There will also be people available
in #ubuntu-bugs who can answer any questions you might have.  
Subsequently, it is a great time to get started triaging bugs and 
helping to make Ubuntu better.

> Oh and how can i start working on bugs ? The latest item on the list i
> can see right now is a month old ...

There are so many ways to get started working on bugs that this is a
tough question to answer.  You could help by working with reporters to
make bug reports more complete and useful for developers.  You could
reproduce problems described in bug reports and ensure the steps to
reproduce the bug are clear and well described.  You could test stable
release (from Dapper, Edgy or Feisty) bug reports in the latest
development release (Gutsy) to see if they are still an issue. What are 
you interested in doing?

Which list are you talking about when you say it is a month old?

Thanks, 
-- 
Brian Murray                                                 @ubuntu.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20070807/7732dde8/attachment.sig>

From brian at ubuntu.com  Tue Aug  7 21:59:25 2007
From: brian at ubuntu.com (Brian Murray)
Date: Tue, 7 Aug 2007 14:59:25 -0700
Subject: Gutsy kernel bug 129266
Message-ID: <20070807215925.GS353@murraytwins.com>

I wanted to let all of you know about a kernel bug that I recently ran
across because we may end up seeing duplicates.  I have also added this
information to the BugSquad homepage and invite you to add other high
profile bug reports to the News section also.

Bug 129266[0] deals with a kernel Oops when resuming from suspend or
hibernate and from what we can determine it only affects people with
dual core CPUs.  The fix has been committed to the kernel tree and will
make it in the next version of the kernel.  When looking for duplicates 
you will want to look for kernel Oops reports, identifiable by the string 
"Oops:" in dmesg or '/var/log/messages', and then compare the "Call
Trace:" portion of the Oops report to bug 129266.

[0] https://launchpad.net/bugs/129226

Thanks, 
-- 
Brian Murray                                                 @ubuntu.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20070807/3073adfb/attachment.sig>

From mathiaz at ubuntu.com  Wed Aug  8 00:47:23 2007
From: mathiaz at ubuntu.com (Mathias Gug)
Date: Tue, 7 Aug 2007 20:47:23 -0400
Subject: Standard answer for long standing bugs
Message-ID: <20070808004722.GA8702@mathias.mathiaz.net>

Hi,

I've been going through samba bugs below 90000 in a 'New, Unconfirmed'
state, which means that they are quite old. 

I was wondering if there is a standard answer for bugs that were
reported a long time ago, but we're not sure if the reporter is still
available, has more information, etc..., a sort of 'ping ! Is this bug
still valid after such a long time ?'.

Thanks,

--
Mathias



From gothicx at sapo.pt  Wed Aug  8 00:57:15 2007
From: gothicx at sapo.pt (Marco Rodrigues)
Date: Wed, 08 Aug 2007 01:57:15 +0100
Subject: Standard answer for long standing bugs
In-Reply-To: <20070808004722.GA8702@mathias.mathiaz.net>
References: <20070808004722.GA8702@mathias.mathiaz.net>
Message-ID: <46B914EB.2030807@sapo.pt>

Hi!

We need to wait for https://bugs.launchpad.net/malone/+bug/91925 to help us a
little bit.

Check this:
https://wiki.ubuntu.com/Bugs/Responses#head-6ee6466fdaac8c81274185f0316afd794d2ee0b6

Thanks

Mathias Gug wrote:
> Hi,
> 
> I've been going through samba bugs below 90000 in a 'New, Unconfirmed'
> state, which means that they are quite old. 
> 
> I was wondering if there is a standard answer for bugs that were
> reported a long time ago, but we're not sure if the reporter is still
> available, has more information, etc..., a sort of 'ping ! Is this bug
> still valid after such a long time ?'.
> 
> Thanks,
> 
> --
> Mathias
> 

-- 
Marco Rodrigues

http://Marco.Tondela.org



From brian at ubuntu.com  Wed Aug  8 16:03:36 2007
From: brian at ubuntu.com (Brian Murray)
Date: Wed, 8 Aug 2007 09:03:36 -0700
Subject: Standard answer for long standing bugs
In-Reply-To: <20070808004722.GA8702@mathias.mathiaz.net>
References: <20070808004722.GA8702@mathias.mathiaz.net>
Message-ID: <20070808160336.GV353@murraytwins.com>

On Tue, Aug 07, 2007 at 08:47:23PM -0400, Mathias Gug wrote:
> Hi,
> 
> I've been going through samba bugs below 90000 in a 'New, Unconfirmed'
> state, which means that they are quite old. 

In regards to "New" bugs that have not been touched, only bugs that do
not have questions in them should be in the "New" state, and that are 
quite old I have been using the following response:

"Thank you for taking the time to report this bug and helping to make
Ubuntu better.  You reported this bug a while ago and there hasn't been
any activity in it recently.  We were wondering is this still an issue
for you?  Thanks in advance."

However, as we are actively trying to promote testing of Gutsy I would
also add something like:

"The issue that you reported is one that should be reproducable with the
live environment of the Desktop CD of the development release - Gutsy
Gibbon.  It would help us greatly if you could test with it so we can
work on getting it fixed in the actively developed kernel.  You can find
out more about the development release at http://www.ubuntu.com/testing/
."

If the bug could in fact be reproduced using the live environment.

Thanks,
-- 
Brian Murray                                                 @ubuntu.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20070808/e91d4c84/attachment.sig>

From mathiaz at ubuntu.com  Wed Aug  8 16:50:00 2007
From: mathiaz at ubuntu.com (Mathias Gug)
Date: Wed, 8 Aug 2007 12:50:00 -0400
Subject: Standard answer for long standing bugs
In-Reply-To: <20070808160336.GV353@murraytwins.com>
References: <20070808004722.GA8702@mathias.mathiaz.net>
	<20070808160336.GV353@murraytwins.com>
Message-ID: <20070808164959.GD6157@mathias.mathiaz.net>

Hi Brian,

On Wed, Aug 08, 2007 at 09:03:36AM -0700, Brian Murray wrote:
> In regards to "New" bugs that have not been touched, only bugs that do
> not have questions in them should be in the "New" state, and that are 
> quite old I have been using the following response:
> 
> "Thank you for taking the time to report this bug and helping to make
> Ubuntu better.  You reported this bug a while ago and there hasn't been
> any activity in it recently.  We were wondering is this still an issue
> for you?  Thanks in advance."
> 
> However, as we are actively trying to promote testing of Gutsy I would
> also add something like:
> 
> "The issue that you reported is one that should be reproducable with the
> live environment of the Desktop CD of the development release - Gutsy
> Gibbon.  It would help us greatly if you could test with it so we can
> work on getting it fixed in the actively developed kernel.  You can find
> out more about the development release at http://www.ubuntu.com/testing/
> ."
> 
> If the bug could in fact be reproduced using the live environment.

Could the Bugs/Responses wiki page be updated with this information ?

--
Mathias
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20070808/603e72fe/attachment.sig>

From pascal.devuyst at gmail.com  Fri Aug 10 16:01:08 2007
From: pascal.devuyst at gmail.com (Pascal De Vuyst)
Date: Fri, 10 Aug 2007 18:01:08 +0200
Subject: DebuggingMouseDection,
	DebuggingTouchpadDetection and DebuggingKeyboardDetection
Message-ID: <d17dd890708100901v565c4231g58c1a0106bd67190@mail.gmail.com>

Hello,

While doing some bug triage for mouse related problems in Ubuntu I saw that
most bugs did not provide much usefull information to debug the problem.
Most of these bugs can be categorized as either a non working mouse, a mouse
that stops working or some buttons/scrollwheels that don't work.

I decided to write a debugging procedure for mouse detection [1]. Since
touchpads and keyboards could be categorized into the same bug categories I
decided to write a debugging procedure for touchpads [2] and keyboards [3]
too.

Since pointing devices and keyboards are pretty critical devices for users I
hope these procedures can assist in tackling some nasty kernel and X bugs.
My idea is that a bug reporter should assign these kind of bugs to either
xserver-xorg-input-mouse, xserver-xorg-input-synaptics or
xserver-xorg-input-keyboard and a bug triager can then decide if the problem
really is in these packages, in the kernel or in another package.

I'm open to suggestions that could improve these debugging procedures. If
you have some experience in debugging these kind of devices and you think
there are some bug categories or steps missing please let me know.

I have a few questions:
Should these debugging procedures be added to DebuggingProcedures [4]?
Should we remove the "Howto Debug Keyboard Issues" section from
DebuggingXAutoconfiguration [5]? Why is this section listed twice in that
page?
Should we make the DebuggingXAutoconfiguration dedicated to video detection
and perhaps rename it into something like DebuggingVideoDetection?

[1] https://wiki.ubuntu.com/DebuggingMouseDetection
[2] https://wiki.ubuntu.com/DebuggingTouchpadDetection
[3] https://wiki.ubuntu.com/DebuggingKeyboardDetection
[4] https://wiki.ubuntu.com/DebuggingProcedures
[5] https://help.ubuntu.com/community/DebuggingXAutoconfiguration

Thanks in advance,
Pascal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20070810/5b2fd392/attachment.html>

From brian at ubuntu.com  Fri Aug 17 21:25:34 2007
From: brian at ubuntu.com (Brian Murray)
Date: Fri, 17 Aug 2007 14:25:34 -0700
Subject: Celebratory Hug Day - 22 Aug 2007
Message-ID: <20070817212534.GM6911@murraytwins.com>

In celebration of the 10th anniversary of the GNOME project we are
having a very special Hug Day on Wednesday, August 22nd.  We will be
focusing on the collaboration between the Ubuntu and GNOME projects by
working on the following topics.

* Linking related bugs in Malone to GNOME's bugzilla.
* Ensuring that any forwarded bug reports have the same information and
are complete.
* Reproducing crasher bugs in GNOME's bugzilla in the development 
release of Ubuntu to provide a detailed crash report for GNOME.

There will be a list of types of bugs including specifically targeted 
bugs at:

  https://wiki.ubuntu.com/UbuntuBugDay/20070822

This list will be finalized shortly before the start of the 22nd to
ensure that all the bugs on it still need attention.  Our goal is to
deal with all of the bugs on that list.

So on 22 August 2007, in all timezones, we'll be meeting in #ubuntu-bugs
on irc.freenode.net for a very special Hug Day.

  https://wiki.ubuntu.com/UbuntuBugDay

If you're interested in helping to improve Ubuntu and GNOME, please join
us.  Feel free to ask pedro, bdmurray, heno and the rest of the team for
ways to help out.  We hope to see you there and your name on the list of
bug triagers!

-- 
Brian Murray                                                 @ubuntu.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20070817/ddc2baf0/attachment.sig>

From mathiaz at ubuntu.com  Mon Aug 20 13:42:55 2007
From: mathiaz at ubuntu.com (Mathias Gug)
Date: Mon, 20 Aug 2007 09:42:55 -0400
Subject: Update of Bugs/Responses - Fixed in Development release
Message-ID: <20070820134253.GI6129@mathias.mathiaz.net>

Hi,

I've been working on a couple of bugs where the answer would have been
something like "Fixed in the latest development version. Won't fix in
previous release as it doesn't fit backporting or SRU requirements. Live
with it !"

What would be the proper way to close such bugs ? Mark them as "Fix
released" or "Won't fix" ? What would be the standard response ?

I'd suggest updating the Bugs/Reponses wiki page with:

Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, I am closing it because the bug has been fixed
in the latest development version of Ubuntu - the Gutsy Gibbon. It won't
be fixed in previous versions of Ubuntu because the bug doesn't fit
requirements for backporting or a StableReleaseUpdates. See
https://help.ubuntu.com/community/UbuntuBackports and
https://wiki.ubuntu.com/StableReleaseUpdates for more information.


--
Mathias



From mpt at canonical.com  Tue Aug 21 06:14:10 2007
From: mpt at canonical.com (Matthew Paul Thomas)
Date: Tue, 21 Aug 2007 18:14:10 +1200
Subject: Launchpad bug pages are about to change
Message-ID: <1683f0478cc43afe9e5d2efd2b67cc3c@canonical.com>

On Wednesday, Launchpad's bug report pages will change, and this will 
affect where you click to update bug reports.

To change the status, Importance, milestone, or assignee of a bug (or 
to see the milestone of a bug), you will now need to click on the 
current status or Importance, instead of clicking on the name of the 
project or package.

Clicking on the project or package name will now take you to the Bugs 
page for that project or package, instead of showing/hiding the bug 
status controls for that project or package.

If you want to test the new interface ahead of time, you can do this on 
<https://bugs.staging.launchpad.net/>.

Cheers
-- 
Matthew Paul Thomas
http://mpt.net.nz/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20070821/7043b386/attachment.sig>

From onno at itmaze.com.au  Tue Aug 21 06:55:53 2007
From: onno at itmaze.com.au (Onno Benschop)
Date: Tue, 21 Aug 2007 14:55:53 +0800
Subject: Launchpad bug pages are about to change
In-Reply-To: <1683f0478cc43afe9e5d2efd2b67cc3c@canonical.com>
References: <1683f0478cc43afe9e5d2efd2b67cc3c@canonical.com>
Message-ID: <46CA8C79.2030002@itmaze.com.au>

Thanks for the heads up.

Is there any reason why Status and Importance are two columns with two
links to the same URL?

Also, the link to the "Assigned to" person doesn't underline, nor does
the icon underline, but the Status and Importance links both underline
the icon. Furthermore, the link to the package name underlines, but not
the icon.

So, the interface rendering is a little inconsistent.


Also, I personally think that a link that reveals something shouldn't
look like a link that goes somewhere.

You can change that with a style entry, something like this:

    .reveal{
     cursor:url(zoom.cur),pointer;
    }
      



-- 
Onno Benschop

Connected via Optus B3 at S31°54'06" - E115°50'39" (Yokine, WA)
--
()/)/)()        ..ASCII for Onno..
|>>?            ..EBCDIC for Onno..
--- -. -. ---   ..Morse for Onno..

ITmaze   -   ABN: 56 178 057 063   -  ph: 04 1219 8888   -   onno at itmaze.com.au




From mpt at canonical.com  Wed Aug 22 03:40:07 2007
From: mpt at canonical.com (Matthew Paul Thomas)
Date: Wed, 22 Aug 2007 15:40:07 +1200
Subject: Launchpad bug pages are about to change
In-Reply-To: <46CA8C79.2030002@itmaze.com.au>
References: <1683f0478cc43afe9e5d2efd2b67cc3c@canonical.com>
	<46CA8C79.2030002@itmaze.com.au>
Message-ID: <daca4e6b353fdde749809da1c3858aa8@canonical.com>

On Aug 21, 2007, at 6:55 PM, Onno Benschop wrote:
>
> Thanks for the heads up.
>
> Is there any reason why Status and Importance are two columns with two
> links to the same URL?

It is useful for them to be two columns for easy scanning when a bug 
affects multiple projects/packages. But they are changed in the same 
form.

> Also, the link to the "Assigned to" person doesn't underline, nor does
> the icon underline, but the Status and Importance links both underline
> the icon. Furthermore, the link to the package name underlines, but not
> the icon.
>
> So, the interface rendering is a little inconsistent.

Thanks for raising this. I've reported the bug.
<http://launchpad.net/bugs/133971>

> Also, I personally think that a link that reveals something shouldn't
> look like a link that goes somewhere.
>
> You can change that with a style entry, something like this:
>
>     .reveal{
>      cursor:url(zoom.cur),pointer;
>     }
> ...

I agree, and it's something I'll consider for a future design.

Cheers
-- 
Matthew Paul Thomas
http://mpt.net.nz/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20070822/c29ce611/attachment.sig>