The GNOME team needs your help

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

The GNOME team needs your help

Josselin Mouette
Dear Debian/GNOME users,

Since the creation of the GNOME team, the GNOME packages have been in a
good state. As you may have followed, the packaging is going on at a
reasonable pace, and we have enough manpower for packaging new GNOME
versions, although not as fast as we'd like to.

However, it could be much better. One area where we've been constantly
lagging behind is the handling of bugs. Of course, release-critical bugs
or bugs that affect us directly are fixed. But some packages like
nautilus are rotting in the BTS with piles of bugs we simply can't
handle because we don't have the time. We don't know whether those bugs
are still here, we don't know whether they are known upstream, we don't
know how to reproduce them or we don't know where to start to fix them.

That's why we're requesting help about bug triage. This is a task any of
you can do, provided you have some time and know how to use the BTS and
Bugzilla.

What can you do for helping? Start at:
http://qa.debian.org/developer.php?login=pkg-gnome-maintainers@...
Here, you can look for packages needing attention. High numbers in the
bug columns are a good hint.

What to do to deal with a specific bug:
      * Check whether you can reproduce the bug. If it's meant to be
        easily reproducible, check whether it can be reproduced with the
        latest version.
      * Check whether a similar bug has been reported in
        http://bugzilla.gnome.org/ and whether it has a patch available.
      * Check for a fix in the CVS tree. You don't need to grab patches
        if you're not used to, pointing us at the relevant change is
        enough.
      * Forward the bug if it isn't reported there. Don't forget to add
        [hidden email] in the Cc field.

If you think a bug is already fixed, you should close it. Otherwise,
once you have an idea of what can be done to fix the bug (a patch, a CVS
log, an idea on how to change the package), the best way to get the bug
fixed is to find a maintainer on #gnome-debian@GimpNet and harass him
until the fix is in our SVN repository.

In short, if you're willing to improve GNOME in Debian, your
contribution is welcome. Of course, people more familiar with GNOME
packaging are welcome to join the team itself to work on the packages.
--
 .''`.           Josselin Mouette        /\./\
: :' :           [hidden email]
`. `'                        [hidden email]
   `-  Debian GNU/Linux -- The power of freedom


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: The GNOME team needs your help

Andrea Vettorello
On 1/16/06, Josselin Mouette <[hidden email]> wrote:
> Dear Debian/GNOME users,

[...]

>
> If you think a bug is already fixed, you should close it. Otherwise,
> once you have an idea of what can be done to fix the bug (a patch, a CVS
> log, an idea on how to change the package), the best way to get the bug
> fixed is to find a maintainer on #gnome-debian@GimpNet and harass him
> until the fix is in our SVN repository.
>

I'm looking at "http://www.debian.org/Bugs/Developer#closing", can i
close a bug in the Debian BTS even if i'm not the bug submitter or the
mantainer of the package?

For exemple, #319534


Andrea

Reply | Threaded
Open this post in threaded view
|

Re: The GNOME team needs your help

Jérôme Warnier
Le lundi 16 janvier 2006 à 15:45 +0100, Andrea Vettorello a écrit :

> On 1/16/06, Josselin Mouette <[hidden email]> wrote:
> > Dear Debian/GNOME users,
>
> [...]
>
> >
> > If you think a bug is already fixed, you should close it. Otherwise,
> > once you have an idea of what can be done to fix the bug (a patch, a CVS
> > log, an idea on how to change the package), the best way to get the bug
> > fixed is to find a maintainer on #gnome-debian@GimpNet and harass him
> > until the fix is in our SVN repository.
> >
>
> I'm looking at "http://www.debian.org/Bugs/Developer#closing", can i
> close a bug in the Debian BTS even if i'm not the bug submitter or the
> mantainer of the package?
Yes, of course, though some maintainers will probably not be happy with
it, it seems that GNOME maintainers will welcome it, so go ahead!

> For exemple, #319534
>
>
> Andrea

Reply | Threaded
Open this post in threaded view
|

Re: The GNOME team needs your help

Josselin Mouette
In reply to this post by Andrea Vettorello
Le lundi 16 janvier 2006 à 15:45 +0100, Andrea Vettorello a écrit :

> > If you think a bug is already fixed, you should close it. Otherwise,
> > once you have an idea of what can be done to fix the bug (a patch, a CVS
> > log, an idea on how to change the package), the best way to get the bug
> > fixed is to find a maintainer on #gnome-debian@GimpNet and harass him
> > until the fix is in our SVN repository.
>
> I'm looking at "http://www.debian.org/Bugs/Developer#closing", can i
> close a bug in the Debian BTS even if i'm not the bug submitter or the
> mantainer of the package?
>
> For exemple, #319534

Yes, this is a perfect example of a bug that can be closed. The BTS
doesn't forbid anyone from acting on other people's bugs.

Thanks for your interest.
--
 .''`.           Josselin Mouette        /\./\
: :' :           [hidden email]
`. `'                        [hidden email]
   `-  Debian GNU/Linux -- The power of freedom

Reply | Threaded
Open this post in threaded view
|

Re: The GNOME team needs your help

Ondřej Surý-4
In reply to this post by Andrea Vettorello
On Mon, 2006-01-16 at 15:45 +0100, Andrea Vettorello wrote:
> I'm looking at "http://www.debian.org/Bugs/Developer#closing", can i
> close a bug in the Debian BTS even if i'm not the bug submitter or the
> mantainer of the package?
>
> For exemple, #319534

Sure, just send email to [hidden email] with explanation why
you are closing the bug.

Ondrej
--
Ondrej Sury <[hidden email]>

signature.asc (196 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: The GNOME team needs your help

Andrea Vettorello
In reply to this post by Josselin Mouette
On 1/16/06, Josselin Mouette <[hidden email]> wrote:

> Le lundi 16 janvier 2006 à 15:45 +0100, Andrea Vettorello a écrit :
> > > If you think a bug is already fixed, you should close it. Otherwise,
> > > once you have an idea of what can be done to fix the bug (a patch, a CVS
> > > log, an idea on how to change the package), the best way to get the bug
> > > fixed is to find a maintainer on #gnome-debian@GimpNet and harass him
> > > until the fix is in our SVN repository.
> >
> > I'm looking at "http://www.debian.org/Bugs/Developer#closing", can i
> > close a bug in the Debian BTS even if i'm not the bug submitter or the
> > mantainer of the package?
> >
> > For exemple, #319534
>
> Yes, this is a perfect example of a bug that can be closed. The BTS
> doesn't forbid anyone from acting on other people's bugs.
>
> Thanks for your interest.

Ok, done.


Andrea

Reply | Threaded
Open this post in threaded view
|

Re: The GNOME team needs your help

Christine Spang
In reply to this post by Josselin Mouette
* Josselin Mouette <[hidden email]> [2006:01:16 14:06 +0100]:
> Dear Debian/GNOME users,
>
> That's why we're requesting help about bug triage. This is a task any of
> you can do, provided you have some time and know how to use the BTS and
> Bugzilla.

I've been taking a look at some Epiphany bugs and have a question.

Take, for example: http://bugs.debian.org/308384

It's been previously reported in GNOME bugzilla[1], and there's a patch
submitted there. It doesn't seem to have ever been applied to upstream
source, however.

Would we test the patch on the latest upstream and prod upstream into
putting the fix into the next release? I assume we don't want to
diverge our version too much by applying fixes that haven't been
applied upstream.

1. http://bugzilla.gnome.org/show_bug.cgi?id=145581

Cheers,
--
A. Christine Spang
http://frisia.middle-earth.us/

signature.asc (196 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: The GNOME team needs your help

Josselin Mouette
Le lundi 16 janvier 2006 à 18:44 -0500, Christine Spang a écrit :
> I've been taking a look at some Epiphany bugs and have a question.
>
> Take, for example: http://bugs.debian.org/308384
>
> It's been previously reported in GNOME bugzilla[1], and there's a patch
> submitted there. It doesn't seem to have ever been applied to upstream
> source, however.
 
> Would we test the patch on the latest upstream and prod upstream into
> putting the fix into the next release? I assume we don't want to
> diverge our version too much by applying fixes that haven't been
> applied upstream.
>
> 1. http://bugzilla.gnome.org/show_bug.cgi?id=145581

We generally try to be very conservative with UI changes, especially
when they involve non-translated strings. However, this one doesn't look
very intrusive, as it doesn't appear until you actually hit F7. The
patch hasn't been committed, but it was written by chpe himself (an
epiphany developer).

I'd say it is okay to include it in the package and report any issues
with it in the bugzilla report.
--
 .''`.           Josselin Mouette        /\./\
: :' :           [hidden email]
`. `'                        [hidden email]
   `-  Debian GNU/Linux -- The power of freedom

Reply | Threaded
Open this post in threaded view
|

Re: The GNOME team needs your help

Sjoerd Simons-2
On Tue, Jan 17, 2006 at 10:01:31AM +0100, Josselin Mouette wrote:

> Le lundi 16 janvier 2006 à 18:44 -0500, Christine Spang a écrit :
> > I've been taking a look at some Epiphany bugs and have a question.
> >
> > Take, for example: http://bugs.debian.org/308384
> >
> > It's been previously reported in GNOME bugzilla[1], and there's a patch
> > submitted there. It doesn't seem to have ever been applied to upstream
> > source, however.
>  
> > Would we test the patch on the latest upstream and prod upstream into
> > putting the fix into the next release? I assume we don't want to
> > diverge our version too much by applying fixes that haven't been
> > applied upstream.
> >
> > 1. http://bugzilla.gnome.org/show_bug.cgi?id=145581
>
> We generally try to be very conservative with UI changes, especially
> when they involve non-translated strings. However, this one doesn't look
> very intrusive, as it doesn't appear until you actually hit F7. The
> patch hasn't been committed, but it was written by chpe himself (an
> epiphany developer).
>
> I'd say it is okay to include it in the package and report any issues
> with it in the bugzilla report.

It also can't hurt to report success back to bugzilla if you test this patch.
 In this case it looks like it's currently stalled, attracting some
 attention/providing feedback to it might help :)

  Sjoerd
--
We warn the reader in advance that the proof presented here depends on a
clever but highly unmotivated trick.
                -- Howard Anton, "Elementary Linear Algebra"


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: The GNOME team needs your help

Christine Spang
* Sjoerd Simons <[hidden email]> [2006:01:17 10:35 +0100]:
>
> It also can't hurt to report success back to bugzilla if you test this patch.
>  In this case it looks like it's currently stalled, attracting some
>  attention/providing feedback to it might help :)
>
>   Sjoerd

OK, sounds good to me. One more thing: when asking a submitter if a problem
still persists/for more information, how long do you generally wait for
a reply before taking further action on a bug? E.g. closing something that
you can't reproduce and likely has been fixed or no longer appears in
current unstable, especially when the bug has been reported on a package
that has progressed two or so major versions since the reporting.

--
A. Christine Spang
http://frisia.middle-earth.us/

signature.asc (196 bytes) Download Attachment