There's been several cases recently of folks publishing new modules to
CPAN in the DateTime namespace that don't really fit in with the DateTime
project as a whole. Sometimes these modules are duplicative of existing
efforts, and the authors can hopefully be redirected towards helping an
existing project.
In some cases, the functionality may be useful, but the namespace chosen
doesn't make sense, or the API doesn't really fit well with other DateTime
stuff.
I usually ask the module authors to rename or withdraw modules, with
varying responses from "fuck you" to "ok, sure". I was thinking that it
might be good to encourage people to use DateTimeX to publish things that
use/produce/relate to DateTime modules but aren't blessed by the DateTime
project (err, whatever that means ;)
That way authors would have a simply place to publish stuff without me
hassling them. If a few people publish DateTimeX modules, hopefully future
module authors will pick up on that and just use it. It's also a good
namespace for experimental modules that folks "in the know" might want to
publish.
Of course, if someone published a DateTimeX module that should be part of
the "official" project, we could ask them to rename it, but that's a nice
problem to have.
What do folks think?
-dave
/*===================================================
VegGuide.Org www.BookIRead.com
Your guide to all that's veg. My book blog
===================================================*/
