----- Original Message ----- > From: "Randall Hansen" <rand...@puppetlabs.com> > To: puppet-dev@googlegroups.com > Sent: Wednesday, April 18, 2012 4:41:57 PM > Subject: Re: [Puppet-dev] Changes to variable scoping in Telly > > On Wed, Apr 18, 2012 at 12:18 AM, Ken Barber <k...@puppetlabs.com> > wrote: > > > I would prefer to see a high-level specification of where we want > > to > > be in a year, two years ... let it be nutted out in > > workshops/discussions ... and then develop against it. Maybe I'm > > wrong, and others feel they do have a high enough perspective of > > how > > it should _all_ ultimately fit together - just expressing my 2p/2c. > > Ken, I think you've described the problem exactly: the Puppet > language needs curation. That doesn't mean a single person to make > all the decisions, but it does mean one person to find the worst pain > points, the best ideas, the most pressing needs, and drive us as a > company and community towards the future. > > When I started a year ago I was hoping to do this myself. I've not > devoted the time that it deserves. A month ago I got out of denial > and asked Pieter van de Bruggen to curate the DSL. He's held two > design reviews internally and is currently gathering information from > any source he can get to sit still for a few minutes. > > Very soon I expect him to start talking about it more in public. > We've not done this sort of thing before so it's going to be a little > messy to begin with, but I believe it's the right path.
This is kind of what I attempt to do with these kinds of comments I sent to this thread - throw in the bigger picture and larger direction I think we should take or point out where the design of the language is falling short or leading users down the incorrect path. Puppet is pretty frustrating, without years of using it its just really hard to grasp some of the problems people have with the language. A suggestion or statement about what is "never needed" is often incorrect coming from someone who studies the language design from an academic perspective. Puppet is more about the act of managing servers than the act of writing code. You cannot evaluate the language solely from the point of writing code (or managing servers). So we need to be sure when we do set up a group of people curating the language - I believe Nigel has tried before fwiw - that this reality is considered. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to puppet-dev@googlegroups.com. To unsubscribe from this group, send email to puppet-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
