Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Lucy CPAN distribution.

Report information
The Basics
Id: 68639
Status: resolved
Priority: 0/
Queue: Lucy

People
Owner: Nobody in particular
Requestors: anonymous [...] anonymitaet-im-inter.net
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Please consider Search::Lucy
Date: Fri, 3 Jun 2011 22:39:33 +0200 (CEST)
To: bug-Lucy [...] rt.cpan.org
From: Dave U. Random <anonymous [...] anonymitaet-im-inter.net>
Please consider renaming Lucy to Search::Lucy. Most of the other search engine interfaces are in the Search:: namespace. Besides existing convention, it's recommended in the naming policy to avoid top-level namespaces if possible: http://pause.perl.org/pause/query?ACTION=pause_namingmodules
Thanks for the suggestion. I'm aware of the Search:: namespace. Of the 35 modules in that namespace today, I authored and maintain 8 of them. Guess that makes me responsible for only a quarter of the namespace. I've got to get cracking if my plan for universal domination is to succeed! Lucy is the follow-on to KinoSearch, which also occupies a top-level namespace. While it's recommended to avoid top-level namespaces, it's also noted in that same naming doc that Big Projects "organize the activity under their namespace to ensure everything works together nicely." Lucy has over 180 classes. By comparison, Catalyst-Runtime has 46. How do you measure "big"? Likewise, comparable projects on CPAN like "Lucene" and "Sphinx::Search" also occupy their own top-level namespaces. So Lucy is not exactly breaking ground here. Search::Lucy might make it easier to find; maybe we'll add a stub file. Again, thanks for taking the time to recommend a name change. Lucy's been registered for several years and we're excited to finally have a release to occupy the space.