Non-responsive maintainer process for Damien Durand

Michael Schwendt mschwendt at gmail.com
Tue Jan 13 08:37:50 UTC 2009


On Mon, 12 Jan 2009 17:49:14 +0530, Rakesh wrote:

> > On Mon, 12 Jan 2009 16:34:45 +0530, Rakesh wrote:
> >
> >> But what prevents one to assigning bugs to himself before fixing it
> >> and doing the build after commits? Not even importing the source for
> >> which fix was done ? why half work ?
> >
> > Can't answer that and don't want to guess. ;)
> >
> >
> > Let me point out the following, though:
> >
> > This would be less of an issue, if the package had a maintainer instead of
> > a non-responsive one.
> >
> 
> I request FISco member attention here.  The non-responsive maintainer
> policy was initiated long ago here.
 
It might be that the Wiki explains how to contact FESCo.

Meanwhile it would be nice if you reverted the changes in cvs.
Some of them are confusing, such as the GPL+ -> GPLv2 change,
which is not explained in the spec/changelog, or the duplicate
directory inclusion.




More information about the fedora-devel-list mailing list