Hi,

I have read the "On The Naming of Modules" page 
(https://pause.perl.org/pause/authenquery?ACTION=pause_namingmodules), and 
agree that:

"top level namespaces are bad, unless they are a nexus for several modules 
under that namespace or they are a fanciful name that describes something more 
application oriented"

My project (https://github.com/lucastheisen/footprintless), I think, meets the 
"fanciful name that describes something more application oriented" requirement. 
 At its core, it is


*         A framework for automation related tasks

*         An automation agent for managing systems both local and remote using 
tools generally available on the systems

*         A configuration management system

Would it still be rude to request the namespace "Footprintless"?

Thank You,
Lucas Theisen
[email protected]

Reply via email to