Re: Desktop team weekly report -- 2009-09-22

2009-10-05 Thread Bryce Harrington
On Sat, Oct 03, 2009 at 01:55:13PM -0700, Jono Bacon wrote:
> On 10/03/2009 11:39 AM, Bryce Harrington wrote:
> >You know, in these cases the current +filebug is destroying information
> >we need.  If the bug reporter already knows at time of filing that it is
> >a 'translation', 'wishlist', 'usability', 'packaging', etc. issue, then
> >this is extremely valuable information as to how to handle the bug.
> >
> >There are specific teams with interest in each of these classes of bugs,
> >who do not regularly troll through individual packages bug listings but
> >who might be able to handle these issues directly if they were tagged as
> >such.
> >
> >Currently, this info is not captured at time of bug filing, so someone
> >else has to think and tag it later.  This adds unnecessary delay and
> >increases the workload on the triager.
> >
> This sounds like great feedback, Bryce. What do you feel is the best
> solution?

I'm imagining a set of radio buttons on the +filebug page, which apply
the given tag to the bug on submit.

I'm sure there's more than one way to do it though.

Bryce

-- 
ubuntu-desktop mailing list
ubuntu-desktop@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop


Re: Desktop team weekly report -- 2009-09-22

2009-10-03 Thread Jono Bacon
On 10/03/2009 11:39 AM, Bryce Harrington wrote:
> You know, in these cases the current +filebug is destroying information
> we need.  If the bug reporter already knows at time of filing that it is
> a 'translation', 'wishlist', 'usability', 'packaging', etc. issue, then
> this is extremely valuable information as to how to handle the bug.
>
> There are specific teams with interest in each of these classes of bugs,
> who do not regularly troll through individual packages bug listings but
> who might be able to handle these issues directly if they were tagged as
> such.
>
> Currently, this info is not captured at time of bug filing, so someone
> else has to think and tag it later.  This adds unnecessary delay and
> increases the workload on the triager.
>
>
This sounds like great feedback, Bryce. What do you feel is the best 
solution?
> One other side benefit:  When doing automated bug triaging, it is
> extremely hard to mechanically differentiate between ordinary bugs and
> wishlist/packaging/usability issues.  By tagging the bugs at filing
> time, it allows automated scripts to not request logs and other info
> inappropriately.
>
>
Sounds good.

It also seems we should allow people to file translations bugs and 
community bugs via ubuntu-bug too. Maybe the symptom-based bug reporting 
would be good for this. What do you think, Brian?

 Jono


-- 
Jono Bacon
Ubuntu Community Manager
www.ubuntu.com / www.jonobacon.org
www.identi.ca/jonobacon www.twitter.com/jonobacon


-- 
ubuntu-desktop mailing list
ubuntu-desktop@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop


Re: Desktop team weekly report -- 2009-09-22

2009-10-03 Thread Bryce Harrington
On Wed, Sep 23, 2009 at 11:29:32AM +0200, Martin Pitt wrote:
> == Changed bug reporting process ==
> 
> Feedback about the `+filebug` redirection: 
>  * many bugs can legitimately be filed without apport information (such as 
> translation bugs), wishlist bugs, or UI problems

You know, in these cases the current +filebug is destroying information
we need.  If the bug reporter already knows at time of filing that it is
a 'translation', 'wishlist', 'usability', 'packaging', etc. issue, then
this is extremely valuable information as to how to handle the bug.

There are specific teams with interest in each of these classes of bugs,
who do not regularly troll through individual packages bug listings but
who might be able to handle these issues directly if they were tagged as
such.

Currently, this info is not captured at time of bug filing, so someone
else has to think and tag it later.  This adds unnecessary delay and
increases the workload on the triager.

One other side benefit:  When doing automated bug triaging, it is
extremely hard to mechanically differentiate between ordinary bugs and
wishlist/packaging/usability issues.  By tagging the bugs at filing
time, it allows automated scripts to not request logs and other info
inappropriately.

Bryce

-- 
ubuntu-desktop mailing list
ubuntu-desktop@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop


Desktop team weekly report -- 2009-09-22

2009-09-23 Thread Martin Pitt
This is also available on the wiki:
https://wiki.ubuntu.com/DesktopTeam/Meeting/2009-09-22

<>

For minutes of previous meetings, please see DesktopTeam/Meeting.

= Meeting Minutes =
== Present ==
=== Main Meeting ===
 * Alexander Sack (asac)
 * Alberto Milone (tseliot)
 * Arne Goetje (ArneGoetje)
 * Chris Cheney (calc)
 * Jonathan Riddell (Riddell)
 * Ken VanDine (kenvandine)
 * Martin Pitt (pitti) - chair
 * Sebastien Bacher (seb128)
 * Till Kamppeter (tkamppeter)  
 * Tony Espy

=== Eastern Edition ===
 * Luke Yelavich (TheMuso)
 * Robert Ancell (robert_ancell)

== Apologies ==
 * Rick Spencer (rickspencer3)
 * Bryce Harrington (bryce)

== Agenda ==
 * Outstanding actions from last meeting
 * Changed bug reporting process
 * Partner Update
 * Kubuntu Update
 * Release Bugs/Release Status
 * Ricks' heartache list
 * Review work items
 * Review activity reports
 * Any other business

== Actions from this meeting ==

 * https://wiki.ubuntu.com/Bugs/FindRightPackage: TheMuso to update the page 
for audio
 * https://wiki.ubuntu.com/Bugs/FindRightPackage: robert_ancell to update the 
page for compiz
 * pitti to talk to bdmurray about +filebug feedback (Done, see bug Bug:432088)
 * Riddell to clean up Kubuntu/Todo/Karmic

== Outstanding actions from last meeting ==

 * https://wiki.ubuntu.com/Bugs/FindRightPackage: TheMuso to update the page 
for audio
  * Not done, pushed to this week
 * https://wiki.ubuntu.com/Bugs/FindRightPackage: robert_ancell to update the 
page for compiz
  * Not done, pushed to this week
 * https://wiki.ubuntu.com/Bugs/FindRightPackage: pitti to update the page for 
storage devices
  * Done

== Changed bug reporting process ==

Feedback about the `+filebug` redirection: 
 * many bugs can legitimately be filed without apport information (such as 
translation bugs), wishlist bugs, or UI problems
 * Devs still want an easily accessible "file it anyway" link 
 * Proposal from Alex: Firefox protocol handler like apturl 
(`ubuntu-bug:file/firefox-3.5`), but that requires new code and will only work 
with Firefox
 * Ideal solution: `+filebug` page shows wiki page contents and offers a "file 
it anyway" link at the bottom
 * Compromise: Disable redirection for `~ubuntu-bug-control` members.

''ACTION:'' pitti to talk to bdmurray about +filebug feedback

Done in bug Bug:432088; other developers proposed the same solution.

== Partner Update ==
=== UbuntuOne: ===
 * Online services team is sprinting this week, and I haven't gotten an update 
from them yet
 * couchdb
   * split server from the rest of couch so it doesn't start at boot
 * bindwood
   * we need bug fix release with oauth enabled
 * desktopcouch
   * we need bug fix release with oauth enabled (to allow syncing)
 * ubuntuone-client
   * There will likely be a UI freeze exception requested to deal with the 
preferences dialog usability issue 

Martin pointed out that enabling oauth and peer-to-peer sync is a new feature 
which comes very late.

=== DX: ===

 * [[DesktopExperienceTeam/KarmicWeeklyReleases|Weekly releases]]
   * user list in the session applet
   * menu ordering bug 
   * notify-osd crashers
 * New gdm artwork still needs to land

== Kubuntu Update ==

 * DVDs oversized, next Amarok upload may fix that
 * OEM installer broken, but broken in Ubuntu Desktop too
 * Upgrade from Jaunty works but with some config file quirks that I need to 
work around
 * jockey and apport still need investigation

== Rick's list of heartache ==

 Boot 
 * lots of incoming bugs about not being able to boot: 
https://bugs.launchpad.net/bugs/+bugs?field.tag=ubuntu-boot
  * under active investigation (mostly by Scott)
 * lots of messages and other crufty looking things:
  * many of them were already fixed in latest udev

 Empathy 
 * audio/video is crashy:
  * Ken will spend some time debugging this this week
  * Audio has been relatively stable since recently
  * Video is broken and consistently crashing
  * Ken will talk to cassidy (upstream)
  * New telepathy-farsight was synced yesterday and is supposed to help a lot
 * not interacting well with messaging menu

 X 
 * Is there something keeping compiz from working on intel 945?
  * Race condition on boot, sometimes does not load DRM modules and thus enable 
KMS and acceleration
  * related to bug Bug:392039 and bug 431812, Scott proposed a solution in the 
bug

 Gwibber 
 * Not displaying messages atm
  * Not reproducible; Rick needs to file a bug
 * crashy, including daemon
  * Not reproducible; Rick needs to file a bug
 * not interacting well with messaging
  * fixed yesterday

 Session menu 
 * haven't implemented user list yet (regression)
  * tracked in bug Bug:422052
  * gdm offers the API now
 * status interactions with apps not working well
  * needs to be ported to telepathy-mission-control-5 (right now it uses the 4 
API)
  * scheduled to land on Thursday

 work items 
 * above trend line
 * asac still has quite a few open items
 * s