Re: Module submission Dancer::Plugin::Legacy

2014-01-30 Thread Robert Stone
Greetings,

Upon further reflection, I feel that the name
Dancer::Plugin::Legacy::Routing is more appropriate.
 Dancer::Plugin::Legacy is too broad and is hogging too much namespace.

I apologies for the confusion and I hope a member of the list can make this
change.

Much appreciated!

Best Regards,
Robert Stone


On Wed, Jan 29, 2014 at 11:26 AM, Perl Authors Upload Server 
upl...@pause.perl.org wrote:


 The following module was proposed for inclusion in the Module List:

   modid:   Dancer::Plugin::Legacy
   DSLIP:   adpfp
   description: Support and Denote Deprecated Routes
   userid:  DRZIGMAN (Robert Stone)
   chapterid:   16 (Server_and_Daemon_Utilities)
   communities:

   similar:

   rationale:

 Dancer's convention is for all plugins to live in the
 Dancer::Plugin::* namespace. This module allows users to in place
 refactor their routing tables in pieces rather than en masse.

 get /bad/name/for/route = controller_do_thing;

 Can become: get /good/name/for/route = controller_do_thing
 legacy_get /bad/name/for/route = controller_do_thing;

 This allows developers to restructure and clean up their routing
 tables while preserving the interface for integration points until
 such time as the consumers can update their code as well.

 The legacy_* prefix will also support additional logging (to
 identify who is still calling legacy routes) and other features as
 it continues to be developed (deprecated routes, obsolete routes,
 etc).

   enteredby:   DRZIGMAN (Robert Stone)
   enteredon:   Wed Jan 29 17:26:05 2014 UTC

 The resulting entry would be:

 Dancer::Plugin::
 ::Legacy  adpfp Support and Denote Deprecated Routes
 DRZIGMAN


 Thanks for registering,
 --
 The PAUSE

 PS: The following links are only valid for module list maintainers:

 Registration form with editing capabilities:

 https://pause.perl.org/pause/authenquery?ACTION=add_modUSERID=e4d0_ef963e5961843c27SUBMIT_pause99_add_mod_preview=1
 Immediate (one click) registration:

 https://pause.perl.org/pause/authenquery?ACTION=add_modUSERID=e4d0_ef963e5961843c27SUBMIT_pause99_add_mod_insertit=1
 Peek at the current permissions:

 https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=mepause99_peek_perms_query=Dancer%3A%3APlugin%3A%3ALegacy



Module submission Dancer::Plugin::Legacy

2014-01-30 Thread Ron Savage

Hi Robert

I hope a member of the list can make this
change.

Nope. /You/ do that by uploading a re-named module and deleting the 
original, all via the PAUSE web site.


Cheers

--
Ron Savage
http://savage.net.au/


Module submission Dancer::Plugin::Legacy::Routing

2014-01-30 Thread Perl Authors Upload Server

The following module was proposed for inclusion in the Module List:

  modid:   Dancer::Plugin::Legacy::Routing
  DSLIP:   adpfp
  description: Support and Denote Deprecated Routes
  userid:  DRZIGMAN (Robert Stone)
  chapterid:   16 (Server_and_Daemon_Utilities)
  communities:

  similar:

  rationale:

Dancer's convention is for all plugins to live in the
Dancer::Plugin::* namespace. This module allows users to in place
refactor their routing tables in pieces rather than en masse.

get /bad/name/for/route = controller_do_thing;

Can become:

get /good/name/for/route = controller_do_thing legacy_get
/bad/name/for/route = controller_do_thing;

This allows developers to restructure and clean up their routing
tables while preserving the interface for integration points until
such time as the consumers can update their code as well.

The legacy_* prefix will also support additional logging (to
identify who is still calling legacy routes) and other features as
it continues to be developed (deprecated routes, obsolete routes,
etc).

  enteredby:   DRZIGMAN (Robert Stone)
  enteredon:   Thu Jan 30 23:58:53 2014 UTC

The resulting entry would be:

Dancer::Plugin::Legacy::
::Routing adpfp Support and Denote Deprecated Routes DRZIGMAN


Thanks for registering,
-- 
The PAUSE

PS: The following links are only valid for module list maintainers:

Registration form with editing capabilities:
  
https://pause.perl.org/pause/authenquery?ACTION=add_modUSERID=25d0_dbc81860cd145b21SUBMIT_pause99_add_mod_preview=1
Immediate (one click) registration:
  
https://pause.perl.org/pause/authenquery?ACTION=add_modUSERID=25d0_dbc81860cd145b21SUBMIT_pause99_add_mod_insertit=1
Peek at the current permissions:
  
https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=mepause99_peek_perms_query=Dancer%3A%3APlugin%3A%3ALegacy%3A%3ARouting


Re: Module submission Dancer::Plugin::Legacy

2014-01-30 Thread Ron Savage

Hi Robert

OK. Thanx for the follow-up.

On 31/01/14 10:58, Robert Stone wrote:

Greetings,

I apologize for not being more clear.

I was referring to my application to register the errantly named namespace
of Dancer::Plugin::Legacy.  I am not able to Edit Module Metadata on an
unapproved namespace, which means I'm afraid I can not mark it as Can Be
Deleted from database.  However, I think your message does give me an idea
on an action I can take.

I have resubmitted the registration request, this time for the correct
namespace of Dancer::Plugin::Legacy::Routing.  If the original request is
denied then there is no need to delete or change anything.  If my correct
request is approved, then an approval of just the correct namespace takes
care of everything.

Apologies for the confusion.

Best Regards,
Robert Stone

On Thu, Jan 30, 2014 at 5:10 PM, Ron Savage r...@savage.net.au wrote:


Hi Robert

I hope a member of the list can make this
change.

Nope. /You/ do that by uploading a re-named module and deleting the
original, all via the PAUSE web site.

Cheers

--
Ron Savage
http://savage.net.au/





--
Ron Savage
http://savage.net.au/


Re: Module submission Dancer::Plugin::Legacy

2014-01-30 Thread brian d foy
Oops, I clicked the registration link because I thought I was looking
at the wrong message. :(

-- 
brian d foy (one of many PAUSE admins), http://pause.perl.org
PAUSE instructions:  http://pause.perl.org/pause/query?ACTION=pause_04about
Archives: http://www.xray.mpe.mpg.de/mailing-lists/modules
Please send all messages back to modules@perl.org with no CC to me.


Re: Module submission Dancer::Plugin::Legacy

2014-01-30 Thread Robert Stone
Greetings,

I apologize for not being more clear.

I was referring to my application to register the errantly named namespace
of Dancer::Plugin::Legacy.  I am not able to Edit Module Metadata on an
unapproved namespace, which means I'm afraid I can not mark it as Can Be
Deleted from database.  However, I think your message does give me an idea
on an action I can take.

I have resubmitted the registration request, this time for the correct
namespace of Dancer::Plugin::Legacy::Routing.  If the original request is
denied then there is no need to delete or change anything.  If my correct
request is approved, then an approval of just the correct namespace takes
care of everything.

Apologies for the confusion.

Best Regards,
Robert Stone

On Thu, Jan 30, 2014 at 5:10 PM, Ron Savage r...@savage.net.au wrote:

 Hi Robert

 I hope a member of the list can make this
 change.

 Nope. /You/ do that by uploading a re-named module and deleting the
 original, all via the PAUSE web site.

 Cheers

 --
 Ron Savage
 http://savage.net.au/



Module submission Dancer::Plugin::Legacy

2014-01-29 Thread Perl Authors Upload Server

The following module was proposed for inclusion in the Module List:

  modid:   Dancer::Plugin::Legacy
  DSLIP:   adpfp
  description: Support and Denote Deprecated Routes
  userid:  DRZIGMAN (Robert Stone)
  chapterid:   16 (Server_and_Daemon_Utilities)
  communities:

  similar:

  rationale:

Dancer's convention is for all plugins to live in the
Dancer::Plugin::* namespace. This module allows users to in place
refactor their routing tables in pieces rather than en masse.

get /bad/name/for/route = controller_do_thing;

Can become: get /good/name/for/route = controller_do_thing
legacy_get /bad/name/for/route = controller_do_thing;

This allows developers to restructure and clean up their routing
tables while preserving the interface for integration points until
such time as the consumers can update their code as well.

The legacy_* prefix will also support additional logging (to
identify who is still calling legacy routes) and other features as
it continues to be developed (deprecated routes, obsolete routes,
etc).

  enteredby:   DRZIGMAN (Robert Stone)
  enteredon:   Wed Jan 29 17:26:05 2014 UTC

The resulting entry would be:

Dancer::Plugin::
::Legacy  adpfp Support and Denote Deprecated Routes DRZIGMAN


Thanks for registering,
-- 
The PAUSE

PS: The following links are only valid for module list maintainers:

Registration form with editing capabilities:
  
https://pause.perl.org/pause/authenquery?ACTION=add_modUSERID=e4d0_ef963e5961843c27SUBMIT_pause99_add_mod_preview=1
Immediate (one click) registration:
  
https://pause.perl.org/pause/authenquery?ACTION=add_modUSERID=e4d0_ef963e5961843c27SUBMIT_pause99_add_mod_insertit=1
Peek at the current permissions:
  
https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=mepause99_peek_perms_query=Dancer%3A%3APlugin%3A%3ALegacy