Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 7 Apr 2015 08:58:03 +0000
From:      Alexey Dokuchaev <danfe@FreeBSD.org>
To:        marino@freebsd.org
Cc:        Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org>, svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org, Adam Weinberger <adamw@adamw.org>
Subject:   Re: svn commit: r383472 - head/audio/muse
Message-ID:  <20150407085803.GA82210@FreeBSD.org>
In-Reply-To: <55238F29.1010404@marino.st>
References:  <201504061859.t36IxK0v000969@svn.freebsd.org> <20150407012902.GA22994@FreeBSD.org> <91AB85D3-A8DE-491C-A2D7-4E8D7E1CDC12@adamw.org> <20150407023204.GA44784@FreeBSD.org> <552376AD.7010903@marino.st> <20150407070711.GA90710@FreeBSD.org> <552386FA.7030007@marino.st> <20150407075154.GA58322@FreeBSD.org> <55238F29.1010404@marino.st>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 07, 2015 at 10:02:49AM +0200, John Marino wrote:
> Well, we've had this discussion before.  There's no reason to release
> maintainership now with the more lax blankets.  The fear of committing
> to a maintained port is mostly gone with the exception of a very few
> maintainers that insist even spelling error and typo fixes still need to
> run by them somehow.

Fair enough; recent changes in perception of what should be (thankfully)
allowed to commit without explicit approval had mitigated the need for
release of maintainership (as hard lock) considerably.

> "maintained by community" means "maintained by nobody" and you only have
> to look at pkgsrc to see how successful this approach is.

Interesting.  Given your DragonFly experience, can you elaborate a bit on
the situation with pkgsrc, which I think was used as primary collection for
third-party software, yet later had switched (back?) to dports?  Or point
me to some article or blog entry (WRT "how successful this approach is").

> I'll continue work under the concept "ports@FreeBSD.org" ports are
> unloved and fair game.  I don't think I'm alone.

Another solution is team-maintainership; I still do not quite understand
why it did not work out with games@ (several months ago, all games@ ports
were reset to ports@).  There was some discussion AFAIR, but I didn't find
it convincing (nor can remember it now).

./danfe



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150407085803.GA82210>