This is the mail archive of the
mailing list for the Cygwin project.
RE: General cuestions about package mantainership
- From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder at niaid dot nih dot gov>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Sat, 17 Apr 2010 15:28:36 -0400
- Subject: RE: General cuestions about package mantainership
- References: <20100417105912.GC4103@ghost.local.lan>
d.sastre.medina wrote on Saturday, April 17, 2010 6:59 AM
> I'm taking into consideration the possibility of taking over the
> maintainership of an orphaned package, but I'd need some
> clarifications regarding this task, in order to decide if I am capable
> enough to do it. Caution comes from the assumption of my limitations.
> To me it's clear that the notion of Community implies giving back to
> it, at least, within someone's own ability and knowledge. In my case,
> this limit is the lack of C programming background.
> Would such a maintainer be totally useless?
> To my understanding, a maintainer should be able to patch the sources if
> necessary, not only build/package/publish them and act as a proxy
> between bug reporters and developers.
> Despite the fact that I'm probably answering myself, I'd be glad to
> know your opinion.
>  http://cygwin.com/cygwin-pkg-maint.
I'm not sure that says everything that's been written on the subject but
it's a start. (I seem to remember something by cgf (that I evidently
neglected to save) that I took to mean that even if it compiles OOTB,
one should be able to debug it so that if it breaks in the future, it
wouldn't become abandoned.)
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple