Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace the role of the Director in concluding AC Review #646

Merged
merged 1 commit into from Oct 27, 2022

Conversation

frivoal
Copy link
Collaborator

@frivoal frivoal commented Sep 23, 2022

The pre-existing seciton had a number of issues already, but they would be made worse without the oversight of the Director:

  • No link between the consensus of the AC and which decision is taken
  • No constraint on what decision may be taken
  • Ability to make (certain) changes unannounced
  • Unrestricted ability to make substantive changes to a document
  • Ability to make substantive changes to a REC without triggering patent exclusion opportunities, or fullfilling other REC criteria

Preview | Diff

@frivoal frivoal added Agenda+ Marks issues that are ready for discussion on the call Director-free (all) All issues & pull request related to director-free. See also the topic-branch labels Sep 23, 2022
@frivoal frivoal mentioned this pull request Sep 28, 2022
@frivoal frivoal force-pushed the ac-review-conclusion branch 2 times, most recently from ef89a9e to e8b7de2 Compare September 30, 2022 09:27
The pre-existing seciton had a number of issues already, but they would
be made worse without the oversight of the Director:
* No link between the consensus of the AC and which decision is taken
* No constraint on what decision may be taken
* Ability to make (certain) changes unannounced
* Unrestricted ability to make substantive changes to a document
* Ability to make substantive changes to a REC without triggering patent
  exclusion opportunities, or fullfilling other REC criteria
@css-meeting-bot
Copy link
Member

The Revising W3C Process CG just discussed Director-free [continuation to completion].

The full IRC log of that discussion <fantasai> Topic: Director-free [continuation to completion]
<fantasai> github: https://github.com//pull/646

@frivoal frivoal added Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion and removed Agenda+ Marks issues that are ready for discussion on the call labels Oct 27, 2022
@frivoal frivoal merged commit 6458dad into w3c:main Oct 27, 2022
@css-meeting-bot
Copy link
Member

The Revising W3C Process CG just discussed Replace the role of the Director in concluding AC Review, and agreed to the following:

  • RESOLVED: Merge 646
The full IRC log of that discussion <fantasai> subtopic: Replace the role of the Director in concluding AC Review
<fantasai> github: https://github.com//pull/646
<fantasai> florian: Old process relied on Director here
<fantasai> ... first there was AC review
<fantasai> ... then Director decides to do something after the review
<fantasai> ... There's no actual linkage between the results of the review and what the Director does
<fantasai> ... You'd expect that Director would try to reflect consensus, but this was not required
<fantasai> florian: There was also issue that Director could make editorial changes without even announcing the changes
<fantasai> ... sure, reasonable to change; but shouldn't be allowed to change it secretly
<fantasai> florian: So now if go through AC Review and AC says yes, expected to adopt
<fantasai> ... if objections, goes to Council ...
<fantasai> ... and added allowances for edits, with appropriate notifications etc.
<fantasai> florian: basically encodes existing practice, which is important now that we don't have a Director
<fantasai> plh: Do we have a link to the guidebook?
<fantasai> florian: Various places, but not here specifically
<fantasai> plh: When adopting proposal with substantial changes [reads]
<fantasai> ... we do have specific mailing lists that we copy
<fantasai> ... maybe worth adding a link to the proper subpart of the guide?
<fantasai> florian: I think we could do that in a separate PR
<fantasai> ... this has been up for review for awhile, let's merge and then do tweaks
<fantasai> plh: fair enough
<fantasai> plh: Any objection to merge 646?
<fantasai> florian: btw, while dsinger isn't here today, he was with us when we wrote this, and is in support
<TallTed> +1 merge
<fantasai> plh: I don't hear anyone asking to wait or raising objections, so shall we resolve?
<florian> +1
<fantasai> RESOLVED: Merge 646
<cwilso> +1

@frivoal frivoal deleted the ac-review-conclusion branch October 27, 2022 14:18
@frivoal frivoal added this to the Process 2022 milestone Oct 27, 2022
@frivoal frivoal added Commenter satisfied/accepting conclusion confirmed as accepted by the commenter, even if not preferred choice and removed Commenter satisfied/accepting conclusion confirmed as accepted by the commenter, even if not preferred choice labels Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion Director-free (all) All issues & pull request related to director-free. See also the topic-branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants