- From: David Singer <singer@apple.com>
- Date: Fri, 13 Sep 2013 14:15:14 -0700
- To: Matthias Schunter <mts-std@schunter.org> (Intel Corporation)
- Cc: public-tracking@w3.org
On Sep 13, 2013, at 4:43 , Matthias Schunter (Intel Corporation) <mts-std@schunter.org> wrote: > Hi Ninja, > > > thanks for the feedback. > > Yes: "no text" (with appropriate argument) is a sound change proposal to resolve an issue. Similarly, the HTML group had a number of change proposals with a "no change" or "zero change" proposal, i.e. that the text was correct as it stood. I am not sure whether this is what you mean by "no text" (would "no text" mean a change proposal to delete existing text?). > > What is important that "no text" is documented as one alternative change proposal within the wiki. > If there is only one change proposal (e.g. an issue only having the "no text" resultion), the chairs may interpret this as this single proposal that has consensus. > However, if there is some text and "no text" as an alternative, we need to actually jointly decide among those options. > > > Regards, > matthias > > > > On 13/09/2013 11:54, Ninja Marnau wrote: >> Hi Matthias, >> >> just a clarification question regarding the "single text rule": I guess >> it will not be considered a single text, if we have one text proposal >> and the proposal to not include this text. >> >> Do we specifically need to write it to the mailing list, if we object to >> include a proposed text and rather have the spec stay silent on the >> issue? This would mean for each text proposal that silence is considered >> agreement/consensus to include the text - is this what you are suggesting? >> >> Ninja >> >> Am 13.09.2013 11:30, schrieb Matthias Schunter (Intel Corporation): >>> Hi Folks, >>> >>> I had some ideas how to further improve the plan by adding the following >>> rules. >>> Feedback is welcome! >>> >>> Regards, >>> matthias >>> >>> ----------- >>> - Single text rule: If there is only one proposed text/resolution by end >>> of month, the chairs may pick this text as our consensus for an issue. >>> >>> - Close in writing: Before closing an issue, a reminder (e.g., the batch >>> closing emails used in the past) is sent to our mailing list. >>> (Between this email and the closing, there are at least 14 calendar >>> days for review) >>> >>> - Each substantial change proposal must point to an open issue it tries >>> to resolve. >>> >>> - Issues must have one change proposal; issues that have no single >>> change proposal (or otherwise do not satisfy the requirements put >>> forward) will be closed >>> shortly after October 02. >>> >>> >>> > > David Singer Multimedia and Software Standards, Apple Inc.
Received on Friday, 13 September 2013 21:15:31 UTC