[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: F7 Release Discussion (was Re: Slightly OT: bad rap for Fedora, and realistic effects)

On Mon, 26 Feb 2007 22:52:25 +0100
mschwendt tmp0701 nospam arcor de (Michael Schwendt) wrote:

> On Mon, 26 Feb 2007 11:29:10 -0700, Kevin Fenzi wrote:
> > > > > Now it's getting interesting. Being a sponsor has never before
> > > > > implied that you have to fix orphans or take over packages
> > > > > when a sponsored person leaves the project or is AWOL. With
> > > > > such a requirement, the sponsorship system would be too
> > > > > burdensome and too much of a risk.  
> > > > 
> > > > ok. So, who should handle those things? FESCo? 
> > > > No one?  
> > > 
> > > Quite obviously, those are not the only two options. And hence the
> > > answer to the latter two questions is "no".  
> > 
> > Perhaps I wasn't being clear... 
> > 
> > What are your thoughts/opinions on how this should work? 
> > I would love to hear your input. 
> Do you disagree? Do you think that if somebody leaves the project, the
> sponsor is responsible for the orphaned packages?

Perhaps I am not being clear on what I am proposing. 
Of course a sponsor shouldn't be required to start maintaining all the
leaving maintainers packages. There's no way that would work. 

What I am saying is that they should be able to drive forward the
AWOLmaintainer process for those packages, and do things like posting
emails to the list saying "I sponsored maintainer foo, who is no longer
around, the following packages are orphaned, does anyone want to take
over them?". 

Is that more clear?

> These tools are in "fedora" cvs. Sometimes the scripts are tweaked
> for the buildsys installation environment and may need a few
> modifications if used elsewhere. The upgradecheck.py script simply
> takes an external config file with definitions of SRPMS repos.
> Whether it would work to include the needsign repo, I don't know,
> because the needsign repo is a multi-arch repo -- all archs including
> SRPMS in a single repo. :)

ok. I can take a look. 

Thanks for all your hard work on those scripts. :) 


Attachment: signature.asc
Description: PGP signature

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]