Re: [Puppet-dev] Re: Replacement for puppet doc

On Aug 12, 2014 1:00 PM, "Daniele Sluijters" wrote: > > Please don't use `dox`. It's like a teenager who wasn't taught enough English in school, or simply doesn't care, to know that the accepted plural of doc is docs, not dox, dawg. I have to agree, if for a different reason -- "dox" has taken on

Re: [Puppet-dev] Re: Decision: Near future of resource expressions

> On Aug 12, 2014, at 3:51 PM, Henrik Lindberg > wrote: > >> On 2014-12-08 19:47, Luke Kanies wrote: >> On Aug 5, 2014, at 6:41 PM, Reid Vandewiele > > wrote: >> >>> Visual review, for convenience: >>> >>> file { $title: * => $attributes; } >>> file { $title: => $attri

Re: [Puppet-dev] Re: Syntax of resource expressions (was: Decision: Near future of resource expressions)

> On Aug 12, 2014, at 3:07 PM, Henrik Lindberg > wrote: > >> On 2014-12-08 22:02, Spencer Krum wrote: >> >> >> 1) I really don't want to see variable expansion in >>expressions that >> resolve to the names of types. This will be misused, it >>will make code

[Puppet-dev] Re: Decision: Near future of resource expressions

On 2014-12-08 19:47, Luke Kanies wrote: On Aug 5, 2014, at 6:41 PM, Reid Vandewiele mailto:r...@puppetlabs.com>> wrote: Visual review, for convenience: file { $title: * => $attributes; } file { $title: => $attributes; } file { $title: ($attributes); } file { $title: attribute_defaults => $attr

[Puppet-dev] Saucy leaving apt.puppetlabs.com

Ubuntu saucy has reached end of life on July 17, 2014 [1]. As such, we will not be building new packages for saucy. We will remove it from our apt repository on Monday, September 15. [1] - https://lists.ubuntu.com/archives/ubuntu-announce/2014-July/000187.html -- Melissa Stone Release Engineer,

[Puppet-dev] Re: Replacement for puppet doc

On 2014-12-08 23:52, Nick Fagerlund wrote: Well, something I've learned over the last four years is that cute names age a lot faster than you'd think. So I'm generally in favor of descriptive ones instead, at least when we're dealing with command -line tools. And unfortunately, "puppet doc" is p

[Puppet-dev] Re: Syntax of resource expressions (was: Decision: Near future of resource expressions)

On 2014-12-08 22:02, Spencer Krum wrote: 1) I really don't want to see variable expansion in expressions that resolve to the names of types. This will be misused, it will make code unreadable. Please leave it out. Sets of parameters only

Re: [Puppet-dev] Re: Replacement for puppet doc

Well, something I've learned over the last four years is that cute names age a lot faster than you'd think. So I'm generally in favor of descriptive ones instead, at least when we're dealing with command -line tools. And unfortunately, "puppet doc" is pretty much the perfect name for it. :/ So

[Puppet-dev] Today's outage on tickets.puppetlabs.com

We had an outage today on the Puppet Labs JIRA ticket tracker. tickets.puppetlabs.com was unavailable from 1800 GMT to 2000 GMT (1110 PDT to 1300 PDT) The service is back up, and no data has been lost. For anyone who is interested, we'll be publishing the results of our post-mortem on the Puppet

Re: [Puppet-dev] Re: Syntax of resource expressions (was: Decision: Near future of resource expressions)

> > > > 1) I really don't want to see variable expansion in expressions that >> resolve to the names of types. This will be misused, it will make code >> unreadable. Please leave it out. Sets of parameters only make sense to >> distinct types anyways, if two types really do accept a

Re: [Puppet-dev] Re: Replacement for puppet doc

Please don't use `dox`. It's like a teenager who wasn't taught enough English in school, or simply doesn't care, to know that the accepted plural of doc is docs, not dox, dawg. On Tuesday, 12 August 2014 19:33:04 UTC+2, Andy Parker wrote: > > On Tue, Aug 12, 2014 at 10:19 AM, Hailee Kenney > wr

Re: [Puppet-dev] Re: Syntax of resource expressions (was: Decision: Near future of resource expressions)

On Aug 12, 2014, at 10:02 AM, Andy Parker wrote: > On Mon, Aug 11, 2014 at 8:54 PM, Spencer Krum wrote: > 1) I really don't want to see variable expansion in expressions that resolve > to the names of types. This will be misused, it will make code unreadable. > Please leave it out. Sets of par

Re: [Puppet-dev] Decision: Near future of resource expressions

On Aug 5, 2014, at 6:41 PM, Reid Vandewiele wrote: > Visual review, for convenience: > > file { $title: * => $attributes; } > file { $title: => $attributes; } > file { $title: ($attributes); } > file { $title: attribute_defaults => $attributes; } > file { $title: attribute_hash => $attributes; }

Re: [Puppet-dev] Re: Replacement for puppet doc

On Tue, Aug 12, 2014 at 10:19 AM, Hailee Kenney wrote: > > Thanks for all the feedback everyone! Going back to the issue of naming, I > have a list of suggestions I've collected that I wanted throw out there for > discussion: > > puppet strings (this seems to be a popular choice) > I like this o

Re: [Puppet-dev] Re: Replacement for puppet doc

On Sat, Aug 9, 2014 at 1:29 PM, Henrik Lindberg < henrik.lindb...@cloudsmith.com> wrote: > On 2014-09-08 20:32, Wil Cooley wrote: > >> On Aug 8, 2014 5:15 PM, "Hailee Kenney" > > wrote: >> > >> > Right now, Charlie Sharpsteen has an awesome prototype which uses >> Y

Re: [Puppet-dev] Re: Syntax of resource expressions (was: Decision: Near future of resource expressions)

On Mon, Aug 11, 2014 at 8:54 PM, Spencer Krum wrote: > 1) I really don't want to see variable expansion in expressions that > resolve to the names of types. This will be misused, it will make code > unreadable. Please leave it out. Sets of parameters only make sense to > distinct types anyways, i

[Puppet-dev] Re: Syntax of resource expressions (was: Decision: Near future of resource expressions)

On 2014-12-08 5:54, Spencer Krum wrote: 1) I really don't want to see variable expansion in expressions that resolve to the names of types. This will be misused, it will make code unreadable. Please leave it out. Sets of parameters only make sense to distinct types anyways, if two types really do