He named the GitHub repo which has his name in big bold letters:
https://github.com/nanoscopic
Re: the app framework naming, there's some partial conversation involving Brian Foy at https://www.mail-archive.com/modules@perl.org/msg34595.html. It doesn't seem to merit nanoscopic's comments, so I wonder if there's more to the story or if nanoscopic is being unfair.
I tried to find archives of the Grant McLean XML stuff, but cursory Google searches were unsuccessful.
If you want to name and shame people (and let's be honest: if you're naming people, saying they did bad things and inviting others to Google it, you are shaming them, explicit disclaimer of shaming intentions notwithstanding), you should (a) use your name and (b) provide adequate breadcrumbs for others to see that your position is just.
If you are so interested, I requested repeatedly to Brian and the list to approve the module after the name "Ginger" was agreed upon, but nobody with authority was willing to move it to the registered list. The leaders of CPAN basically stopped approving stuff. Registered modules were dropped entirely shortly after that.
I tried to talk reasonably to Brian, but he seemed oversensitive, likely due to being overwhelmed with his tasks. I am more sad that registered modules were dropped than anything.
It is likely that Grant McLean's comments attacking my module are no longer around; due to the changes to CPAN and the related bug tracking. He publicly stated that my XML parser has no right to call it an XML parser, in reaction to me including benchmarks showing how slow his parser is even when backed with LibXML.
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.
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.
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 :)
Once again, my point in referencing these people is to say that negative attitudes and attacks are widespread, and happens by many professional ( the people I mentioned ). I don't blame them; it is a hard community; I'd just like us all to have better attitudes.
Congrats on top comment BTW.
Notice above comment from mst ( Matt S Trout ). I appreciate him saying sorry and it actually means a lot to me. I have even more respect for those who recognize when their actions have been misunderstood and hurt people. He didn't need to apologize, but it helps the community and I wish more developers were willing to see that there are many different opinions and we need to respect them all.