Hi,

One thing I've always found very useful when discussing proposals like this is to use the issue tracking system early on. It's easy to cross reference even individual comments and also to obtain links to them when referencing from email. Aside from the ability to comment anonymously, it fits Nigel's bullets very well.

I've been working a lot with the Eclipse community for some time. They make heavy use of their bugzilla. As soon as a discussion commences on a list that is likely to lead to something to be implemented, an issue (sometimes several) is started and the discussion moves.

Personally, I don't care much about being able to comment anonymously and I don't think people in general feel that they are blocked out if they need to register in order to participate in the discussion.

Regarding the proposal. One thing that I'm not able to extract is how to derive what a module will need in terms of data. If this is about separating the data from the actual use of the data, then there should be some meta-data describing it. Let's assume I want to create an IDE extension for editing the data for a specific module. How can I assist the user in entering this data and then validate that it is correct?

Regards,
Thomas Hallgren


On 2011-01-16 02:26, Nigel Kersten wrote:
On Sat, Jan 15, 2011 at 5:20 PM, R.I.Pienaar <[email protected]> wrote:

I dont know what is the best solution, but email is in every way better
than google docs.

I agree. I think this experiment ruled out Docs as a method for this. It works quite well with a small group of people, but not very well for a large group.

I think one simple change would make these discussions significantly better on email though.

Don't include the document inline, add line numbers to the reference document and keep a revision number highly visible, then encourage people to use those references in their replies on email.

I was primarily hoping we would get feedback from people other than the usual suspects... but that doesn't really seem to be the case.

I worry sometimes that the community heavyweights (through no fault of your own) end up intimidating others into not speaking.


I have no doubt at all that its needed and keen to see some solution reached

awesome.

--
You received this message because you are subscribed to the Google Groups "Puppet Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.

--
You received this message because you are subscribed to the Google Groups "Puppet Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.

Reply via email to