This is the mail archive of the cygwin-apps mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Do we need a new maintainer for fetchmail?

On Nov 30 15:08, Matthias Andree wrote:
> Am 30.11.2010 13:42, schrieb Corinna Vinschen:
> > So, first I'd really like to get a word from you, Jason.
> > 
> > If Jason is AWOL for a longer period of time (which I doubt, since he
> > was still active on the cygwin list early November), then we can talk
> > about taking over maintainership, if that's an option for you.
> Dear Corinna, *,
> Taking over is not really an option for me, as I don't mean to commit to
> Cygwin-related projects, or take maintainership from anyone (including Jason).
> I also don't want to become YAMWHTLT (yet another maintainer who has too little
> time).

No worries.

> Just to explain my background a bit more, and acknowledging the differences
> between projects -- in FreeBSD third-party ports, there is a policy [1] that
> developers ("committers", i. e. those with CVS write access) can perform minor
> updates (such as patchlevel, bug fixes, ...) even without maintainer consent
> after two weeks.  I wonder if it might be an option that Cygwin establishes
> similar policies to deal at least with critical bugs in packages, or establishes
> the concept of a "shared maintainer" or "also permitted to upload minor updates".

We don't have a problem with maintainance sharing and we already have
packages doing that.  The X server is maintained by two guys, for
instance.  But it's an item of consent between the sharing maintainers.
>From our perspective it's rather important to have at least *one*
maintainer for a package who's willing not only to keep a package in a
good shape, but also to answer user questions on the cygwin list.  This
is due to the fact that we have a rather small base of experienced users
on the list, who can help less experienced users.  It doesn't help to
have thousands of packages if there's nobody who keeps an eye on the
package *and* the problems of the users.

Having said that, if Jason is ok with sharing maintainership between the
two of you, even if you don't participate on the cygwin ML, we're
certainly content with the arrangement.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]