├── .gitignore ├── .pr-preview.json ├── w3c.json ├── CODE_OF_CONDUCT.md ├── .github ├── ISSUE_TEMPLATE │ ├── bug.md │ ├── question.md │ ├── implementation.md │ ├── enhancement.md │ ├── editorial.md │ └── agenda.md └── workflows │ └── compile.yml ├── compile.sh ├── README.md ├── deploy.sh ├── issues-20210603.txt ├── issues-20200915.txt ├── retiring-rec.svg ├── snapshots ├── 2021-07-23-doc.html ├── 2023-04-faq.html ├── 2023-05-24-doc.bsi └── 2023-05-24-doc.html ├── CONTRIBUTING.md ├── basic-rec-track.svg ├── issues-20180201.txt ├── issues-20190301.txt └── issues-20211102.html /.gitignore: -------------------------------------------------------------------------------- 1 | index.html 2 | issues-*.html 3 | !issues-20211102.html 4 | -------------------------------------------------------------------------------- /.pr-preview.json: -------------------------------------------------------------------------------- 1 | { 2 | "src_file": "index.bs", 3 | "type": "bikeshed" 4 | } 5 | -------------------------------------------------------------------------------- /w3c.json: -------------------------------------------------------------------------------- 1 | { 2 | "group": [ "other/ab", "cg/w3process" ] 3 | , "contacts": ["plehegar", "fantasai", "frivoal"] 4 | , "policy": "restricted" 5 | , "repo-type": "process" 6 | } 7 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Code of Conduct 2 | 3 | This repository, being work of the 4 | [World Wide Web Consortium (W3C)](https://www.w3.org/), is subject to the 5 | [W3C Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc/). 6 | 7 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Bugs affecting interpretation of the document 4 | title: '' 5 | labels: 'Type: bug' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ## Describe the bug affecting interpretation of the document 11 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/question.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Question 3 | about: General question related to the W3C Process or its implementation 4 | title: '' 5 | labels: 'Type: Question' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ## Describe the general question related to the W3C Process or its implementation 11 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/implementation.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Implementation 3 | about: Not an actual issue about the process, but something to be handled for implementing it 4 | title: '' 5 | labels: 'Type: Implementation' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ## Describe the implementation of the process issue 11 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/enhancement.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Enhancement 3 | about: Enhancements that affect current interpretation or that add new functionality 4 | title: '' 5 | labels: 'Type: Enhancement' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ## Describe the enhancement that affect current interpretation or that add new functionality 11 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/editorial.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Editorial issue 3 | about: Editorial improvements or errors that do not affect interpretation of the document 4 | title: '' 5 | labels: 'Type: Editorial improvements' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ## Describe the editorial improvements or errors that do not affect interpretation of the document 11 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/agenda.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Meeting agenda 3 | about: Agenda discussion for a given Process CG meeting 4 | title: '[agenda] 2025-0x-xx' 5 | labels: 'Meeting agenda' 6 | assignees: 'brentzundel,plehegar' 7 | 8 | --- 9 | 10 | ## Proposed Agenda 11 | 12 | 1. agenda item 1 13 | 1. agenda item 2 14 | 1. agenda item 3 15 | 1. AOB 16 | 17 | --- 18 | 19 | * [label:"Agenda+"](https://github.com/w3c/process/issues?q=state%3Aopen%20label%3AAgenda%2B) 20 | * [label:"Proposed to close"](https://github.com/w3c/process/issues?q=state%3Aopen%20label%3A%22Proposed%20to%20close%22) 21 | * [label:"Needs proposed PR"](https://github.com/w3c/process/issues?q=state%3Aopen%20label%3A%22Needs%20proposed%20PR%22) 22 | * [Mailing list](https://lists.w3.org/Archives/Public/public-w3process/) 23 | * [open pull requests](https://github.com/w3c/process/pulls), [open issues](https://github.com/w3c/process/issues) 24 | --- 25 | 26 | [Process Milestone](https://github.com/w3c/process/milestone/13) 27 | 28 | --- 29 | 30 | Please add comments to this issue if you have suggestions for agenda items 31 | -------------------------------------------------------------------------------- /.github/workflows/compile.yml: -------------------------------------------------------------------------------- 1 | name: Process Builder 2 | 3 | # Reference documentation: https://docs.github.com/en/actions/reference 4 | on: [push, pull_request] 5 | 6 | jobs: 7 | deploy: 8 | runs-on: ubuntu-24.04 9 | name: Build and deploy to gh-pages 10 | if: ${{ github.repository == 'w3c/process' && github.event_name == 'push' }} 11 | env: 12 | GITHUB_TOKEN: ${{ secrets.W3CGRUNTBOT_TOKEN }} 13 | GH_BRANCH: ${{ github.head_ref }} 14 | GH_EVENT_NUMBER: ${{ github.event.number }} 15 | steps: 16 | - name: Checkout the repository 17 | uses: actions/checkout@v4 18 | - name: Setup python 3.12 19 | uses: actions/setup-python@v5 20 | with: 21 | python-version: "3.12" 22 | architecture: x64 23 | - name: Install bikeshed 24 | run: | 25 | pip install bikeshed 26 | bikeshed update 27 | echo Bikeshed is ready 28 | - name: invoke deploy.sh 29 | run: ./deploy.sh 30 | shell: bash 31 | build: 32 | runs-on: ubuntu-24.04 33 | name: Check that the Process builds cleanly 34 | if: ${{ github.repository != 'w3c/process' || github.event_name == 'pull_request' }} 35 | steps: 36 | - name: Checkout the repository 37 | uses: actions/checkout@v4 38 | - name: Setup python 3.12 39 | uses: actions/setup-python@v5 40 | with: 41 | python-version: "3.12" 42 | architecture: x64 43 | - name: Install bikeshed 44 | run: | 45 | pip install bikeshed 46 | bikeshed update 47 | echo Bikeshed is ready 48 | - name: invoke compile.sh 49 | run: ./compile.sh 50 | shell: bash 51 | -------------------------------------------------------------------------------- /compile.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | # So we can see what we're doing 4 | set -x 5 | 6 | # Exit with nonzero exit code if anything fails 7 | set -e 8 | 9 | # Run bikeshed. If there are errors, exit with a non-zero code 10 | # Include a warning in the status for topic branches 11 | if [ $1 ] ; then 12 | bikeshed --print=plain -f spec index.bs index.html \ 13 | --md-status-text="
This is not the latest Editor’s Draft of the W3C Process.\ 14 |

This is the “$1” topic branch; make sure this is indeed the one you’re looking for.\ 15 | If not, the current Editor’s Draft can be found at\ 16 | https://www.w3.org/policies/process/drafts/.
\ 17 | (The Status of this document section may have information about the purpose of this branch.)

" \ 18 | --md-ED="https://www.w3.org/policies/process/drafts/$1/" 19 | else 20 | bikeshed --print=plain -f spec 21 | fi 22 | 23 | # Bikeshed the DoCs as well, unless we're on a topic branch 24 | if ! [ $1 ] ; then 25 | for i in issues-*.txt; do 26 | if [ -f $i ]; then 27 | bikeshed --print=plain -f issues-list $i 28 | fi 29 | done 30 | fi 31 | 32 | # The out/$1 directory needs to contain everything needed 33 | # to publish the HTML version of the spec. 34 | # Copy things there if the directory exists. 35 | # Only copy the actual Process if we're on a topic branch, 36 | # and everything else too (DoCs, snapshots) if we're on the main branch. 37 | 38 | if [ -d out/$1 ]; then 39 | if ! [ $1 ] ; then 40 | if [ -d snapshots ]; then 41 | cp -r snapshots out/$1/ 42 | fi 43 | for i in issues-*.html; do 44 | if [ -f $i ]; then 45 | cp -r $i out/$1/ 46 | fi 47 | done 48 | fi 49 | cp index.html out/$1/ 50 | fi 51 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # W3C Process Document repository 2 | 3 | 4 | This repository is for the editor's draft of the [World Wide Web Consortium Process Document](https://www.w3.org/policies/process/). 5 | 6 | The Process document is updated most years by the W3C. 7 | Discussion happens in the context of the W3C Process Community Group 8 | [https://www.w3.org/community/w3process/](https://www.w3.org/community/w3process/), mostly in this Github repository, but also on the archived public mailing list. 9 | 10 | ---- 11 | ## Branches under development 12 | 13 | * [main](https://github.com/w3c/process/tree/main) branch (current draft of the CG): 14 | [Preview](https://www.w3.org/policies/process/drafts/) 15 | * [ab-tag-discipline](https://github.com/w3c/process/tree/ab-tag-discipline) branch, where potential procedures for removal and recall of AB or TAG members are being worked out: [preview](https://www.w3.org/policies/process/drafts/ab-tag-discipline/) 16 | 17 | ---- 18 | ## Useful searches 19 | 20 | * [Issues and PRs without a milestone](https://github.com/w3c/process/issues?q=is%3Aopen%20no%3Amilestone) 21 | * [Issues and PR included and targetted for the next release](https://github.com/w3c/process/issues?q=is%3Aopen%20milestone%3A%22Process%202024%2F2025%22%20) 22 | * [Issues and PR marked as Agenda+](https://github.com/w3c/process/issues?q=%20label%3AAgenda%2B%20) 23 | 24 | ---- 25 | ## Bikeshed 26 | 27 | This document is maintained using [Bikeshed](https://tabatkins.github.io/bikeshed/). 28 | See the [section about markup](https://tabatkins.github.io/bikeshed/#markup-shortcuts) in Bikeshed's documentation for full details about the syntax. 29 | 30 | **Only the source (index.bs) should be committed**, 31 | as this repository is configured to run bikeshed server-side and push the result to the gh-pages branch. 32 | 33 | To run Bikeshed locally, 34 | Follow [the instructions](https://tabatkins.github.io/bikeshed/#installing) in Bikeshed's documentation. 35 | Once Bikeshed is installed, just type `bikeshed` to compile the document. 36 | 37 | ---- 38 | ## Setting up Branches 39 | 40 | To set up long-lived topic branches which get built server side and published to github.io, 41 | follow these steps: 42 | 43 | 1. **On the main branch** edit deploy.sh to add the name of your topic branch to the `TOPIC_BRANCHES` array. Example: 44 | 45 | ```bash 46 | TOPIC_BRANCHES=("topic1" "topic2" "topic3") 47 | ``` 48 | 49 | 2. (Optional Step) Edit the README.md file to line for your topic branch. 50 | See the "Branches under development" section and use existing branches as a model. 51 | 52 | 3. Commit the change(s) above, and push to github.com/w3c/w3process (not your personal fork). Example: 53 | 54 | ```bash 55 | git add deploy.sh README.md 56 | git commit -m "Register topic branch for topic3" 57 | git push upstream main 58 | ``` 59 | 60 | 4. Create a new branch from the main branch (after the previous commit), using the same name as the one you used in the `TOPIC_BRANCHES` array, and push it to github.com/w3process (not your personal fork). Example: 61 | 62 | ```bash 63 | git checkout -b topic3 64 | git push upstream topic3 65 | ``` 66 | -------------------------------------------------------------------------------- /deploy.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | set -e # Exit with nonzero exit code if anything fails 3 | 4 | SOURCE_BRANCH="main" 5 | TARGET_BRANCH="gh-pages" 6 | 7 | # List of long-lived topic branch names to be published on github.io as a subdirectory 8 | # Once added, branches should not be removed from here, 9 | # because cool URLs don't change. 10 | # (But you can stop advertising them in README.md) 11 | # Even if the branch itself is retired, 12 | # the built copies will continue to be served unless and until its name is removed from here. 13 | TOPIC_BRANCHES=( 14 | "director-free" 15 | "tooling" 16 | "registries" 17 | "registries-on-rec-track" 18 | "registries-separable" 19 | "evergreen" 20 | "everblue" 21 | "section-6-clean-up" 22 | "maintenance-2020" 23 | "p2021-before-reorg" 24 | "p2021" 25 | "ab-tag-discipline") 26 | 27 | containsElement () { 28 | local e match="$1" 29 | shift 30 | for e; do [[ "$e" == "$match" ]] && return 0; done 31 | return 1 32 | } 33 | 34 | # So we can see what we're doing 35 | set -x 36 | 37 | # set up the github credentials 38 | 39 | git config --global user.email 87540780+w3cgruntbot@users.noreply.github.com 40 | git config --global user.name w3cgruntbot 41 | git config --global user.password $GITHUB_TOKEN 42 | 43 | REPO_URL="https://w3cbot:$GITHUB_TOKEN@github.com/$GITHUB_REPOSITORY.git" 44 | 45 | # set up old travis env 46 | 47 | TRAVIS_BRANCH=${GH_BRANCH:-$(echo $GITHUB_REF | awk 'BEGIN { FS = "/" } ; { print $3 }')} 48 | TRAVIS_PULL_REQUEST=${GH_EVENT_NUMBER:-false} 49 | 50 | 51 | # Pull requests and commits to other branches shouldn't try to deploy, just build to verify 52 | if [ "$TRAVIS_PULL_REQUEST" != "false" ] || { [ "$TRAVIS_BRANCH" != "$SOURCE_BRANCH" ] && ! containsElement "$TRAVIS_BRANCH" "${TOPIC_BRANCHES[@]}" ; }; then 53 | echo "Skipping deploy; just doing a build." 54 | ./compile.sh 55 | exit 0 56 | fi 57 | 58 | # Clone the existing gh-pages for this repo into out/ 59 | # Create a new empty branch if gh-pages doesn't exist yet (should only happen on first deploy) 60 | git clone $REPO_URL out 61 | cd out 62 | git checkout $TARGET_BRANCH || git checkout --orphan $TARGET_BRANCH 63 | git reset --hard 64 | 65 | if containsElement "$TRAVIS_BRANCH" "${TOPIC_BRANCHES[@]}" ; then 66 | # Delete all existing contents except in the topic branch directory (we will re-create them) 67 | mkdir -p "$TRAVIS_BRANCH" 68 | cd "$TRAVIS_BRANCH" 69 | find -maxdepth 1 ! -name . | xargs rm -rf 70 | cd ../.. 71 | 72 | ./compile.sh "$TRAVIS_BRANCH" 73 | else 74 | # Delete all existing contents except .git and topic branches (we will re-create them) 75 | for i in "${TOPIC_BRANCHES[@]}"; do 76 | echo exclude="$exclude ! -name '$i'"; 77 | exclude="$exclude ! -name '$i'"; 78 | done 79 | eval find -maxdepth 1 ! -name .git ! -name . "$exclude" | xargs rm -rf 80 | cd .. 81 | 82 | ./compile.sh 83 | fi 84 | 85 | # Now let's go have some fun with the cloned repo 86 | cd out 87 | 88 | # If there are no changes to the compiled out (e.g. this is a README update) then just bail. 89 | if [[ -z $(git status --porcelain) ]]; then 90 | echo "No changes to the output on this push; exiting." 91 | exit 0 92 | fi 93 | 94 | # Commit the "changes", i.e. the new version. 95 | # The delta will show diffs between new and old versions. 96 | git add -A . 97 | git commit -m ":robot: Deploy to GitHub Pages: ${GITHUB_SHA} from branch \"${TRAVIS_BRANCH}\"" 98 | 99 | 100 | # Now that we're all set up, we can push. 101 | git push $REPO_URL $TARGET_BRANCH 102 | -------------------------------------------------------------------------------- /issues-20210603.txt: -------------------------------------------------------------------------------- 1 | Draft: https://www.w3.org/Consortium/Process/Drafts/snapshots/2020-06-03 2 | ED: https://www.w3.org/Consortium/Process/Drafts/ 3 | Title: W3C Process 4 | Date: 2021-07-23 5 | Status: Proposed 2021 Process 6 | Intro: 7 |

8 | This disposition of comments covers the issues submitted 9 | during the AC informal review period announced on 3 June 2021, 10 | which ran through 2 July 2021, 11 | and those submitted by during AC Review and Accepted by the Director. 12 | 13 |

14 | For a more complete list of comments and issues 15 | raised since the previous edition of the process was published, 16 | please refer to Github: 17 | 18 |

24 | 25 | There's an incomplete DoC in this format for the whole 2020 to 2021 cycle in issues-20200915.txt 26 | 27 | ---- 28 | Issue 1. 29 | Summary: Clarify expectation of horizontal review as part of wide review 30 | From: Judy Brewer 31 | Comment: https://github.com/w3c/w3process/issues/535#issuecomment-854121607 32 | Response: https://github.com/w3c/w3process/issues/535#issuecomment-879943488 33 | Changes: https://github.com/w3c/w3process/commit/af51456b9fbdaba7486329fd9efa8c44fcd1e9e9 34 | Closed: Accepted 35 | ---- 36 | Issue 2. 37 | Summary: Clarify that tooling must be accessible for people with disabilities 38 | From: Judy Brewer 39 | Comment: https://github.com/w3c/w3process/issues/537 40 | Response: https://github.com/w3c/w3process/issues/537#issuecomment-857879755 41 | Changes: https://github.com/w3c/w3process/commit/0abef35f9630add41a6889d244467b530694396b 42 | Closed: Accepted 43 | ---- 44 | Issue 3. 45 | Summary: Editorial tweak to AB Composition 46 | From: Philippe Le Hégaret 47 | Comment: https://github.com/w3c/w3process/issues/540 48 | Response: https://github.com/w3c/w3process/issues/540#issuecomment-859224830 49 | Changes: https://github.com/w3c/w3process/commit/c8e0872052b91fca0f8936f21f419e352a912a20 50 | Closed: Accepted 51 | ---- 52 | Issue 4. 53 | Summary: Ensure specs and standards have published user research 54 | From: Daniel Appelquist 55 | Comment: https://github.com/w3c/w3process/issues/551 56 | Response: https://github.com/w3c/w3process/issues/551#issuecomment-872610856 57 | Closed: Deferred (Out Of Scope) 58 | ---- 59 | Issue 5. 60 | Summary: Archiving discussion attachments 61 | From: fantasai 62 | Comment: https://github.com/w3c/w3process/issues/552 63 | Closed: Deferred 64 | Verified: Reporter is editor 65 | ---- 66 | Issue 6. 67 | Summary: Misleading characterization of the Patent Policy 68 | From: Wendy Seltzer 69 | Comment: https://github.com/w3c/w3process/issues/570 70 | Response: https://github.com/w3c/w3process/pull/569 71 | Closed: Accepted 72 | Verified: Director's decision 73 | ---- 74 | Issue 7. 75 | Summary: Should not be possible to change Normative references of the Process without member approval 76 | From: James Rosewell 77 | Comment: https://lists.w3.org/Archives/Public/public-w3process/2021Aug/0006.html 78 | Response: https://github.com/w3c/w3process/pull/571 79 | Closed: Accepted 80 | Verified: Director's decision 81 | ---- 82 | Issue 8. 83 | Summary: Define how to interpret potential conflicts between the Membership Agreement, Process document and normative references 84 | From: James Rosewell 85 | Comment: https://github.com/w3c/w3process/issues/574 86 | Response: https://github.com/w3c/w3process/pull/572 87 | Closed: Deferred 88 | Verified: Director's Decision 89 | -------------------------------------------------------------------------------- /issues-20200915.txt: -------------------------------------------------------------------------------- 1 | Draft: https://www.w3.org/2020/Process-20200915/ 2 | Title: W3C Process Document 3 | Date: 2020-09-15 4 | Status: Version 5 | ED: https://www.w3.org/Consortium/Process/Drafts/ 6 | 7 | This DoC for the 2020 to 2021 cycle of the Process is not complete. 8 | 9 | ---- 10 | Issue 1. 11 | Summary: "short term" is undefined 12 | From: Coralie Mercier 13 | Comment: https://github.com/w3c/w3process/issues/333 14 | Response: https://github.com/w3c/w3process/pull/431 15 | Closed: Accepted 16 | Resolved: https://www.w3.org/2020/08/12-w3process-minutes.html#r02 17 | ---- 18 | Issue 2. 19 | Summary: Editorial tweaks 20 | From: Coralie Mercier 21 | Comment: https://github.com/w3c/w3process/issues/376 22 | Closed: Accepted 23 | Resolved: https://www.w3.org/2020/08/12-w3process-minutes.html#r02 24 | ---- 25 | Issue 3. 26 | Summary: Fix terminology mixup 27 | From: Florian Rivoal 28 | Comment: https://github.com/w3c/w3process/issues/430 29 | Closed: Accepted 30 | Resolved: https://www.w3.org/2020/08/12-w3process-minutes.html#r02 31 | ---- 32 | Issue 4. 33 | Summary: Remove Gratuitous mentions of the Director 34 | From: Florian Rivoal 35 | Comment: https://github.com/w3c/w3process/issues/254 36 | Closed: Accepted 37 | Resolved: https://www.w3.org/2020/08/12-w3process-minutes.html#r03 38 | ---- 39 | Issue 5. 40 | Summary: Re-envisioning the CRUD/Snapshot split 41 | From: Wendy Seltzer 42 | Comment: https://github.com/w3c/w3process/issues/346 43 | Closed: Rejected 44 | Resolved: https://github.com/w3c/w3process/issues/346#issuecomment-658799591 45 | Verified: https://github.com/w3c/w3process/issues/346#issuecomment-658799591 46 | ---- 47 | Issue 6. 48 | Summary: Switch plural term to singular 49 | From: Coralie Mercier 50 | Comment: https://github.com/w3c/w3process/issues/386 51 | Closed: Rejected 52 | Resolved: https://github.com/w3c/w3process/pull/386#issuecomment-658826867 53 | Verified: https://github.com/w3c/w3process/pull/386#issuecomment-658855009 54 | ---- 55 | Issue 7. 56 | Summary: Remove mentions of when various groups were created 57 | From: Florian Rivoal 58 | Comment: https://github.com/w3c/w3process/pull/420 59 | Closed: Accepted 60 | Resolved: https://github.com/w3c/w3process/pull/420#issuecomment-658813800 61 | ---- 62 | Issue 8. 63 | Summary: Editorial tweak in Superseded Recommendation note 64 | From: Tantek Çelik 65 | Comment: https://github.com/w3c/w3process/pull/445 66 | Closed: Accepted 67 | Resolved: Editor's Discretion 68 | ---- 69 | Issue 9. 70 | Summary: Reduce redundant text about how to substantively revise a REC 71 | From: Florian Rivoal 72 | Comment: https://github.com/w3c/w3process/pull/427 73 | Closed: Accepted 74 | Resolved: https://github.com/w3c/w3process/pull/427#issuecomment-672912287 75 | ---- 76 | Issue 10. 77 | Summary: Remove reference to stale document 78 | From: Florian Rivoal 79 | Comment: https://github.com/w3c/w3process/pull/274 80 | Closed: Retracted 81 | Resolved: https://github.com/w3c/w3process/pull/274#issuecomment-673288144 82 | ---- 83 | Issue 11. 84 | Summary: What does the document status "discontinued" mean? 85 | From: rduerr 86 | Comment: https://github.com/w3c/w3process/issues/262 87 | Response: https://github.com/w3c/w3process/issues/262#issuecomment-692918581 88 | Closed: Accepted 89 | Resolved: https://www.w3.org/2020/09/16-w3process-minutes.html#x047 90 | ---- 91 | Issue 12. 92 | Summary: Concerns about Amended Recommendations 93 | From: Andreas 94 | Comment: https://github.com/w3c/w3process/issues/137 95 | Response: https://github.com/w3c/w3process/pull/428 96 | Closed: Accepted 97 | Resolved: https://www.w3.org/2020/09/16-w3process-minutes.html#x030 98 | ---- 99 | Issue 13. 100 | Summary: Rename Candidate Change / Proposed Change to Candidate Amendment / Proposed Amendment 101 | From: Elika J. Etemad 102 | Comment: https://github.com/w3c/w3process/issues/449 103 | Response: https://github.com/w3c/w3process/pull/451 104 | Closed: Accepted 105 | Resolved: https://www.w3.org/2020/09/16-w3process-minutes.html#x093 106 | ---- 107 | Issue 14. 108 | Summary: Consolidate discipline-related text 109 | From: Coralie Mercier 110 | Comment: https://github.com/w3c/w3process/issues/418 111 | Comment: https://github.com/w3c/w3process/pull/432 112 | Closed: Accepted 113 | Resolved: https://github.com/w3c/w3process/pull/432#issuecomment-741839423 114 | -------------------------------------------------------------------------------- /retiring-rec.svg: -------------------------------------------------------------------------------- 1 | 2 | Supersede, Obsolete or Rescind a W3C Recommendation 3 | 4 | 5 | 6 | Recommendation (Rec) 7 | 8 | 9 | 10 | A major problem and an AC review can lead to a Recommendation being Rescinded. 11 | There are no new IPR licences issued under the W3C Patent Policy, 12 | and reinstating the Recommendation requires going through the full Rec-track process again. 13 | 14 | Major problem, AC review 15 | 16 | 17 | Rescinded Recommendation - no new IPR licenses 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | With little uptake, following AC review a specification may become an Obsolete Recommendation 27 | 28 | 29 | 30 | 31 | Obsolete Recommendation 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | If there is new uptake, with AC review an Obsolete Recommendation may return to normal Recommendation status 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | Replaced by a new version, AC review 52 | 53 | Superseded Recommendation 54 | 55 | 56 | 57 | 58 | 59 | 60 | A Superseded Recommendation can become a normal Recommendation with AC review 61 | 62 | 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | -------------------------------------------------------------------------------- /snapshots/2021-07-23-doc.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | W3C Process Disposition of Comments for 2021-07-23 Proposed 2021 Process 4 | 12 | 13 |

W3C Process Disposition of Comments for 2021-07-23 Proposed 2021 Process

14 | 15 |

Review document: https://www.w3.org/Consortium/Process/Drafts/snapshots/2020-06-03 16 | 17 |

Editor's draft: https://www.w3.org/Consortium/Process/Drafts/ 18 | 19 |

20 | This disposition of comments covers the issues submitted 21 | during the AC informal review period announced on 3 June 2021, 22 | which ran through 2 July 2021. 23 | 24 |

25 | For a more complete list of comments and issues 26 | raised since the previous edition of the process was published, 27 | please refer to Github: 28 | 29 |

35 | 36 |

The following color coding convention is used for comments:

37 | 38 | 45 | 46 |

Open issues are marked like this

47 | 48 |

An issue can be closed as Accepted, OutOfScope, 49 | Invalid, Rejected, or Retracted. 50 | Verified indicates commentor's acceptance of the response.

51 | 
 52 | Issue 1. #
 53 | Summary:  Clarify expectation of horizontal review as part of wide review
 54 | From:     Judy Brewer
 55 | Comment:  https://github.com/w3c/w3process/issues/535#issuecomment-854121607
 56 | Response: https://github.com/w3c/w3process/issues/535#issuecomment-879943488
 57 | Changes:  https://github.com/w3c/w3process/commit/af51456b9fbdaba7486329fd9efa8c44fcd1e9e9
 58 | Closed:   Accepted
59 | 
 60 | Issue 2. #
 61 | Summary:  Clarify that tooling must be accessible for people with disabilities
 62 | From:     Judy Brewer
 63 | Comment:  https://github.com/w3c/w3process/issues/537
 64 | Response: https://github.com/w3c/w3process/issues/537#issuecomment-857879755
 65 | Changes:  https://github.com/w3c/w3process/commit/0abef35f9630add41a6889d244467b530694396b
 66 | Closed:   Accepted
67 | 
 68 | Issue 3. #
 69 | Summary:  Editorial tweak to AB Composition
 70 | From:     Philippe Le Hégaret
 71 | Comment:  https://github.com/w3c/w3process/issues/540
 72 | Response: https://github.com/w3c/w3process/issues/540#issuecomment-859224830
 73 | Changes:  https://github.com/w3c/w3process/commit/c8e0872052b91fca0f8936f21f419e352a912a20
 74 | Closed:   Accepted
75 | 
 76 | Issue 4. #
 77 | Summary:  Ensure specs and standards have published user research
 78 | From:     Daniel Appelquist
 79 | Comment:  https://github.com/w3c/w3process/issues/551
 80 | Response: https://github.com/w3c/w3process/issues/551#issuecomment-872610856
 81 | Closed:   Deferred (Out of Scope)
82 | 
 83 | Issue 5. #
 84 | Summary:  Archiving discussion attachments
 85 | From:     fantasai
 86 | Comment:  https://github.com/w3c/w3process/issues/552
 87 | Closed:   Deferred
 88 | Verified: Reporter is editor
89 | 120 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing to the W3C Process Document 2 | Thank-you for offering to contribute to the [W3C Process Document](https://www.w3.org/policies/process/). Here we provide some details on how you can contribute. 3 | 4 | Changes to the process document tend to fall into a few classes, and how the W3C handles these varies. Simple editorial changes may require little review, but more substantial changes will require a more substantial review and discussions by the W3C community. Please read the material below, and get involved as explained. 5 | 6 | If you have any questions, please [raise an issue](/../../issues). 7 | 8 | ## Simple Editorial Changes 9 | For simple editorial changes, please feel free to raise a `pull request` or [raise an issue](/../../issues) on this repository. A simple editorial change can be things like spelling and grammar mistakes, broken links, and so on. 10 | 11 | Some changes may appear simple but may actually be more complicated than they appear. Don't worry - please continue to send your `pull request` or [raise an issue](/../../issues) and we can discuss. 12 | 13 | ## The W3C Process Community Group 14 | The W3C runs a [Process Community Group](https://www.w3.org/community/w3process/), which is an open group created to manage discussions on developing the [W3C Process Document](https://www.w3.org/policies/process/). Some suggestions for changes to the [W3C Process Document](https://www.w3.org/policies/process/) will need to be made within the [Process Community Group](https://www.w3.org/community/w3process/), please see information below as to whether you need to take your suggestions to the group or can just raise a `pull request` or `issue`. 15 | 16 | ## Changes that Affect the Way the W3C Operates but Do Not Change the Policy 17 | For changes that affect the way that the W3C operates but do not change policy please do the following: 18 | 19 | * [Raise an issue](/../../issues) on this repo 20 | * Make sure the [Process Community Group](https://www.w3.org/community/w3process/) adds the issue to its agenda. This will allow you to explain why you think this is an improvement to the operation of the W3C (it's probably not helpful to provide a Pull Request until you have consensus on the approach). 21 | 22 | The best way to ensure your issue gets added to the [Process Community Group](https://www.w3.org/community/w3process/) agenda is to add yourself to the group, please visit [the group homepage](https://www.w3.org/community/w3process/) and select the button "Join or Leave this Group". 23 | 24 | Another way to ensure the [Process Community Group](https://www.w3.org/community/w3process/) addressed your issue is to check back on the [issues page](/../../issues) page and ask whether it has been addressed. It is more effective to join the group, but you have this option if you need it. 25 | 26 | The [Process Community Group](https://www.w3.org/community/w3process/) will discuss your issue, and decide whether the change can be made or whether the issue needs to be brought to the [Advisory Board](https://www.w3.org/policies/process/#AB) or [Advisory Committee](https://www.w3.org/policies/process/#AC) for discussion; see the next section for more information on this process. 27 | 28 | If the [Process Community Group](https://www.w3.org/community/w3process/) agrees the issue does not change the policy and agrees to make the changes detailed in your issue, you may either raise a `pull request` or wait for the Editor to make the required changes. Note: raising a `pull request` **will** be faster. See more details about `pull requests` below. 29 | 30 | ## Changes that Affect the Way the W3C Operates and Change the Policy 31 | For changes that represent a change of policy in the W3C, the idea will need to be brought to the [Advisory Board](https://www.w3.org/2002/ab/) or [Advisory Committee](https://www.w3.org/participate/meetings). Again, a Pull Request can wait until you have gained consensus with these two committees. 32 | 33 | You can raise the issue with the [Process Community Group](https://www.w3.org/community/w3process/), and you can suggest (or they will notice) that it needs policy discussion and refer it onwards. But you may prefer to initiate that discussion yourself. 34 | 35 | Getting something in front of both the [Advisory Board](https://www.w3.org/policies/process/#AB) or [Advisory Committee](https://www.w3.org/policies/process/#AC) can be tricky. If your organisation is a W3C member please let your Advisory Committee member know; they will then be able to email the Advisory Committee or bring the issue up at an Advisory Committee meeting. To reach the [Advisory Board](https://www.w3.org/2002/ab/) you can [raise an issue](/../../issues) on this repo (at least two AB members monitor this repo) or send an email to ab@w3.org. 36 | 37 | Gaining consensus from the [Advisory Board](https://www.w3.org/2002/ab/) or [Advisory Committee](https://www.w3.org/participate/meetings) will take some time. After consensus has been reached you may either raise a `pull request` which include the changes agreed by these committees or wait for the Editor to make the required changes. See more details about `pull requests` below. 38 | 39 | ## Edit and Pull Request Instructions 40 | To make an edit to the document simply edit the [`index.bs`](index.bs) file 41 | and send a pull request when your changes are done. 42 | This document is maintained using [Bikeshed](https://tabatkins.github.io/bikeshed/). 43 | See the [section about markup](https://tabatkins.github.io/bikeshed/#markup-shortcuts) in Bikeshed's documentation 44 | for full details about the syntax. 45 | 46 | **Only the source (`index.bs`) should be committed**, 47 | as this repository is configured to run bikeshed server-side and push the result to the gh-pages branch. 48 | 49 | If you want to run Bikeshed locally to check the results of your edits before committing or sending a pull request, 50 | follow [the installation instructions](https://tabatkins.github.io/bikeshed/#installing) in Bikeshed's documentation. 51 | Once Bikeshed is installed, just type `bikeshed` to generate `index.html` from `index.bs`. 52 | 53 | If you have the rights to edit this repo your edits will need to be made on a new branch. If you do not have the rights to edit this repo please `fork` the repo, make your edits, then send a `pull request`. 54 | 55 | Pull Requests should result in a correct-looking document (formats and lays out correctly). 56 | 57 | ## Notes 58 | Please feel free to suggest how this document can improve by [raising an issue](/../../issues) on this repo. 59 | -------------------------------------------------------------------------------- /basic-rec-track.svg: -------------------------------------------------------------------------------- 1 | 2 | Basic W3C Recommendation Track 3 | 4 | 5 | 6 | 7 | 8 | 9 | First Public Working Draft (FPWD) - Exclusion opportunity 10 | 11 | 12 | 13 | WG Decision + 14 | Team Approval 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | Working Draft (WD) 25 | 26 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | Publish a new Working Draft 35 | 36 | 37 | WG Decision 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | Advance to Candidate Recommendation 48 | 49 | WG Decision + 50 | Team Approval 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | Candidate Recommendation Snapshot (CRS) - Patent Policy exclusion opportunity 62 | 63 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | Publish revised Candidate Recommendation Draft 72 | 73 | 74 | WGDecision 75 | 76 | 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | Publish revised Candidate Recommendation Snapshot 85 | 86 | 87 | WG Decision 88 | Team Approval 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | Advance to Recommendation 98 | 99 | WG Decision + 100 | Team Approval + 101 | AC Review 102 | 103 | 104 | 105 | 106 | 107 | 108 | 109 | 110 | Return to Working Draft 111 | 112 | 113 | WG Decision 114 | (or Team Decision with AB+TAG Approval) 115 | 116 | 117 | 118 | 119 | 120 | 121 | 122 | 123 | 124 | 125 | 126 | Candidate Recommendation Draft (CRD) 127 | 128 | 130 | 131 | 132 | 133 | 134 | 135 | 136 | Publish revised Candidate Recommendation Draft 137 | 138 | 139 | WG Decision 140 | 141 | 142 | 143 | 144 | 145 | 146 | 147 | 148 | 149 | Publish revised Candidate Recommendation Snapshot 150 | 151 | 152 | WG Decision + 153 | Team Approval 154 | 155 | 156 | 157 | 158 | 159 | 160 | 161 | 162 | 163 | 164 | 165 | Recommendation 166 | 167 | 169 | 170 | 171 | 172 | 173 | 174 | 175 | Return to Candidate Recommendation Snapshot 176 | 177 | 178 | WG Decision 179 | (or Team Decision 180 | with AB+TAG 181 | Approval) 182 | 183 | 184 | 185 | 186 | 187 | 188 | 189 | 190 | 191 | Return to Working Draft 192 | 193 | 194 | WG Decision 195 | (or Team Decision 196 | with AB+TAG 197 | Approval) 198 | 199 | 200 | 201 | 202 | 203 | 204 | 205 | 206 | 207 | Publish revised Recommendation with editorial changes 208 | 209 | 210 | WG Decision 211 | (editorial) 212 | 213 | 214 | 215 | 216 | 217 | 218 | 219 | 220 | 221 | Publish revised Recommendation with substantive changes 222 | 223 | 224 | WG Decision + 225 | Team Approval + 226 | AC Review 227 | (substantive) 228 | 229 | 230 | 231 | 232 | 233 | 234 | 235 | 236 | 237 | -------------------------------------------------------------------------------- /snapshots/2023-04-faq.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | Process 2023 FAQ 8 | 9 |
10 |

11 |

Process 2023 FAQ

12 |

13 |

Copyright © 2023 World Wide Web Consortium. W3C® liability, trademark and permissive document license rules apply. 14 |

15 |
16 | 17 | 27 | 28 |

29 | 1. 30 | Why a Council and not some other option?

31 | 32 |

33 | Various other options were considered, 34 | but all were found to have more downsides than a Council-based approach. 35 | Among the many variants discussed, the following are notable: 36 | 37 |

68 | 69 |

70 | We combined the AB (process expertise) and TAG (technical expertise), 71 | who are both AC-elected (community legitimacy) 72 | with the CEO (to represent the Team perspective) 73 | to create the Council, 74 | with the intention that this 21-person combined team would sufficiently balance itself out 75 | to provide high quality resolution of FOs consistent with the values of W3C. 76 | 77 |

78 | 2. 79 | Why (group-voted) dismissal rather than (self-chosen or automatic) recusal?

80 | 81 |

82 | There are a few problems with recusals: 83 |

123 | 124 |

125 | Lastly, we've found through our experiences in the experimental Councils 126 | that the Council process works quite well in practice: 127 | in every instance where some participants in the Council could be seen as having a strong stake in the decision, 128 | they were deliberately deferential, 129 | and contributed their perspective to the debate without any attempt at steering the group in a particular direction. 130 | 131 |

132 | 3. 133 | Why has the Council been so awfully slow?

134 | 135 |

136 | The AB, TAG, and Team apologize for the delays, 137 | and recognize the need to do better. 138 | We’ve been learning, making mistakes, and improving, 139 | and anticipate a faster response time going ahead. 140 | 141 |

142 | The Council was introduced as an experiment under delegation from the Director, 143 | and has been evolving over the duration of the experiment. 144 | While it started slow, a number of things have changed to make it faster. 145 | 146 |

197 | 198 |

199 | It is also worth noting that a large part of the Council experiment period 200 | overlapped with the ramp up to the launch of W3C as a legal entity, 201 | during which both the AB and the Team were overloaded with important and urgent matters, 202 | leaving less time that would have otherwise been appropriate for Formal Objection resolution. 203 | 204 |

205 | 4. 206 | What about chartering?

207 | 208 |

209 | Formally, the Director has been in charge of initiating AC Review of new charters 210 | and interpreting the results. 211 | In practice, 212 | this task has been long been delegated to the Team. 213 | Therefore what this Process proposal encodes 214 | is merely the practice we've been running under for years: 215 | that the Team initiates charter reviews, 216 | and abides by the results of AC reviews. 217 | We have, however, tightened up how AC reviews are conducted 218 | and what outcomes may come of them. 219 | 220 |

221 | There is a clear sense that more transparency and Member involvement in chartering is desired, 222 | and the Team is making improvements in this direction informally 223 | through changes in their practices and guidelines. 224 | However, we weren't ready yet to make additional concrete changes to the Process itself for 2023 225 | (though we anticipate this discussion to continue into a future Process revision cycle). 226 | 227 |

For now, the proposed Process, 228 | aside from recognizing that it is the Team, 229 | not the Director, 230 | that moves chartering along, 231 | is not different from current practice, 232 | and thus no worse. 233 | 234 |

235 | 5. 236 | What about a NomComm for the TAG?

237 | 238 |

239 | Diversity and representation are considered especially important in the TAG, 240 | to ensure an ability to handle any technical topic from any industry. 241 | Some proposed that using a Nominating Committee (NomComm) would be a good way to accomplish that, 242 | and an earlier revision of the Director-free Process did in fact have a NomComm 243 | randomly selected (mostly) from the set of WG chairs. 244 | However the TAG felt this was too complicated 245 | (and it was, in fact, quite complicated 246 | once all the details were worked in), 247 | and asked the AB to simply have the Team make the appointments with the input of the community. 248 | This enables the kind of deliberate balancing that a NomComm would provide 249 | and avoids a lot of complexity 250 | 251 |

252 | As a safety measure, 253 | we added a 2/3 ratification step by both the TAG and the AB 254 | to ensure the Team appointments are acceptable to the community; 255 | and a term limit of two consecutive appointments to ensure the Team doesn't simply re-appoint old members as a habit. 256 | 257 |

258 | Note the TAG appointment process has also been moved to be after the election, 259 | in order to allow the appointments to serve their intended purpose of balancing out the elected TAG. 260 | -------------------------------------------------------------------------------- /issues-20180201.txt: -------------------------------------------------------------------------------- 1 | Draft: https://www.w3.org/2018/Process-20180201/ 2 | Title: W3C Process Document 3 | Date: 2018-02-01 4 | Status: Version 5 | ED: https://www.w3.org/Consortium/Process/Drafts/ 6 | 7 | No Disposition of Comments was produced for versions of the Process Prior to this one. 8 | Issues in Github (and other trackers) closed prior to the 2018-02-01 will not be documented individually, 9 | except that issues closed before that date 10 | but still during the period during which the 2018 Process was being finalized are included 11 | (i.e. from mid December 2017). 12 | 13 | ---- 14 | Issue 1. 15 | Summary: Contraints on participation to the AB and TAG are confusingly phrased. 16 | From: Fuqiao Xue 17 | Comment: https://github.com/w3c/w3process/pull/229 18 | Response: https://github.com/w3c/w3process/pull/229#issuecomment-439770518 19 | Response: https://github.com/w3c/w3process/pull/231 20 | Closed: Accepted 21 | Resolved: https://lists.w3.org/Archives/Public/public-w3process/2018Dec/0013.html 22 | ---- 23 | Issue 2. 24 | Summary: Introduce voting for "No Other Candidate" in the Process and describe effects. 25 | From: Michael Champion 26 | Comment: https://github.com/w3c/w3process/issues/47 27 | Closed: Rejected (no consensus) 28 | Verified: https://github.com/w3c/w3process/issues/47#issuecomment-442693572 29 | Resolved: AB Resolution at 2018 Tokyo F2F 30 | ---- 31 | Issue 3. 32 | Summary: Clarify meaning of require specs to be "REC ready" in order to enter CR. 33 | From: Nigel Meggit 34 | Comment: https://github.com/w3c/w3process/issues/172 35 | Comment: https://github.com/w3c/w3process/pull/181 36 | Response: https://github.com/w3c/w3process/pull/214 37 | Closed: Accepted 38 | Resolved: https://github.com/w3c/w3process/pull/214#issuecomment-439231629 39 | ---- 40 | Issue 4. 41 | Summary: What are the requirements to update a CR? 42 | From: Florian Rivoal 43 | Comment: https://github.com/w3c/w3process/issues/172#issuecomment-413196028 44 | Comment: https://github.com/w3c/w3process/issues/207 45 | Response: https://github.com/w3c/w3process/pull/215 46 | Closed: Accepted 47 | Resolved: https://github.com/w3c/w3process/pull/215#issuecomment-439232516 48 | ---- 49 | Issue 5. 50 | Summary: Should the AB and maybe TAG have lower/upper bounds for membership? 51 | From: David Singer 52 | Comment: https://github.com/w3c/w3process/issues/204 53 | Comment: https://github.com/w3c/w3process/pull/216 54 | Response: https://github.com/w3c/w3process/pull/224 55 | Closed: Accepted 56 | Resolved: https://github.com/w3c/w3process/pull/224#issuecomment-439231292 57 | ---- 58 | Issue 6. 59 | Summary: Document Common Standards Issues. 60 | From: Natasha Rooney 61 | Comment: https://github.com/w3c/w3process/issues/201 62 | Response: https://github.com/w3c/w3process/issues/201#issuecomment-442688505 63 | Closed: OutOfScope 64 | Resolved: AB Resolution at 2018 Tokyo F2F 65 | Verified: Issue submitter present when taking the resolution 66 | ---- 67 | Issue 7. 68 | Summary: Policy on use of W3C's github repo. 69 | From: Karen Coyle 70 | Comment: https://github.com/w3c/w3process/issues/194 71 | Response: https://github.com/w3c/w3process/issues/194#issuecomment-442688266 72 | Closed: OutOfScope 73 | Resolved: AB Resolution at 2018 Tokyo F2F 74 | ---- 75 | Issue 8. 76 | Summary: Policy on use of W3C's github repo. 77 | From: Karen Coyle 78 | Comment: https://github.com/w3c/w3process/issues/194 79 | Response: https://github.com/w3c/w3process/issues/194#issuecomment-442688266 80 | Closed: OutOfScope 81 | Resolved: AB Resolution at 2018 Tokyo F2F 82 | ---- 83 | Issue 9. 84 | Summary: Address/recognize funding barriers to elected bodies? 85 | From: Brian Kardell 86 | Comment: https://github.com/w3c/w3process/issues/189 87 | Response: https://github.com/w3c/w3process/issues/189#issuecomment-442688245 88 | Closed: OutOfScope 89 | Resolved: AB Resolution at 2018 Tokyo F2F 90 | ---- 91 | Issue 10. 92 | Summary: AB and TAG nominations should be announced as they occur and not wait until close of noms. 93 | From: David Singer 94 | Comment: https://github.com/w3c/w3process/issues/193 95 | Closed: Rejected (no consensus) 96 | Resolved: AB Resolution at 2018 Tokyo F2F 97 | Verified: Issue submitter present when taking the resolution 98 | ---- 99 | Issue 11. 100 | Summary: Should we have term limits for the AB (and possibly TAG)? 101 | From: Tantek Çelik 102 | Comment: https://github.com/w3c/w3process/issues/165 103 | Closed: Rejected (no consensus) 104 | Resolved: AB Resolution at 2018 Tokyo F2F 105 | ---- 106 | Issue 12. 107 | Summary: Should we use a NomCom? 108 | From: David Singer 109 | Comment: https://github.com/w3c/w3process/issues/31 110 | Closed: Duplicate 111 | Resolved: AB Resolution at 2018 Tokyo F2F 112 | Verified: Issue submitter present when taking the resolution 113 | ---- 114 | Issue 13. 115 | Summary: "Implementation experience" description should clearly identify likelihood of broad acceptance? 116 | From: Erik Anderson 117 | Comment: https://github.com/w3c/w3process/issues/32 118 | Closed: Rejected 119 | Resolved: AB Resolution at 2018 Tokyo F2F 120 | ---- 121 | Issue 14. 122 | Summary: Correct unclear phrasing that seems to limit W3C staff participation. 123 | From: Wendy Seltzer 124 | Comment: https://github.com/w3c/w3process/issues/208 125 | Response: https://github.com/w3c/w3process/pull/220 126 | Comment: https://github.com/w3c/w3process/issues/208#issuecomment-438494615 127 | Response: https://github.com/w3c/w3process/pull/227 128 | Closed: Accepted 129 | Resolved: https://github.com/w3c/w3process/pull/227#issuecomment-439230846 130 | ---- 131 | Issue 15. 132 | Summary: Clarify that written notifications must be recorded. 133 | From: Léonie Watson 134 | Comment: https://github.com/w3c/w3process/issues/83 135 | Response: https://github.com/w3c/w3process/pull/184 136 | Response: https://github.com/w3c/w3process/pull/188 137 | Closed: Accepted 138 | Resolved: https://github.com/w3c/w3process/issues/83#issuecomment-421185430 139 | ---- 140 | Issue 16. 141 | Summary: W3C should be more transparent. 142 | From: Natasha Rooney 143 | Comment: https://github.com/w3c/w3process/issues/116 144 | Response: https://github.com/w3c/w3process/issues/116#issuecomment-425364651 145 | Closed: Invalid 146 | Resolved: https://www.w3.org/2018/10/03-w3process-minutes.html 147 | ---- 148 | Issue 17. 149 | Summary: Document relationship between W3C and CG/BGs. 150 | From: Charles McCathie Nevile 151 | Comment: https://www.w3.org/community/w3process/track/issues/130 152 | Comment: https://github.com/w3c/w3process/issues/17 153 | Comment: https://github.com/w3c/w3process/issues/180 154 | Response: https://github.com/w3c/w3process/pull/221 155 | Closed: Accepted 156 | Resolved: https://www.w3.org/2018/10/03-w3process-minutes.html 157 | ---- 158 | Issue 18. 159 | Summary: Should participants in Working Groups be allowed to represent more than one organisation? 160 | From: Charles McCathie Nevile 161 | Comment: https://github.com/w3c/w3process/issues/9 162 | Comment: https://github.com/w3c/w3process/pull/54 163 | Response: https://github.com/w3c/w3process/pull/219 164 | Closed: Accepted 165 | Resolved: https://www.w3.org/2018/10/03-w3process-minutes.html 166 | ---- 167 | Issue 19. 168 | Summary: Text about member submissions seems to deny CGs as a way to start work. 169 | From: Jeff Jaffe 170 | Comment: https://github.com/w3c/w3process/issues/169 171 | Response: https://github.com/w3c/w3process/pull/212 172 | Closed: Accepted 173 | Resolved: https://www.w3.org/2018/10/03-w3process-minutes.html 174 | ---- 175 | Issue 20. 176 | Summary: Make sure "First Public Working Draft" is defined. 177 | From: Natasha Rooney 178 | Comment: https://github.com/w3c/w3process/issues/155 179 | Response: https://github.com/w3c/w3process/pull/211 180 | Closed: Accepted 181 | Resolved: https://www.w3.org/2018/10/03-w3process-minutes.html 182 | ---- 183 | Issue 21. 184 | Summary: Introduce Hard Requirements for Security, Privacy, Internationalisation and Accessibility Considerations. 185 | From: Natasha Rooney 186 | Comment: https://github.com/w3c/w3process/issues/117 187 | Response: https://github.com/w3c/w3process/issues/117#issuecomment-425362762 188 | Closed: Rejected 189 | Resolved: https://www.w3.org/2018/10/03-w3process-minutes.html 190 | Verified: Issue submitter is co-editor and member of the AB, did not push back 191 | ---- 192 | Issue 22. 193 | Summary: *Imediately* vacate AB seats when participation constrains are no longer met. 194 | From: David Singer 195 | Comment: https://github.com/w3c/w3process/issues/175 196 | Resolved https://github.com/w3c/w3process/pull/186 197 | Closed: Rejected 198 | Resolved: https://www.w3.org/2018/08/15-w3process-minutes.html 199 | Verified: https://github.com/w3c/w3process/pull/186#issuecomment-420506209 200 | ---- 201 | Issue 23. 202 | Summary: Define "transition request". 203 | From: Samuel Weiler 204 | Comment: https://github.com/w3c/w3process/issues/160 205 | Response: https://github.com/w3c/w3process/pull/195 206 | Closed: Accepted 207 | Resolved: https://github.com/w3c/w3process/pull/195#pullrequestreview-155154661 208 | ---- 209 | Issue 24. 210 | Summary: Clarify dual affiliation for non-members at the TAG/AB. 211 | From: Yves Lafon 212 | Comment: https://github.com/w3c/w3process/issues/163 213 | Response: https://github.com/w3c/w3process/pull/185 214 | Closed: Accepted 215 | Resolved: https://www.w3.org/2018/06/13-w3process-minutes.html 216 | ---- 217 | Issue 25. 218 | Summary: Increase membership of the AB. 219 | From: Chris Wilson 220 | Comment: https://github.com/w3c/w3process/issues/190 221 | Response: https://github.com/w3c/w3process/pull/202 222 | Closed: Accepted 223 | Resolved: https://www.w3.org/2018/09/12-w3process-minutes.html 224 | ---- 225 | Issue 26. 226 | Summary: The term "Affiliation" is used in several places but not strictly defined. 227 | From: Chris Wilson 228 | Comment: https://github.com/w3c/w3process/issues/176 229 | Response: https://github.com/w3c/w3process/pull/203 230 | Closed: Accepted 231 | Resolved: https://www.w3.org/2018/09/12-w3process-minutes.html 232 | ---- 233 | Issue 27. 234 | Summary: Clarify the handling contributions from guests, non-w3c members, and non-WG members. 235 | From: David Singer 236 | Comment: https://github.com/w3c/w3process/issues/67 237 | Response: https://github.com/w3c/w3process/pull/196 238 | Response: https://github.com/w3c/w3process/pull/200 239 | Response: https://github.com/w3c/w3process/pull/222 240 | Closed: Accepted 241 | Resolved: https://www.w3.org/2018/09/12-w3process-minutes.html 242 | ---- 243 | Issue 28. 244 | Summary: Review TAG Election / Appointment Process, Role of the Director. 245 | From: Natasha Rooney 246 | Comment: https://github.com/w3c/w3process/issues/118 247 | Closed: OutOfScope 248 | Resolved: https://github.com/w3c/w3process/issues/118#issuecomment-365680504 249 | Verified: https://github.com/w3c/w3process/issues/118#issuecomment-365680643 250 | ---- 251 | Issue 29. 252 | Summary: Improve Errata management in W3C. 253 | From: Jeff Jaffe 254 | Comment: https://www.w3.org/community/w3process/track/issues/141 255 | Comment: https://github.com/w3c/w3process/issues/5 256 | Closed: Invalid (too broad) 257 | ---- 258 | Issue 30. 259 | Summary: What are the rights and obligations of non-member participants in the creation of a member submission? 260 | From: Charles McCathie Nevile 261 | Comment: https://www.w3.org/community/w3process/track/issues/139 262 | Comment: https://github.com/w3c/w3process/issues/19 263 | Response: https://github.com/w3c/w3process/issues/19#issuecomment-356677702 264 | Closed: Accepted 265 | ---- 266 | Issue 31. 267 | Summary: Chairs are asking for clarification for Wide Review. 268 | From: Jeff Jaffe 269 | Comment: https://www.w3.org/community/w3process/track/issues/144 270 | Comment: https://github.com/w3c/w3process/issues/7 271 | Response: https://github.com/w3c/w3process/issues/7#issuecomment-356673617 272 | Closed: OutOfScope 273 | ---- 274 | Issue 32. 275 | Summary: href for Candidate Rec link is broken fragment. 276 | From: Nigel Megitt 277 | Comment: https://github.com/w3c/w3process/issues/171 278 | Response: https://github.com/w3c/w3process/pull/187 279 | Closed: Accepted 280 | Resolved: https://github.com/w3c/w3process/pull/187#pullrequestreview-154758502 281 | ---- 282 | Issue 33. 283 | Summary: Enforce Process Working Group and Interest Group charter extension. 284 | From: Virginia Fournier 285 | Comment: https://github.com/w3c/w3process/issues/177 286 | Response: https://github.com/w3c/w3process/issues/177#issuecomment-420434103 287 | Closed: OutOfScope 288 | ---- 289 | Issue 34. 290 | Summary: Remove duplication of Text. 291 | From: Léonie Watson 292 | Comment: https://github.com/w3c/w3process/issues/86 293 | Comment: https://github.com/w3c/w3process/pull/197 294 | Response: https://github.com/w3c/w3process/issues/86#issuecomment-413172927 295 | Closed: Retracted (in favor of https://github.com/w3c/w3process/issues/198) 296 | ---- 297 | Issue 35. 298 | Summary: Define "independent". 299 | From: Nigel Meggit 300 | Comment: https://github.com/w3c/w3process/issues/167 301 | Response: https://github.com/w3c/w3process/issues/167#issuecomment-380498842 302 | Response: https://github.com/w3c/w3process/issues/167#issuecomment-380511138 303 | Closed: Deferred 304 | Resolved: https://github.com/w3c/w3process/issues/167#issuecomment-447038484 305 | Verified: https://github.com/w3c/w3process/issues/167#issuecomment-445755075 306 | ---- 307 | Issue 36. 308 | Summary: Should TAG appointees be automatically nominated for the next TAG election when their term expires? 309 | From: David Singer 310 | Comment: https://github.com/w3c/w3process/issues/166 311 | Response: https://github.com/w3c/w3process/issues/166#issuecomment-380511537 312 | Closed: Retracted 313 | ---- 314 | Issue 37. 315 | Summary: The team/director should be removed from being in-loop on spec. obsoletion. 316 | From: David Signer 317 | Comment: https://github.com/w3c/w3process/issues/174 318 | Response: https://github.com/w3c/w3process/issues/174#issuecomment-380503764 319 | Closed: Retracted 320 | ---- 321 | Issue 38. 322 | Summary: Proposed text change for TAG, AB vacated seat. 323 | From: Natasha Rooney 324 | Comment: https://github.com/w3c/w3process/issues/179 325 | Response: https://github.com/w3c/w3process/issues/179#issuecomment-378280008 326 | Closed: Retracted 327 | ---- 328 | Issue 39. 329 | Summary: Claim the the Process can be updated as a REC is meaningless. 330 | From: Charles McCathie Nevile 331 | Comment: https://github.com/w3c/w3process/issues/146 332 | Response: https://github.com/w3c/w3process/pull/147 333 | Closed: Accepted 334 | Resolved: https://github.com/w3c/w3process/pull/147#issuecomment-371950509 335 | ---- 336 | Issue 40. 337 | Summary: Fix leftover phrasing about CR/PR AC review. 338 | From: Philippe Le Hegaret 339 | Comment: https://github.com/w3c/w3process/issues/34#issuecomment-371202943 340 | Response: https://github.com/w3c/w3process/pull/170 341 | Closed: Accepted 342 | Resolved: Editor determined consensus 343 | ---- 344 | Issue 41. 345 | Summary: Allow reduction in charter scope without AC Review. 346 | From: Carine Bournez 347 | Comment: https://github.com/w3c/w3process/issues/142 348 | Response: https://github.com/w3c/w3process/issues/142#issuecomment-367402614 349 | Closed: Rejected 350 | Resolved: https://github.com/w3c/w3process/issues/142#event-1485191962 351 | Verified: https://github.com/w3c/w3process/issues/142#issuecomment-445521296 352 | ---- 353 | Issue 42. 354 | Summary: Require a super Majority for Appeal. 355 | From: Christopher Allen 356 | Comment: https://github.com/w3c/w3process/issues/131 357 | Response: https://github.com/w3c/w3process/issues/131#issuecomment-367400103 358 | Closed: Rejected 359 | ---- 360 | Issue 43. 361 | Summary: Is there a rationale for relying on GitHub? 362 | From: Reto Gmür 363 | Comment: https://github.com/w3c/w3process/issues/132 364 | Response: https://github.com/w3c/w3process/issues/132#issuecomment-353405492 365 | Closed: OutOfScope 366 | ---- 367 | Issue 44. 368 | Summary: Do we audit which members actually have an AC Rep? 369 | From: Terence Eden 370 | Comment: https://github.com/w3c/w3process/issues/107 371 | Response: https://github.com/w3c/w3process/issues/107#issuecomment-332900963 372 | Closed: OutOfScope 373 | ---- 374 | Issue 45. 375 | Summary: Do we need clearer the requirements be for specifications produced by more than one WG. 376 | From: Liam Quin 377 | Comment: https://www.w3.org/community/w3process/track/issues/93 378 | Comment: https://github.com/w3c/w3process/issues/2 379 | Response: https://github.com/w3c/w3process/issues/2#issuecomment-323383639 380 | Closed: Accepted (Nothing to do) 381 | ---- 382 | Issue 46. 383 | Summary: Process CG should have a CONTRIBUTING.md file. 384 | From: Charles McCathie Nevile 385 | Comment: https://github.com/w3c/w3process/issues/156 386 | Response: https://github.com/w3c/w3process/pull/162 387 | Closed: Accepted 388 | Resolved: https://github.com/w3c/w3process/pull/162#issuecomment-365390113 389 | ---- 390 | Issue 47. 391 | Summary: Fix typo 392 | From: Natasha Rooney 393 | Comment: https://github.com/w3c/w3process/issues/161 394 | Response: https://github.com/w3c/w3process/pull/162 395 | Closed: Accepted 396 | Resolved: https://github.com/w3c/w3process/pull/162#issuecomment-365390113 397 | ---- 398 | Issue 48. 399 | Summary: When are tests required? 400 | From: Nigel Meggit 401 | Comment: https://github.com/w3c/w3process/issues/129 402 | Response: https://github.com/w3c/w3process/issues/129#issuecomment-358285243 403 | Closed: Deferred 404 | ---- 405 | Issue 49. 406 | Summary: What happens if one wishes to update, delete, or replace a member submission? 407 | From: David Cramer 408 | Comment: https://github.com/w3c/w3process/issues/154 409 | Response: https://github.com/w3c/w3process/issues/154#issuecomment-354342898 410 | Response: https://github.com/w3c/w3process/issues/154#issuecomment-355441019 411 | Closed: OutOfScope 412 | ---- 413 | Issue 50. 414 | Summary: Redefine what "Consensus" means. 415 | From: Joakim Hedlund 416 | Comment: https://github.com/w3c/w3process/pull/101 417 | Response: https://github.com/w3c/w3process/pull/101#issuecomment-331278884 418 | Closed: Rejected 419 | Verified: https://github.com/w3c/w3process/pull/101#issuecomment-365686583 420 | ---- 421 | Issue 51. 422 | Summary: Revert accidental substantive change made during editorial commit. 423 | From: Elika Etemad 424 | Comment: https://lists.w3.org/Archives/Public/public-w3process/2018Nov/0014.html 425 | Response: https://github.com/w3c/w3process/pull/228 426 | Closed: Accepted 427 | Resolved: https://github.com/w3c/w3process/pull/228#issuecomment-439231058 428 | ---- 429 | Issue 52. 430 | Summary: Fix typo 431 | From: Chris Wilson 432 | Comment: https://github.com/w3c/w3process/pull/226 433 | Closed: Accepted 434 | Resolved: https://github.com/w3c/w3process/pull/226#issuecomment-437087491 435 | ---- 436 | Issue 53. 437 | Summary: Editorial clarification 438 | From: Wendy Seltzer 439 | Comment: https://github.com/w3c/w3process/pull/210 440 | Response: https://github.com/w3c/w3process/pull/210#issuecomment-425347032 441 | Closed: Accepted 442 | Resolved: Editor determined consensus 443 | ---- 444 | Issue 54. 445 | Summary: Editorial clarification. 446 | From: Wendy Seltzer 447 | Comment: https://github.com/w3c/w3process/pull/210 448 | Response: https://github.com/w3c/w3process/pull/210#issuecomment-425347032 449 | Closed: Accepted 450 | Resolved: Editor determined consensus 451 | ---- 452 | Issue 55. 453 | Summary: Grammar Fix. 454 | From: Wendy Seltzer 455 | Comment: https://github.com/w3c/w3process/pull/209 456 | Closed: Accepted 457 | Resolved: Editor determined consensus 458 | ---- 459 | Issue 56. 460 | Summary: Update Metadata. 461 | From: Florian Rivoal 462 | Comment: https://github.com/w3c/w3process/pull/206 463 | Closed: Accepted 464 | Resolved: https://github.com/w3c/w3process/pull/206#pullrequestreview-155176088 465 | ---- 466 | Issue 57. 467 | Summary: Markup fixes. 468 | From: Florian Rivoal 469 | Comment: https://github.com/w3c/w3process/pull/205 470 | Closed: Accepted 471 | Resolved: https://github.com/w3c/w3process/pull/205#pullrequestreview-155164935 472 | ---- 473 | Issue 58. 474 | Summary: Editorial improvements to obsolete/superceded 475 | From: Andreas Tai 476 | Comment: https://github.com/w3c/w3process/issues/138 477 | Response: https://github.com/w3c/w3process/pull/199 478 | Closed: Accepted 479 | Resolved: Editor determined consensus 480 | ---- 481 | Issue 59. 482 | Summary: Clarify the 'personal capacity' aspect of AB/TAG participation. 483 | From: Kevin P. Fleming 484 | Comment: https://github.com/w3c/w3process/pull/191 485 | Closed: Accepted 486 | Resolved: Editor determined consensus 487 | ---- 488 | Issue 60. 489 | Summary: Update link 490 | From: Fuqiao Xue 491 | Comment: https://github.com/w3c/w3process/pull/164 492 | Closed: Accepted 493 | Resolved: https://github.com/w3c/w3process/pull/164#issuecomment-365696625 494 | ---- 495 | Issue 61. 496 | Summary: Add diagram to 6.9 497 | From: Charles McCathie Nevile 498 | Comment: https://github.com/w3c/w3process/pull/152 499 | Closed: Accepted 500 | Resolved: Editor determined consensus 501 | ---- 502 | Issue 62. 503 | Summary: Markup fixes 504 | From: Charles McCathie Nevile 505 | Comment: https://github.com/w3c/w3process/pull/153 506 | Closed: Accepted 507 | Resolved: https://github.com/w3c/w3process/pull/153#pullrequestreview-91714395 508 | ---- 509 | Issue 63. 510 | Summary: Markup and Editorial Fixes 511 | From: Philippe Le Hegaret 512 | Comment: https://github.com/w3c/w3process/pull/159 513 | Closed: Accepted 514 | Resolved: Editor determined consensus 515 | ---- 516 | Issue 64. 517 | Summary: Clarify withdrawing a Rec. 518 | From: Charles McCathie Nevile 519 | Comment: https://github.com/w3c/w3process/pull/145 520 | Closed: Rejected 521 | Verified: Issue submitter is co-editor and member of the AB, did not push back 522 | ---- 523 | Issue 65. 524 | Summary: Update maturity states description 525 | From: Charles McCathie Nevile 526 | Comment: https://github.com/w3c/w3process/pull/144 527 | Closed: Accepted 528 | Resolved: https://github.com/w3c/w3process/pull/144#issuecomment-371951311 529 | ---- 530 | Issue 66. 531 | Summary: RFC2777 is obsolete, update to RFC3797 532 | From: Florian Rivoal 533 | Comment: https://github.com/w3c/w3process/issues/233 534 | Response: https://github.com/w3c/w3process/pull/234 535 | Closed: Accepted 536 | Resolved: https://github.com/w3c/w3process/pull/234#issuecomment-449017548 537 | ---- 538 | Issue 67. 539 | Summary: Spelling fixes and one typo fix 540 | From: David Baron 541 | Comment: https://github.com/w3c/w3process/pull/237 542 | Response: https://github.com/w3c/w3process/pull/237#issuecomment-459576230 543 | Closed: Accepted 544 | Resolved: Editorial https://github.com/w3c/w3process/pull/237#issuecomment-459642272 545 | ---- 546 | Issue 68. 547 | Summary: Clarification of Introduction 548 | From: Rachel Comerford 549 | Comment: https://github.com/w3c/w3process/issues/232 550 | Response: https://github.com/w3c/w3process/issues/232#issuecomment-445088494 551 | Closed: Deferred 552 | Verified: https://github.com/w3c/w3process/issues/232#issuecomment-447664296 553 | ---- 554 | Issue 69. 555 | Summary: TAG Appointment via a NomCom 556 | From: Natasha Rooney 557 | Comment: https://github.com/w3c/w3process/issues/230 558 | Response: https://github.com/w3c/w3process/issues/230#issuecomment-459664413 559 | Closed: Deferred 560 | ---- 561 | Issue 70. 562 | Summary: Misleading characterisation about WDs in 6.2.1 563 | From: David Singer 564 | Comment: https://github.com/w3c/w3process/issues/235 565 | Response: https://github.com/w3c/w3process/issues/230#issuecomment-459664413 566 | Closed: Deferred 567 | ---- 568 | Issue 71. 569 | Summary: Does the process assume all WDs are on the Rec. Track? 570 | From: Nigel Megitt 571 | Comment: https://github.com/w3c/w3process/issues/236 572 | Response: https://github.com/w3c/w3process/issues/236#issuecomment-459665646 573 | Closed: Deferred 574 | ---- 575 | Issue 72. 576 | Summary: Clarification on vacant seats and elections 577 | From: David Baron 578 | Comment: https://github.com/w3c/w3process/issues/238 579 | Response: https://github.com/w3c/w3process/issues/238#issuecomment-460024169 580 | Closed: Deferred 581 | Verified: https://github.com/w3c/w3process/issues/238#issuecomment-460036573 582 | ---- 583 | Issue 73. 584 | Summary: Allow AB to choose its own chair 585 | From: Elika Etemad 586 | Comment: https://github.com/w3c/w3process/issues/223 587 | Closed: Deferred 588 | -------------------------------------------------------------------------------- /snapshots/2023-05-24-doc.bsi: -------------------------------------------------------------------------------- 1 | Draft: https://www.w3.org/Consortium/Process/Drafts/snapshots/2023-04 2 | Title: W3C Process Document 2023 (AC Review) 3 | 4 | 34 | 35 |

This Disposition of Comments covers comments received during the formal AC Review period for Process 2023. 36 | 37 |

Substantive Changes

38 | 39 |

Several review comments received during the AC Review period generated proposals for substantive changes: 40 | 41 |

170 | 171 |

Editorial Changes

172 | 173 |

AC Review raised a number of suggestions for clarification, 174 | which the Process CG accepted and are summarized below: 175 | 176 |

256 | 257 |

Index of Comments and Responses

258 | 259 | ---- 260 | Issue 1. 261 | Summary: Timeline for publishing formal objections 262 | From: Jeffrey Yasskin 263 | Comment: https://github.com/w3c/w3process/issues/735 264 | Closed: Deferred 265 | Verified: https://github.com/w3c/w3process/issues/735 266 | ---- 267 | Issue 2. 268 | Summary: Mention Archiving in Tooling section title 269 | From: fantasai 270 | Comment: https://github.com/w3c/w3process/issues/736 271 | Changes: https://github.com/w3c/w3process/commit/14f4644c9008bf10021628d78c3238a39b139e58 272 | Closed: Accepted 273 | Verified: Reporter is editor 274 | Resolved: Editorial 275 | ---- 276 | Issue 3. 277 | Summary: Improve wording of note about addressing FOs before advancement 278 | From: Jeffrey Yasskin 279 | Comment: https://github.com/w3c/w3process/issues/737 280 | Closed: Deferred 281 | Verified: By AC comment 282 | ---- 283 | Issue 4. 284 | Summary: AC Review questionnaire option to express disagreement 285 | From: Jeffrey Yasskin 286 | Comment: https://github.com/w3c/w3process/issues/738 287 | Response: https://github.com/w3c/w3process/issues/738#issuecomment-1525644054 288 | Response: https://github.com/w3c/w3process/issues/738#issuecomment-1544643945 289 | Closed: Invalid 290 | Verified: https://github.com/w3c/w3process/issues/738#issuecomment-1544662439 291 | ---- 292 | Issue 5. 293 | Summary: FO resolution isn't explicitly invoked 294 | From: Jeffrey Yasskin 295 | Comment: https://github.com/w3c/w3process/issues/739 296 | Closed: Deferred 297 | Verified: By AC comment 298 | ---- 299 | Issue 6. 300 | Summary: Clarify that AB/TAG approval uses their normal decision policy 301 | From: Jeffrey Yasskin 302 | Comment: https://github.com/w3c/w3process/issues/741 303 | Closed: Deferred 304 | Verified: By AC comment 305 | ---- 306 | Issue 7. 307 | Summary: Clarify where Submission Appeals go 308 | From: Jeffrey Yasskin 309 | Comment: https://github.com/w3c/w3process/issues/742 310 | Response: https://github.com/w3c/w3process/issues/742#issuecomment-1544656020 311 | Changes: https://github.com/w3c/w3process/commit/189b5ec060b46094c70a3ff343cc0ddb7968e0de 312 | Closed: Accepted 313 | Verified: [reporter thumbs up on response] 314 | Resolved: Bugfix 315 | ---- 316 | Issue 8. 317 | Summary: Remove normative keywords from non-normative notes 318 | From: Jeffrey Yasskin 319 | Comment: https://github.com/w3c/w3process/issues/745 320 | Closed: Deferred 321 | Verified: https://github.com/w3c/w3process/issues/745 322 | ---- 323 | Issue 9. 324 | Summary: Avoid two different meanings for “sustain” 325 | From: Jeffrey Yasskin 326 | Comment: https://github.com/w3c/w3process/issues/746 327 | Changes: https://github.com/w3c/w3process/pull/762 328 | Closed: Accepted 329 | Resolved: Editorial 330 | ---- 331 | Issue 10. 332 | Summary: Clarify which formal contexts require FO for dissent 333 | From: Chris Needham 334 | Comment: https://github.com/w3c/w3process/issues/746#issuecomment-1549991610 335 | Response: https://github.com/w3c/w3process/issues/746#issuecomment-1553935933 336 | Changes: https://github.com/w3c/w3process/pull/763 337 | Closed: Accepted 338 | Verified: Reporter is change author 339 | Resolved: Editorial 340 | ---- 341 | Issue 11. 342 | Summary: Clarify purpose of dismissal 343 | From: Mark Nottingham 344 | Comment: https://github.com/w3c/w3process/issues/747 345 | Response: https://github.com/w3c/w3process/issues/747#issuecomment-1544708674 346 | Changes: https://github.com/w3c/w3process/pull/757/commits/4f20cd1b0ebb44b07987e8ceedbda4b8db382fb7 347 | Closed: Accepted 348 | Verified: https://github.com/w3c/w3process/issues/747#issuecomment-1562212194 349 | ---- 350 | Issue 12. 351 | Summary: “potential Council member” phrasing is wordy 352 | From: Mark Nottingham 353 | Comment: https://github.com/w3c/w3process/issues/747 354 | Response: https://github.com/w3c/w3process/issues/747#issuecomment-1544708674 355 | Response: https://github.com/w3c/w3process/issues/747#issuecomment-1545309505 356 | Closed: Rejected 357 | Verified: https://github.com/w3c/w3process/issues/747#issuecomment-1562212194 358 | Resolved: Editorial 359 | ---- 360 | Issue 13. 361 | Summary: Note wrt nature of Council is oddly placed 362 | From: Mark Nottingham 363 | Comment: https://github.com/w3c/w3process/issues/747#issuecomment-1529019322 364 | Response: https://github.com/w3c/w3process/issues/747#issuecomment-1544708674 365 | Closed: Rejected 366 | Verified: https://github.com/w3c/w3process/issues/747#issuecomment-1562212194 367 | Resolved: Editorial 368 | ---- 369 | Issue 14. 370 | Summary: Unclear antecedent for “they” 371 | From: Mark Nottingham 372 | Comment: https://github.com/w3c/w3process/issues/747#issuecomment-1529019871 373 | Changes: https://github.com/w3c/w3process/pull/757/commits/e23a195b5775231ea33ca169ec204217cf33948d 374 | Closed: Accepted 375 | Verified: https://github.com/w3c/w3process/issues/747#issuecomment-1562212194 376 | Resolved: Editorial 377 | ---- 378 | Issue 15A. 379 | Summary: Use supermajority for dismissal voting (instead of majority) 380 | From: Mark Nottingham 381 | Comment: https://github.com/w3c/w3process/issues/748 382 | Comment: https://github.com/w3c/w3process/issues/748#issuecomment-1529728892 383 | Response: https://github.com/w3c/w3process/issues/748#issuecomment-1529464611 384 | Response: https://github.com/w3c/w3process/issues/748#issuecomment-1530089344 385 | Response: https://github.com/w3c/w3process/issues/748#issuecomment-1545665413 386 | Changes: https://github.com/w3c/w3process/pull/760 387 | Closed: Rejected 388 | Note: The AB resolved not to change the voting threshold, 389 | but did resolve to make the dismissal vote counts public. 390 | Resolved: AB May 2023 F2F 391 | ---- 392 | Issue 15B. 393 | Summary: Use single-person veto for dismissal (instead of majority) 394 | From: Nigel Megitt 395 | Comment: https://github.com/w3c/w3process/issues/748#issuecomment-1531724271 396 | Response: https://github.com/w3c/w3process/issues/748#issuecomment-1545665413 397 | Changes: https://github.com/w3c/w3process/pull/760 398 | Closed: Rejected 399 | Note: The AB resolved not to change the voting threshold, 400 | but did resolve to make the dismissal vote counts public. 401 | Resolved: AB May 2023 F2F 402 | ---- 403 | Issue 16. 404 | Summary: Improve transparency of dismissal process 405 | From: Advisory Board 406 | Comment https://github.com/w3c/w3process/issues/748 407 | Response: https://github.com/w3c/w3process/issues/748#issuecomment-1545665413 408 | Changes: https://github.com/w3c/w3process/pull/760 409 | Open: Accepted by AB, proposed to the Director for either Process or /Guide 410 | Note: As a result of the discussion in GitHub issue 748 (see above) 411 | the AB resolved to require reporting dismissal vote counts, 412 | to show the level of support or concern for the participation 413 | of each member of the Council. 414 | ---- 415 | Issue 17. 416 | Summary: AB/TAG Decisions and Council Conflict of Interest 417 | From: Mark Nottingham 418 | Comment: https://github.com/w3c/w3process/issues/749 419 | Response: https://github.com/w3c/w3process/issues/749#issuecomment-1551892219 420 | Changes: https://github.com/w3c/w3process/pull/761 421 | Open: Accepted by AB, recommended to adopt into practice by CG 422 | Note: The AB resolved not to remove the TAG/AB from the Council, 423 | but to exclude them from a Council Decision vote (if any) 424 | if the decision/proposal in question came from the TAG/AB. 425 | They may still participate in a consensus Council Decision. 426 | Note: The Council can always delegate in cases where it feels that 427 | would provide a more legitimate decision; and the AC still 428 | retains the ability to appeal a Council Decision if necessary. 429 | Resolved: AB May 2023 F2F 430 | ---- 431 | Issue 18. 432 | Summary: Expressing disagreement in AC review without Formal Objection 433 | From: Mark Nottingham 434 | Comment: https://github.com/w3c/w3process/issues/750 435 | Response: https://github.com/w3c/w3process/issues/750#issuecomment-1529053389 436 | Closed: Retracted 437 | ---- 438 | Issue 19A. 439 | Summary: Council/Team Powers of Mitigation too broad 440 | From: Mark Nottingham 441 | Comment: https://github.com/w3c/w3process/issues/751 442 | Response: https://github.com/w3c/w3process/issues/751#issuecomment-1529453863 443 | Comment: https://github.com/w3c/w3process/issues/751#issuecomment-1554703461 444 | Response: https://github.com/w3c/w3process/issues/751#issuecomment-1559068321 445 | Closed: Invalid 446 | Verified: https://github.com/w3c/w3process/issues/751#issuecomment-1563685512 447 | ---- 448 | Issue 19B. 449 | Summary: Limits on Council/Team Powers of Mitigation hard to understand 450 | From: Mark Nottingham 451 | Comment: https://github.com/w3c/w3process/issues/751#issuecomment-1560306816 452 | Response: https://github.com/w3c/w3process/issues/751#issuecomment-1560492526 453 | Closed: Deferred 454 | Verified: https://github.com/w3c/w3process/issues/751#issuecomment-1563685512 455 | ---- 456 | Issue 20. 457 | Summary: Publication of Minority opinions 458 | From: Mark Nottingham 459 | Comment: https://github.com/w3c/w3process/issues/752 460 | Response: https://github.com/w3c/w3process/issues/752#issuecomment-1529175671 461 | Closed: Retracted 462 | ---- 463 | Issue 21. 464 | Summary: Why is AC review of MoU appeal-based rather than approval-based? 465 | From: Mark Nottingham 466 | Comment: https://github.com/w3c/w3process/issues/753 467 | Response: https://github.com/w3c/w3process/issues/753#issuecomment-1529194913 468 | Response: https://github.com/w3c/w3process/issues/753#issuecomment-1530815822 469 | Closed: Deferred 470 | Verified: https://github.com/w3c/w3process/issues/753#issuecomment-1530815822 471 | ---- 472 | Issue 22. 473 | Summary: Define “joint deliverables” 474 | From: Eric Siow 475 | Comment: https://github.com/w3c/w3process/issues/754 476 | Response: https://github.com/w3c/w3process/issues/754#issuecomment-1532480890 477 | Closed: Deferred 478 | Verified: https://github.com/w3c/w3process/issues/754 479 | ---- 480 | Issue 23. 481 | Summary: What to do in case of non-responsiveness during FO resolution 482 | From: Philippe Le Hegaret 483 | Comment: https://github.com/w3c/w3process/issues/755 484 | Response: https://github.com/w3c/w3process/issues/755#issuecomment-1551893751 485 | Closed: OutOfScope 486 | Note: The AB resolved that /Guide should advise the Team to spin up 487 | the Council after a reasonable timeout when the objector or 488 | decider is non-responsive while trying to broker consensus or 489 | clarify their position. 490 | Verified: Reporter is co-chair 491 | Resolved: AB May 2023 F2F 492 | ---- 493 | Issue 24. 494 | Summary: Increase size of TAG 495 | From: Theresa O'Connor 496 | Comment: https://github.com/w3c/AB-memberonly/issues/171 497 | Comment: https://github.com/w3c/w3process/issues/465 498 | Comment: https://github.com/w3c/AB-memberonly/issues/171#issuecomment-1517110155 499 | Comment: https://github.com/w3c/AB-memberonly/issues/171#issuecomment-1517166312 500 | Response: https://github.com/w3c/AB-memberonly/issues/171#issuecomment-1551895803 501 | Changes: https://github.com/w3c/w3process/pull/733 502 | Open: Accepted by AB, proposed to Director 503 | Resolved: AB May 2023 F2F 504 | ---- 505 | Issue 25. 506 | Summary: Council composition is broken due to “member” vs “participant” 507 | From: Tantek Çelik 508 | Comment: https://github.com/w3c/w3process/issues/764 509 | Response: https://github.com/w3c/w3process/issues/764#issuecomment-1562177663 510 | Closed: Invalid 511 | Verified: https://github.com/w3c/w3process/issues/764#issuecomment-1562300254 512 | ---- 513 | Issue 26. 514 | Summary: Various Objections 515 | From: James Rosewell 516 | Comment: See https://www.w3.org/2002/09/wbs/33280/Process-2023/results 517 | Open: Formal Objection; deferred to the Director 518 | ---- 519 | Issue 27. 520 | Summary: Various Concerns 521 | From: Jon Andrieu 522 | Comment: See https://www.w3.org/2002/09/wbs/33280/Process-2023/results 523 | Note: Needs specific issues / discussion to be actionable 524 | Open: Deferred ; needs Team response 525 | ---- 526 | Issue 28. 527 | Summary: Clarify informative nature of references 528 | From: Tantek Çelik 529 | Comment: https://github.com/w3c/w3process/issues/765 530 | Response: https://github.com/w3c/w3process/pull/766 531 | Closed: Approved by the Director 532 | ---- 533 | -------------------------------------------------------------------------------- /issues-20190301.txt: -------------------------------------------------------------------------------- 1 | Draft: https://www.w3.org/2019/Process-20190301/ 2 | Title: W3C Process Document 3 | Date: 2019-03-01 4 | Status: Version 5 | ED: https://www.w3.org/Consortium/Process/Drafts/ 6 | 7 | ---- 8 | Issue 1. 9 | Summary: Define "independent". 10 | From: Nigel Meggit 11 | Comment: https://github.com/w3c/w3process/issues/167 12 | Response: https://github.com/w3c/w3process/issues/167#issuecomment-367498122 13 | Response: https://github.com/w3c/w3process/issues/167#issuecomment-372415200 14 | Response: https://github.com/w3c/w3process/issues/167#issuecomment-380498842 15 | Closed: Deferred 16 | ---- 17 | Issue 2. 18 | Summary: Clarification of Introduction 19 | From: Rachel Comerford 20 | Comment: https://github.com/w3c/w3process/issues/232 21 | Response: https://github.com/w3c/w3process/issues/232#issuecomment-445088494 22 | Closed: Retracted 23 | Verified: https://github.com/w3c/w3process/issues/232#event-2359816536 24 | ---- 25 | Issue 3. 26 | Summary: TAG Appointment via a NomCom 27 | From: Natasha Rooney 28 | Comment: https://github.com/w3c/w3process/issues/230 29 | Response: https://github.com/w3c/w3process/issues/230#issuecomment-442692389 30 | Response: https://github.com/w3c/w3process/issues/230#issuecomment-442721522 31 | Response: https://github.com/w3c/w3process/issues/230#issuecomment-443498734 32 | Response: https://github.com/w3c/w3process/issues/230#issuecomment-443529197 33 | Response: https://github.com/w3c/w3process/issues/230#issuecomment-443814364 34 | Closed: Deferred 35 | ---- 36 | Issue 4. 37 | Summary: Misleading characterisation about WDs in 6.2.1 38 | From: David Singer 39 | Comment: https://github.com/w3c/w3process/issues/235 40 | Response: https://github.com/w3c/w3process/issues/235#issuecomment-449206538 41 | Response: https://github.com/w3c/w3process/issues/235#issuecomment-449347229 42 | Response: https://github.com/w3c/w3process/issues/235#issuecomment-451580525 43 | Response: https://github.com/w3c/w3process/issues/235#issuecomment-451613228 44 | Response: https://github.com/w3c/w3process/issues/235#issuecomment-451910585 45 | Response: https://github.com/w3c/w3process/issues/235#issuecomment-461233194 46 | Closed: Accepted 47 | Resolved: https://github.com/w3c/w3process/issues/235#issuecomment-490509529 48 | ---- 49 | Issue 5. 50 | Summary: Does the process assume all WDs are on the Rec. Track? 51 | From: Nigel Megitt 52 | Comment: https://github.com/w3c/w3process/issues/236 53 | Response: https://github.com/w3c/w3process/issues/236#issuecomment-494898411 54 | Response: https://github.com/w3c/w3process/issues/236#issuecomment-514654606 55 | Response: https://github.com/w3c/w3process/issues/236#issuecomment-642704181 56 | Response: https://github.com/w3c/w3process/issues/236#issuecomment-643057849 57 | Response: https://github.com/w3c/w3process/issues/236#issuecomment-643217094 58 | Response: https://github.com/w3c/w3process/issues/236#issuecomment-643579948 59 | Closed: Deferred 60 | Verified: https://github.com/w3c/w3process/issues/236#issuecomment-643969336 61 | ---- 62 | Issue 6. 63 | Summary: Clarification on vacant seats and elections 64 | From: David Baron 65 | Comment: https://github.com/w3c/w3process/issues/238 66 | Comment: https://github.com/w3c/w3process/issues/238#issuecomment-485549398 67 | Comment: https://github.com/w3c/w3process/issues/238#issuecomment-494497999 68 | Comment: https://github.com/w3c/w3process/issues/238#issuecomment-494593856 69 | Comment: https://github.com/w3c/w3process/issues/238#issuecomment-494701431 70 | Comment: https://github.com/w3c/w3process/issues/238#issuecomment-494706103 71 | Response: https://github.com/w3c/w3process/issues/286 72 | Closed: Accepted 73 | Resolved: https://github.com/w3c/w3process/issues/238#issuecomment-506748061 74 | ---- 75 | Issue 7. 76 | Summary: Allow AB to choose its own chair 77 | From: Elika Etemad 78 | Comment: https://github.com/w3c/w3process/issues/223 79 | Comment: https://github.com/w3c/w3process/pull/225 80 | Closed: Deferred 81 | Resolved: https://github.com/w3c/w3process/issues/223#issuecomment-490326127 82 | ---- 83 | Issue 8. 84 | Summary: Add an index of Terms and Acronyms 85 | From: Natasha Rooney 86 | Comment: https://github.com/w3c/w3process/issues/198 87 | Response: https://github.com/w3c/w3process/issues/198#issuecomment-461235578 88 | Closed: Accepted 89 | ---- 90 | Issue 9. 91 | Summary: Clarify how Superseded state interacts with other maintenance processes 92 | From: David Baron 93 | Comment: https://github.com/w3c/w3process/issues/183 94 | Comment: https://github.com/w3c/w3process/issues/183#issuecomment-386461173 95 | Comment: https://github.com/w3c/w3process/issues/183#issuecomment-386465352 96 | Comment: https://github.com/w3c/w3process/issues/183#issuecomment-386472282 97 | Comment: https://github.com/w3c/w3process/issues/183#issuecomment-386865827 98 | Response: https://github.com/w3c/w3process/pull/213 99 | Closed: Accepted 100 | Resolved: https://github.com/w3c/w3process/pull/213#issuecomment-530399323 101 | ---- 102 | Issue 10. 103 | Summary: Define charter review process to require addressing comments 104 | From: Elika Etemad 105 | Comment: https://github.com/w3c/w3process/issues/182 106 | Comment: https://github.com/w3c/w3process/issues/182#issuecomment-385958175 107 | Comment: https://github.com/w3c/w3process/issues/182#issuecomment-386750897 108 | Comment: https://github.com/w3c/w3process/issues/182#issuecomment-387124626 109 | Comment: https://github.com/w3c/w3process/issues/182#issuecomment-388929432 110 | Comment: https://github.com/w3c/w3process/issues/182#issuecomment-389719860 111 | Comment: https://github.com/w3c/w3process/issues/182#issuecomment-390356337 112 | Closed: Deferred 113 | ---- 114 | Issue 11. 115 | Summary: Review the role of the Director in the process document 116 | From: David Singer 117 | Comment: https://github.com/w3c/w3process/issues/173 118 | Closed: Duplicate 119 | Resolved: https://github.com/w3c/w3process/issues/173#issuecomment-514367457 120 | Verified: https://github.com/w3c/w3process/issues/173#issuecomment-514367457 121 | ---- 122 | Issue 12. 123 | Summary: We need a process for handling registries, APIs and other enumerations 124 | From: David Singer 125 | Comment: https://github.com/w3c/w3process/issues/168 126 | Closed: Deferred 127 | ---- 128 | Issue 13. 129 | Summary: Should the process include something about Testing? 130 | From: Natasha Rooney 131 | Comment: https://github.com/w3c/w3process/issues/157 132 | Closed: Deferred 133 | ---- 134 | Issue 14. 135 | Summary: provide clearer/common wording for transitions to Obsolete/Superseded status 136 | From: Tantek Çelik 137 | Comment: https://github.com/w3c/w3process/issues/141 138 | Closed: Deferred 139 | ---- 140 | Issue 15. 141 | Summary: Concerns about Amended Recommendations 142 | From: Andreas Tai 143 | Comment: https://github.com/w3c/w3process/issues/137 144 | Closed: Deferred 145 | ---- 146 | Issue 16. 147 | Summary: Enumerate the requirements for wide review 148 | From: Nigel Megitt 149 | Comment: https://github.com/w3c/w3process/issues/130 150 | Comment: https://github.com/w3c/w3process/issues/264 151 | Closed: Deferred 152 | ---- 153 | Issue 17. 154 | Summary: Process should say how W3T can update NOTES 155 | From: Ralph Swick 156 | Comment: https://github.com/w3c/w3process/issues/120 157 | Closed: Deferred 158 | ---- 159 | Issue 18. 160 | Summary: We need to consider equal-preference voting 161 | From: David Signer 162 | Comment: https://github.com/w3c/w3process/issues/115 163 | Closed: Deferred 164 | ---- 165 | Issue 19. 166 | Summary: Should the process allow REC->WD transition directly? 167 | From: David Baron 168 | Comment: https://github.com/w3c/w3process/issues/103 169 | Closed: Deferred 170 | ---- 171 | Issue 20. 172 | Summary: Update Graphics 173 | From: Charles McCathie Nevile 174 | Comment: https://github.com/w3c/w3process/issues/91 175 | Closed: Retracted 176 | Verified: https://github.com/w3c/w3process/issues/91#issuecomment-442686352 177 | ---- 178 | Issue 21. 179 | Summary: Process supporting "Living Standards"? 180 | From: https://github.com/joanmarie 181 | Comment: https://github.com/w3c/w3process/issues/79 182 | Closed: Accepted 183 | Resolved: https://github.com/w3c/w3process/issues/79#issuecomment-597657227 184 | ---- 185 | Issue 22. 186 | Summary: Should there be good standing / supermajority criteria in authoritative ballots? 187 | From: Michael Champion 188 | Comment: https://github.com/w3c/w3process/issues/76 189 | Closed: Deferred 190 | ---- 191 | Issue 23. 192 | Summary: Allow AC Reviews to be made public 193 | From: Coralie Mercier 194 | Comment: https://github.com/w3c/w3process/issues/63 195 | Comment: https://github.com/w3c/w3process/issues/38 196 | Comment: https://github.com/w3c/w3process/issues/39 197 | Closed: Deferred 198 | ---- 199 | Issue 24. 200 | Summary: Clarify the voting Process 201 | From: Jeff Jaffe 202 | Comment: https://github.com/w3c/w3process/issues/60 203 | Closed: Deferred 204 | ---- 205 | Issue 25. 206 | Summary: Substantive changes undefined for Charter and Process reviews 207 | From: Daniel Glazman 208 | Comment: https://www.w3.org/community/w3process/track/issues/176 209 | Comment: https://github.com/w3c/w3process/issues/28 210 | Comment: https://github.com/w3c/w3process/pull/217 211 | Comment: https://github.com/w3c/w3process/pull/218 212 | Closed: Deferred 213 | ---- 214 | Issue 26. 215 | Summary: Sections 3.4 and 6.2.6 have different statements about Voting rules in a Charter 216 | From: Steve Zilles 217 | Comment: https://github.com/w3c/w3process/issues/24 218 | Comment: https://github.com/w3c/w3process/issues/24#issuecomment-422468295 219 | Response: https://github.com/w3c/w3process/issues/24#issuecomment-422474665 220 | Closed: Accepted 221 | Resolved: https://github.com/w3c/w3process/issues/24#issuecomment-490507215 222 | ---- 223 | Issue 28. 224 | Summary: The word “dissent” is used more broadly than appropriate given its specific definition 225 | From: Florian Rivoal 226 | Comment: https://github.com/w3c/w3process/issues/239 227 | Comment: https://github.com/w3c/w3process/issues/239#issuecomment-461338765 228 | Comment: https://github.com/w3c/w3process/issues/239#issuecomment-461428887 229 | Response: https://github.com/w3c/w3process/pull/256 230 | Closed: Accepted 231 | Resolved: https://github.com/w3c/w3process/issues/239#issuecomment-472435499 232 | ---- 233 | Issue 29. 234 | Summary: Grammar fix 235 | From: Florian Rivoal 236 | Comment: https://github.com/w3c/w3process/pull/240 237 | Comment: https://github.com/w3c/w3process/pull/240#pullrequestreview-200978577 238 | Response: https://github.com/w3c/w3process/pull/240#issuecomment-461396167 239 | Closed: Accepted 240 | Resolved: https://www.w3.org/2019/02/13-w3process-minutes.html 241 | ---- 242 | Issue 30. 243 | Summary: Applicability of the Pantent Policy on Tag members 244 | From: Florian Rivoal 245 | Comment: https://github.com/w3c/w3process/issues/241 246 | Comment: https://github.com/w3c/w3process/issues/241#issuecomment-461640451 247 | Comment: https://github.com/w3c/w3process/issues/241#issuecomment-462754733 248 | Comment: https://github.com/w3c/w3process/issues/241#issuecomment-468832300 249 | Comment: https://github.com/w3c/w3process/issues/241#issuecomment-494177264 250 | Response: https://github.com/w3c/w3process/pull/282 251 | Closed: Accepted 252 | Resolved: https://www.w3.org/2019/05/22-w3process-minutes.html 253 | ---- 254 | Issue 31. 255 | Summary: Resignation of AB and TAG members is illdefined 256 | From: Florian Rivoal 257 | Comment: https://github.com/w3c/w3process/issues/242 258 | Comment: https://github.com/w3c/w3process/issues/242#issuecomment-493619703 259 | Response: https://github.com/w3c/w3process/pull/283 260 | Closed: Accepted 261 | Resolved: https://github.com/w3c/w3process/issues/242#issuecomment-494939326 262 | ---- 263 | Issue 32. 264 | Summary: Clarify terminology: minor changes vs editorial changes 265 | From: Florian Rivoal 266 | Comment: https://github.com/w3c/w3process/issues/243 267 | Response: https://github.com/w3c/w3process/pull/269 268 | Closed: Accepted 269 | Resolved: https://github.com/w3c/w3process/pull/269#pullrequestreview-260554355 270 | ---- 271 | Issue 33. 272 | Summary: Undefined term: member-visible 273 | From: Florian Rivoal 274 | Comment: https://github.com/w3c/w3process/issues/244 275 | Closed: Accepted 276 | Resolved: https://github.com/w3c/w3process/issues/244#issuecomment-490520494 277 | ---- 278 | Issue 34. 279 | Summary: Incorrect use of the specialized term "publish" 280 | From: Florian Rivoal 281 | Comment: https://github.com/w3c/w3process/issues/245 282 | Response: https://github.com/w3c/w3process/pull/257 283 | Closed: Accepted 284 | Resolved: https://github.com/w3c/w3process/issues/245#issuecomment-472436157 285 | ---- 286 | Issue 35. 287 | Summary: Does the “Team Submission“ mechanism still serve a purpose? 288 | From: Florian Rivoal 289 | Comment: https://github.com/w3c/w3process/issues/246 290 | Comment: https://github.com/w3c/w3process/issues/246#issuecomment-461428127 291 | Comment: https://github.com/w3c/w3process/issues/246#issuecomment-464979340 292 | Comment: https://github.com/w3c/w3process/issues/246#issuecomment-465001121 293 | Comment: https://github.com/w3c/w3process/issues/246#issuecomment-472009020 294 | Comment: https://github.com/w3c/w3process/pull/261 295 | Response: https://github.com/w3c/w3process/pull/255 296 | Closed: Accepted 297 | Resolved: https://github.com/w3c/w3process/pull/255#issuecomment-473982997 298 | ---- 299 | Issue 36. 300 | Summary: Remove extraneous phrasing (Editorial) 301 | From: Florian Rivoal 302 | Comment: https://github.com/w3c/w3process/pull/247 303 | Closed: Accepted 304 | Resolved: https://www.w3.org/2019/02/13-w3process-minutes.html 305 | ---- 306 | Issue 37. 307 | Summary: Drop redundant word (Editorial) 308 | From: Florian Rivoal 309 | Comment: https://github.com/w3c/w3process/pull/248 310 | Closed: Accepted 311 | Resolved: Editorial 312 | ---- 313 | Issue 38. 314 | Summary: Define "Working Group Decision" 315 | From: Charles McCathie Nevile 316 | Comment: https://github.com/w3c/w3process/issues/249 317 | Response: https://github.com/w3c/w3process/pull/270 318 | Closed: Accepted 319 | Resolved: https://github.com/w3c/w3process/pull/270#issuecomment-514653370 320 | ---- 321 | Issue 39. 322 | Summary: Remove unneeded sentence fragment (editorial) 323 | From: Florian Rivoal 324 | Comment: https://github.com/w3c/w3process/issues/250 325 | Comment: https://github.com/w3c/w3process/issues/250#issuecomment-461744375 326 | Closed: Accepted 327 | Resolved: https://github.com/w3c/w3process/issues/250#issuecomment-472437269 328 | ---- 329 | Issue 40. 330 | Summary: First meeting of a WG allowed too soon 331 | From: Florian Rivoal 332 | Comment: https://github.com/w3c/w3process/issues/251 333 | Closed: Deferred 334 | ---- 335 | Issue 41. 336 | Summary: Fix misplaced punctuation 337 | From: Florian Rivoal 338 | Comment: https://github.com/w3c/w3process/pull/252 339 | Closed: Accepted 340 | Resolved: Editorial 341 | ---- 342 | Issue 42. 343 | Summary: Update Editor and Former Editors' affiliation 344 | From: Coralie Mercier 345 | Comment: https://github.com/w3c/w3process/issues/253 346 | Comment: https://github.com/w3c/w3process/issues/253#issuecomment-463399703 347 | Comment: https://github.com/w3c/w3process/issues/253#issuecomment-463640019 348 | Comment: https://github.com/w3c/w3process/issues/253#issuecomment-463949262 349 | Closed: Accepted 350 | Resolved: Editorial 351 | ---- 352 | Issue 43. 353 | Summary: Remove overly specific mention of PR in generic sentence about AC reviews 354 | From: Coralie Mercier 355 | Comment: https://github.com/w3c/w3process/issues/259 356 | Closed: Accepted 357 | Resolved: https://github.com/w3c/w3process/issues/259#issuecomment-472438787 358 | ---- 359 | Issue 44. 360 | Summary: Add sub-section headings to revising a REC 361 | From: Florian Rivoal 362 | Comment: https://github.com/w3c/w3process/pull/294 363 | Closed: Accepted 364 | Resolved: https://github.com/w3c/w3process/pull/294#pullrequestreview-254696601 365 | ---- 366 | Issue 45. 367 | Summary: CR change documentation requirement should be for substantive changes only 368 | From: Elika Etemad 369 | Comment: https://github.com/w3c/w3process/issues/307 370 | Response: https://github.com/w3c/w3process/pull/308 371 | Closed: Accepted 372 | Resolved: https://github.com/w3c/w3process/pull/308#issuecomment-530397840 373 | ---- 374 | Issue 46. 375 | Summary: Evolution of documents that are linked to the process 376 | From: Jeff Jaffe, Florian Rivoal 377 | Comment: https://github.com/w3c/w3process/issues/305 378 | Comment: https://github.com/w3c/w3process/issues/319 379 | Comment: https://github.com/w3c/w3process/issues/318 380 | Response: https://github.com/w3c/w3process/pull/309 381 | Closed: Accepted 382 | Resolved: https://github.com/w3c/w3process/pull/309#issuecomment-521268434 383 | ---- 384 | Issue 47. 385 | Summary: Add note to Process about flexibility of consensus 386 | From: Florian Rivoal 387 | Comment: https://github.com/w3c/w3process/issues/296 388 | Response: https://github.com/w3c/w3process/pull/323 389 | Closed: Accepted 390 | Resolved: https://github.com/w3c/w3process/pull/323#issuecomment-530397628 391 | ---- 392 | Issue 48. 393 | Summary: Typo 394 | From: Coralie Mercier 395 | Comment: https://github.com/w3c/w3process/issues/332 396 | Closed: Accepted 397 | Resolved: Editorial 398 | ---- 399 | Issue 49. 400 | Summary: Purpose of short terms undefined 401 | From: Coralie Mercier 402 | Comment: https://github.com/w3c/w3process/issues/333 403 | Closed: Deferred 404 | ---- 405 | Issue 50. 406 | Summary: Add references to "Open Stand" principles to the Process 407 | From: Larry Masinter 408 | Comment: https://github.com/w3c/w3process/issues/325 409 | Response: https://github.com/w3c/w3process/issues/325#issuecomment-545684526 410 | Closed: Rejected 411 | Resolved: https://github.com/w3c/w3process/issues/325#issuecomment-545480250 412 | ---- 413 | Issue 51. 414 | Summary: Drop the distinction between REC and Edited REC 415 | From: Florian Rivoal 416 | Comment: https://github.com/w3c/w3process/issues/362 417 | Response: https://github.com/w3c/w3process/pull/364 418 | Closed: Accepted 419 | Resolved: https://github.com/w3c/w3process/pull/364#issuecomment-579800586 420 | ---- 421 | Issue 52. 422 | Summary: Don't create different classes of RECs for those that can accept new features vs those that cannot 423 | From: Elika Etemad 424 | Comment: https://github.com/w3c/w3process/issues/345 425 | Response: https://github.com/w3c/w3process/pull/365 426 | Closed: Accepted 427 | Resolved: https://github.com/w3c/w3process/pull/365#issuecomment-579799691 428 | ---- 429 | Issue 53. 430 | Summary: Should W3C drop the idea of a separate Evergreen Track? 431 | From: Elika Etemad 432 | Comment: https://github.com/w3c/w3process/issues/343 433 | Comment: https://github.com/w3c/w3process/pull/304 434 | Comment: https://github.com/w3c/w3process/issues/303 435 | Comment: https://github.com/w3c/w3process/issues/302 436 | Comment: https://github.com/w3c/w3process/issues/301 437 | Comment: https://github.com/w3c/w3process/issues/300 438 | Comment: https://github.com/w3c/w3process/pull/298 439 | Comment: https://github.com/w3c/w3process/issues/297 440 | Comment: https://github.com/w3c/w3process/issues/273 441 | Comment: https://github.com/w3c/w3process/issues/272 442 | Comment: https://github.com/w3c/w3process/issues/271 443 | Comment: https://github.com/w3c/w3process/issues/267 444 | Comment: https://github.com/w3c/w3process/issues/263 445 | Closed: Accepted 446 | Resolved: https://github.com/w3c/w3process/issues/343#issuecomment-580173062 447 | ---- 448 | Issue 54. 449 | Summary: Section 6 is poorly organized and hard to read 450 | From: Elika Etemad 451 | Comment: https://github.com/w3c/w3process/issues/336 452 | Comment: https://github.com/w3c/w3process/issues/340 453 | Comment: https://github.com/w3c/w3process/issues/341 454 | Response: https://github.com/w3c/w3process/pull/348 455 | Closed: Accepted 456 | Resolved: https://github.com/w3c/w3process/issues/344#issuecomment-572121863 457 | ---- 458 | Issue 55. 459 | Summary: Should W3C adopt the so-called Everblue/teal modifications to the REC track? 460 | From: Elika Etemad 461 | Comment: https://github.com/w3c/w3process/issues/344 462 | Closed: Accepted 463 | Resolved: https://github.com/w3c/w3process/issues/344#issuecomment-572121863 464 | ---- 465 | Issue 56. 466 | Summary: Rephrase Evolution of the Process section 467 | From: Wendy Seltzer 468 | Comment: https://github.com/w3c/w3process/issues/355 469 | Response: https://github.com/w3c/w3process/pull/367 470 | Closed: Accepted 471 | Resolved: https://github.com/w3c/w3process/pull/367#issuecomment-585252380 472 | ---- 473 | Issue 57. 474 | Summary: Avoid using the word "contributor" to limit conflicts with the patent policy 475 | From: Florian Rivoal 476 | Comment: https://github.com/w3c/w3process/pull/359 477 | Closed: Accepted 478 | Resolved: https://github.com/w3c/w3process/pull/359#issuecomment-572125274 479 | ---- 480 | Issue 58. 481 | Summary: Define a type of publication that is sumultaneously FPWD and CR 482 | From: Jeff Jaffe 483 | Comment: https://github.com/w3c/w3process/issues/352 484 | Closed: Rejected 485 | Resolved: https://github.com/w3c/w3process/issues/352#issuecomment-585260875 486 | Verified: https://github.com/w3c/w3process/issues/352#issuecomment-585259948 487 | ---- 488 | Issue 59. 489 | Summary: Further automating transition requests 490 | From: Florian Rivoal 491 | Comment: https://github.com/w3c/w3process/issues/260 492 | Closed: Retracted 493 | ---- 494 | Issue 60. 495 | Summary: Fix typo 496 | From: Tab Atkins 497 | Comment: https://github.com/w3c/w3process/pull/266 498 | Closed: Accepted 499 | Resolved: Editorial 500 | ---- 501 | Issue 61. 502 | Summary: Can records of appeals ever be made public? 503 | From: Nigel Megitt 504 | Comment: https://github.com/w3c/w3process/issues/268 505 | Response: https://github.com/w3c/w3process/issues/268#issuecomment-490750384 506 | Closed: Retracted 507 | ---- 508 | Issue 62. 509 | Summary: Add more convenient links for review 510 | From: Mark Nottingham 511 | Comment: https://github.com/w3c/w3process/issues/317 512 | Closed: Accepted 513 | Resolved: Editorial 514 | ---- 515 | Issue 63. 516 | Summary: Are W3C hosts members of W3C 517 | From: Charles McCathie Nevile 518 | Comment: https://github.com/w3c/w3process/issues/10 519 | Closed: OutOfScope 520 | Resolved: https://github.com/w3c/w3process/issues/10#issuecomment-521317797 521 | ---- 522 | Issue 64. 523 | Summary: Update REC-track diagrams 524 | From: David Singer 525 | Comment: https://github.com/w3c/w3process/issues/390 526 | Closed: Accepted 527 | Resolved: Editorial 528 | ---- 529 | Issue 65. 530 | Summary: Use consistent spelling for "judgment" vs "judgement" 531 | From: Wendy Seltzer 532 | Comment: https://github.com/w3c/w3process/pull/357 533 | Closed: Accepted 534 | Resolved: Editorial 535 | ---- 536 | Issue 66. 537 | Summary: Tie everblue to new patent policy 538 | From: Wendy Seltzer 539 | Comment: https://github.com/w3c/w3process/pull/361 540 | Comment: https://github.com/w3c/w3process/pull/306 541 | Comment: https://github.com/w3c/w3process/pull/320 542 | Comment: https://github.com/w3c/w3process/pull/363 543 | Comment: https://github.com/w3c/w3process/pull/395 544 | Closed: Accepted 545 | Resolved: https://github.com/w3c/w3process/pull/395#issuecomment-611010980 546 | ---- 547 | Issue 67. 548 | Summary: Fix typo 549 | From: Ralph Swick 550 | Comment: https://github.com/w3c/w3process/pull/387 551 | Closed: Accepted 552 | Resolved: Editorial 553 | ---- 554 | Issue 68. 555 | Summary: Consistent usage of "Team's Publication Rules" 556 | From: Coralie Mercier 557 | Comment: https://github.com/w3c/w3process/pull/385 558 | Closed: Accepted 559 | Resolved: Editorial 560 | ---- 561 | Issue 69. 562 | Summary: description for "The Art of Consensus" 563 | From: Coralie Mercier 564 | Comment: https://github.com/w3c/w3process/pull/384 565 | Closed: Accepted 566 | Resolved: Editorial 567 | ---- 568 | Issue 70. 569 | Summary: Use actual title of the linked document 570 | From: Coralie Mercier 571 | Comment: https://github.com/w3c/w3process/pull/383 572 | Closed: Accepted 573 | Resolved: Editorial 574 | ---- 575 | Issue 71. 576 | Summary: The guidebook is no longer member-only 577 | From: Coralie Mercier 578 | Comment: https://github.com/w3c/w3process/pull/371 579 | Closed: Accepted 580 | Resolved: Editorial 581 | ---- 582 | Issue 72. 583 | Summary: Add hyphen 584 | From: Coralie Mercier 585 | Comment: https://github.com/w3c/w3process/pull/369 586 | Closed: Accepted 587 | Resolved: Editorial 588 | ---- 589 | Issue 73. 590 | Summary: TAG appointed participants announcement by Director 591 | From: Coralie Mercier 592 | Comment: https://github.com/w3c/w3process/issues/368 593 | Closed: Deferred 594 | ---- 595 | Issue 74. 596 | Summary: ambiguous statement for proxy in WG/IG 597 | From: Coralie Mercier 598 | Comment: https://github.com/w3c/w3process/issues/368 599 | Comment: https://github.com/w3c/w3process/issues/373 600 | Closed: Deferred 601 | ---- 602 | Issue 75. 603 | Summary: Removed spurious period mid-sentence 604 | From: Coralie Mercier 605 | Comment: https://github.com/w3c/w3process/pull/370 606 | Closed: Accepted 607 | Resolved: Editorial 608 | ---- 609 | Issue 76. 610 | Summary: Update link that redirected 611 | From: Coralie Mercier 612 | Comment: https://github.com/w3c/w3process/pull/372 613 | Closed: Accepted 614 | Resolved: Editorial 615 | ---- 616 | Issue 77. 617 | Summary: link to ML archive rather than ML mailto 618 | From: Coralie Mercier 619 | Comment: https://github.com/w3c/w3process/pull/374 620 | Closed: Accepted 621 | Resolved: Editorial 622 | ---- 623 | Issue 78. 624 | Summary: Fix typo 625 | From: Coralie Mercier 626 | Comment: https://github.com/w3c/w3process/pull/375 627 | Closed: Accepted 628 | Resolved: Editorial 629 | ---- 630 | Issue 79. 631 | Summary: Fix typo 632 | From: Coralie Mercier 633 | Comment: https://github.com/w3c/w3process/pull/377 634 | Closed: Accepted 635 | Resolved: Editorial 636 | ---- 637 | Issue 80. 638 | Summary: Fixed letter case 639 | From: Coralie Mercier 640 | Comment: https://github.com/w3c/w3process/pull/378 641 | Closed: Accepted 642 | Resolved: Editorial 643 | ---- 644 | Issue 81. 645 | Summary: Write numbers consistently 646 | From: Coralie Mercier 647 | Comment: https://github.com/w3c/w3process/pull/379 648 | Closed: Accepted 649 | Resolved: Editorial 650 | ---- 651 | Issue 82. 652 | Summary: Correct punctuation 653 | From: Coralie Mercier 654 | Comment: https://github.com/w3c/w3process/pull/380 655 | Closed: Accepted 656 | Resolved: Editorial 657 | ---- 658 | Issue 83. 659 | Summary: Consitently order the same terms in the same order 660 | From: Coralie Mercier 661 | Comment: https://github.com/w3c/w3process/pull/381 662 | Comment: https://github.com/w3c/w3process/pull/382 663 | Closed: Accepted 664 | Resolved: Editorial 665 | ---- 666 | Issue 84. 667 | Summary: Fix punctuation 668 | From: Ivan Herman 669 | Comment: https://github.com/w3c/w3process/pull/397 670 | Closed: Accepted 671 | Resolved: Editorial 672 | ---- 673 | Issue 85. 674 | Summary: Clarify W3C Decision 675 | From: Jeff Jaffe 676 | Comment: https://github.com/w3c/w3process/issues/404 677 | Closed: Accepted 678 | Resolved: https://github.com/w3c/w3process/issues/404#issuecomment-634693844 679 | ---- 680 | Issue 86. 681 | Summary: Adjust wording of the Process Evolution section 682 | From: Ralph Swick 683 | Commment: https://github.com/w3c/w3process/issues/388 684 | Closed: Accepted 685 | Resolved: https://www.w3.org/2020/05/27-w3process-minutes.html#resolution01 686 | ---- 687 | Issue 87. 688 | Summary: "Candidate Recommendation" is no longer an accurate term 689 | From: Pierre-Anthony Lemieux 690 | Comment: https://github.com/w3c/w3process/issues/402 691 | Closed: Deferred 692 | Resolved: https://www.w3.org/2020/05/27-w3process-minutes.html#resolution04 693 | ---- 694 | Issue 88. 695 | Summary: Patent Policy application to Proposed Changes 696 | From: Elika Etemad 697 | Comment: https://github.com/w3c/w3process/issues/403 698 | Comment: https://www.w3.org/mid/B9DBE3C4-53AB-4801-9695-853257EA3410@rivoal.net 699 | Closed: Accepted 700 | Resolved: https://github.com/w3c/w3process/issues/403#issuecomment-642036601 701 | ---- 702 | Issue 89. 703 | Summary: Streamlining horizontal reviews 704 | From: Lukasz Olejnik 705 | Comment: https://github.com/w3c/w3process/issues/347 706 | Closed: Deferred 707 | ---- 708 | Issue 90. 709 | Summary: Part of introductory text about REC track is confusing / inaccurate / ineffective 710 | From: Pierre-Anthony Lemieux 711 | Comment: https://github.com/w3c/w3process/issues/406 712 | Closed: Accepted 713 | Resolved: https://github.com/w3c/w3process/issues/406#issuecomment-642057764 714 | ---- 715 | Issue 91. 716 | Summary: Community Groups and Business Groups should be incorporated into the Process 717 | From: Chris Wilson 718 | Comment: https://github.com/w3c/w3process/issues/409 719 | Closed: Deferred 720 | ---- 721 | Issue 92. 722 | Summary: Increasing voter turnout in AC reviews with incentives 723 | From: Anssi Kostiainen 724 | Comment: https://github.com/w3c/w3process/issues/410 725 | Closed: Deferred 726 | ---- 727 | Issue 93. 728 | Summary: Remove the term "blacklisted" from W3C communications 729 | From: guest271314 730 | Comment: https://github.com/w3c/w3process/issues/415 731 | Comment: https://github.com/w3c/w3process/issues/415#issuecomment-644448791 732 | Comment: https://github.com/w3c/w3process/issues/415#issuecomment-644461987 733 | Comment: https://github.com/w3c/w3process/issues/415#issuecomment-644521759 734 | Closed: OutOfScope 735 | ---- 736 | Issue 94. 737 | Summary: Trim the Changes section 738 | From: Elika Etemad 739 | Comment: https://github.com/w3c/w3process/issues/412 740 | Response: https://github.com/w3c/w3process/pull/416 741 | Closed: Accepted 742 | Resolved: https://github.com/w3c/w3process/issues/412#issuecomment-648842528 743 | ---- 744 | Issue 95. 745 | Summary: Find name for Proposed Changes under patent review 746 | From: Elika Etemad 747 | Comment: https://github.com/w3c/w3process/issues/408 748 | Response: https://github.com/w3c/w3process/pull/413 749 | Closed: Accepted 750 | Resolved: https://github.com/w3c/w3process/pull/413#issuecomment-648843546 751 | ---- 752 | Issue 96. 753 | Summary: Adjust section title for the sake of ease of referencing 754 | From: Philipe Le Hegaret 755 | Comment: https://github.com/w3c/w3process/issues/437 756 | Closed: Accepted 757 | Resolved: https://www.w3.org/2020/08/12-w3process-minutes.html#r01 758 | ---- 759 | Issue 97. 760 | Summary: Use terminology consistently 761 | From: Travis Leithead 762 | Comment: https://github.com/w3c/w3process/issues/439 763 | Closed: Accepted 764 | Resolved: Director's decision in response to AC Review 765 | ---- 766 | Issue 98. 767 | Summary: Grammar fix: adjust sentence to have the correct subject 768 | From: Travis Leithead 769 | Comment: https://github.com/w3c/w3process/issues/440 770 | Closed: Accepted 771 | Resolved: Director's decision in response to AC Review 772 | ---- 773 | Issue 99. 774 | Summary: Minor vocabulary tweak and typo fix 775 | From: Tantek Çelik 776 | Comment: https://github.com/w3c/w3process/pull/444 777 | Closed: Accepted 778 | Resolved: Director's decision in response to AC Review 779 | -------------------------------------------------------------------------------- /snapshots/2023-05-24-doc.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | W3C Process Document 2023 (AC Review) Disposition of Comments for 2023-05-24- Draft 4 | 29 | 30 |

W3C Process Document 2023 (AC Review) Disposition of Comments for 2023-05-24- Draft

31 | 32 |
33 |
Dated Draft:
https://www.w3.org/Consortium/Process/Drafts/snapshots/2023-04 34 |
Editor's Draft:
https://www.w3.org/Consortium/Process/Drafts/ 35 |
36 | 37 | 67 |

This Disposition of Comments covers comments received during the formal AC Review period for Process 2023. 68 |

Substantive Changes

69 |

Several review comments received during the AC Review period generated proposals for substantive changes: 70 |

176 |

Editorial Changes

177 |

AC Review raised a number of suggestions for clarification, 178 | which the Process CG accepted and are summarized below: 179 |

251 |

Index of Comments and Responses

252 | 253 | 254 |
255 | Disposition Status Legend and Filters 256 |

The following color coding convention is used for comments:

257 | 258 | 265 | 266 |

Open issues are marked like this

267 | 268 |

An issue can be closed as Accepted, OutOfScope, 269 | Invalid, Rejected, or Retracted. 270 | Verified indicates commentor's acceptance of the response.

271 |
272 | 
273 | Issue 1. #
274 | Summary:  Timeline for publishing formal objections
275 | From:     Jeffrey Yasskin
276 | Comment:  https://github.com/w3c/w3process/issues/735
277 | Closed:   Deferred
278 | Verified: https://github.com/w3c/w3process/issues/735
279 | 
280 | Issue 2. #
281 | Summary:  Mention Archiving in Tooling section title
282 | From:     fantasai
283 | Comment:  https://github.com/w3c/w3process/issues/736
284 | Changes:  https://github.com/w3c/w3process/commit/14f4644c9008bf10021628d78c3238a39b139e58
285 | Closed:   Accepted
286 | Verified: Reporter is editor
287 | Resolved: Editorial
288 | 
289 | Issue 3. #
290 | Summary:  Improve wording of note about addressing FOs before advancement
291 | From:     Jeffrey Yasskin
292 | Comment:  https://github.com/w3c/w3process/issues/737
293 | Closed:   Deferred
294 | Verified: By AC comment
295 | 
296 | Issue 4. #
297 | Summary:  AC Review questionnaire option to express disagreement
298 | From:     Jeffrey Yasskin
299 | Comment:  https://github.com/w3c/w3process/issues/738
300 | Response: https://github.com/w3c/w3process/issues/738#issuecomment-1525644054
301 | Response: https://github.com/w3c/w3process/issues/738#issuecomment-1544643945
302 | Closed:   Invalid
303 | Verified: https://github.com/w3c/w3process/issues/738#issuecomment-1544662439
304 | 
305 | Issue 5. #
306 | Summary:  FO resolution isn't explicitly invoked
307 | From:     Jeffrey Yasskin
308 | Comment:  https://github.com/w3c/w3process/issues/739
309 | Closed:   Deferred
310 | Verified: By AC comment
311 | 
312 | Issue 6. #
313 | Summary:  Clarify that AB/TAG approval uses their normal decision policy
314 | From:     Jeffrey Yasskin
315 | Comment:  https://github.com/w3c/w3process/issues/741
316 | Closed:   Deferred
317 | Verified: By AC comment
318 | 
319 | Issue 7. #
320 | Summary:  Clarify where Submission Appeals go
321 | From:     Jeffrey Yasskin
322 | Comment:  https://github.com/w3c/w3process/issues/742
323 | Response: https://github.com/w3c/w3process/issues/742#issuecomment-1544656020
324 | Changes:  https://github.com/w3c/w3process/commit/189b5ec060b46094c70a3ff343cc0ddb7968e0de
325 | Closed:   Accepted
326 | Verified: [reporter thumbs up on response]
327 | Resolved: Bugfix
328 | 
329 | Issue 8. #
330 | Summary:  Remove normative keywords from non-normative notes
331 | From:     Jeffrey Yasskin
332 | Comment:  https://github.com/w3c/w3process/issues/745
333 | Closed:   Deferred
334 | Verified: https://github.com/w3c/w3process/issues/745
335 | 
336 | Issue 9. #
337 | Summary:  Avoid two different meanings for “sustain”
338 | From:     Jeffrey Yasskin
339 | Comment:  https://github.com/w3c/w3process/issues/746
340 | Changes:  https://github.com/w3c/w3process/pull/762
341 | Closed:   Accepted
342 | Resolved: Editorial
343 | 
344 | Issue 10. #
345 | Summary:  Clarify which formal contexts require FO for dissent
346 | From:     Chris Needham
347 | Comment:  https://github.com/w3c/w3process/issues/746#issuecomment-1549991610
348 | Response: https://github.com/w3c/w3process/issues/746#issuecomment-1553935933
349 | Changes:  https://github.com/w3c/w3process/pull/763
350 | Closed:   Accepted
351 | Verified: Reporter is change author
352 | Resolved: Editorial
353 | 
354 | Issue 11. #
355 | Summary:  Clarify purpose of dismissal
356 | From:     Mark Nottingham
357 | Comment:  https://github.com/w3c/w3process/issues/747
358 | Response: https://github.com/w3c/w3process/issues/747#issuecomment-1544708674
359 | Changes:  https://github.com/w3c/w3process/pull/757/commits/4f20cd1b0ebb44b07987e8ceedbda4b8db382fb7
360 | Closed:   Accepted
361 | Verified: https://github.com/w3c/w3process/issues/747#issuecomment-1562212194
362 | 
363 | Issue 12. #
364 | Summary:  “potential Council member” phrasing is wordy
365 | From:     Mark Nottingham
366 | Comment:  https://github.com/w3c/w3process/issues/747
367 | Response: https://github.com/w3c/w3process/issues/747#issuecomment-1544708674
368 | Response: https://github.com/w3c/w3process/issues/747#issuecomment-1545309505
369 | Closed:   Rejected
370 | Verified: https://github.com/w3c/w3process/issues/747#issuecomment-1562212194
371 | Resolved: Editorial
372 | 
373 | Issue 13. #
374 | Summary:  Note wrt nature of Council is oddly placed
375 | From:     Mark Nottingham
376 | Comment:  https://github.com/w3c/w3process/issues/747#issuecomment-1529019322
377 | Response: https://github.com/w3c/w3process/issues/747#issuecomment-1544708674
378 | Closed:   Rejected
379 | Verified: https://github.com/w3c/w3process/issues/747#issuecomment-1562212194
380 | Resolved: Editorial
381 | 
382 | Issue 14. #
383 | Summary:  Unclear antecedent for “they”
384 | From:     Mark Nottingham
385 | Comment:  https://github.com/w3c/w3process/issues/747#issuecomment-1529019871
386 | Changes:  https://github.com/w3c/w3process/pull/757/commits/e23a195b5775231ea33ca169ec204217cf33948d
387 | Closed:   Accepted
388 | Verified: https://github.com/w3c/w3process/issues/747#issuecomment-1562212194
389 | Resolved: Editorial
390 | 
391 | Issue 15A. #
392 | Summary:  Use supermajority for dismissal voting (instead of majority)
393 | From:     Mark Nottingham
394 | Comment:  https://github.com/w3c/w3process/issues/748
395 | Comment:  https://github.com/w3c/w3process/issues/748#issuecomment-1529728892
396 | Response: https://github.com/w3c/w3process/issues/748#issuecomment-1529464611
397 | Response: https://github.com/w3c/w3process/issues/748#issuecomment-1530089344
398 | Response: https://github.com/w3c/w3process/issues/748#issuecomment-1545665413
399 | Changes:  https://github.com/w3c/w3process/pull/760
400 | Closed:   Rejected
401 | Note:     The AB resolved not to change the voting threshold,
402 |           but did resolve to make the dismissal vote counts public.
403 | Resolved: AB May 2023 F2F
404 | 
405 | Issue 15B. #
406 | Summary:  Use single-person veto for dismissal (instead of majority)
407 | From:     Nigel Megitt
408 | Comment:  https://github.com/w3c/w3process/issues/748#issuecomment-1531724271
409 | Response: https://github.com/w3c/w3process/issues/748#issuecomment-1545665413
410 | Changes:  https://github.com/w3c/w3process/pull/760
411 | Closed:   Rejected
412 | Note:     The AB resolved not to change the voting threshold,
413 |           but did resolve to make the dismissal vote counts public.
414 | Resolved: AB May 2023 F2F
415 | 
416 | Issue 16. #
417 | Summary:  Improve transparency of dismissal process
418 | From:     Advisory Board
419 | Comment   https://github.com/w3c/w3process/issues/748
420 | Response: https://github.com/w3c/w3process/issues/748#issuecomment-1545665413
421 | Changes:  https://github.com/w3c/w3process/pull/760
422 | Open:     Accepted by AB, proposed to the Director for either Process or /Guide
423 | Note:     As a result of the discussion in GitHub issue 748 (see above)
424 |           the AB resolved to require reporting dismissal vote counts,
425 |           to show the level of support or concern for the participation
426 |           of each member of the Council.
427 | 
428 | Issue 17. #
429 | Summary:  AB/TAG Decisions and Council Conflict of Interest
430 | From:     Mark Nottingham
431 | Comment:  https://github.com/w3c/w3process/issues/749
432 | Response: https://github.com/w3c/w3process/issues/749#issuecomment-1551892219
433 | Changes:  https://github.com/w3c/w3process/pull/761
434 | Open:     Accepted by AB, recommended to adopt into practice by CG
435 | Note:     The AB resolved not to remove the TAG/AB from the Council,
436 |           but to exclude them from a Council Decision vote (if any)
437 |           if the decision/proposal in question came from the TAG/AB.
438 |           They may still participate in a consensus Council Decision.
439 | Note:     The Council can always delegate in cases where it feels that
440 |           would provide a more legitimate decision; and the AC still
441 |           retains the ability to appeal a Council Decision if necessary.
442 | Resolved: AB May 2023 F2F
443 | 
444 | Issue 18. #
445 | Summary:  Expressing disagreement in AC review without Formal Objection
446 | From:     Mark Nottingham
447 | Comment:  https://github.com/w3c/w3process/issues/750
448 | Response: https://github.com/w3c/w3process/issues/750#issuecomment-1529053389
449 | Closed:   Retracted
450 | 
451 | Issue 19A. #
452 | Summary:  Council/Team Powers of Mitigation too broad
453 | From:     Mark Nottingham
454 | Comment:  https://github.com/w3c/w3process/issues/751
455 | Response: https://github.com/w3c/w3process/issues/751#issuecomment-1529453863
456 | Comment:  https://github.com/w3c/w3process/issues/751#issuecomment-1554703461
457 | Response: https://github.com/w3c/w3process/issues/751#issuecomment-1559068321
458 | Closed:   Invalid
459 | Verified: https://github.com/w3c/w3process/issues/751#issuecomment-1563685512
460 | 
461 | Issue 19B. #
462 | Summary:  Limits on Council/Team Powers of Mitigation hard to understand
463 | From:     Mark Nottingham
464 | Comment:  https://github.com/w3c/w3process/issues/751#issuecomment-1560306816
465 | Response: https://github.com/w3c/w3process/issues/751#issuecomment-1560492526
466 | Closed:   Deferred
467 | Verified: https://github.com/w3c/w3process/issues/751#issuecomment-1563685512
468 | 
469 | Issue 20. #
470 | Summary:  Publication of Minority opinions
471 | From:     Mark Nottingham
472 | Comment:  https://github.com/w3c/w3process/issues/752
473 | Response: https://github.com/w3c/w3process/issues/752#issuecomment-1529175671
474 | Closed:   Retracted
475 | 
476 | Issue 21. #
477 | Summary:  Why is AC review of MoU appeal-based rather than approval-based?
478 | From:     Mark Nottingham
479 | Comment:  https://github.com/w3c/w3process/issues/753
480 | Response: https://github.com/w3c/w3process/issues/753#issuecomment-1529194913
481 | Response: https://github.com/w3c/w3process/issues/753#issuecomment-1530815822
482 | Closed:   Deferred
483 | Verified: https://github.com/w3c/w3process/issues/753#issuecomment-1530815822
484 | 
485 | Issue 22. #
486 | Summary:  Define “joint deliverables”
487 | From:     Eric Siow
488 | Comment:  https://github.com/w3c/w3process/issues/754
489 | Response: https://github.com/w3c/w3process/issues/754#issuecomment-1532480890
490 | Closed:   Deferred
491 | Verified: https://github.com/w3c/w3process/issues/754
492 | 
493 | Issue 23. #
494 | Summary:  What to do in case of non-responsiveness during FO resolution
495 | From:     Philippe Le Hegaret
496 | Comment:  https://github.com/w3c/w3process/issues/755
497 | Response: https://github.com/w3c/w3process/issues/755#issuecomment-1551893751
498 | Closed:   OutOfScope
499 | Note:     The AB resolved that /Guide should advise the Team to spin up
500 |           the Council after a reasonable timeout when the objector or
501 |           decider is non-responsive while trying to broker consensus or
502 |           clarify their position.
503 | Verified: Reporter is co-chair
504 | Resolved: AB May 2023 F2F
505 | 
506 | Issue 24. #
507 | Summary:  Increase size of TAG
508 | From:     Theresa O'Connor
509 | Comment:  https://github.com/w3c/AB-memberonly/issues/171
510 | Comment:  https://github.com/w3c/w3process/issues/465
511 | Comment:  https://github.com/w3c/AB-memberonly/issues/171#issuecomment-1517110155
512 | Comment:  https://github.com/w3c/AB-memberonly/issues/171#issuecomment-1517166312
513 | Response: https://github.com/w3c/AB-memberonly/issues/171#issuecomment-1551895803
514 | Changes:  https://github.com/w3c/w3process/pull/733
515 | Open:     Accepted by AB, proposed to Director
516 | Resolved: AB May 2023 F2F
517 | 
518 | Issue 25. #
519 | Summary:  Council composition is broken due to “member” vs “participant”
520 | From:     Tantek Çelik
521 | Comment:  https://github.com/w3c/w3process/issues/764
522 | Response: https://github.com/w3c/w3process/issues/764#issuecomment-1562177663
523 | Closed:   Invalid
524 | Verified: https://github.com/w3c/w3process/issues/764#issuecomment-1562300254
525 | 
526 | Issue 26. #
527 | Summary:  Various Objections
528 | From:     James Rosewell
529 | Comment:  See https://www.w3.org/2002/09/wbs/33280/Process-2023/results
530 | Open:     Formal Objection; deferred to the Director
531 | 
532 | Issue 27. #
533 | Summary:  Various Concerns
534 | From:     Jon Andrieu
535 | Comment:  See https://www.w3.org/2002/09/wbs/33280/Process-2023/results
536 | Note:     Needs specific issues / discussion to be actionable
537 | Open:     Deferred ; needs Team response
538 | 
539 | Issue 28. #
540 | Summary:  Clarify informative nature of references
541 | From:     Tantek Çelik
542 | Comment:  https://github.com/w3c/w3process/issues/765
543 | Response: https://github.com/w3c/w3process/pull/766
544 | Closed:   Approved by the Director
545 | 576 | -------------------------------------------------------------------------------- /issues-20211102.html: -------------------------------------------------------------------------------- 1 | 2 | 12 | 13 | 14 | 15 | 16 | 70 | 71 | Disposition of Comments for the 2023 cycle of the W3C Process 72 | 73 |
74 |

75 |

Disposition of Comments for the 2023 cycle of the W3C Process

76 |

77 |

Copyright © 2023 World Wide Web Consortium. W3C® liability, trademark and permissive document license rules apply. 78 |

79 |
80 | 81 |

82 | Introduction

83 | 84 |

85 | This documents the way issues were filed and resolved during the revision cycle of the W3C Process 86 | starting from the publication of the 2 November 2021 version 87 | leading to the proposed 2023 version. 88 | 89 |

90 | All issues were tracked in GitHub. 91 | Closed issues and pull requests were given labels to characterize the way they were closed; 92 | see the glossary for details. 93 | 94 |

95 | Open issues

96 | 97 |
98 | 99 | 66 issues reported during this cycle or earlier remain open, 100 | but were deferred by the group to be handled during 101 | a subsequent revision of the W3C Process. 102 | 103 |

104 | 105 | Live list from GitHub. 106 |

Static copy of this list at the time of writing: 107 |

175 |
176 | 177 |
178 | 179 | No issue remains open (unless deferred). 180 | 181 |

182 | 183 | Live list from GitHub. 184 | 189 |

190 | 191 |

192 | Issues Resolved

193 | 194 |
195 | 196 | 125 issues or pull requests were closed as 197 | Closed: Accepted, 198 | Closed: Retracted, 199 | or Closed: Question answered. 200 | 201 |

202 | 203 | Live list from GitHub. 204 |

Static copy of this list at the time of writing: 205 |

332 |
333 | 334 |

335 | Invalid, Duplicate, Out-of-scope

336 | 337 |
338 | 339 | 20 issues or pull requests were closed as 340 | Closed: Invalid, 341 | Closed: Out of scope, 342 | or Closed: Duplicate, 343 | and tagged as either 344 | Commenter satisfied/accepting 345 | or Commenter Timed Out (Assumed Satisfied). 346 | 347 |

348 | 349 | Live list from GitHub. 350 |

Static copy of this list at the time of writing: 351 |

373 |
374 | 375 |
376 | 377 | No issues or pull requests were closed as 378 | Closed: Invalid, 379 | Closed: Out of scope, 380 | or Closed: Duplicate, 381 | and tagged as 382 | Commenter Response Pending. 383 | 384 |

385 | 386 | Live list from GitHub. 387 | 392 |

393 | 394 |
395 | 396 | No issues or pull requests were closed as 397 | Closed: Invalid, 398 | Closed: Out of scope, 399 | or Closed: Duplicate, 400 | and tagged as 401 | Commenter Not Satisfied. 402 | 403 |

404 | 405 | Live list from GitHub. 406 | 411 |

412 | 413 |

414 | Rejected Issues

415 | 416 |
417 | 418 | 12 issues or pull requests were closed as 419 | Closed: Rejected 420 | and tagged as either 421 | Commenter satisfied/accepting 422 | or Commenter Timed Out (Assumed Satisfied). 423 | 424 |

425 | 426 | Live list from GitHub. 427 |

Static copy of this list at the time of writing: 428 |

442 |
443 | 444 |
445 | 446 | 1 issues was closed as 447 | Closed: Rejected 448 | and tagged as 449 | Commenter Response Pending. 450 | 451 |

452 | 453 | Live list from GitHub. 454 |

Static copy of this list at the time of writing: 455 |

458 |
459 | 460 |
461 | 462 | 2 issues were closed as 463 | Closed: Rejected 464 | and tagged as 465 | Commenter Not Satisfied. 466 | 467 |

468 | 469 | Live list from Github. 470 |

471 |
Number: 472 |
473 | Issue 628 474 | 475 |
Title: 476 |
477 | Limit the scope of FO Council deliberations 478 | 479 |
From: 480 |
481 | Pierre-Anthony Lemieux 482 | 483 |
Summary: 484 |
485 | The FO Council should sustain an FO only if rejecting the FO would necessarily result in a violation of the W3C process. 486 | As it stands, there are no limitations to what folks can file as FO and what the Council will consider. 487 | 488 |
Resolution to close: 489 |
490 | RESOLVED: Close 628 no change, flag Commenter Not Satisfied 491 | 492 |
Summary of rationale to close: 493 |
494 | W3C normally makes decisions by consensus. 495 | Formal objections happen when we fail to reach consensus 496 | (regardless of why) 497 | but try to move forward anyway. 498 | The Council is there to determine the best way forward 499 | in the face of irreconcilable differences of opinion, 500 | not to adjudicate right vs wrong in terms of rules being followed. 501 | Simple process violations typically result in the team handling them, not FOs. 502 | Focusing the Council solely on process violations would make the Council mostly useless. 503 | 504 |
AB Confirmation: 505 |
506 | RESOLUTION: “The AB accepts the resolution of issue #628 knowing it was closed over objection.” 507 |
508 |
509 |
Number: 510 |
511 | Issue 478 512 | 513 |
Title: 514 |
515 | Appeal process for proposals 516 | 517 |
From: 518 |
519 | James Rosewell 520 | 521 |
Summary: 522 |
523 | From the opening GitHub comment: 524 |
525 | Group chairs [should] make the initial decision should a complaint be received 526 | relating to the scope of a proposal fulfilling the goals of the W3C 527 | as defined in the membership agreement […] 528 | within 7 elapsed days. 529 | […] 530 | Should disagreement remain, 531 | the General Counsel of the W3C [would] be asked to intervene 532 | by at least one member to seek to obtain consensus within 7 elapsed days. 533 | Should consensus still not be possible 534 | a majority vote of the AC […] [should] make the final decision within 7 elapsed days. 535 | In the event of a tie arbitration [should] be used to resolve the matter. 536 |
537 | 538 |
Resolution to close: 539 |
540 | RESOLVED: #478 is closed 541 | 542 |
Summary of rationale to close: 543 |
544 | Full details in GitHub comment, 545 | with the main point being: 546 |
547 | “Adding” an appeal process would be redundant with existing appeal processes. 548 | From expressing disagreement when a proposal is initially made, 549 | to registering dissent, 550 | to having FOs processed by the Council, 551 | to having the ability to file an AC Appeal, 552 | there's already a path to express and escalate disagreement, 553 | and no decision is final until these are all exhausted. 554 |
555 | 556 |
AB Confirmation: 557 |
558 | RESOLUTION: “The AB accepts the resolution of issue #478 as summarized in w3c/w3process#478 (comment)”. 559 |
560 |
561 | 562 |
563 | 564 |

565 | Glossary

566 | 567 |

568 | All closed issues were given one of the following label: 569 | 570 |

571 |
Closed: Accepted 572 |
573 | A proposition was made or a problem was raised, 574 | and the group accepted the proposition 575 | or some alternative solution that addresses the problem. 576 | 577 |
Closed: Retracted 578 |
579 | A proposition was made or a problem was raised, 580 | but he person who had done so eventually changed their mind 581 | or otherwise decided no longer to pursue the question. 582 | 583 |
Closed: Question answered 584 |
585 | An issue was open which was more of a request for information 586 | than a problem statement or a suggestion for change, 587 | and the question asked was given an answer. 588 | 589 |
Closed: Duplicate 590 |
591 | The issue or pull request is redundant with another one. 592 | 593 |
Closed: Out of scope 594 |
595 | The issue is not about the W3C Process. 596 | 597 |
Closed: Invalid 598 |
599 | The issue is as stated is inapplicable. 600 | It may for instance raise a problem with a piece of text 601 | which is no longer present in the current version of the Process. 602 | 603 |
Closed: Rejected 604 |
605 | The Group decided to close the issue 606 | without making any change to the Process. 607 |
608 | 609 |

610 | Further, for all issues classified as Closed: Rejected, 611 | Closed: Invalid, 612 | Closed: Out of scope, 613 | or Closed: Duplicate, 614 | the group sought to confirm with the person who raised the issue 615 | if they were willing to accept the conclusions of the group, 616 | which was documented by additional labels: 617 |

618 |
Commenter satisfied/accepting 619 |
620 | The conclusion was confirmed as accepted by the commenter, 621 | even if it may not be their preferred choice. 622 | 623 |
Commenter Timed Out (Assumed Satisfied) 624 |
625 | The commenter was explicitly asked whether they were willing to accept the conclusion, 626 | given ample time do answer, 627 | and did not respond. 628 | In the absence of negative feedback, 629 | it is assumed they are OK with the conclusion. 630 | 631 |
Commenter Response Pending 632 |
633 | The commenter was explicitly asked whether they were willing to accept the conclusion, 634 | and has not yet responded. 635 | Not enough time has elapsed yet 636 | to draw any conclusion 637 | as to their satisfaction. 638 | 639 |
Commenter Not Satisfied 640 |
641 | The commenter has explicitly indicated 642 | that the Group’s conclusion was not acceptable to them. 643 |
644 | --------------------------------------------------------------------------------