Rather than reply and quote lots of points, I'll just bring up a few things which could help clarify our goals. I'm sure not everybody will agree or love all of them, we know there are compromises here but attempted to make choices with the user's benefit and ease of use in mind.
* The package is called puppet-agent because Puppet is more than the tool puppet at this point. It's an ecosystem. It's a suite of tools working together to manage infrastructure and applications. The agent is the word that means "all the stuff you need to run an endpoint in this ecosystem." * We wanted to get away from our users having to carry the cognitive load of understanding each component we have, what it does and what versions work well together or have conflicts, what dependencies are required, and where do I get those? * The bits inside the agent should be able to be more of a single user experience. A key message for this point was when the head of technical docs said "Nobody wakes up in the morning and says 'I want to hiera today'". We want the user experience to be easy to manage and work with. That doesn't mean that if somebody wants to get into the bits/packages/projects/source they shouldn't be able to -- we just don't want that to be a requirement. * Version numbers - they are hard. We restarted at 1.0 because it was a new thing. Eric and I were talking yesterday and maybe it would have made more sense to put it at 4; however because of the argument that he made earlier in the thread, there are cases where that could create other types of confusion. * Somewhere in the thread somebody asked about Puppet's new filesystem layout and if things would work in another location. I've seen Fedora already pick up the puppet 4 source and package it right up for their distro, so I think that's working. [1] * The packaging toolchain will be opened up. We're not quite there yet because there are some hard-coded assumptions that need to be abstracted away. We also need some documentation and examples -- otherwise that's going to be a difficult climb. * I'm not sure if introducing Collections and the AIO and Puppet 4 all at the same time helped with cognitive load. I'm sorry if that hasn't worked out. Collections from a user's perspective are mostly a package repo. The AIO is the end point. Puppet 4 is a subcomponent of that, which can be a bit confusing. We'll be working on our messaging, tooling and way we talk about this to make the largest amount of people happy. I do welcome questions and criticism here. We do like to hear opinions and options. I certainly can't promise we'll act on every complaint or suggestion, but I'm sure the criticisms are valid. [1] http://koji.fedoraproject.org/koji/buildinfo?buildID=631538 -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users/CAMto7LLwJg4GOmmEkgys74-2FdKxvSapL4QOJJV%2BN1E%3DZbQEtA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
