Hi > In general, I find what's most missing from documentation these days > is the explanation of the philosophical underpinnings of a design -- > to me, that's the "how do the developers think about this?" question, > and that's what I most need to have explained to me to start making > sense of something. And the documentation tends to start at the > bottom, with cookbook explanations of how to do a few things, and no > explanations of how things relate. > > Very frequently, it makes *perfect* sense if I can just figure out > what position I need to get my mind into first!
most parts of the documentation are public editable wikis, so feel free to add content. greets pete --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
