Hi there, I'd like to collect some feedback on a conceptual simple Puppet Common Module I want to propose;
http://reductivelabs.com/trac/puppet/wiki/PuppetCommonModules/SSH I'm thinking about things like; - the way virtual resources are used, - the way operating system specific sub-classes are used, - use-cases I haven't met (although secondary), - simple errors I've made (I whipped this up from the top of my head), although the best thing is maybe to jump on the Wiki and correct my error, - further enhancements in making this a really viable PCM. I guess what is not needed (yet) includes (I'm sorry if this sound harsh); - discussions about the indentation I used I can live with any form of indentation, and I guess so can you. I *just so happen* to use 4 spaces to a tab. - the way I aggregate types into resources It to me is a habit / matter of convenience, while I'd like to focus the discussion on technical arguments instead. - namespacing of modules or classes again I can live with *any* namespacing, and it's not about setting the defacto standard for all Puppet Common Modules, it's about making a *start* in "code". - module or class extensions that everyone uses because these often-used extensions should go *in* the module (upstream, upstream, upstream is my motto), and such can only be done when there is an upstream module to begin with. Thanks in advance for review/comments, Kind regards, Jeroen van Meeuwen -kanarip --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
