[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ws-tx] Avoiding motions on text drafted during telcons
|
This is an excellent idea. In other TCs we
have been able to address this using proposals on concepts/directions, achieving
convergence on these, then if/when accepted, providing proposed spec text to
address the concept/direction in question (provided to the TC at minimum 2-3
working days before discussion). I think this is an approach which would fit in
nicely with your suggestion. -Charlton. -- Adobe Systems Incorporated +1 (408) 536-4496 p cbarreto@adobe.com From: Duane Nickull
[mailto:dnickull@adobe.com] I concur. It is important to balance
the requirements for a standard vs. ensuring the quality of the standard. The
output of this TC will be scrutinized by our peers worldwide and I for one want
to ensure we strive for technical excellence. Duane Nickull ******************************* From: Colleen Evans
[mailto:coevans@microsoft.com] I strongly suggest that we avoid making hasty motions to
accept language proposed in the same meeting in cases where such proposals
represent a substantive change to previous proposals or to the original spec
text. Several times on today’s call substantively changed
text was proposed on the fly and potential motions were discussed to accept the
text on the call. IMO this is a dangerous way to proceed. I propose
we recap all substantive proposed text in email, giving members time to
consider it in the context of the spec, and delay voting on its acceptance or
rejection until the following meeting. If the changes are minor, such as the resolution we
ultimately approved for issue 12 which included a combination of previously
proposed text and a very slight modification to the original text, it may be
appropriate to craft the text and consider a motion in the same meeting. Colleen |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]