On Fri, 02 Nov 2012 16:44:06 +0000 "Jóhann B. Guðmundsson" <johan...@gmail.com> wrote:
> On 11/02/2012 04:25 PM, Tom Lane wrote: > > =?UTF-8?B?IkrDs2hhbm4gQi4gR3XDsG11bmRzc29uIg==?= > > <johan...@gmail.com> writes: > >> On 11/02/2012 03:32 PM, Matthew Miller wrote: > >>> On Fri, Nov 02, 2012 at 03:12:56PM +0000, "Jóhann B. > >>> Guðmundsson" wrote: > >>>> Dead/un-maintained packages need to be removed/reassigned at the > >>>> very *beginning* of an new development cycle so feature owners > >>>> and others working in the community are dealing with active and > >>>> actively maintained packages. > > How exactly are you going to force maintainers who go missing to do > > so at a prescheduled time? Real life is seldom that convenient. > > If at this point we dont have any process that can actively tell if a > maintainer is present and active within the project then we have > bigger fish to fry then the feature process... If we have problem A and problem B, can't we work on both at the same time? :) > Seriously it should not be anymore complex than monitoring last login > into the relevant infrastructure pieces to determine if the relevant > maintainer is active or not. > > bash script + a cron job should suffice to achieve just that. It's not at all that simple, I'm afraid. How long since last activity do you consider someone 'inactive' ? What if the packages that maintain simply don't need any changes? What if they are on vacation? What if they are active on package A, but not doing something on package B that you wish they would? I've long wanted to revamp our process. I welcome concrete proposals to do so. kevin
signature.asc
Description: PGP signature
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
