Fwd: Namespace Request: Concierge
[email protected] (Bruce Van Allen) Mon, 9 Feb 2026 12:21:08 -0800
| Newsgroups | perl.module-authors |
|---|---|
| Message-ID | <[email protected]> |
--Apple-Mail=_F0D5160D-2D5B-4E85-908B-C5BA2AD0F08A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 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, =E2=80=94 Bruce _bruce__van_allen__santa_cruz_ca_ > Begin forwarded message: >=20 > From: Bruce Van Allen <[email protected]> > Subject: Fwd: Namespace Request: Concierge > Date: February 9, 2026 at 11:31:59=E2=80=AFAM PST > To: Neil Bowers <[email protected]> > Cc: [email protected], [email protected] >=20 > Hi Neil, >=20 > Thanks for your response. >=20 > Yes, my intention is to keep 'Concierge' as the top level, and the = docs will expressly emphasize that added modules should stay under that.=20= >=20 > I am CC:ing this to the module authors list for suggestions|comments. = I am eager, but I want to get this right. >=20 > Thanks, and much appreciation for your contributions to the Perl = world! >=20 > =E2=80=94 Bruce >=20 > _bruce__van_allen__santa_cruz_ca_ >=20 >=20 > =E2=80=94 Bruce >=20 > _bruce__van_allen__santa_cruz_ca_ >=20 >> Begin forwarded message: >>=20 >> From: Neil Bowers <[email protected]> >> Subject: Re: Namespace Request: Concierge >> Date: February 9, 2026 at 7:37:12=E2=80=AFAM PST >> To: Bruce Van Allen <[email protected]>, [email protected] >>=20 >> Hi Bruce, >> =20 >> I am requesting permission to use the top-level "Concierge" namespace = for a new Perl distribution focused on user management services for = applications [...] >> =20 >> I don't see any problem with this. >> =20 >> 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. >> =20 >> 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 ;-) >> =20 >> Cheers, >> Neil >> =20 >=20 >=20 >=20 >> Begin forwarded message: >>=20 >> From: Bruce Van Allen <[email protected]> >> Subject: Namespace Request: Concierge >> Date: January 21, 2026 at 12:34:27=E2=80=AFAM PST >> To: [email protected] >>=20 >> PAUSE maintainers, >>=20 >> I am requesting permission to use the top-level "Concierge" namespace = for a new Perl distribution focused on user management services for = applications. >>=20 >> ## Namespace Request >>=20 >> **Proposed Namespace:** Concierge=20 >>=20 >> **Module Prefixes:**=20 >> - Concierge (platform composition)=20 >> - Concierge::Auth (authentication services)=20 >> - Concierge::Users (user data management) >> - Concierge::Sessions (session management)=20 >>=20 >> ## Description >>=20 >> Concierge is an integrated user management service platform for = applications. It provides a cohesive suite of modules that work = separately or together to offer: >>=20 >> 1. **Authentication Services** (Concierge::Auth) - AVAILABLE NOW >>=20 >> 2. **User Data Management** (Concierge::Users) - AVAILABLE NOW >>=20 >> 3. **Session Management** (Concierge::Sessions) - AVAILABLE NOW >>=20 >> 4. **Unified Service Composer** (Concierge) - FUTURE=20 >> - Suite module affordances composed as specified by the application=20= >> - Single API for complete user management=20 >> - Enables Plug-in replacements for suite modules=20 >> - Auth, Users, and Sessions modules still work separately >>=20 >> ## Justification for Top-Level Namespace >>=20 >> I am requesting a top-level namespace rather than nesting under a = category because: >>=20 >> 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. >>=20 >> 2. **Distinctive Branding**: "Concierge" clearly conveys the purpose = (service-oriented user management) and is memorable. >>=20 >> 3. **Service Platform**: This is a service-oriented platform meant = for composing multiple distinct services (Auth, Users, Sessions) into a = unified but customizable whole. >>=20 >> 4. **Standalone Components**: Each Concierge::* module can be used = independently or as part of the integrated platform. >>=20 >> 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. >>=20 >> ## Current Status >>=20 >> - **Concierge::Sessions** is complete and ready for CPAN release >>=20 >> - **Concierge::Auth is complete**, final documentation being prepared >>=20 >> - **Concierge::Users** is complete, final documentation being = prepared >>=20 >> - **Concierge** is under active development, full API not final >>=20 >> ## Distribution Details >>=20 >> - **Author**: Bruce Van Allen ([email protected])=20 >> - **Perl Version Required**: 5.36+=20 >> - **Dependencies**: DBI, DBD::SQLite, JSON::PP (all core/common)=20 >> - **Testing**: Test2::V0=20 >> - **License**: Artistic License 2.0 (same as Perl) >>=20 >> ## Alternative Considered >>=20 >> I considered using a nested namespace (e.g., Web::Concierge or = User::Concierge), but these feel sub-optimal because: >>=20 >> - Web::Concierge suggests it's web-framework specific (it's not)=20 >>=20 >> - User::Concierge is too narrow (hierachy seems backwards)=20 >>=20 >> - Service::Concierge is less clear and the Service:: namespace is = sparse >>=20 >> The top-level Concierge namespace best represents a cohesive service = platform. >>=20 >> ## Additional Information >>=20 >> **Repository Location**: Private (will be made public before first = release)=20 >>=20 >> **First Release**: Concierge v0.1.0 (Placeholder, docs only), = Concierge::Sessions v0.7.0, Concierge::Auth v0.18.0, Concierge::Users = v0.8.0=20 >>=20 >> **Timeline**: Ready to release within 1 week of namespace approval=20 >>=20 >> **Tests**: All modules have test suites (using Test2::V0)=20 >>=20 >> **Documentation**: Complete POD & comprehensive README.md in all = modules=20 >>=20 >> **Examples**: Working example scripts included in distribution >>=20 >> ## Request >>=20 >> 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. >>=20 >> Thank you for your consideration. >>=20 >> =E2=80=94 Bruce >>=20 >> _bruce__van_allen__santa_cruz_ca_ >>=20 >=20 --Apple-Mail=_F0D5160D-2D5B-4E85-908B-C5BA2AD0F08A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html aria-label=3D"message body"><head><meta http-equiv=3D"content-type" = content=3D"text/html; charset=3Dutf-8"></head><body = style=3D"overflow-wrap: break-word; -webkit-nbsp-mode: space; = line-break: after-white-space;">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 [email protected], 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=3D"lineBreakAtBeginningOfMessage"><div> <meta charset=3D"UTF-8"> =E2=80=94 = Bruce<br><br>_bruce__van_allen__santa_cruz_ca_<br><br> </div> <div><br><blockquote type=3D"cite"><div>Begin forwarded = message:</div><br class=3D"Apple-interchange-newline"><div = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px;"><span style=3D"font-family: -webkit-system-font, = Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, = 1.0);"><b>From: </b></span><span style=3D"font-family: = -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;">Bruce Van = Allen <[email protected]><br></span></div><div style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span = style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, = sans-serif; color:rgba(0, 0, 0, 1.0);"><b>Subject: </b></span><span = style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, = sans-serif;"><b>Fwd: Namespace Request: = Concierge</b><br></span></div><div style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span = style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, = sans-serif; color:rgba(0, 0, 0, 1.0);"><b>Date: </b></span><span = style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, = sans-serif;">February 9, 2026 at 11:31:59=E2=80=AFAM = PST<br></span></div><div style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px;"><span style=3D"font-family: = -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; = color:rgba(0, 0, 0, 1.0);"><b>To: </b></span><span style=3D"font-family: = -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;">Neil Bowers = <[email protected]><br></span></div><div style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span = style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, = sans-serif; color:rgba(0, 0, 0, 1.0);"><b>Cc: </b></span><span = style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, = sans-serif;">[email protected], = [email protected]<br></span></div><br><div><meta = http-equiv=3D"content-type" content=3D"text/html; charset=3Dutf-8"><div = style=3D"overflow-wrap: break-word; -webkit-nbsp-mode: space; = line-break: after-white-space;"><span style=3D"font-family: = Menlo-Regular, monospace;">Hi Neil,</span><div style=3D"font-family: = Menlo-Regular, monospace;"><br></div><div style=3D"font-family: = Menlo-Regular, monospace;">Thanks for your response.</div><div = style=3D"font-family: Menlo-Regular, monospace;"><br></div><div = style=3D"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=3D"font-family: Menlo-Regular, monospace;"><br></div><div = style=3D"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=3D"font-family: Menlo-Regular, = monospace;"><br></div><div style=3D"font-family: Menlo-Regular, = monospace;">Thanks, and much appreciation for your contributions to the = Perl world!</div><div style=3D"font-family: Menlo-Regular, = monospace;"><br = id=3D"lineBreakAtBeginningOfMessage"><div> =E2=80=94= Bruce<br><br>_bruce__van_allen__santa_cruz_ca_<br><br></div></div><br = class=3D"Apple-interchange-newline"><div> <meta charset=3D"UTF-8"> =E2=80=94 = Bruce<br><br>_bruce__van_allen__santa_cruz_ca_</div><div><br></div><div><b= lockquote type=3D"cite" style=3D""><div>Begin forwarded = message:</div><br class=3D"Apple-interchange-newline"><div = style=3D"margin: 0px;"><span style=3D"font-family: -webkit-system-font, = "Helvetica Neue", Helvetica, = sans-serif;"><b>From: </b></span><span style=3D"font-family: = -webkit-system-font, "Helvetica Neue", Helvetica, = sans-serif;">Neil Bowers <[email protected]><br></span></div><div = style=3D"margin: 0px;"><span style=3D"font-family: -webkit-system-font, = "Helvetica Neue", Helvetica, = sans-serif;"><b>Subject: </b></span><span style=3D"font-family: = -webkit-system-font, "Helvetica Neue", Helvetica, = sans-serif;"><b>Re: Namespace Request: = Concierge</b><br></span></div><div style=3D"margin: 0px;"><span = style=3D"font-family: -webkit-system-font, "Helvetica Neue", = Helvetica, sans-serif;"><b>Date: </b></span><span = style=3D"font-family: -webkit-system-font, "Helvetica Neue", = Helvetica, sans-serif;">February 9, 2026 at 7:37:12=E2=80=AFAM = PST<br></span></div><div style=3D"margin: 0px;"><span = style=3D"font-family: -webkit-system-font, "Helvetica Neue", = Helvetica, sans-serif;"><b>To: </b></span><span style=3D"font-family:= -webkit-system-font, "Helvetica Neue", Helvetica, = sans-serif;">Bruce Van Allen <[email protected]>, = [email protected]<br></span></div><br><div><div = name=3D"messageBodySection"><div>Hi = Bruce,</div><div> </div><blockquote style=3D"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=3D"Apple-interchange-newline"><br> </div> <div><br><blockquote type=3D"cite"><div>Begin forwarded = message:</div><br class=3D"Apple-interchange-newline"><div = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px;"><span style=3D"font-family: -webkit-system-font, = "Helvetica Neue", Helvetica, sans-serif;"><b>From: = </b></span><span style=3D"font-family: -webkit-system-font, Helvetica = Neue, Helvetica, sans-serif;">Bruce Van Allen = <[email protected]><br></span></div><div style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span = style=3D"font-family: -webkit-system-font, "Helvetica Neue", = Helvetica, sans-serif;"><b>Subject: </b></span><span style=3D"font-family:= -webkit-system-font, Helvetica Neue, Helvetica, = sans-serif;"><b>Namespace Request: Concierge</b><br></span></div><div = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px;"><span style=3D"font-family: -webkit-system-font, = "Helvetica Neue", Helvetica, sans-serif;"><b>Date: = </b></span><span style=3D"font-family: -webkit-system-font, Helvetica = Neue, Helvetica, sans-serif;">January 21, 2026 at 12:34:27=E2=80=AFAM = PST<br></span></div><div style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px;"><span style=3D"font-family: = -webkit-system-font, "Helvetica Neue", Helvetica, = sans-serif;"><b>To: </b></span><span style=3D"font-family: = -webkit-system-font, Helvetica Neue, Helvetica, = sans-serif;">[email protected]<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 ([email protected]) <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>=E2=80=94 = Bruce<br><br>_bruce__van_allen__santa_cruz_ca_<br><br></div></div></blockq= uote></div><br></div></div></blockquote></div><br></div></body></html>= --Apple-Mail=_F0D5160D-2D5B-4E85-908B-C5BA2AD0F08A--