Apologies for not responding to your original inquiry Lukas, it slipped through the cracks. I assure you I wasn't being hostile in missing the one email you'd sent on the matter. :)
Are you talking about using my namespace for a different purpose, or for the same functionality? If this is for different functionality, I don't think re-purposing existing namespaces in CPAN is a good idea in principle, since any code using the module would break in a spectacular and explodey ways when upgraded. I wouldn't want that, even for this module; others might not view my code as silly as I do. If you are talking about implementing the same functionality using the same conventions and provably better underpinnings, I like the idea. However, I wouldn't want the module to suddenly be incompatible with older perls only for the sake of using a new perl feature. Source filtering gets a bad rap, but this module is so simple in its usage of it that I can call the code relatively bulletproof. I'd like to see what you have to replace it. -Kilna On Mon, May 13, 2013 at 1:10 PM, Lukas Mai <l....@web.de> wrote: > Hi, > > on 2013-03-31 I sent the following message to Anthony Kilna < > anth...@kilna.com>, the author of Quote::Reference: > > ------------------------------**------------------------------** > ----------- > Hi, > > I want to upload a module I've written to CPAN. My preferred name for it > would be "Quote::Reference". Obviously that's not possible because you're > already using this name. (To be honest, I actually uploaded a v0.01 without > checking the name was available first. I'm sorry about that.) > > I wanted to ask you if you'd agree to rename your module and let me take > over the name Quote::Reference. > > Your documentation says the module is just a silly experiment and you > don't expect anyone to actually use it. And it uses source filtering, which > can cause mysterious failures in code. For these reasons I assume you're > not overly attached to the code. > > My version is based on the "pluggable keyword" mechanism in newer perls > (so it doesn't break), and of course I intend to use it in real code. :-) > ------------------------------**------------------------------** > ----------- > > I haven't received a response yet. > > My questions: What can I do? Should I just choose a different name? Or can > I get comaintainership even though I intend to completely replace the > module by an incompatible version? Is there another way to reach KILNA > (apparently inactive since 2012-08-30)? > > > Looking for advice, > -- > Lukas Mai <l....@web.de> >
