Re: Success Criteria of the WebApps WG [was: Re: CfC to publish DeviceOrientation Event CR Snapshot - review by 11 March]

Hi Xiaoqian,

Thanks for bringing this issue to our attention. No need to apologize. From what I understand, the situation is developing positively:

By adopting the standard Success Criteria [1] in its latest charter [2] WebApps WG ensured it satisfies the Joint deliverables principles [3], specifically: "Any conflict between the success criteria sections ought to be resolved before the charters are approved.” This standard Success Criteria [1] now adopted by WebApps WG is widely endorsed: it has been adopted by 39 out of 42 Working Groups [4] based on my napkin math.

Process details aside, what does this mean to DAS WG and WebApps WG participants?

Thanks to this Success Criteria alignment and approval these Working Groups can soon start collaborating on the new joint deliverables.

Thank you for your contributions and patience, everyone. I can’t wait to kick off this long-awaited collaboration and welcome new folks on board who are eager to start contributing.

Thanks,

-Anssi

[1] https://w3c.github.io/charter-drafts/charter-template.html#success-criteria

[2] https://www.w3.org/2024/01/webappswg-charter-2024.html#success-criteria

[3] https://www.w3.org/Guide/process/joint-deliverables.html

[4] https://www.w3.org/groups/wg/


> On 22. Mar 2024, at 15.01, Xiaoqian Wu <xiaoqian@w3.org> wrote:
> 
> hi WebApps WG members,
> 
> We sincerely apologize for a mistake made during the recent rechartering of the WebApps WG.
> 
> As Anssi and Marcos pointed out in a previous discussion, when we were updating the document with the latest template, a critical paragraph was overlooked and removed [1]:
> [[
> In order to advance to Candidate Recommendation and to add features after reaching Candidate Recommendation, each feature is expected to be supported by at least two implementations, which may be judged by factors including existing implementations, expressions of interest, and lack of opposition.
> ]]
> 
> This paragraph has a great influence on the implementation of the specifications in the group. The co-chairs will follow up on the issue and find a compact way to fix it.
> 
> Thanks.
> 
> Xiaoqian Wu
> WebApps WG Team Contact
> 
> [1] https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2F2022%2F04%2Fwebapps-wg-charter.html&doc2=https%3A%2F%2Fwww.w3.org%2F2024%2F01%2Fwebappswg-charter-2024.html#/success-criteria

> 
> On 2024-03-22 17:30, Kostiainen, Anssi wrote:
>>> On 22. Mar 2024, at 9.53, Marcos Caceres <caceres_m@apple.com>
>>> wrote:
>> […]
>>> WebApps charter explicitly states that, "In order to advance to
>>> Candidate Recommendation and to add features after reaching
>>> Candidate Recommendation, each feature is expected to be supported
>>> by at least two implementations, which may be judged by factors
>>> including existing implementations, expressions of interest, and
>>> lack of opposition.”
>>> [1] “Success Criteria” of
>>> https://www.w3.org/2022/04/webapps-wg-charter.html

>> I feel obligated to point out you are referencing and quoting the old
>> obsoleted WebApps WG charter.
>> The current WebApps WG charter [2], effective 21 February 2024, does
>> not include such text, but states:
>> "In order to advance to Proposed Recommendation, each normative
>> specification is expected to have at least two independent
>> interoperable implementations of every feature defined in the
>> specification, where interoperability can be verified by passing open
>> test suites, and two or more implementations interoperating with each
>> other. In order to advance to Proposed Recommendation, each normative
>> specification must have an open test suite of every feature defined in
>> the specification."
>> This CfC was about advancing to Candidate Recommendation, not Proposed
>> Recommendation.
>> Thanks,
>> -Anssi
>> [2]
>> https://www.w3.org/2024/01/webappswg-charter-2024.html#success-criteria

Received on Monday, 25 March 2024 12:04:12 UTC