Thank you.
Bruce S.
On 6/26/23 2:03 AM, Neil Bowers wrote:
Hi Bruce,
My attempts to contact Richard have also failed, so I’ve given you
co-maint on Date::Business.
Cheers,
Neil
Hi Patrick,
> I now would like to upload a different module on CPAN so would need
> first-come on a new namespace,
> which I would like to be Geo::TCX.
When you upload a release to PAUSE, it goes through all the files looking for
package statements. It then looks to see whether anyone
Hi perl modules folks,
My pause id is PATJOL and I recently adopted Geo::Gpx. I now would like to
upload a different module on CPAN so would need first-come on a new
namespace, which I would like to be Geo::TCX.
I developed a module over the years to parse Garmin TCX files and you can
look it up
an,
>
> I tried to transfer permission for Cookies to your account (JDEGUEST);
> Could you please check if it was normally transferred?
>
> Sincerely,
> Kazunori Minoda
>
> 2021年12月13日(月) 19:08 Kazunori Minoda :
>
>> Hi Jacques-san,
>>
>> Ok, I'll try i
Kind regards,
>> Jacques
>>
>> On 2021/12/15 4:45, Kazunori Minoda wrote:
>>
>> Hi Jacques-san,
>>
>> I tried to transfer permission for Cookies to your account (JDEGUEST);
>> Could you please check if it was normally transferred?
>>
>
Hi Jacques,
> Somehow, I do not have a tab "View Permissions per module" and even when I
> search for a distribution with an exact match, it still does not find
> it.Maybe it is just a matter of a refresh. I will check it later again.
Sorry, I should have mentioned that the link isn’t in the sid
rely,
Kazunori Minoda
2021年12月13日(月) 19:08 Kazunori Minoda
:
Hi Jacques-san,
Ok, I'll try it tomorrow.
Sincerely,
Kazunori Minoda
2021年12月13日(月) 18:02 Jacques Deguest :
Thank you Minoda-san for your reply and
our account
(JDEGUEST); Could you please check if it was normally transferred?
Sincerely,
Kazunori Minoda
2021年12月13日(月) 19:08 Kazunori Minoda :
Hi Jacques-san,
Ok, I'll try it tomorrow.
Sincerely,
Kazunori Minoda
2021年12月13日(月) 18:02
reply and action.
I tried to use that namespace, but could not. I still get the
error you are the primary maintainer.
I think, as Neil Bowers stated, you still need to "transfer
the first-come permission on Cookies to" me.
何度も迷惑をかけてしまいまして、本当にすみませんが、宜しくお
Hi Seyhan,
I’ve just scheduled the deletion of your older release of the HTML-STable
distribution, as that was the release that had the Date module.
Thank you for your understanding and support on these changes.
Cheers,
Neil
>>>>> "Matt" == Matt S Trout writes:
Matt> I want to use it to create a Babel.js like thing for perl, and my
checks
Matt> before picking the name completely failed to notice that you'd
uploaded an
Matt> RSS reader thing many years ago.
Hi Matt
Is this what you expected? I hope so.
"
Change Permissions
Made MSTROUT primary maintainer of Babble.
Made MSTROUT primary maintainer of Babble::Cache.
Made MSTROUT primary maintainer of Babble::Cache::Class::Hash.
Made MSTROUT primary maintainer of Babble::Cache::Dumper.
Made M
Just in case this got spamtrapped
- Forwarded message from Gergely Nagy -
Date: Thu, 02 Aug 2018 07:09:15 +0200
From: Gergely Nagy
To: Matt S Trout
Cc: modules@perl.org
Cc:
Subject: Re: Permission to steal the Babble CPAN namespace?
User-Agent: Notmuch/0.25+24~g178d62c (https
On Thu, Aug 02, 2018 at 04:55:33PM +1000, Ron Savage wrote:
> Hi Matt
>
> I don't mind if you adopt it, but I'm confused about your choice of
> spelling, babel 'v' babble, but either way, I think we'll survive
> the 'adjustment'.
Because (1) their CLI is already called babel and I often have that
Hi Matt
I don't mind if you adopt it, but I'm confused about your choice of
spelling, babel 'v' babble, but either way, I think we'll survive the
'adjustment'.
--
Ron Savage - savage.net.au
I want to use it to create a Babel.js like thing for perl, and my checks
before picking the name completely failed to notice that you'd uploaded an
RSS reader thing many years ago.
May I steal the namespace? If you can 'reply all' to this message saying yes
then I can make the re
Hi Thiago,
> Yes please
I just set your secret email address, and set the email forwarding to come to
that, so you’re contactable again :-)
Cheers,
Neil
Thank you Neil.
I would be happy to work on this new module with Thiago if he wants.
The github is at https://github.com/jackdeguest/URI-tel
Kind regards,
Jacques Deguest
On 07/06/2018 17:40, Neil Bowers wrote:
> Hi Jacques,
>
>> I wrote sometime ago a perl module URI::tel fully compliant with th
Hi Jacques,
> I wrote sometime ago a perl module URI::tel fully compliant with the rfc and
> which provides a much better implementation than the currently existing
> module.
> I tried to contact the author initially, but it seems the author cannot be
> reached. The e-mail did not work.
>
> I
Hello,
I wrote sometime ago a perl module URI::tel fully compliant with the rfc and
which provides a much better implementation than the currently existing module.
I tried to contact the author initially, but it seems the author cannot be
reached. The e-mail did not work.
I have already submitt
I just did some reading on PAUSE and found out that using top level
namespace is considered bad and impolite, I don't know whether that's
the reason that indexing failed for my module [1], but I think it indeed
qualifies as a top level package.
First, it's an object system, just
On Wed, May 30, 2018 at 06:42:41AM +0200, Andreas Koenig wrote:
> Since I could not fix the issue in the indexer's code, I manually gave
> you permissions on the 'Dot' namespace. Please make another upload
> attempt with a better $VERSION line and let us know whether it
e I couldn't find any match, yet I received a email
> from PAUSE saying that I do not have the permission for the package Dot
> and indexing has failed, here's the full content of the mail:
>> The following report has been written by the PAUSE namespace indexer.
>>
r the package Dot
and indexing has failed, here's the full content of the mail:
> The following report has been written by the PAUSE namespace indexer.
> Please contact modules@perl.org if there are any open questions.
>
> User: RSLOVERS (æ¨ å)
> Distribution file: Dot-v1
that name. Some of your old PerlQt releases which used
the slots package are still in your CPAN directory as well (but they’re not
indexed).
Stevan Little (the original author of Moose) would like to use the slots
namespace.
Are you happy for me to transfer the PAUSE permission on it to Stevan
indexing permission on
the iperl namespace. If you search for “iperl” in MetaCPAN you’ll find:
https://metacpan.org/release/iPerl <https://metacpan.org/release/iPerl>
You can use the PAUSE web interface to look for indexing permissions on a
particular module. Doing so will show:
: PAUSE
To: zaki.mug...@gmail.com, andreas.koenig.gmwojprw+pa...@franz.ak.mind.de
Subject: Failed: PAUSE indexer report ZMUGHAL/Devel-IPerl-0.007.tar.gz
Message-Id: <20170908035024.49e241...@pause.perl.org>
The following report has been written by the PAUSE namespace indexer.
Please contact m
He want me to reserve the
Kollos namespace for the upcoming 1st release (which he's been calling
Marpa::R3).
So, is it OK if I upload a placeholder such as Kollos::Placeholder?
My thought on this:
I think this is ok as long it doesn’t end up sitting there for
years, unused, and
> Jeffrey Kegler, author of Marpa (Marpa::R2), is re-writing Marpa and it now
> has the Lua language embedded in it. He want me to reserve the Kollos
> namespace for the upcoming 1st release (which he's been calling Marpa::R3).
>
> So, is it OK if I upload a placeh
Hi
Jeffrey Kegler, author of Marpa (Marpa::R2), is re-writing Marpa and it
now has the Lua language embedded in it. He want me to reserve the
Kollos namespace for the upcoming 1st release (which he's been calling
Marpa::R3).
So, is it OK if I upload a placeholder such as Kollos::Placeh
I should clarify -- yes the next uploader will get first-come, as if no one
had ever had that namespace before. But please don't do that for namespaces
that are attached to legitimate modules that people might still be using!
No signal is given that you are no longer interested in the mo
;>> rid of it.
>>>
>>> -Chad
>>>
>>> On Oct 19, 2016 4:51 AM, "Yuval Kogman"
>>> wrote:
>>>
>>>> Failed to reply to all... Sorry
>>>>
>>>>
>>>> -- Forwarded message --
ot; wrote:
>>
>>> Failed to reply to all... Sorry
>>>
>>>
>>> -- Forwarded message --
>>> From: Yuval Kogman
>>> Date: 19 October 2016 at 12:48
>>> Subject: Re: The 't2' namespace
>>> To: Matt S Trout
&
> -Chad
>
> On Oct 19, 2016 4:51 AM, "Yuval Kogman" wrote:
>
>> Failed to reply to all... Sorry
>>
>>
>> -- Forwarded message --
>> From: Yuval Kogman
>> Date: 19 October 2016 at 12:48
>> Subject: Re: The 't2
r 2016 at 12:48
> Subject: Re: The 't2' namespace
> To: Matt S Trout
>
>
> I've just done this myself, to save mst the trouble and as a form of
> agreeing.
>
> Anybody want t1? ;-)
>
> On 18 October 2016 at 16:47, Matt S Trout wrote:
>
>> Given t
Failed to reply to all... Sorry
-- Forwarded message --
From: Yuval Kogman
Date: 19 October 2016 at 12:48
Subject: Re: The 't2' namespace
To: Matt S Trout
I've just done this myself, to save mst the trouble and as a form of
agreeing.
Anybody want t1? ;-)
On
Given this namespace is just one for testing, if nobody objects in a day
or two I'll transfer it NUFFIN -> EXODIST.
(sent to modules@perl.org for a public record of this and a chance for others
to tell me if I'm wrong)
On Tue, Oct 18, 2016 at 08:22:56AM -0700, Chad Granum wrote:
&g
our author directory. That means people will still be able
> to find it by looking in your author directory, but it will no longer appear
> in the CPAN index.
I have just dropped Tom’s ownership of the UnderScore namespace, and brian’s
co-maint on it. This now resolves the clash with DANKOGAI’s underscore pragma.
Cheers,
Neil
Hi Christian,
> Thank you for your effort!
>
> Your approach is fine with me.
Thank you — I have dropped your permissions on a number of example modules, to
resolve a couple of conflicts.
> I will see to it that I move the examples to the correct location so they
> don't confuse the indexer.
Hi Christian,
I’m one of the PAUSE admins. I’m still working on resolving conflicts caused by
PAUSE now considering CPAN package names case insensitively. This has left us
with some situations where people are owners of namespaces previously
considered distinct, and now considered the same.
Yo
Hi again Tom,
>> I’m emailing you wearing my PAUSE admin hat: I’m working on resolving
>> conflicts caused by PAUSE now considering package names case insensitively.
>> This has left us with some situations where two or more people are owners of
>> namespaces previously considered distinct, and
nct, and now considered the same.
>
> Your PBJ-JNI release uses the “MAIN” namespace, so you currently have
> ownership of “MAIN”. But this now conflicts with the “Main” namespace, which
> is owned by FGLOCK.
>
> You could resolve this by releasing a new version of the module, wh
Hi Eric,
>> You have ownership of the “ICal::Parser" namespace, but you don’t have an
>> “ICal::Parser" module on CPAN now. This conflicts with the “iCal::Parser"
>> module, owned by RFRANKEL, and currently on CPAN in the
>> R/RF/RFRANKEL/iCal-Parser-1.20
w considered the same.
>
> You have ownership of the “git" namespace, which is used for a cuckoo package
> in your Git::Sub module. The trouble is that this now conflicts with the
> “Git” module, which is owned by MSOUTH, and indexed on CPAN in the
> M/MS/MSOUTH/Git-0.41.tar.
Hi Elliot,
>> To resolve this clash I propose dropping both of your permissions on
>> “Foo”. I don’t think this will cause any problems, but wanted to
>> check that you’re happy for me to do this?
>
> No problem for me. I don't know how I got this.
Heh — you’re not the first person to say that
On 6/28/16 3:50 PM, Neil Bowers wrote:
To resolve this clash I propose dropping both of your permissions on
“Foo”. I don’t think this will cause any problems, but wanted to
check that you’re happy for me to do this?
No problem for me. I don't know how I got this.
now considered the same.
Joel (RATAXIS) has ownership of the “Foo” namespace, and Elliot (ELLIOTJS) has
co-maint. There isn’t a “Foo” module on CPAN. This clashes with the FOO and
“foo” namespaces, both of which are currently on CPAN (though I’m working to
resolve that clash too!).
To resolve
nsidered the same.
>
> You have ownership of the “ICal::Parser" namespace, but you don’t have an
> “ICal::Parser" module on CPAN now. This conflicts with the “iCal::Parser"
> module, owned by RFRANKEL, and currently on CPAN in the
> R/RF/RFRANKEL/iCal-Parser-1.20.tar
;> previously considered distinct, and now considered the same.
>>>
>>> You have ownership of the “Class" namespace, but don’t have a “Class"
>>> module on CPAN (any more); maybe at some point in the past you had a Class
>>> module as part of one of y
by PAUSE now considering package names case insensitively.
>> This has left us with some situations where people are owners of namespaces
>> previously considered distinct, and now considered the same.
>>
>> You have ownership of the “Class" namespace, but don’t have a “Clas
Hi Sven,
> Yes, you can remove me. Thanks for asking!
Thank you, I’ve dropped your permissions.
Cheers,
Neil
Hi Tom,
> I’m emailing you wearing my PAUSE admin hat: I’m working on resolving
> conflicts caused by PAUSE now considering package names case insensitively.
> This has left us with some situations where two or more people are owners of
> namespaces previously considered distinct, and now consi
nct, and now considered the same.
>
> You have ownership of the Env::path namespace, but you don’t have an
> Env::path module on CPAN.
> This now conflicts with the Env::Path package, owned by DSB, and currently on
> CPAN in the D/DS/DSB/Env-Path-0.19.tar.gz release.
>
> To resolve th
nsidered the same.
>
> You have ownership of the “Class" namespace, but don’t have a “Class" module
> on CPAN (any more); maybe at some point in the past you had a Class module as
> part of one of your Class-* dists?. Your ownership of “Class” now conflicts
> with the “
Hi again Yung-Chung,
> I notice that you also have ownership of 20 Var::* packages, from
> Var::Compress to Var::XML. Having dropped the parent, should we drop these as
> well?
>
> Yes. Please do.
Thank you — I’ve dropped those permissions as well.
Cheers,
Neil
gt; To resolve the conflict, I would like to drop your permission on “Var”. I
>> don’t think this should cause you any problems, but I want to check that
>> you’re ok with this?
>
> Are you ok with me dropping your permissions on “Var”?
I have dropped your permissions on the
the same.
Your PBJ-JNI release uses the “MAIN” namespace, so you currently have ownership
of “MAIN”. But this now conflicts with the “Main” namespace, which is owned by
FGLOCK.
You could resolve this by releasing a new version of the module, which uses
PBJ::JNI::Main, in both PBJ::JNI
Hi XERN,
> You have ownership of the package name “Var”, but you don’t have a “Var”
> module on CPAN. This permission conflicts with SMUELLER’s “var” module, which
> *is* on CPAN in the S/SM/SMUELLER/Perl-APIReference-0.20.tar.gz release.
>
> To resolve the conflict, I would like to drop your p
permissions on the rogue namespace.
Cheers,
Neil
considered the same.
You have ownership of the “INTEGER” namespace, but don’t have an INTEGER module
on CPAN. This conflicts with the “integer” pragma, which ships with Perl 5, and
always has.
To resolve this conflict I’d like to drop your permissions on INTEGER. I don’t
think this will cause any
“Html"
namespace. I don’t think this will cause any problems, but wanted to check
you’re ok with me doing this?
PAUSE doesn’t let this sort of situation arise any more, so I’m just tidying up
the historical cases.
Cheers,
Neil
the same.
Your Tamino release includes package “timer”, which you’re the owner of. This
conflicts with the PHILCROW’s Timer module.
The best solution would be to rename “timer” to “Tamino::Tran::Timer”, so
that’s it contained within your distribution’s namespace. Then I could drop
your
Hi Tom,
I’m emailing you wearing my PAUSE admin hat: I’m working on resolving conflicts
caused by PAUSE now considering package names case insensitively. This has left
us with some situations where two or more people are owners of namespaces
previously considered distinct, and now considered th
Hi 永忠,
I’m emailing you wearing my PAUSE admin hat: I’m working on resolving conflicts
caused by PAUSE now considering package names case insensitively. This has left
us with some situations where two or more people are owners of namespaces
previously considered distinct, and now considered the
.
You have ownership of the “git" namespace, which is used for a cuckoo package
in your Git::Sub module. The trouble is that this now conflicts with the “Git”
module, which is owned by MSOUTH, and indexed on CPAN in the
M/MS/MSOUTH/Git-0.41.tar.gz release.
To resolve this I’d like to drop
.
You have ownership of the “Class" namespace, but don’t have a “Class" module on
CPAN (any more); maybe at some point in the past you had a Class module as part
of one of your Class-* dists?. Your ownership of “Class” now conflicts with the
“CLASS" module, owned by MSCHWERN, and cu
Hi Matt,
> I'm really struggling with this. I might like to unknowingly squat on the
> namespace for another, uh, how long have I had it?
>
> J/k. I think I came by the namespace accidentally. I hereby relinquish my
> claim upon it. And mourn the loss of something I did
.
You have ownership of the “ICal::Parser" namespace, but you don’t have an
“ICal::Parser" module on CPAN now. This conflicts with the “iCal::Parser"
module, owned by RFRANKEL, and currently on CPAN in the
R/RF/RFRANKEL/iCal-Parser-1.20.tar.gz release.
To resolve this conflict I’d li
.
You have ownership of the “Helloworld" namespace, but you don’t have an
“Helloworld" module on CPAN (maybe you did in the past). This now conflicts
with the “HelloWorld" module, owned by DYACOB, and currently on CPAN in the
D/DY/DYACOB/Aw-0.16.7.tar.gz release.
To resolve th
.
You have ownership of the “or" namespace, but you don’t have an “or" module on
CPAN (maybe you did in the past). This now conflicts with the “Or" module,
owned by YVESP, and currently on CPAN in the Y/YV/YVESP/llg-1.07.tar.gz release.
To resolve this conflict I’d like to drop your o
Hi Daniel,
> this is ancient. Years ago I have moved it to "package Mpp::profiler;”.
Thanks — I’ve dropped your permissions on “profiler”.
Cheers,
Neil
resolving
> conflicts caused by PAUSE now considering package names case insensitively.
> This has left us with some situations where people are owners of namespaces
> previously considered distinct, and now considered the same.
>
> You have ownership of the “profiler” namespace, but
I've given up ownership of "autoload." Let me know if I did it correctly.
Lincoln
On Tue, May 24, 2016 at 6:39 PM, Neil Bowers
wrote:
> > Sure will. Thanks for letting me know. Do I transfer, or just relinquish?
>
> Just relinquish the ownership. When you do that a co-maint permission will
> al
> I've given up ownership of "autoload.”
Thank you!
> Let me know if I did it correctly.
When you gave up ownership you ended up still having co-maint on “autoload”. I
just dropped that for you.
Cheers,
Neil
> Sure.
Thanks Brian — I’ve dropped those permissions.
Cheers,
Neil
> I’m fine with it. thanks for checking!
Thanks. I’ve just noticed that you have a bunch of AO::* package names owned as
well. These aren’t in conflict, but I’m given I’m deleting the parent
namespace, shall I drop your permissions on the subsidiary namespaces as well?
Hi Brian,
I’m emailing you wearing my PAUSE admin hat: I’m working on resolving conflicts
caused by PAUSE now considering package names case insensitively. This has left
us with some situations where people are owners of namespaces previously
considered distinct, and now considered the same.
Y
> Sure will. Thanks for letting me know. Do I transfer, or just relinquish?
Just relinquish the ownership. When you do that a co-maint permission will
almost certainly appear, so you’ll then need to drop that as well.
I can do this for you, if you like? I’m doing it a lot at the moment, so well
.
You have ownership of the “cwd” namespace, but don’t have an “cwd" module
(indexed) on CPAN - in 2006 you renamed your “cwd” module to “swd". The “cwd”
namespace conflicts with the “Cwd” core module, which has shipped with Perl
since Perl 5.0.
To resolve this conflict I’d like to
.
You have ownership of the “autoload” namespace, but don’t have an autoload
module (indexed) on CPAN. This conflicts with the “AutoLoad” module that user
BBB has on CPAN, in release B/BB/BBB/Module-AutoLoad-0.04.tar.gz
To resolve this conflict I’d like to drop your permissions on “autoload”, so
ons where people are owners of namespaces
> previously considered distinct, and now considered the same.
>
> You have ownership of the “Input” namespace, but you don’t have a “Input”
> module on CPAN — you renamed it from Input to Term::RawInput in January 2011.
> But your ownership of
Hi Brian,
> I'm surprised that I'm still considered the "owner". I renamed it to RawInput
> in response to a conversation with the CPAN admin at the time, and was under
> the impression that I had essentially "given up" Term::Input at that time.
>
> Yes - you may take the ownership back.
Than
Hi Peter,
> I have no recollection of obtaining the Feature name space and have no plans
> to use it. I'm completely happy for it to be re-purposed.
Thanks — I have dropped your permissions on the “Feature” namespace.
Cheers,
Neil
.
You have ownership of the “Input” namespace, but you don’t have a “Input”
module on CPAN — you renamed it from Input to Term::RawInput in January 2011.
But your ownership of the “Input” namespace conflicts with the “input” package,
owned by JPRIT, and currently on CPAN in the J/JP/JPRIT/ObjStore
.
You have ownership of the Feature namespace, but you don’t have a Feature
module on CPAN.
This now conflicts with the feature module, which is included with Perl itself.
To resolve this conflict I’d like to drop your ownership of the Feature
package. I don’t think this will cause any problems
.
You have ownership of the Env::path namespace, but you don’t have an Env::path
module on CPAN.
This now conflicts with the Env::Path package, owned by DSB, and currently on
CPAN in the D/DS/DSB/Env-Path-0.19.tar.gz release.
To resolve this conflict I’d like to drop your ownership of the Env::Path
.
You have ownership of the “Chart::GnuPlot” namespace, but you don’t have a
“Chart::GnuPlot” module on CPAN — your two releases of this were in 1998.
This now conflicts with the “Chart::Gnuplot” module, owned by KWMAK, and
currently on CPAN in the K/KW/KWMAK/Chart/Gnuplot/Chart-Gnuplot-0.23.tar.gz
onsidered distinct, and now
> considered the same.
>
> You have ownership of the “future” namespace, but you don’t have a “future”
> module on CPAN.
> This now conflicts with the “Future” package, owned by PEVANS, and currently
> on CPAN in the P/PE/PEVANS/Future-0.33.tar.gz
>
.
You have ownership of the “profiler” namespace, but you don’t have a “profiler”
module on CPAN.
This now conflicts with the “Profiler” package, owned by NIGE, and currently on
CPAN in the N/NI/NIGE/Goo-0.09.tar.gz release.
To resolve this conflict I’d like to drop your ownership of the
.
You have ownership of the “autoload” namespace, but there isn’t an autoload
module on CPAN, and from what I can see (looking at BackPAN), there never has
been.
User BBB has ownership of the AutoLoad namespace, and has an AutoLoad module
indexed on CPAN.
These were previously considered
Hi Slaven,
> feel free to drop it. I still have an unpublished "future" pragma on my
> disk, but I doubt I'll ever release it (and if, I'll choose another
> name).
Thank you — I’ve dropped your perms on “future”.
Cheers,
Neil
.
You have ownership of the “future” namespace, but you don’t have a “future”
module on CPAN.
This now conflicts with the “Future” package, owned by PEVANS, and currently on
CPAN in the P/PE/PEVANS/Future-0.33.tar.gz
To resolve this conflict I’d like to drop your ownership of the “future”
package
Hi Jörn,
>> You have ownership of the “USER” namespace, but don’t have a “USER” module
>> on CPAN.
>> This conflict’s with TBONE’s “User” module, which *is* on CPAN.
>
> I wasn't even aware of having any ownership of the USER namespace ;)
Heh, you’re not the fir
Hi,
I have read the "On The Naming of Modules" page
(https://pause.perl.org/pause/authenquery?ACTION=pause_namingmodules), and
agree that:
"top level namespaces are bad, unless they are a nexus for several modules
under that namespace or they are a fanciful name that describes
ul of the top competing libraries.My question here once again is whether it is acceptable and reasonable to create a single consistent place to put all of the various JS libraries I am going to import. I'd rather not home them inside the Ginger namespace if there is some better place to pu
ed for official ginger modules. In order to make that be true, do I need to also release a 'Ginger/Reference.pm' module in the release to ensure people don't add random things under that namespace?2. Is it acceptable to create a 'Ginger::WebApp' namespace, and suggest people p
Hi David,
> I have uploaded the changed module to my pause account, but it says I do not
> have permissions to the top level namespace. Could someone please give
> permissions to my account so that I can make this change?
>
> "This distribution name can only be used by u
As discussed previously on this mailing list, I am moving the Framework system I have developed to the top level namespace 'Ginger'. Original discussion is simply that it is multi-purpose and has many components. More and more modules will be added to it over time and it doesn'
Hi Hagen,
Just over six months ago I wrote to you about the chart/Chart namespace on CPAN:
> I’m writing this email in my role as a PAUSE admin.
>
> Following on from my previous emails, I am going to give co-maint permissions
> for the ‘chart’ namespace to the CHARTGRP pause id
Please stop shipping a P.pm.
That's already owned by LAWALSH.
--
Matt S Trout - Shadowcat Systems - Perl consulting with a commit bit and a clue
http://shadowcat.co.uk/blog/matt-s-trout/ http://twitter.com/shadowcat_mst/
Email me now on mst (at) shadowcat.co.uk and let's chat about how our C
1 - 100 of 850 matches
Mail list logo
