# from Pedro Melo on Friday 07 September 2012:
>... personal modules that don't fit into any other namespace, for
>public experimental modules, and for author metadata.
>...
>You can skip indexing them on search/metacpan, or index them and not
>include them on general search results. Make that opt-in.
>
>You can more aggressively remove old versions. You can delete old
>versions to Backpan. Or even send skip sending them at all to Backpan.
>
>And you can skip them when you create your local CPAN mirror, pulling
>only your own namespace.

It sounds like you're mostly talking about experimental modules (or 
experimental forks of existing ones) -- which is not what I would call 
"personal", so I think that's the wrong term for this discussion (and 
somewhat loaded/possessive.)

I think the notion of using your PAUSE ID as a sub-namespace is pretty 
well-established for BeLike &c (for better or worse.)

As for the plan of having somewhere to put experiments or forks, 
Author::EWILHELM doesn't seem right, and it's also too long, and what if 
I wrote it, but at some point in the future, someone else is going to 
maintain/co-maintain it?  This problem of "what to name a fork" is 
partly an artifact of not having namespace/authority support in 
require(), no?  Why not name the first fork of Foo, X1::Foo and if 
someone wants to fork it again, X2::Foo, etc?  The same could work for 
experiments like x201209090002.pm

If you're tempted to prefix a distribution with your name, why is that?  
What if we just had a tmp:: namespace and deleted anything in there 
older than 2 years?

I think there's some way to control indexing with meta.ymlson, though 
one would probably want to go read the mldistwatch code and see.

As for what's in a backpan: that's an rsync cron job running on many 
servers (some of which may have been drywalled-over by now) and not 
likely to change much unless disk space gets much more expensive.

--Eric
-- 
---------------------------------------------------
    http://scratchcomputing.com
---------------------------------------------------

Reply via email to