Re: Fwd: Namespace Request: Concierge
[email protected] (Guido Brugnara via module-authors) Tue, 10 Feb 2026 07:28:09 +0100
| Newsgroups | perl.module-authors |
|---|---|
| Message-ID | <[email protected]> |
--------------0jayzc8dID0HC0GOvRqksBZY Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi, I am not a CPAN veteran, but as a student, many times ago, I worked as a “Concierge” at night and shared the role of supervisor/mediator between users and hotel services. In your case, “Concierge” identifies a specific application, as there are many others in CPAN. Top-level names are not just generic, and I don't know any generic names for frameworks or applications. Furthermore, the new name is not generic or misleading in relation to existing ICT technologies (or at least I have not found any). As someone who is inexperienced with CPAN, looking at the names used previously, I also find your proposal too appropriate. Goodluckwithyourwork. Guido Brugnara Il 09/02/26 21:21, Bruce Van Allen ha scritto: > 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_ >>> >> > --------------0jayzc8dID0HC0GOvRqksBZY Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit <!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <p>Hi,<br> I am not a CPAN veteran, but as a student, many times ago, I worked as a “Concierge” at night and shared the role of supervisor/mediator between users and hotel services.<br> In your case, “Concierge” identifies a specific application, as there are many others in CPAN. Top-level names are not just generic, and I don't know any generic names for frameworks or applications.<br> Furthermore, the new name is not generic or misleading in relation to existing ICT technologies (or at least I have not found any).<br> As someone who is inexperienced with CPAN, looking at the names used previously, I also find your proposal too appropriate. <br> <br> </p> <p _d-id="120271"><span _d-id="120459" class="--l --r hover:bg-blue-100 hover:dark:bg-blue-600"><span _d-id="120568" class="container-target"><span _d-id="120666" class="bg-blue-50 dark:bg-blue-500 text-unit-target">Good</span></span></span><span _d-id="120569" class="container-target"><span _d-id="120667" class="bg-blue-50 dark:bg-blue-500 text-unit-target"> </span></span><span _d-id="120463" class="--l --r hover:bg-blue-100 hover:dark:bg-blue-600"><span _d-id="120570" class="container-target"><span _d-id="120668" class="bg-blue-50 dark:bg-blue-500 text-unit-target">luck</span></span></span><span _d-id="120571" class="container-target"><span _d-id="120669" class="bg-blue-50 dark:bg-blue-500 text-unit-target"> </span></span><span _d-id="120467" class="--l --r hover:bg-blue-100 hover:dark:bg-blue-600"><span _d-id="120572" class="container-target"><span _d-id="120670" class="bg-blue-50 dark:bg-blue-500 text-unit-target">with</span></span></span><span _d-id="120573" class="container-target"><span _d-id="120671" class="bg-blue-50 dark:bg-blue-500 text-unit-target"> </span></span><span _d-id="120471" class="--l --r hover:bg-blue-100 hover:dark:bg-blue-600"><span _d-id="120574" class="container-target"><span _d-id="120672" class="bg-blue-50 dark:bg-blue-500 text-unit-target">your</span></span></span><span _d-id="120575" class="container-target"><span _d-id="120673" class="bg-blue-50 dark:bg-blue-500 text-unit-target"> </span></span><span _d-id="120475" class="--l --r hover:bg-blue-100 hover:dark:bg-blue-600"><span _d-id="120576" class="container-target"><span _d-id="120674" class="bg-blue-50 dark:bg-blue-500 text-unit-target">work</span></span></span><span _d-id="120577" class="--r container-target"><span _d-id="120675" class="--r bg-blue-50 dark:bg-blue-500 text-unit-target">.<br> Guido Brugnara</span></span></p> <p><br> <br> </p> <div class="moz-cite-prefix">Il 09/02/26 21:21, Bruce Van Allen ha scritto:<br> </div> <blockquote type="cite" cite="mid:[email protected]"> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> Hi Friends, <div><br> </div> <div>I am new to this list. I have proposed a top-level namespace at the CPAN, as described below. I sent my request to <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a>, and Neil B suggested I might check for feedback on this list.</div> <div><br> </div> <div>Anything appreciated!</div> <div><br> </div> <div>Thanks,</div> <div><br id="lineBreakAtBeginningOfMessage"> <div> <meta charset="UTF-8"> — Bruce<br> <br> _bruce__van_allen__santa_cruz_ca_<br> <br> </div> <div><br> <blockquote type="cite"> <div>Begin forwarded message:</div> <br class="Apple-interchange-newline"> <div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);"><b>From: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;">Bruce Van Allen <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a><br> </span></div> <div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);"><b>Subject: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;"><b>Fwd: Namespace Request: Concierge</b><br> </span></div> <div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);"><b>Date: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;">February 9, 2026 at 11:31:59 AM PST<br> </span></div> <div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);"><b>To: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;">Neil Bowers <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a><br> </span></div> <div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);"><b>Cc: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;"><a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a>, <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a><br> </span></div> <br> <div> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> <div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><span style="font-family: Menlo-Regular, monospace;">Hi Neil,</span> <div style="font-family: Menlo-Regular, monospace;"><br> </div> <div style="font-family: Menlo-Regular, monospace;">Thanks for your response.</div> <div style="font-family: Menlo-Regular, monospace;"><br> </div> <div style="font-family: Menlo-Regular, monospace;">Yes, my intention is to keep 'Concierge' as the top level, and the docs will expressly emphasize that added modules should stay under that. </div> <div style="font-family: Menlo-Regular, monospace;"><br> </div> <div style="font-family: Menlo-Regular, monospace;">I am CC:ing this to the module authors list for suggestions|comments. I am eager, but I want to get this right.</div> <div style="font-family: Menlo-Regular, monospace;"><br> </div> <div style="font-family: Menlo-Regular, monospace;">Thanks, and much appreciation for your contributions to the Perl world!</div> <div style="font-family: Menlo-Regular, monospace;"><br id="lineBreakAtBeginningOfMessage"> <div> — Bruce<br> <br> _bruce__van_allen__santa_cruz_ca_<br> <br> </div> </div> <br class="Apple-interchange-newline"> <div> <meta charset="UTF-8"> — Bruce<br> <br> _bruce__van_allen__santa_cruz_ca_</div> <div><br> </div> <div> <blockquote type="cite" style=""> <div>Begin forwarded message:</div> <br class="Apple-interchange-newline"> <div style="margin: 0px;"><span style="font-family: -webkit-system-font, "Helvetica Neue", Helvetica, sans-serif;"><b>From: </b></span><span style="font-family: -webkit-system-font, "Helvetica Neue", Helvetica, sans-serif;">Neil Bowers <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a><br> </span></div> <div style="margin: 0px;"><span style="font-family: -webkit-system-font, "Helvetica Neue", Helvetica, sans-serif;"><b>Subject: </b></span><span style="font-family: -webkit-system-font, "Helvetica Neue", Helvetica, sans-serif;"><b>Re: Namespace Request: Concierge</b><br> </span></div> <div style="margin: 0px;"><span style="font-family: -webkit-system-font, "Helvetica Neue", Helvetica, sans-serif;"><b>Date: </b></span><span style="font-family: -webkit-system-font, "Helvetica Neue", Helvetica, sans-serif;">February 9, 2026 at 7:37:12 AM PST<br> </span></div> <div style="margin: 0px;"><span style="font-family: -webkit-system-font, "Helvetica Neue", Helvetica, sans-serif;"><b>To: </b></span><span style="font-family: -webkit-system-font, "Helvetica Neue", Helvetica, sans-serif;">Bruce Van Allen <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a>, <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a><br> </span></div> <br> <div> <div name="messageBodySection"> <div>Hi Bruce,</div> <div> </div> <blockquote style="margin: 5px; padding-left: 10px; border-left-width: thin; border-left-style: solid; border-left-color: rgb(26, 188, 156);">I am requesting permission to use the top-level "Concierge" namespace for a new Perl distribution focused on user management services for applications [...]</blockquote> <div> </div> <div>I don't see any problem with this.</div> <div> </div> <div>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.</div> <div> </div> <div>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 ;-)</div> <div> </div> <div>Cheers,<br> Neil</div> <div> </div> </div> </div> </blockquote> <br class="Apple-interchange-newline"> <br> </div> <div><br> <blockquote type="cite"> <div>Begin forwarded message:</div> <br class="Apple-interchange-newline"> <div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family: -webkit-system-font, "Helvetica Neue", Helvetica, sans-serif;"><b>From: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;">Bruce Van Allen <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a><br> </span></div> <div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family: -webkit-system-font, "Helvetica Neue", Helvetica, sans-serif;"><b>Subject: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;"><b>Namespace Request: Concierge</b><br> </span></div> <div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family: -webkit-system-font, "Helvetica Neue", Helvetica, sans-serif;"><b>Date: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;">January 21, 2026 at 12:34:27 AM PST<br> </span></div> <div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family: -webkit-system-font, "Helvetica Neue", Helvetica, sans-serif;"><b>To: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;"><a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a><br> </span></div> <br> <div> <div>PAUSE maintainers,<br> <br> I am requesting permission to use the top-level "Concierge" namespace for a new Perl distribution focused on user management services for applications.<br> <br> ## Namespace Request<br> <br> **Proposed Namespace:** Concierge <br> <br> **Module Prefixes:** <br> - Concierge (platform composition) <br> - Concierge::Auth (authentication services) <br> - Concierge::Users (user data management)<br> - Concierge::Sessions (session management) <br> <br> ## Description<br> <br> Concierge is an integrated user management service platform for applications. It provides a cohesive suite of modules that work separately or together to offer:<br> <br> 1. **Authentication Services** (Concierge::Auth) - AVAILABLE NOW<br> <br> 2. **User Data Management** (Concierge::Users) - AVAILABLE NOW<br> <br> 3. **Session Management** (Concierge::Sessions) - AVAILABLE NOW<br> <br> 4. **Unified Service Composer** (Concierge) - FUTURE <br> - Suite module affordances composed as specified by the application <br> - Single API for complete user management <br> - Enables Plug-in replacements for suite modules <br> - Auth, Users, and Sessions modules still work separately<br> <br> ## Justification for Top-Level Namespace<br> <br> I am requesting a top-level namespace rather than nesting under a category because:<br> <br> 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.<br> <br> 2. **Distinctive Branding**: "Concierge" clearly conveys the purpose (service-oriented user management) and is memorable.<br> <br> 3. **Service Platform**: This is a service-oriented platform meant for composing multiple distinct services (Auth, Users, Sessions) into a unified but customizable whole.<br> <br> 4. **Standalone Components**: Each Concierge::* module can be used independently or as part of the integrated platform.<br> <br> 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.<br> <br> ## Current Status<br> <br> - **Concierge::Sessions** is complete and ready for CPAN release<br> <br> - **Concierge::Auth is complete**, final documentation being prepared<br> <br> - **Concierge::Users** is complete, final documentation being prepared<br> <br> - **Concierge** is under active development, full API not final<br> <br> ## Distribution Details<br> <br> - **Author**: Bruce Van Allen (<a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a>) <br> - **Perl Version Required**: 5.36+ <br> - **Dependencies**: DBI, DBD::SQLite, JSON::PP (all core/common) <br> - **Testing**: Test2::V0 <br> - **License**: Artistic License 2.0 (same as Perl)<br> <br> ## Alternative Considered<br> <br> I considered using a nested namespace (e.g., Web::Concierge or User::Concierge), but these feel sub-optimal because:<br> <br> - Web::Concierge suggests it's web-framework specific (it's not) <br> <br> - User::Concierge is too narrow (hierachy seems backwards) <br> <br> - Service::Concierge is less clear and the Service:: namespace is sparse<br> <br> The top-level Concierge namespace best represents a cohesive service platform.<br> <br> ## Additional Information<br> <br> **Repository Location**: Private (will be made public before first release) <br> <br> **First Release**: Concierge v0.1.0 (Placeholder, docs only), Concierge::Sessions v0.7.0, Concierge::Auth v0.18.0, Concierge::Users v0.8.0 <br> <br> **Timeline**: Ready to release within 1 week of namespace approval <br> <br> **Tests**: All modules have test suites (using Test2::V0) <br> <br> **Documentation**: Complete POD & comprehensive README.md in all modules <br> <br> **Examples**: Working example scripts included in distribution<br> <br> ## Request<br> <br> 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.<br> <br> Thank you for your consideration.<br> <br> — Bruce<br> <br> _bruce__van_allen__santa_cruz_ca_<br> <br> </div> </div> </blockquote> </div> <br> </div> </div> </blockquote> </div> <br> </div> </blockquote> </body> </html> --------------0jayzc8dID0HC0GOvRqksBZY--