[Puppet-dev] Re: Euro/London Presence (was: Re: Re: The Future of Puppet [Was: Deprecation logs])

Am 13.04.2016 um 19:04 schrieb Thomas Gelf: > [...] but I have always been (and still am) asked whether there is > available something like a "Best practices training". NB: It didn't matter what kind of Puppet class this was. Something like a "Best practices training&quo

[Puppet-dev] Re: Euro/London Presence (was: Re: Re: The Future of Puppet [Was: Deprecation logs])

Am 13.04.2016 um 17:05 schrieb Rob Nelson: > More of a workshop, than a hackathon? Yes. Kind of a "Getting started hands on workshop". How often have you been asked how to write a module "the right way"? You could use a lot of words explaining many things, or just sit down together and build a con

[Puppet-dev] Re: Euro/London Presence (was: Re: Re: The Future of Puppet [Was: Deprecation logs])

Am 13.04.2016 um 16:15 schrieb Nigel Kersten: > Thomas, it does feel like you're describing a mix between our > Contributor Summit and #puppethack events. Not really, I guess I didn't cleanly distinct my thoughts. It should read: "Hackathons will not work at entry-level-camps, but you could run so

[Puppet-dev] Re: Euro/London Presence (was: Re: Re: The Future of Puppet [Was: Deprecation logs])

Am 13.04.2016 um 02:15 schrieb Nigel Kersten: > On Tue, Apr 12, 2016 at 5:07 PM, Trevor Vaughan > wrote: > This is a tangent, but I would also like to see more advanced > content at the Puppet Camps. > > Would anyone be open to a dual tracked Puppet Camp

[Puppet-dev] Re: The Future of Puppet [Was: Deprecation logs]

Am 11.04.2016 um 03:01 schrieb Rob Nelson: > Of course there's lock in. You can't click a button and go from Puppet > OSS to Chef OSS; [...] > Is their concern about being able to contribute to it or even fork? I > suspect that's what most lock in concerns are really based on. It's about going f

[Puppet-dev] Re: Idea: Deprecation logs

Am 11.04.2016 um 00:47 schrieb James Turnbull: >> One last very important factor to the mentioned frustration is the fact >> that Puppet is an Open Source product. People over here in Europe see >> this stricter than they might in the US. If you say "...and it has an >> Enterprise version", 99% of

[Puppet-dev] Re: Idea: Deprecation logs

Hi Eric! Am 10.04.2016 um 21:16 schrieb Eric Sorenson: > On Apr 10, 2016, at 2:05 AM, Alex Harvey > wrote: > > [...] I've been the product manager for Puppet for the > four years you're talking about and thus bear at least partial > responsibility for the changes in

[Puppet-dev] Re: Idea: Deprecation logs

I feel a little bit guilty, as my short comment somehow started this thread. But as the discussion seems to move to a good direction, let me jump in :) Am 10.04.2016 um 18:51 schrieb R.I.Pienaar: >> I guess what this shows is that even when changes don't appear to be >> user-impacting, they are. [

[Puppet-dev] Re: Puppet RFC 23 - XPP Files

Am 04.04.2016 um 03:21 schrieb Henrik Lindberg: >>> We are happy if we initially only get 5-10% out of this... >> >> And this is where I currently disagree. Very often I invest lots of time >> for just 1%. But being able to run without a fragile caching layer could >> be worth even 50% as long as I

[Puppet-dev] Re: Puppet RFC 23 - XPP Files

Am 01.04.2016 um 20:59 schrieb R.I.Pienaar: > Indeed and if you recall there was a similar outcry when passenger became > the de facto way. The java stack as delivered by PL in PuppetDB and Server is > a LOT more manageable than the passenger stack. I do not agree on this, at least I never had

[Puppet-dev] Re: Puppet RFC 23 - XPP Files

Hi Deepak, great to hear from you. Didn't expect you to join the conversation, but as I offended your baby... sorry for this ;) Am 01.04.2016 um 20:42 schrieb Deepak Giridharagopal: > ... Maybe the thing to do here is to try some experiments and post back > some numbers that could hopefully grou

[Puppet-dev] Re: Puppet RFC 23 - XPP Files

Hi Henrik, thanks a lot for your response! Am 01.04.2016 um 20:21 schrieb Henrik Lindberg: > The C++ implementation is several orders of magnitudes faster than the > ruby implementation. i.e. something silly like tens of thousands of > times faster. No doubt on this, I believe you without any be

[Puppet-dev] Re: Puppet RFC 23 - XPP Files

Hi Eric, your dedication in getting Puppet faster is really appreciated. My post is absolutely not in favor of XPP, but please don't get me wrong: it is meant to be a constructive contribution to the current design process. In my personal opinion we have a sad history of optimizations focusing a

[Puppet-dev] Re: Idea: Deprecation logs

Hi Rob, nice proposal, would definitively help people to deal with the stated problem. Another approach could be to break and deprecate less things. Sure, I'm just kidding ;-) I love moving things forward. But you know, there's a grain of truth in every joke. We should not forget about the fact