On 01/16/2014 01:01 AM, James Turnbull wrote: > I think this is a broadly good idea but I've got one concern about the > on ramp to using Puppet. Whatever is done, pull out some/pull out all, > the user experience of getting started with Puppet should remain > seamless or at least as good as it is now. For example, if there's > suddenly another step to get started with Puppet, i.e.: > > 1. Install Puppet. > 2. Add resources. > 3. See Puppet in action. > > Then I think the getting started user experience suffers. Especially > with so many tutorials out there that just assume various resources will > be available. If the user gets some esoteric error (Dog forbid Puppet > having an esoteric error :)) when they try to run a local .pp file or do > a puppet resource then that's a big turn-off. > > Puppet's learning curve can be steep for many users. Let's not make it > any harder.
I feel that this is a very valid point. As Pawel pointed out, this can be approached with package dependencies. Would it make sense to take this a step further and rename the remainder of puppet to puppet-core and supplement it with, say, puppet-core-modules? Puppet proper would comprise both. Just a thought. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/52DAB7D0.2070206%40Alumni.TU-Berlin.de. For more options, visit https://groups.google.com/groups/opt_out.
