An update on the works. There's a github organization where discussion and code can be provided in a more "neutral" way: https://github.com/stdmod
The contents of the Good docs have been collected and moved to https://github.com/stdmod/puppet-modules Here you can see a list of possible naming standards for different cases: https://github.com/stdmod/puppet-modules/blob/master/Parameters_List.md Incidentally I'd like to add / include there this suggestion from John (on another thread) as it makes sense and doesn't forse specific modules structures: << For example, in a class ntp::service, I would certainly choose the parameter name "ensure" over "service_ensure" >> Some sample POC modules have been made in order to test and see how these naming convention actually work: https://github.com/stdmod/puppet-openssh https://github.com/stdmod/puppet-elasticsearch the latter, in particular, even if not complete, I think is a good example of the reusability and interoperability options that these naming standard suggest. al On Monday, June 17, 2013 11:37:50 AM UTC+2, Alessandro Franceschi wrote: > > Dear all, > I'd like to submit to the list's attention this post about Puppet Modules > Standard naming conventions: > http://www.example42.com/?q=The_handy_Grail_of_Modules_Standards > > and this working draft of a proposal for a version 0.0.1 of them: > > https://docs.google.com/document/d/1D4OqEI5iuGJe63ODU91N6rnFKcxVAg1sAWbaQrGBlWA/edit?usp=sharing > > The topic is not new, and on this list there have already been various > discussions on how to manage modules' interoperability ( for example this > interesting one on cross-modules dependencies: > https://groups.google.com/forum/?fromgroups#!searchin/puppet-users/modules$20standards|sort:date/puppet-users/Fvl0aOe4RPE) > > . > > Along with the current discussions on the topic and the Puppet evolution, > I think that few simple *suggested* naming conventions on common parameters > for classes and defines would benefit a lot the module's ecosystem with a > small effort. > > I hope the discussion will have a real follow up, this time, and possibly > move under the more authoritative PuppetLabs umbrella, for the moment is > just a personal proposal, even if shared, at least in the intentions, with > many modules' authors and Puppetteers. > > You can actively contribute to the proposed naming standards on the above > Google document (let me know your gmail account) and you are invited to > comment here what do you think of this (not new) idea: if you think that > starting from simple naming convention is a step to be done, what's your > general idea on the proposed naming standards, if you have better ideas on > naming and approach. > > Let's grab this handy Grail :-) > Alessandro Franceschi > Example42 > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
