Re: Self-assessment of the quality of the maintenance work
On 2008-12-20, Raphael Hertzog <email@example.com> wrote:
> maintainer receives a mail with a link to a web form where he'll have a
> list of all the packages that he maintains/co-maintains and for each
> package he has to answer several questions that explain his relationship
> with the package (the answer are preseeded with the values he selected
> the previous time so that he can quickly skim over it if nothing has
> - what kind of maintainer he is
> - active (responding quickly, forwarding bugs, ???)
> - passive (responds only to major problems)
> - backup (not doing anything unless solicited)
> - if the package needs an active maintainer or not (most perl modules are
> well maintained with a single "passive" maintainer)
> - if the package needs help from another volunteer
> We could integrate various heuristics/data in the process to help the
> maintainer recognize that he's (not) keeping up and that he needs help
> or maybe that he's no more "active" but only "passive".
> If the maintainer doesn't respond, he automatically enters the MIA
> process and the package is quickly marked as needing help/attention
> from someone else.
I'd rather spend my time on fixing my packages than on filling web forms
with bureaucratic bullshit.
> The collation of all those data will give us a better view on the
> maintenance status of each package and it could be displayed on the PTS.
> We could also use those info to direct new contributors to help in
> existing packages instead of packaging new stuff.
> What do you think of the idea ?
> I would like to formalize the idea a bit more and we could use the DEP
> process for this. I would be willing to work on the implementation once
> we agree on the process.
> Raphaël Hertzog
> Le best-seller français mis à jour pour Debian Etch :