Where is Alexander Larsson (Nautilus bug)?

[Lamont R. Peterson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Where in the World is Alexander Larson?  #243309
[ https://bugzilla.redhat.com/show_bug.cgi?id=243309 ] (Nautilus folder
icons get stuck in open state) is assigned to him, but he isn't
responding to it.

The bug was filed on 2007-06-08 (over 3 months ago) by J H Ettle and
added my +1 to it on 2007-08-29.  Is Alexander missing?  Is there a
co-maintainer who should be available?

I would think that this bug would be very easy to fix (seems like a
regression, but what would I know about it), and that we would want it
fixed for F8.

I have not tried this in F8t2 (haven't downloaded or installed it yet,
as I've been traveling since before its release).  If anyone who has
F8 test 2 handy would mind checking on this bug and reporting results,
that would be great.  If not, I may get one up in the next couple of
days.
- -- 
Lamont Peterson <lamont(a)gurulabs.com&gt;
Senior Instructor
Guru Labs, L.C. [ http://www.GuruLabs.com/ ]

NOTE:  All messages from this email address should be digitally signed
with my 0xDC0DD409 GPG key. It is available on the pgp.mit.edu
keyserver as well as other keyservers that sync with MIT's.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
>
> iD8DBQFG7Z8V+YBsl9wN1AkRAk9UAKCCXaa5Mkj8PgSNTplqat0UEkarjgCfRlK2
> A0bWz2sb0WIqSytFu17AWTE=
> =z273
> -----END PGP SIGNATURE-----

[Dr. Michael J. Chudobiak]

Lamont Peterson wrote:
>  
>  Where in the World is Alexander Larson?  #243309
>  [ https://bugzilla.redhat.com/show_bug.cgi?id=243309 ] (Nautilus folder
>  icons get stuck in open state) is assigned to him, but he isn't
>  responding to it. 
I imagine he has a million high-priority bugs and new features to deal 
with...


>  The bug was filed on 2007-06-08 (over 3 months ago) by J H Ettle and
>  added my +1 to it on 2007-08-29. 
If it's not fixed in 30 days, it's free... Seriously, though, try 
investigating the bug upstream. For instance:

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

looks similar. I can not reproduce the problem on my F7 system. Are you 
using the default theme?

- Mike

[Lamont R. Peterson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, 16 Sep 2007 20:22:32 -0400
"Dr. Michael J. Chudobiak" <mjc(a)avtechpulse.com&gt; wrote:

>  Lamont Peterson wrote:
>  > 
>  > Where in the World is Alexander Larson?  #243309
>  > [ https://bugzilla.redhat.com/show_bug.cgi?id=243309 ] (Nautilus
>  > folder icons get stuck in open state) is assigned to him, but he
>  > isn't responding to it.
>  
>  I imagine he has a million high-priority bugs and new features to
>  deal with... 
I can appreciate a man being busy.

>  > The bug was filed on 2007-06-08 (over 3 months ago) by J H Ettle
> and
>  > added my +1 to it on 2007-08-29.
>  
>  If it's not fixed in 30 days, it's free... Seriously, though, try 
>  investigating the bug upstream. For instance:
>  
>  http://bugzilla.gnome.org/show_bug.cgi?id=314137 
Yeah, I should have looked, but I was lazy this time as I was traveling, working on 5
other projects at once and participating (including some presentations) at a conference.

>  looks similar. I can not reproduce the problem on my F7 system. Are
>  you using the default theme? 
I am using the default theme.

I'll also explore it some more, looking at the upstream bug, maybe I can track it
down.
- -- 
Lamont Peterson <lamont(a)gurulabs.com&gt;
Senior Instructor
Guru Labs, L.C. [ http://www.GuruLabs.com/ ]

NOTE:  All messages from this email address should be digitally signed with my
       0xDC0DD409 GPG key. It is available on the pgp.mit.edu keyserver as
       well as other keyservers that sync with MIT's.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
>
> iD8DBQFG7xYV+YBsl9wN1AkRAge6AKC9mT+xgO0QlLiSlhzO8Wjpbji+PQCfdJJX
> utmXqTVgNnrk9osUTFl/Yx4=
> =AqX3
> -----END PGP SIGNATURE-----

[Alexander Larsson]

On Sun, 2007-09-16 at 15:24 -0600, Lamont Peterson wrote:
>  -----BEGIN PGP SIGNED MESSAGE-----
>  Hash: SHA1
>  
>  Where in the World is Alexander Larson?  #243309
>  [ https://bugzilla.redhat.com/show_bug.cgi?id=243309 ] (Nautilus folder
>  icons get stuck in open state) is assigned to him, but he isn't
>  responding to it. 
I'm here. I also have 2295 open nautils bugs upstream (being the primary
upstream maintainer),  lots of nautilus bugs in redhat bugzilla (which
are all likely dups of some upstream bug). At the same time I'm trying
to work on new features like replacing gnome-vfs with the new gvfs glib
module. 

In practice this means I'm very busy and thus I won't fix all bugs, or
even have time to look at most of them. In fact, if I were to drop all
new feature development and spend 2 hours on each open bug I would have
to work over two man-years (8 hour days, 5 days a week).

I tend to look over bugzilla looking for really high priority bugs, and
I also have a bunch of bugsquad people who point me to these when they
find them. This means less-than-high-prio bugs just show up quite low on
the TODO list unfortunately. If people want to help out that would be
very nice.

>  The bug was filed on 2007-06-08 (over 3 months ago) by J H Ettle and
>  added my +1 to it on 2007-08-29.  Is Alexander missing?  Is there a
>  co-maintainer who should be available? 
I don't know what help a co-maintainer for fedora would do. What we need
are more people to look at bugs, come up with patches that fix them and
post them upstream, where I can review and commit them. This will then
instantly come back to fedora (beacuse we track upstream closely).

Unfortunately, not many people seem interested in doing this work. :(

[Richi Plana]

On Tue, 2007-09-18 at 10:59 +0200, Alexander Larsson wrote:
>  > The bug was filed on 2007-06-08 (over 3 months ago) by J H Ettle
> and
>  > added my +1 to it on 2007-08-29.  Is Alexander missing?  Is there a
>  > co-maintainer who should be available?
>  
>  I don't know what help a co-maintainer for fedora would do. What we need
>  are more people to look at bugs, come up with patches that fix them and
>  post them upstream, where I can review and commit them. This will then
>  instantly come back to fedora (beacuse we track upstream closely).
>  
>  Unfortunately, not many people seem interested in doing this work. :( 
Either that or bugzilla needs a better way to allocate tasks.

Having worked as a software developer for quite some time, I know how
many developers would rather just work on a problem rather than try to
validate bug reports and gather missing information. Personally, I would
rather work on bugs that either interest me really well, or are provided
in a format that allows me to work on the problem immediately.

Unfortunately, qualifying bug reports (finding dupes, going back to the
reporter for missing information) can only be done by people who know
exactly what real problems are and what's needed to resolve them.

I know this is something that requires discipline and structure ...
something that doesn't always go hand-in-hand with the nature of
volunteer work, but it's something that has to be addressed in order for
bugs to be proactively addressed (rather than wait for someone to bring
it up on a mailing list). As FOSS endeavors grow (and the number of
users increase), there's got to be ways to improve on volunteer
bug-fixing.

Any ideas?

I've always wondered if the assignment of tasks can be round-robin'd (or
pick some better way of scheduling tasks that's completely and really
fair, ;) ) assuming we had a couple of more volunteers.
--

Richi Plana

[Christopher Brown]

On 18/09/2007, Richi Plana <myfedora(a)richip.dhs.org&gt; wrote:
>  On Tue, 2007-09-18 at 10:59 +0200, Alexander Larsson wrote:
>  > > The bug was filed on 2007-06-08 (over 3 months ago) by J H Ettle and
>  > > added my +1 to it on 2007-08-29.  Is Alexander missing?  Is there a
>  > > co-maintainer who should be available?
>  >
>  > I don't know what help a co-maintainer for fedora would do. What we need
>  > are more people to look at bugs, come up with patches that fix them and
>  > post them upstream, where I can review and commit them. This will then
>  > instantly come back to fedora (beacuse we track upstream closely).
>  >
>  > Unfortunately, not many people seem interested in doing this work. :(
>
>  Either that or bugzilla needs a better way to allocate tasks.
>
>  Having worked as a software developer for quite some time, I know how
>  many developers would rather just work on a problem rather than try to
>  validate bug reports and gather missing information. Personally, I would
>  rather work on bugs that either interest me really well, or are provided
>  in a format that allows me to work on the problem immediately.
>
>  Unfortunately, qualifying bug reports (finding dupes, going back to the
>  reporter for missing information) can only be done by people who know
>  exactly what real problems are and what's needed to resolve them. 

This is simply untrue. I am currently about halfway through a bug triage of
all Fedora 7 kernel bugs and am doing so solely on the basis of one page
from the wiki which the kernel team put together. I know nothing of kernel
code but I do know having had a few pointers from people in the know what
information to request under what circumstances. If I can do that for the
kernel I'm sure the same goes for any application.

I know this is something that requires discipline and structure ...
>  something that doesn't always go hand-in-hand with the nature of
>  volunteer work, but it's something that has to be addressed in order for
>  bugs to be proactively addressed (rather than wait for someone to bring
>  it up on a mailing list). As FOSS endeavors grow (and the number of
>  users increase), there's got to be ways to improve on volunteer
>  bug-fixing.
>
>  Any ideas?
>
>  I've always wondered if the assignment of tasks can be round-robin'd (or
>  pick some better way of scheduling tasks that's completely and really
>  fair, ;) ) assuming we had a couple of more volunteers.
>
>  I think you just need to dive right into bugzilla and whatever component 
interests
you then start with that. Bug triage is quite rewarding and people
actually feel a little loved. Surely there is nothing like the hurt and pain
of an un-answered bug report?

Cheers
Chris

-- 
http://www.chruz.com