cvs commit: ports/archivers/p5-PerlIO-gzip Makefile ports/archivers/p5-PerlIO-via-Bzip2 Makefile ports/comms/p5-Device-SerialPort Makefile ports/converters/p5-Text-Iconv Makefile ports/databases/p5-Cache-Memcached-XS Makefile ports/databases/p5-C

[Andrej Zverev]

On Mon, May 7, 2012 at 11:58 PM, Doug Barton <dougb at freebsd.org> wrote:
> On 05/07/2012 12:47, Chris Rees wrote:
>>
>> On 7 May 2012 20:15, "Doug Barton" <dougb at freebsd.org
>> <mailto:dougb at freebsd.org>> wrote:
>>>
>>> On 05/07/2012 08:42, Sergey Skvortsov wrote:
>>> >   Pass maintainership of almost of my "p5-*" ports to "perl@".
>>> >
>>> >   (I hope updating of them will be improved).
>>>
>>> Did you discuss this with anyone from perl@? The list should not be used
>>> as a dumping ground for unloved p5-* ports. It may have been better to
>>> pass these to ports@ instead.
>>>
>>
>> I'd rather have them in perl@ than ports@; it means anyone is allowed to
>> update them rather than messing with approval etc.  Note that Sergey
>> didn't say he wouldn't update them again (or imply it IMO)
>
> I don't understand your answer. MAINTAINER= ports@ means that anyone can
> update them. Traditionally, MAINTAINER= perl@ means that a specific
> group of people have accepted responsibility for maintenance.

II would not say that responsibility maybe more same interests. If you
want to do something with perl@ ports - go ahead, but if you want to
break perl ports please consult with perl@ and of course perl@
interested to move whole CPAN into ports (it actual secret mission of
this group) :-)