I don't know the complete process and chain of responsabilities, as
I've said before.

But I think that could exist some way of help with fast patches as
this, were several people (even a not very experienced as me) could
help.

Abot Göran words: I understand (I suffer the same) that the free time
is ever little, but in this case is only a line to patch, and having
the responsability of the package, I think that the maintainer must
patch. (About how many time we are talking, 5 minutes, 10 muinutes?).

Well, is only my opinion.

Cheers.

2006/3/30, stéphane ducasse <ducasse at iam.unibe.ch>:
>
> On 30 mars 06, at 13:48, Marcus Denker wrote:
>
> > It's a one line fix, but that has to be done in a repository where
> > I have no access
> > to, so I can not fix it myself.... sorry. There is a downside of
> > "maintained" packages:
> > Nothing happens with Network for 3 Months, we have not seen a Unix
> > vm build since
> > three years, and SqueakMap is broken for 3 Months. Maybe we need to
> > define more
> > clearly what it really means to be a Maintainer. Right now I have
> > the feeling that
> > making something "maintained" is the best way to ensure that
> > nothing happns at all.
>
> Yes we should fix that.
>
> Stef
>
>