- From: Wayne Carr <wayne.carr@linux.intel.com>
- Date: Wed, 02 Jan 2013 20:24:56 -0800
- To: "Young, Milan" <Milan.Young@nuance.com>
- CC: Ian Jacobs <ij@w3.org>, "public-council@w3.org" <public-council@w3.org>
I'm starting to understand Milan's point better. Saying "ask them" when the problem he's worried about is not trusting them, doesn't help, and possibly hurts. But I'd also like to keep it positive in tone, like it is. How about: Note: This group does not (yet) have a charter that describes its scope, deliverables, and decision process. Groups that clearly document their practices promote participation, build trust, and avoid conflict that arises from differing expectations. In the absence of a charter, participants may find that the way decisions are made change over time or violate their expectations of how the group was to operate. On 12/27/2012 5:05 PM, Young, Milan wrote: >> From: Ian Jacobs [mailto:ij@w3.org] >> I think our obligation is to say "You must be attentive." I do not think our obligation is to scare people off. > [Milan] I don't want to scare people off either, but it's wrong to omit details that would surprise them. I'm certain people would be surprised to learn, for example, a chair can make commitments on a public forum and then recount without due process to the group. > > There are only two choices: > * Educate participants on topics that are likely to surprise them. The visibility of the education must be in proportion to the expected surprise. A "note" that participants should "seek additional information" isn't proportional to the potential dangers. > * Change the rules so that surprising circumstances are prevented by the framework. I'm sympathetic to the difficulties opposing this approach. > >
Received on Thursday, 3 January 2013 04:25:27 UTC