I had no awareness of the office hours (which is probably also my fault), but that sounds like a great idea.
I struggle with the same problem in Buildbot: how do I keep people informed and solicit meaningful feedback without overwhelming them? One, perhaps unorthodox, technique is something you're already doing - publicly thank and recognize community members for their contributions and commitment. That creates a virtuous cycle of higher expectations. It's certainly a part of why I feel culpable for not reading ARMs! Other efforts to engage people with the new ideas may help, as well. The ARMs are pretty deeply technical documents, so perhaps these hangouts or office hours can be a place for users to start with a quick summary of the ARM, and then drill down into potential concerns. Luke: the bug about parameterized classes was just the thing that prodded me to the action of sending this email (I originally typed it in Redmine, but it was *way* off-topic!). So let's keep talk of that specific issue in redmine. Your suggestion (errors now, lazy evaluation later) sounds perfectly reasonable. Dustin -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
