: Re: Adoption of CPAN String::LCSS namespace by someone
[[ This message was both posted and mailed: see
the "To," "Cc," and "Newsgroups" headers for details. ]]
In article <01ce3a30$b08c50b0$11a4f210$@org>, "John Washburn"
wrote:
> Th
[[ This message was both posted and mailed: see
the "To," "Cc," and "Newsgroups" headers for details. ]]
In article <01ce3a30$b08c50b0$11a4f210$@org>, "John Washburn"
wrote:
> That is why I am saying there needs to be some slow, deliberate process
There is a process :)
https://pause.pe
Will do.
-Original Message-
From: Ron Savage [mailto:r...@savage.net.au]
Sent: Monday, April 15, 2013 8:06 PM
To: j...@washburnresearch.org
Cc: modules@perl.org; lima...@cpan.org
Subject: Re: Adoption of CPAN String::LCSS namespace by someone
Hi John
On 16/04/13 09:26, John Washburn
unday, April 14, 2013 8:27 PM
To: j...@washburnresearch.org
Cc: modules@perl.org; lima...@cpan.org
Subject: Re: Adoption of CPAN String::LCSS namespace by someone
Hi John
Anyone wishing to take over a namespace must chase up the existing holder of
that namespace.
In other words, CPAN admins won&#x
org
Cc: modules@perl.org; lima...@cpan.org
Subject: Re: Adoption of CPAN String::LCSS namespace by someone
Hi John
Anyone wishing to take over a namespace must chase up the existing holder of
that namespace.
In other words, CPAN admins won't do it for you :-).
So, have you actully done that? If s
Hi John
Anyone wishing to take over a namespace must chase up the existing
holder of that namespace.
In other words, CPAN admins won't do it for you :-).
So, have you actully done that? If so, then give us some details and we
can use that to decide how soon to transfer maint or co-maint to y
