undefined | Better HN

0 pointsmst11y ago0 comments

Honestly, the registered list had been on its way out for quite a while by the time that happened; by the point of the discussion, I was only monitoring registrations because I cared about helping people find better names rather than because I thought the final registration click was relevant in and of itself.

You were, and are, totally welcome to upload the module anyway (and in fact I'd encourage you to do so), and you have my apologies if that part wasn't made sufficiently clear at the time.

0 comments

nanoscopic11y ago

Thank you for your comment; I appreciate the acknowledgement. I do intend to do as you say and change the name properly, since basically it doesn't matter now that "registered modules" are gone. I have not done so yet simply because the framework is poorly documented ( as far as what is published ) at the moment, and I wanted to add the documentation properly when I take over a whole root namespace. Also; I am a bit unclear as to -how- exactly to claim the whole root namespace, since the way it is done is different among several of the modules I observed.

I assume I simply register a module with a root name to claim it, as sort of a placeholder pointing to all the component pieces. I don't want to include the actual pieces in the root module; just use the root module itself as documentation as I see it done among other CPAN modules.

I would like to point out that I realize that my feeling hurt through the discussion is mostly my perspective; hence stating that I recognize you have many other things to do. My frustration was that I had no knowledge that registrations "were on their way out" and my requests at the time to get it registered properly seemed to be ignored. ( I assumed because there were not enough people who cared about registrations at that point to handle doing it )

Once again thank you and I hope to move forwards and be an active member of the community.

mstOP11y ago

There is not, and never has been, any enforcable means of claiming a whole root namespace; the demise of the registered modules list hasn't changed that at all.

Basically, just upload the thing, and document whether you want other people's extensions to live under the root namespace or somewhere else - e.g. DBIx::Class extensions are mostly just under DBIx::Class:: whereas Moose extensions live in MooseX:: - and a hybrid would be Catalyst, where certain types of extensions live under e.g. ::Plugin::, ::Model::, etc. and then things that don't fit in any of the usual extension namespaces go into CatalystX::

You'll find, generally, that people writing an extension to your code will respect your choices, and that any violation of them will usually be an accident and quickly resolved by filing a bug saying "hey, could you follow the policy please".

I did, honestly, mean to email you off list explaining what was likely to happen wrt the registered module list (starting a thread about it at the time on modules@ would likely have been ... unproductive).

Unfortunately, I completely forgot, a failure for which I'm hoping my responses to you today will at least partially compensate :)

j / k navigate · click thread line to collapse