svn commit: r386075 - in head: devel/p5-AnyEvent-DBus devel/p5-App-Control devel/p5-C-Scan devel/p5-CPAN-YACSmoke devel/p5-Cdk devel/p5-Config-Record devel/p5-ConfigReader devel/p5-Data-Hierarchy d...

[Mathieu Arnold]

+--On 11 mai 2015 18:17:38 -0500 Mark Linimon <linimon at lonesome.com> wrote:
| On Mon, May 11, 2015 at 04:56:06PM +0200, Mathieu Arnold wrote:
|> I just added a couple dozen ports to perl@, there are already 2k+ there,
|> it's not changing any number in a significant manner.
| 
| Well, I'm grumbling a bit, I know.

Grumbling is fine, I do it everyday :-p

| But I would like it to be explicit:
| 
|  - can only members of the perl@ team commit to perl@ ports?

Well, it'd be better if People who have a clue about Perl are the one
trying not to break them :-)
Also, like Bryan said, everybody can join.

|  - if so, are we asserting a single team can effectively maintain
|    > 2000 ports?
| 
| If the latter, I am very skeptical.

To be fair, they don't change often, portscout[1] reports about a couple
every day, it takes about five minutes to get them updated.  There are a
couple in that list that don't get updated, mostly because one needs oracle
and the other needs the X server you're going to run it to build.  Also,
the vast majority of Perl ports are *very* easy to maintain, it's as simple
as it can get.

1: <http://portscout.freebsd.org/perl@freebsd.org.html>
-- 
Mathieu Arnold