Date: Thu, 28 Jul 2005 18:41:11 +0200 From: Roman Neuhauser <neuhauser@sigpipe.cz> To: Simon Barner <barner@FreeBSD.org> Cc: ports@freebsd.org, Paul Schmehl <pauls@utdallas.edu>, Kris Kennaway <kris@obsecurity.org> Subject: Re: New port with maintainer ports@FreeBSD.org [was: Question about maintainers] Message-ID: <20050728164111.GA66015@isis.sigpipe.cz> In-Reply-To: <20050728154248.GA943@zi025.glhnet.mhn.de> References: <C3B81AFDB8A5DFB5AB566CC4@utd59514.utdallas.edu> <42E81050.7090305@cs.tu-berlin.de> <66A226C3557B48ED535E3FED@utd59514.utdallas.edu> <20050727230523.GB54954@isis.sigpipe.cz> <20050728154248.GA943@zi025.glhnet.mhn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
# barner@FreeBSD.org / 2005-07-28 17:42:48 +0200:
> Roman Neuhauser wrote:
>
> [...]
> > If I create a new port for software I want to use on
> > FreeBSD (but don't want to maintain the port), I'll use
> >
> > # New ports collection makefile for: $whatever
> > # Date created: $right_now
> > # Whom: Roman Neuhauser
> > ...
> > MAINTAINER= ports@FreeBSD.org
>
> Please don't do that! Otherwise you will force other people to fix, mark
> BROKEN or deprecate the port if it doesn't work properly, and I think,
> that's a bit unfair:
>
> You created it, because you obviously need it, but you don't consider it
> important enough that you also take some care of it, e.g. fix build errors on
> other platforms, take care of bug reports, security issues etc.
>
> If you just need the port, but don't want to risk having to invest some
> more time for looking after it, please consider not submitting the port
> with maintainer ports@FreeBSD.org but keeping it locally. Otherwise, you
> shift your responsibilities onto others, who also only have a limited amount
> of time.
>
> I've Cc'ed Kris, who once had this plea not to commit new ports with
> maintainer ports@, in case he wants to correct me or add something.
Let's pretend the "tag-you're-it" regime is in force, which will
make me think twice before I contribute a port (or send-pr a patch
for anything unmaintained). I'll either maintain my changes (new
ports and patches to existing ones) ouside the ports tree, which
means increased overhead for me, and others will need to reinvent
the wheel.
Or, I'll accept the fact that my address must appear in MAINTAINER
before you accept results of my work, but will ignore any and all
PRs coming my way: I don't use the software in question enough to
be a good maintainer, so I better don't waste my time. In the
meantime, PRs for ports I have been sentenced to "maintain" hang
in GNATS, and later the MAINTAINER either gets reset, or the port
suffers from perpetual maintainer timeouts.
The policy makers won, everybody else lost.
--
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man. You don't KNOW.
Cause you weren't THERE. http://bash.org/?255991
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050728164111.GA66015>