Re: [wbs] response to 'Call for Review: Proposed W3C Process Document'

Per the follow-up comments I made in issue
https://github.com/w3c/w3process/issues/764, our Formal Objection (FO) that
was noted in the WBS Mailer response has been resolved.

This reverts our response back to:

> the reviewer suggests changes, but supports adoption as the W3C Process
whether or not the changes are adopted.

And:

> Mozilla supports this quite significant W3C Process revision, including
any changes (hence "suggests changes") in response to the comments on this
Call for Review as proposed by the W3C Process CG and approved by the AB.
As participants in this Call for Review, we would like to review that full
set of proposed changes when it is available from the Process CG.

And:

> we will file Process CG issue(s) for non-blocking triage & consideration
by the Process CG.

Thanks to quick responses with new information & clarification on
https://github.com/w3c/w3process/issues/764 which helped us promptly
resolve our FO while allowing for minor & editorial issues to be filed
separately, without awaiting their resolution to resolve our FO.

Tantek Çelik
Mozilla AC Rep

On Wed, May 24, 2023 at 6:21 PM Tantek Çelik via WBS Mailer <
sysbot+wbs@w3.org> wrote:

> The following answers have been successfully submitted to 'Call for Review:
> Proposed W3C Process Document' (Advisory Committee) for Mozilla Foundation
> by Tantek Çelik.
>
> Regarding the "W3C Process Document" specification, the reviewer  suggests
> changes, and only supports adoption as the W3C Process if the changes are
> adopted [Formal Objection].
>
>
> Additional comments about the specification:
>    Mozilla supports this quite significant W3C Process revision, including
> any changes (hence "suggests changes") in response to the comments on this
> Call for Review as proposed by the W3C Process CG and approved by the AB.
> As participants in this Call for Review, we would like to review that full
> set of proposed changes when it is available from the Process CG.
>
> Upon deeper review of new cross-references from new features in the
> proposed Process 2023, Mozilla found one MUSTFIX bug (Formal Objection),
> has filed it accordingly, and thus must change our response to this survey
> to "suggests changes, and only supports adoption as the W3C Process if the
> changes are adopted [Formal Objection]".
>
> * MUSTFIX: New W3C Council and updated TAG Composition section errantly
> only includes Tim Berners-Lee from the TAG, in W3C Council Composition:
> https://github.com/w3c/w3process/issues/764
>
> Fortunately this was the only showstopper we found.
>
> As noted previously: if we subsequently find anything in particular that we
> would like to see changed, we will file a Process CG issue for non-blocking
> triage & consideration by the Process CG.
>
> We did also find inappropriate upgrade-by-references of an informative
> external reference into implied incorporation into normative inline prose,
> that SHOULD be fixed (non-formal objection):
> * Normative prose for role of Chair / Team Contact cites informative
> reference for description: https://github.com/w3c/w3process/issues/765
>
> We will do the work to file separate Pull Requests (PRs) with minimal and
> expected to be uncontroversial edits to address these issues.
>
> Thanks for the excellent work on Process 2023, our feedback & suggestions
> are intended to build on and marginally improve that excellent work.
>
>
> Answers to this questionnaire can be set and changed at
> https://www.w3.org/2002/09/wbs/33280/Process-2023/ until 2023-05-24.
>
>  Regards,
>
>  The Automatic WBS Mailer
>
>
>