What to do with PMEdit?

GrandFather has asked for the wisdom of the Perl Monks concerning the following question:

Some time ago when I was a young Perl programmer and infatuated with PerlMonks (actually both appellations still apply) I wrote PerlMonks Editor and added it to CPAN as a script. Scripts on CPAN are very much second (probably more like fourth) class citizens and it has languished there somewhat. Also I've been busy with various other projects since then and it is only now (with a little prompting from various others) that I have returned to it.

I am considering generating a Tk::PerlMonks name space on CPAN and adding PMEdit.pm to it along with a couple of support modules and what amounts to the existing PMEdit.pl as a sample script.

So the question is: does this seem like an appropriate approach?

The intent is to make PMEdit easier to find, easier to maintain (through rt bug tracking etc) and easier for others to leverage the module code for other purposes.

Update: my initial focus was narrow. Discussion with others and Perlbotics comment suggests that a root PerlMonks name space is most appropriate. CPAN tends to be rather reluctant to grant new root level name spaces however so a little campaigning may be appropriate.

Perl reduces RSI - it saves typing

Comment on What to do with PMEdit?

Replies are listed 'Best First'.
Re: What to do with PMEdit? by McDarren (Abbot) on Oct 19, 2008 at 05:15 UTC
Seems appropriate to me. Having a PerlMonks namespace on CPAN might even encourage others who have written PerlMonks-related utilities to turn them into modules. Cheers, Darren :)	[reply]
Re^2: What to do with PMEdit? by Perlbotics (Archbishop) on Oct 19, 2008 at 18:50 UTC
Yes, I always wondered why there's no such (Update: root-)namespace yet. But let me suggest PerlMonks as the CPAN root namespace (if that is legal), leading to PerlMonks::Tk::PMedit or PerlMonks::PMedit since a lot of PM specific modules might not belong into the Tk-category. Some weeks ago, I dusted off some scripts from the Code Catacombs which might find their way into PerlMonks::XP some day...	[reply]
Re: What to do with PMEdit? by DrHyde (Prior) on Oct 20, 2008 at 09:57 UTC
There's nothing to stop you from uploading something and creating a new "root" namespace". No campaigning required. However, it is normal for modules that exist to talk to a website go in WWW::* (eg WWW::Ebay) or Net::* (eg Net::Amazon).	[reply]
Re^2: What to do with PMEdit? by GrandFather (Saint) on Oct 20, 2008 at 18:54 UTC
Thank you. Good suggestion. WWW::PerlMonks sounds pretty good to me. Perl reduces RSI - it saves typing	[reply]
Re: What to do with PMEdit? by CountZero (Bishop) on Oct 20, 2008 at 04:50 UTC
I'm most surprised PerlMonks doesn't exist already. CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James	[reply]
Re: What to do with PMEdit? by Anonymous Monk on Oct 20, 2008 at 10:08 UTC
CPAN isn't reluctant, CPAN doesn't care :) the module-list may be reluctant to endorse namespaces, but they don't need to be consulted. http://perlmonks-mods.sourceforge.net/ http://sourceforge.net/projects/perlmonks-mods/	[reply]