> mo wrote: > The question is, how would someone name his dist who wants to release a > version of FSA::Role, which uses Role::Basic as Role framework? > > I think we need something like Any::Role :-)
So that implies FSA::Role::Moose for my module, which I don't think would satisfy hdp. If there is an objection about including 'Moose' in the namespace (because it is about how it is implemented, rather than what it *is*) then shouldn't the same argument apply to including 'Role' since this is also about how it is implemented? FSA::Something, rather than FSA::Role? I have done a survey of CPAN modules, (I should have done this previously, sorry) CPAN modules with MooseRole in them (sorry hdp) POE::Test::Helpers::MooseRole We also have the 'Role' namespace used for Moose Roles or not Moose Roles as in. Role::Log::Syslog::Fast Role::Subsystem Role::Log::Syslog::Fast CPAN modules that have 'Role' in their namespace (referring to Moose Roles) Javascript::Framework::jQuery::Role::Plugin Antispam::Toolkit::Role::BerkeleyDB And some with 'Role' that are *not* Moose Reflex::Role Class::Role Chloro::Role::Form Some CPAN modules I have found that are Moose Roles, but which don't have either Moose or Role in their name are. CatalystX::DynamicComponent Nagios::Plugin::OverHTTP::Parser Simulation::discreteEvent::Recorder Graphics::Color::Equal Norma::ORM::Mappable Data::Serializable. I think this survey has shown me that every possible way of doing has been done in CPAN. But perhaps the best way is to avoid both 'Moose' and 'Role' in the namespace, but put in the description 'A Moose Role to ...'. So, that boils down to FSA::Something Which to avoid the existing FSA::Rules gives me a bit of a problem. Perhaps FSA::StateMachine Sorry for the long post but perhaps some recommendations may come out of this for naming conventions in the future? Kind regards Ian -- This e-mail (including any attachments) is confidential, may contain proprietary or privileged information and is intended for the named recipient(s) only. Unintended recipients are prohibited from taking action on the basis of information in this e-mail and must delete all copies. Nomura will not accept responsibility or liability for the accuracy or completeness of, or the presence of any virus or disabling code in, this e-mail. If verification is sought please request a hard copy. Any reference to the terms of executed transactions should be treated as preliminary only and subject to formal written confirmation by Nomura. Nomura reserves the right to monitor e-mail communications through its networks (in accordance with applicable laws). No confidentiality or privilege is waived or lost by Nomura by any mistransmission of this e-mail. Any reference to "Nomura" is a reference to any entity in the Nomura Holdings, Inc. group. Please read our Electronic Communications Legal Notice which forms part of this e-mail: http://www.Nomura.com/email_disclaimer.htm
