Hi Friends,
I am new to this list. I have proposed a top-level namespace at the CPAN, as
described below. I sent my request to [email protected], and Neil B suggested I
might check for feedback on this list.
Anything appreciated!
Thanks,
— Bruce
_bruce__van_allen__santa_cruz_ca_
> Begin forwarded message:
>
> From: Bruce Van Allen <[email protected]>
> Subject: Fwd: Namespace Request: Concierge
> Date: February 9, 2026 at 11:31:59 AM PST
> To: Neil Bowers <[email protected]>
> Cc: [email protected], [email protected]
>
> Hi Neil,
>
> Thanks for your response.
>
> Yes, my intention is to keep 'Concierge' as the top level, and the docs will
> expressly emphasize that added modules should stay under that.
>
> I am CC:ing this to the module authors list for suggestions|comments. I am
> eager, but I want to get this right.
>
> Thanks, and much appreciation for your contributions to the Perl world!
>
> — Bruce
>
> _bruce__van_allen__santa_cruz_ca_
>
>
> — Bruce
>
> _bruce__van_allen__santa_cruz_ca_
>
>> Begin forwarded message:
>>
>> From: Neil Bowers <[email protected]>
>> Subject: Re: Namespace Request: Concierge
>> Date: February 9, 2026 at 7:37:12 AM PST
>> To: Bruce Van Allen <[email protected]>, [email protected]
>>
>> Hi Bruce,
>>
>> I am requesting permission to use the top-level "Concierge" namespace for a
>> new Perl distribution focused on user management services for applications
>> [...]
>>
>> I don't see any problem with this.
>>
>> My one strong suggestion is that you make sure all modules come under your
>> top-level domain (in this case Concierge). Your description only mentions
>> modules which meet this guideline, but we regularly see large distributions
>> where they decided that "User" would be easier as a top-level domain, rather
>> than Foobar::Flange::User. Random generically-named toplevel namespaces
>> often cause indexing permissions clashes.
>>
>> There's a low volume mailing list "CPAN Authors" which is a more appropriate
>> place to ask questions like this. It might be worth sending your message
>> there to get feedback, but if you're keen to get on with it, then go for it
>> ;-)
>>
>> Cheers,
>> Neil
>>
>
>
>
>> Begin forwarded message:
>>
>> From: Bruce Van Allen <[email protected]>
>> Subject: Namespace Request: Concierge
>> Date: January 21, 2026 at 12:34:27 AM PST
>> To: [email protected]
>>
>> PAUSE maintainers,
>>
>> I am requesting permission to use the top-level "Concierge" namespace for a
>> new Perl distribution focused on user management services for applications.
>>
>> ## Namespace Request
>>
>> **Proposed Namespace:** Concierge
>>
>> **Module Prefixes:**
>> - Concierge (platform composition)
>> - Concierge::Auth (authentication services)
>> - Concierge::Users (user data management)
>> - Concierge::Sessions (session management)
>>
>> ## Description
>>
>> Concierge is an integrated user management service platform for
>> applications. It provides a cohesive suite of modules that work separately
>> or together to offer:
>>
>> 1. **Authentication Services** (Concierge::Auth) - AVAILABLE NOW
>>
>> 2. **User Data Management** (Concierge::Users) - AVAILABLE NOW
>>
>> 3. **Session Management** (Concierge::Sessions) - AVAILABLE NOW
>>
>> 4. **Unified Service Composer** (Concierge) - FUTURE
>> - Suite module affordances composed as specified by the application
>> - Single API for complete user management
>> - Enables Plug-in replacements for suite modules
>> - Auth, Users, and Sessions modules still work separately
>>
>> ## Justification for Top-Level Namespace
>>
>> I am requesting a top-level namespace rather than nesting under a category
>> because:
>>
>> 1. **Cohesive Ecosystem**: Concierge is designed for providing a complete
>> system, not simply a utility module. The namespace will enable variations
>> and specializations by other developers, both within the Auth, Users, and
>> Sessions services but perhaps also adding additional services.
>>
>> 2. **Distinctive Branding**: "Concierge" clearly conveys the purpose
>> (service-oriented user management) and is memorable.
>>
>> 3. **Service Platform**: This is a service-oriented platform meant for
>> composing multiple distinct services (Auth, Users, Sessions) into a unified
>> but customizable whole.
>>
>> 4. **Standalone Components**: Each Concierge::* module can be used
>> independently or as part of the integrated platform.
>>
>> 5. **User Need**: I have numerous applications built over time with
>> scattered, inconsistent user management code. Concierge provides a unified,
>> professional solution that I believe will greatly improve my applications
>> and offer a real benefit to the Perl community.
>>
>> ## Current Status
>>
>> - **Concierge::Sessions** is complete and ready for CPAN release
>>
>> - **Concierge::Auth is complete**, final documentation being prepared
>>
>> - **Concierge::Users** is complete, final documentation being prepared
>>
>> - **Concierge** is under active development, full API not final
>>
>> ## Distribution Details
>>
>> - **Author**: Bruce Van Allen ([email protected])
>> - **Perl Version Required**: 5.36+
>> - **Dependencies**: DBI, DBD::SQLite, JSON::PP (all core/common)
>> - **Testing**: Test2::V0
>> - **License**: Artistic License 2.0 (same as Perl)
>>
>> ## Alternative Considered
>>
>> I considered using a nested namespace (e.g., Web::Concierge or
>> User::Concierge), but these feel sub-optimal because:
>>
>> - Web::Concierge suggests it's web-framework specific (it's not)
>>
>> - User::Concierge is too narrow (hierachy seems backwards)
>>
>> - Service::Concierge is less clear and the Service:: namespace is sparse
>>
>> The top-level Concierge namespace best represents a cohesive service
>> platform.
>>
>> ## Additional Information
>>
>> **Repository Location**: Private (will be made public before first release)
>>
>> **First Release**: Concierge v0.1.0 (Placeholder, docs only),
>> Concierge::Sessions v0.7.0, Concierge::Auth v0.18.0, Concierge::Users v0.8.0
>>
>> **Timeline**: Ready to release within 1 week of namespace approval
>>
>> **Tests**: All modules have test suites (using Test2::V0)
>>
>> **Documentation**: Complete POD & comprehensive README.md in all modules
>>
>> **Examples**: Working example scripts included in distribution
>>
>> ## Request
>>
>> I respectfully request permission to register and upload to the Concierge
>> namespace on the CPAN. I believe this module suite will provide value to the
>> Perl community by offering a space for modern, cohesive user management
>> solutions.
>>
>> Thank you for your consideration.
>>
>> — Bruce
>>
>> _bruce__van_allen__santa_cruz_ca_
>>
>
