[ACTION REQUIRED] Retiring packages for F-17

Iain Arnell iarnell at gmail.com
Sat Jan 14 12:10:42 UTC 2012


2012/1/14 "Jóhann B. Guðmundsson" <johannbg at gmail.com>:
> On 01/14/2012 10:44 AM, Iain Arnell wrote:
>>
>> You've got to be kidding. In a little over three years, I've picked up
>> more than 300 packages and only 81 bugs - most of which are from
>> upstream release monitoring. I've got no problem at all keeping up
>> with the work.
>
>
> Nope no kidding with my example above and to point you out others are having
> difficulty's maintaining a single component with 300+  bugs on them ( like
> the kernel ).

Then you can't blindly work the averages and apply hard limits. Just
because some packages are high maintenance, doesn't mean that can't
cope with dozens of low maintenance packages.

> Expecting a maximum of 4 hours of volunteering per day from an individual on
> average in the project is not that far off ( and by some that number might
> be considered to high ) but ofcourse you can twist that math as much as you
> like to suit the outcome you would like to see.
>
> For example you can say I dont have a work and I dont have kids thus I
> should be allowed to maintain more packages but then you suddenly knock up a
> broad and land a job and the scenario becomes very much different...
>
> I personally fail to see this "I maintain gazillion packages and I'm the
> best" mentality that some seem to carry which more often than not they
> poorly maintain those gazillion packages and it would not take more then a
> bus accident to leave the project in limbo...

We just had this situation - cweyl left the project and his 300 or so
packages were orphaned. Most are implicitly co-maintained by other
members of perl-sig. The only difficulty is that pkgdb doesn't make it
easy for other members of the sig to claim the particular packages
they're most interested in - but we're coping and mostly have the
situation under control.

> I would think the projects goal here is to have more individuals maintaining
> the same package not one maintainer maintaining all the packages
>
> How many co-maintainers do you have on those 300 packages you maintain and
> how much time on average did you spend on fixing one of those 81 bugs ( from
> report to build with fix )

I think every single package has perl-sig as co-maintainer. It's a
shame there's no proper infrastructure to support group maintainership
of packages, but we seem to get by with enough provenpackagers in the
sig.

And the time to fix bugs is generally quite short - probably no longer
than the 30 minutes you guestimated earlier.

-- 
Iain.


More information about the devel mailing list