On Tuesday, June 25, 2013 4:49:49 PM UTC-5, Alessandro Franceschi wrote:
>
>
>
> On Tuesday, June 25, 2013 9:16:20 PM UTC+2, jcbollinger wrote:
>>
>>
>> So, here is a version of puppet-stdmod without class parameterization:
>> https://github.com/jcbollinger/puppet-stdmod .
>>
>
> Ok, this is what I expected.
>
Of course it is. I told you in advance what it was going to be.
> Thank you for your time.
> I can definitively argue that this is not fully reusable
> ("So please show me a reusable module without parameters and without
> hiera functions inside, as that would not be reusable by whoever does not
> use Hiera.")
>
And I rejected that standard of reusability, for sound reasons that you did
not rebut. Since we are closing off that line of discussion, we will have
to agree to disagree.
> Yes,
> let's go on.
> I guess the first steps should be to identify a coherent naming pattern,
> even before single names and define more precisely what parameters might be
> recommended, optional, or considered "extensions" .
>
>
Before any decision is made on naming patterns -- or at least in
conjunction with that -- don't you think we should come to grips with the
patterns of data to which we hope to assign names? The Google doc does
address that topic, at least implicitly, but I think we should be satisfied
with the coverage and characterization of the data, else we cannot be
confident that the chosen names are the most appropriate ones. I will
devote some attention to that, but I hope I will not be the only one to do
so.
John
--
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 puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
