Time it takes to review bug/patch in bugzilla?

[Richard Shaw]

I posted the following patch[1] to the livecd-iso-to-disk script on
June 17th and still have not gotten any feedback. Not even a "Hey, you
suck a programming, don't ever do that again".

This list is relatively low volume, but I can't even count the number
of times someone has posted about a problem to other lists and I've
typically seen responses to the effect of, "File a bug report, or
better, submit a patch!"

Well that's exactly what I did, but taking nearly a month (and still
waiting) to receive any feedback does not do much to motivate people
to participate.

Richard

[1] http://bugzilla.redhat.com/show_bug.cgi?id=604942

[Bruno Wolff III]

On Tue, Jul 06, 2010 at 16:43:02 -0500,
  Richard Shaw <hobbes1069(a)gmail.com&gt; wrote:
>  I posted the following patch[1] to the livecd-iso-to-disk script on
>  June 17th and still have not gotten any feedback. Not even a "Hey, you
>  suck a programming, don't ever do that again".
>  
>  This list is relatively low volume, but I can't even count the number
>  of times someone has posted about a problem to other lists and I've
>  typically seen responses to the effect of, "File a bug report, or
>  better, submit a patch!"
>  
>  Well that's exactly what I did, but taking nearly a month (and still
>  waiting) to receive any feedback does not do much to motivate people
>  to participate. 
The live spins area of Fedora is understaffed. I want to do more with getting
things improved with livecd-tools, but I am also stuck taking a bigger role
in the spins SIG part, as we are really short handed there. We really need a
few leaders to step up and some worker bees willing take take on things
assigned to them. (I would prefer to be in the worker bee category.)
I also have some other important stuff (Ogre) that I need to get done before
the alpha and it might end up taking up quite a bit of my time.

I'd like to see reviews of the various pending patches get done and have
some sort of process for deciding what needs to happen (just a single review
or is more than one ack needed) before a patch can get applied.

I was also hoping we could get a meeting set up where this stuff could be
hashed up and we could get things moving again. I really don't have the
time to lead this effort, but will provide some help in doing work if
someone else does.

[Jasper Hartline]

On Tue, Jul 6, 2010 at 3:17 PM, Bruno Wolff III <bruno(a)wolff.to&gt; wrote:
>  On Tue, Jul 06, 2010 at 16:43:02 -0500,
>   Richard Shaw <hobbes1069(a)gmail.com&gt; wrote:
> > I posted the following patch[1] to the livecd-iso-to-disk script on
> > June 17th and still have not gotten any feedback. Not even a "Hey, you
> > suck a programming, don't ever do that again". 
A major patch we need though right now is umounts/rpmdb closing when
something fails.
It is a major issue.

[Richard Shaw]

On Tue, Jul 6, 2010 at 7:18 PM, Jasper Hartline
<jasper.hartline(a)gmail.com&gt; wrote:
>  A major patch we need though right now is umounts/rpmdb closing when
>  something fails.
>  It is a major issue. 
That's definitely out of my league. Out of curiosity, what part/script
of the livecd-tools touches the rpmdb?

Thanks,
Richard

[Jasper Hartline]

On Wed, Jul 7, 2010 at 6:16 AM, Richard Shaw <hobbes1069(a)gmail.com&gt; wrote:
>  On Tue, Jul 6, 2010 at 7:18 PM, Jasper Hartline
>  <jasper.hartline(a)gmail.com&gt; wrote:
> > A major patch we need though right now is umounts/rpmdb closing when
> > something fails.
> > It is a major issue.
>
>  That's definitely out of my league. Out of curiosity, what part/script
>  of the livecd-tools touches the rpmdb? 
When packages are deployed to teh fake root to create the LiveCD
the yum parts may leave the RPM database open if you for example,
ctrl-c while packages are installing to switch to another mirror and it dies.
It'll raise an exception and say it can't unmount
/var/tmp/install_root because the rpm database is
open still. So what ends up happening if you for example kill
livecd-creator a few times
and maybe your repo is incorrect in your ks file once or twice
you get a big huge mess of no loop devices available and mounts in
/var/tmp/install_root
where I have seen livecd-creator won't even run again cause it can't
do any bind mounts.
Leaves old mounts behing, just really ugly.

This is a simple fix but as far as I know astokes dhuff and bruno who
are members of this list
can commit your patches. Maybe send the patches you have again attached here?
Ask them to commit these directly?

[David Huff]

On 07/06/2010 06:17 PM, Bruno Wolff III wrote:
>  On Tue, Jul 06, 2010 at 16:43:02 -0500,
>     Richard Shaw<hobbes1069(a)gmail.com>  wrote:
> > I posted the following patch[1] to the livecd-iso-to-disk script on
> > June 17th and still have not gotten any feedback. Not even a "Hey, you
> > suck a programming, don't ever do that again".
> >
> > This list is relatively low volume, but I can't even count the number
> > of times someone has posted about a problem to other lists and I've
> > typically seen responses to the effect of, "File a bug report, or
> > better, submit a patch!"
> >
> > Well that's exactly what I did, but taking nearly a month (and still
> > waiting) to receive any feedback does not do much to motivate people
> > to participate.
>
>  The live spins area of Fedora is understaffed. I want to do more with getting
>  things improved with livecd-tools, but I am also stuck taking a bigger role
>  in the spins SIG part, as we are really short handed there. We really need a
>  few leaders to step up and some worker bees willing take take on things
>  assigned to them. (I would prefer to be in the worker bee category.)
>  I also have some other important stuff (Ogre) that I need to get done before
>  the alpha and it might end up taking up quite a bit of my time.
>
>  I'd like to see reviews of the various pending patches get done and have
>  some sort of process for deciding what needs to happen (just a single review
>  or is more than one ack needed) before a patch can get applied.
>
>  I was also hoping we could get a meeting set up where this stuff could be
>  hashed up and we could get things moving again. I really don't have the
>  time to lead this effort, but will provide some help in doing work if
>  someone else does. 
I totally agree, unfortunately I have taken on a new roll within Red Hat 
and I will not be able to devote as much time here as I would like.

I also agree that an irc meeting would be a good way to "kickstart" the 
project in the rear. Please check out the link below and indicate when 
would be a good time to hold the first IRC meeting.....

http://whenisgood.net/exg8qz

-D