From 8de16c6eafb9c0e6c4a21e110d81fe0e6e1b007a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Philip=20J=C3=A4genstedt?= Date: Tue, 5 Jul 2022 17:04:06 +0200 Subject: [PATCH 01/16] Interop 2023 --- rfcs/interop_2023.md | 84 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 84 insertions(+) create mode 100644 rfcs/interop_2023.md diff --git a/rfcs/interop_2023.md b/rfcs/interop_2023.md new file mode 100644 index 00000000..49bdaf98 --- /dev/null +++ b/rfcs/interop_2023.md @@ -0,0 +1,84 @@ +# RFC 116: Interop 2023 + +## Summary + +Interop 2023 is an effort to improve interoperability in areas believed to be important to web developers and users. This is the next iteration of [Interop 2022](https://github.com/web-platform-tests/interop-2022), an effort which is still ongoing at the time of this RFC. + +The focus areas will be selected by a proposals period followed by a proposals review and selection process. The [Interop 2023 team](https://github.com/orgs/web-platform-tests/teams/interop-2023) will manage this process and make decisions based on consensus, see [governance](#governance). + +There will be a dashboard at https://wpt.fyi/interop-2023. + +## Details + +### Timeline + +During 2022: + +- September 15 to October 15: Proposals period. +- October 16 to October 30: Proposal discussion/refinement. (New proposals no longer accepted.) +- November 1 to November 30: Proposal selection. (The team must reach consensus no later than November 30.) +- December 1 to December 16: + - Start review of tests. Write needed tests. + - Start involving PR teams. Write rough drafts of announcements. Begin creating dashboard. + +During 2023: + +- January 9 to January 20: + - Finalize test selection. + - Complete announcement plans. Prepare dashboard for launch. +- January 23 to January 27: Launch. + +If necessary, additional changes to the test lists can be made throughout the year with the consensus of the team, see [updating the tests](#updating-the-tests). + +### Governance + +The [Interop 2023 team](https://github.com/orgs/web-platform-tests/teams/interop-2023) will manage the overall Interop 2023 effort. The team will be formed with the same initial membership as the [’22 team](https://github.com/orgs/web-platform-tests/teams/interop-2022). + +The team will meet regularly, with agenda issues created in the repo at least 48 hours in advance, and meeting minutes posted in the issue. + +The team makes decisions based on consensus, which is defined as support from at least two participating organizations and no objections. Additionally, during the [proposal selection](#proposal-selection) process, the positions of implementers in each browser engine are used to determine whether a proposal will be accepted, to ensure that the proposal is on track to interoperability across browser engines. + +The Interop 2023 effort is subject to the [WPT code of conduct](https://github.com/web-platform-tests/wpt/blob/master/CODE_OF_CONDUCT.md). + +The [WPT core team](https://github.com/orgs/web-platform-tests/teams/wpt-core-team/) is not expected to be involved beyond this RFC, but could in exceptional cases intervene via the RFC process to amend the governance. + +### Proposals + +During the proposals period (September 15 to October 15), proposals are submitted as issues in the [Interop 2023 repo](https://github.com/web-platform-tests/interop-2023). A proposal should be as specific as reasonably possible, but multiple proposals may be grouped later in the selection process. + +The following information should be provided: + +- Standard/specification for this feature +- Current test results on wpt.fyi +- How widely used is this feature? For example, [use counters](https://www.chromestatus.com/metrics/feature/popularity), [HTTP Archive](https://httparchive.org/) and [State of CSS](https://2021.stateofcss.com/en-US/features/) can help. +- Is this area a problem for web developers? For example, survey data and browser bug counts can help. +- Is this area a problem for users? + +A proposals template will be created to help with this. + +### Proposal selection + +Proposal selection (November 1 to November 30) will be done using a positions process similar to [Interop 2022](https://github.com/web-platform-tests/interop-2022/issues/38) but with some changes. The process is: + +- Each participating organization takes one of 3 positions on each proposal: support, neutral, or oppose. +- A proposal is accepted if there is implementer support coming from at least 2 browser engines, and no opposition. +- The team reviews the accepted proposals and can decide to group multiple proposals, or to drop proposals. Both actions require team consensus. +- The final list of accepted proposals is decided by team consensus no later than November 30. + +The purpose of the second round of grouping and optionally dropping proposals is to avoid sub-proposals as in the Interop 2022 process. Instead, proposals will be as specific as reasonably possible, and can be grouped into themes afterwards. The expectation is that proposals will only be dropped if there is consensus that they don't make sense in light of which other proposals were accepted. + +### Updating the tests + +No test suite is perfect, and there will likely be a need to add, remove or rewrite tests during the course of the year. To suggest changes, file an issue on the [Interop 2023 repo](https://github.com/web-platform-tests/interop-2023). The team will make decisions based on consensus, see [governance](#governance). + +### Metrics + +Per-area and overall metrics will be defined in a similar fashion to [Interop 2022](https://github.com/web-platform-tests/rfcs/blob/master/rfcs/interop_2022.md#metrics). The number of areas and their contribution to the total score will be decided in the proposal selection phase. + +### Dashboard + +A public dashboard tracking the metrics over time will be available at https://wpt.fyi/interop-2023. + +## Risks + +No set of tests is without flaws, and trying to improve a metric based on test results can lead to bad outcomes such as shallow implementations that pass the tests but still isn't usable in practice. The main mitigation for this is a careful review of the tests for the proposed areas, and to include only tests that are judged to be high quality. Also, the tests are not frozen but can be updated or even removed during the year as issues are uncovered. From 48f9fe782431615c83c67cb2b65e87b623c45fde Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Philip=20J=C3=A4genstedt?= Date: Fri, 8 Jul 2022 10:51:27 +0200 Subject: [PATCH 02/16] Leave core team role implicit --- rfcs/interop_2023.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/rfcs/interop_2023.md b/rfcs/interop_2023.md index 49bdaf98..602afcef 100644 --- a/rfcs/interop_2023.md +++ b/rfcs/interop_2023.md @@ -40,8 +40,6 @@ The team makes decisions based on consensus, which is defined as support from at The Interop 2023 effort is subject to the [WPT code of conduct](https://github.com/web-platform-tests/wpt/blob/master/CODE_OF_CONDUCT.md). -The [WPT core team](https://github.com/orgs/web-platform-tests/teams/wpt-core-team/) is not expected to be involved beyond this RFC, but could in exceptional cases intervene via the RFC process to amend the governance. - ### Proposals During the proposals period (September 15 to October 15), proposals are submitted as issues in the [Interop 2023 repo](https://github.com/web-platform-tests/interop-2023). A proposal should be as specific as reasonably possible, but multiple proposals may be grouped later in the selection process. From f44a434bb72c79ac6bbd95ce092cd2085df068b9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Philip=20J=C3=A4genstedt?= Date: Sun, 24 Jul 2022 13:13:05 +0200 Subject: [PATCH 03/16] Define investigation effort proposals --- rfcs/interop_2023.md | 26 +++++++++++++++++++++----- 1 file changed, 21 insertions(+), 5 deletions(-) diff --git a/rfcs/interop_2023.md b/rfcs/interop_2023.md index 602afcef..71f77c2a 100644 --- a/rfcs/interop_2023.md +++ b/rfcs/interop_2023.md @@ -44,15 +44,31 @@ The Interop 2023 effort is subject to the [WPT code of conduct](https://github.c During the proposals period (September 15 to October 15), proposals are submitted as issues in the [Interop 2023 repo](https://github.com/web-platform-tests/interop-2023). A proposal should be as specific as reasonably possible, but multiple proposals may be grouped later in the selection process. -The following information should be provided: +There are two kinds of proposals: focus areas where progress is measured using test results, and investigation efforts where progress is measuring against a task list. For both kinds of proposals, finishing them should meaningfully advance the state of interoperability for the web platform. + +#### Focus areas + +These proposals are for existing web platform features with good a spec and test suite which can be used to improve interoperability. Progress is measured by test results on wpt.fyi. + +The following information should be provided in a proposal: -- Standard/specification for this feature -- Current test results on wpt.fyi -- How widely used is this feature? For example, [use counters](https://www.chromestatus.com/metrics/feature/popularity), [HTTP Archive](https://httparchive.org/) and [State of CSS](https://2021.stateofcss.com/en-US/features/) can help. - Is this area a problem for web developers? For example, survey data and browser bug counts can help. - Is this area a problem for users? +- How widely used is this feature? For example, [use counters](https://www.chromestatus.com/metrics/feature/popularity), [HTTP Archive](https://httparchive.org/) and [State of CSS](https://2021.stateofcss.com/en-US/features/) can help. +- Standard/specification for this feature. +- A list of tests on wpt.fyi which will be used to score progress towards interoperability on the feature. + +#### Investigation efforts -A proposals template will be created to help with this. +If an area doesn't have a good spec and test suite it's not possible to use wpt.fyi test results to judge progress. Instead, some other work is needed to bring the area to state where test results can be used. + +The following information should be provided in a proposal: + +- Is this area a problem for web developers? For example, survey data and browser bug counts can help. +- Is this area a problem for users? +- How widely used is this feature? For example, [use counters](https://www.chromestatus.com/metrics/feature/popularity), [HTTP Archive](https://httparchive.org/) and [State of CSS](https://2021.stateofcss.com/en-US/features/) can help. +- Standard/specification for this feature, if any. +- A list of tasks which should be completed as part of the effort. This could be producing a report for a working group, a list of spec bugs which should be resolved, or tests/infrastructure which need to be created. A completed investigation effort should unblock the feature for inclusion as a regular focus area in the future. ### Proposal selection From d8e3e002d55a16453d389f0c6aee85a14b6f1f52 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Philip=20J=C3=A4genstedt?= Date: Mon, 25 Jul 2022 16:48:22 +0200 Subject: [PATCH 04/16] Simplify consensus to use the same definition everywhere --- rfcs/interop_2023.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rfcs/interop_2023.md b/rfcs/interop_2023.md index 71f77c2a..fd6276b5 100644 --- a/rfcs/interop_2023.md +++ b/rfcs/interop_2023.md @@ -36,7 +36,7 @@ The [Interop 2023 team](https://github.com/orgs/web-platform-tests/teams/interop The team will meet regularly, with agenda issues created in the repo at least 48 hours in advance, and meeting minutes posted in the issue. -The team makes decisions based on consensus, which is defined as support from at least two participating organizations and no objections. Additionally, during the [proposal selection](#proposal-selection) process, the positions of implementers in each browser engine are used to determine whether a proposal will be accepted, to ensure that the proposal is on track to interoperability across browser engines. +The team makes decisions based on consensus, which is defined as support from at least two participating organizations and no opposition. The Interop 2023 effort is subject to the [WPT code of conduct](https://github.com/web-platform-tests/wpt/blob/master/CODE_OF_CONDUCT.md). @@ -75,7 +75,7 @@ The following information should be provided in a proposal: Proposal selection (November 1 to November 30) will be done using a positions process similar to [Interop 2022](https://github.com/web-platform-tests/interop-2022/issues/38) but with some changes. The process is: - Each participating organization takes one of 3 positions on each proposal: support, neutral, or oppose. -- A proposal is accepted if there is implementer support coming from at least 2 browser engines, and no opposition. +- A proposal is accepted if there is consensus, meaning support from at least two participating organizations and no opposition. - The team reviews the accepted proposals and can decide to group multiple proposals, or to drop proposals. Both actions require team consensus. - The final list of accepted proposals is decided by team consensus no later than November 30. From 43e0847a8bdb854cf958cd46cf095d33e823dc0b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Philip=20J=C3=A4genstedt?= Date: Thu, 28 Jul 2022 10:45:41 +0300 Subject: [PATCH 05/16] Reflect planned repo/team rename --- rfcs/interop_2023.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/rfcs/interop_2023.md b/rfcs/interop_2023.md index fd6276b5..dce50a99 100644 --- a/rfcs/interop_2023.md +++ b/rfcs/interop_2023.md @@ -2,14 +2,16 @@ ## Summary -Interop 2023 is an effort to improve interoperability in areas believed to be important to web developers and users. This is the next iteration of [Interop 2022](https://github.com/web-platform-tests/interop-2022), an effort which is still ongoing at the time of this RFC. +Interop 2023 is an effort to improve interoperability in areas believed to be important to web developers and users. This is the next iteration of [Interop 2022](./interop_2022.md), an effort which is still ongoing at the time of this RFC. -The focus areas will be selected by a proposals period followed by a proposals review and selection process. The [Interop 2023 team](https://github.com/orgs/web-platform-tests/teams/interop-2023) will manage this process and make decisions based on consensus, see [governance](#governance). +The focus areas will be selected by a proposals period followed by a proposals review and selection process. The [Interop team](https://github.com/orgs/web-platform-tests/teams/interop-2022) will manage this process and make decisions based on consensus, see [governance](#governance). There will be a dashboard at https://wpt.fyi/interop-2023. ## Details +The Interop 2022 [repo](https://github.com/web-platform-tests/interop-2022) and [team](https://github.com/orgs/web-platform-tests/teams/interop-2022) will be renamed to omit the year and used for this effort as well. + ### Timeline During 2022: @@ -32,7 +34,7 @@ If necessary, additional changes to the test lists can be made throughout the ye ### Governance -The [Interop 2023 team](https://github.com/orgs/web-platform-tests/teams/interop-2023) will manage the overall Interop 2023 effort. The team will be formed with the same initial membership as the [’22 team](https://github.com/orgs/web-platform-tests/teams/interop-2022). +The [Interop team](https://github.com/orgs/web-platform-tests/teams/interop) will manage the overall Interop 2023 effort. The team will be formed by renaming the [’22 team](https://github.com/orgs/web-platform-tests/teams/interop-2022). The team will meet regularly, with agenda issues created in the repo at least 48 hours in advance, and meeting minutes posted in the issue. @@ -42,7 +44,7 @@ The Interop 2023 effort is subject to the [WPT code of conduct](https://github.c ### Proposals -During the proposals period (September 15 to October 15), proposals are submitted as issues in the [Interop 2023 repo](https://github.com/web-platform-tests/interop-2023). A proposal should be as specific as reasonably possible, but multiple proposals may be grouped later in the selection process. +During the proposals period (September 15 to October 15), proposals are submitted as issues in the [Interop repo](https://github.com/web-platform-tests/interop). A proposal should be as specific as reasonably possible, but multiple proposals may be grouped later in the selection process. There are two kinds of proposals: focus areas where progress is measured using test results, and investigation efforts where progress is measuring against a task list. For both kinds of proposals, finishing them should meaningfully advance the state of interoperability for the web platform. @@ -83,11 +85,11 @@ The purpose of the second round of grouping and optionally dropping proposals is ### Updating the tests -No test suite is perfect, and there will likely be a need to add, remove or rewrite tests during the course of the year. To suggest changes, file an issue on the [Interop 2023 repo](https://github.com/web-platform-tests/interop-2023). The team will make decisions based on consensus, see [governance](#governance). +No test suite is perfect, and there will likely be a need to add, remove or rewrite tests during the course of the year. To suggest changes, file an issue on the [Interop repo](https://github.com/web-platform-tests/interop). The team will make decisions based on consensus, see [governance](#governance). ### Metrics -Per-area and overall metrics will be defined in a similar fashion to [Interop 2022](https://github.com/web-platform-tests/rfcs/blob/master/rfcs/interop_2022.md#metrics). The number of areas and their contribution to the total score will be decided in the proposal selection phase. +Per-area and overall metrics will be defined in a similar fashion to [Interop 2022](./interop_2022.md#metrics). The number of areas and their contribution to the total score will be decided in the proposal selection phase. ### Dashboard From b0c648a0ce80378bad3f4c43fbf09b046f241e78 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Philip=20J=C3=A4genstedt?= Date: Fri, 29 Jul 2022 14:53:43 +0300 Subject: [PATCH 06/16] Update rfcs/interop_2023.md Co-authored-by: Sam Sneddon --- rfcs/interop_2023.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rfcs/interop_2023.md b/rfcs/interop_2023.md index dce50a99..d7726ef1 100644 --- a/rfcs/interop_2023.md +++ b/rfcs/interop_2023.md @@ -50,7 +50,7 @@ There are two kinds of proposals: focus areas where progress is measured using t #### Focus areas -These proposals are for existing web platform features with good a spec and test suite which can be used to improve interoperability. Progress is measured by test results on wpt.fyi. +These proposals are for existing web platform features with good a spec and automated test suite which can be used to improve interoperability. Progress is measured by test results on wpt.fyi. The following information should be provided in a proposal: From eb2bc0df5f305d3b84708fd38c4f03be90497795 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Philip=20J=C3=A4genstedt?= Date: Fri, 29 Jul 2022 14:53:49 +0300 Subject: [PATCH 07/16] Update rfcs/interop_2023.md Co-authored-by: Sam Sneddon --- rfcs/interop_2023.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rfcs/interop_2023.md b/rfcs/interop_2023.md index d7726ef1..180a8592 100644 --- a/rfcs/interop_2023.md +++ b/rfcs/interop_2023.md @@ -57,7 +57,7 @@ The following information should be provided in a proposal: - Is this area a problem for web developers? For example, survey data and browser bug counts can help. - Is this area a problem for users? - How widely used is this feature? For example, [use counters](https://www.chromestatus.com/metrics/feature/popularity), [HTTP Archive](https://httparchive.org/) and [State of CSS](https://2021.stateofcss.com/en-US/features/) can help. -- Standard/specification for this feature. +- Specification for this feature. - A list of tests on wpt.fyi which will be used to score progress towards interoperability on the feature. #### Investigation efforts From 40f4018184d3bc474179870e4023f1faba6d53f9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Philip=20J=C3=A4genstedt?= Date: Fri, 29 Jul 2022 14:53:55 +0300 Subject: [PATCH 08/16] Update rfcs/interop_2023.md Co-authored-by: Sam Sneddon --- rfcs/interop_2023.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rfcs/interop_2023.md b/rfcs/interop_2023.md index 180a8592..32a0b0b7 100644 --- a/rfcs/interop_2023.md +++ b/rfcs/interop_2023.md @@ -69,7 +69,7 @@ The following information should be provided in a proposal: - Is this area a problem for web developers? For example, survey data and browser bug counts can help. - Is this area a problem for users? - How widely used is this feature? For example, [use counters](https://www.chromestatus.com/metrics/feature/popularity), [HTTP Archive](https://httparchive.org/) and [State of CSS](https://2021.stateofcss.com/en-US/features/) can help. -- Standard/specification for this feature, if any. +- Specification for this feature, if any. - A list of tasks which should be completed as part of the effort. This could be producing a report for a working group, a list of spec bugs which should be resolved, or tests/infrastructure which need to be created. A completed investigation effort should unblock the feature for inclusion as a regular focus area in the future. ### Proposal selection From 3a674e9d12644fc3b90ac0c31a7bfaff66b97619 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Philip=20J=C3=A4genstedt?= Date: Thu, 4 Aug 2022 13:04:44 +0200 Subject: [PATCH 09/16] Update rfcs/interop_2023.md --- rfcs/interop_2023.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rfcs/interop_2023.md b/rfcs/interop_2023.md index 32a0b0b7..c99176ca 100644 --- a/rfcs/interop_2023.md +++ b/rfcs/interop_2023.md @@ -89,7 +89,7 @@ No test suite is perfect, and there will likely be a need to add, remove or rewr ### Metrics -Per-area and overall metrics will be defined in a similar fashion to [Interop 2022](./interop_2022.md#metrics). The number of areas and their contribution to the total score will be decided in the proposal selection phase. +Per-area and overall metrics will be defined in a similar (but not necessarily identical) fashion to [Interop 2022](./interop_2022.md#metrics). The number of areas and their contribution to the total score will be decided in the proposal selection phase. ### Dashboard From 6b4f42e520509ca124b6e0017d6dd9ccccc40645 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Philip=20J=C3=A4genstedt?= Date: Thu, 11 Aug 2022 16:28:09 +0200 Subject: [PATCH 10/16] Address remaining feedback --- rfcs/interop_2023.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/rfcs/interop_2023.md b/rfcs/interop_2023.md index c99176ca..ea3a385d 100644 --- a/rfcs/interop_2023.md +++ b/rfcs/interop_2023.md @@ -10,7 +10,7 @@ There will be a dashboard at https://wpt.fyi/interop-2023. ## Details -The Interop 2022 [repo](https://github.com/web-platform-tests/interop-2022) and [team](https://github.com/orgs/web-platform-tests/teams/interop-2022) will be renamed to omit the year and used for this effort as well. +The Interop 2022 [repo](https://github.com/web-platform-tests/interop-2022) and [team](https://github.com/orgs/web-platform-tests/teams/interop-2022) will be renamed to omit the year and used for this effort as well. Proposals from different years will be distinguished by labels or milestones. ### Timeline @@ -36,17 +36,19 @@ If necessary, additional changes to the test lists can be made throughout the ye The [Interop team](https://github.com/orgs/web-platform-tests/teams/interop) will manage the overall Interop 2023 effort. The team will be formed by renaming the [’22 team](https://github.com/orgs/web-platform-tests/teams/interop-2022). -The team will meet regularly, with agenda issues created in the repo at least 48 hours in advance, and meeting minutes posted in the issue. - The team makes decisions based on consensus, which is defined as support from at least two participating organizations and no opposition. +The team will meet regularly, with agenda issues created in the repo at least 48 hours in advance, and meeting minutes posted in the issue. Decisions can be made both in meetings and in the repository, as long as consensus can be established. + The Interop 2023 effort is subject to the [WPT code of conduct](https://github.com/web-platform-tests/wpt/blob/master/CODE_OF_CONDUCT.md). ### Proposals -During the proposals period (September 15 to October 15), proposals are submitted as issues in the [Interop repo](https://github.com/web-platform-tests/interop). A proposal should be as specific as reasonably possible, but multiple proposals may be grouped later in the selection process. +During the proposals period (September 15 to October 15), proposals are submitted in the [Interop repo](https://github.com/web-platform-tests/interop). A proposal should be as specific as reasonably possible, but multiple proposals may be grouped later in the selection process. + +To make proposal scope unambiguous, accepted proposals should be fully documented in the repository. To this end, and to make proposal review easier, the team may require that proposals are submitted as pull requests. Whether and how discussions, issues and pull requests are used in the proposals process is left to the team to decide before the proposal period begins. -There are two kinds of proposals: focus areas where progress is measured using test results, and investigation efforts where progress is measuring against a task list. For both kinds of proposals, finishing them should meaningfully advance the state of interoperability for the web platform. +There are two kinds of proposals: focus areas where progress is measured using test results, and investigation efforts where progress is measuring against a task list. #### Focus areas @@ -77,8 +79,8 @@ The following information should be provided in a proposal: Proposal selection (November 1 to November 30) will be done using a positions process similar to [Interop 2022](https://github.com/web-platform-tests/interop-2022/issues/38) but with some changes. The process is: - Each participating organization takes one of 3 positions on each proposal: support, neutral, or oppose. -- A proposal is accepted if there is consensus, meaning support from at least two participating organizations and no opposition. -- The team reviews the accepted proposals and can decide to group multiple proposals, or to drop proposals. Both actions require team consensus. +- A proposal is tentatively accepted if there is consensus, meaning support from at least two participating organizations and no opposition. +- The team reviews the proposals and can decide to group multiple proposals, or to drop proposals. Proposals that got only neutral positions can also be included. All changes at this point require team consensus; by default the outcome of the previous step stands. - The final list of accepted proposals is decided by team consensus no later than November 30. The purpose of the second round of grouping and optionally dropping proposals is to avoid sub-proposals as in the Interop 2022 process. Instead, proposals will be as specific as reasonably possible, and can be grouped into themes afterwards. The expectation is that proposals will only be dropped if there is consensus that they don't make sense in light of which other proposals were accepted. From 67e27f4c16b261c1c15d43c83edae970eab39f57 Mon Sep 17 00:00:00 2001 From: "Michael[tm] Smith" Date: Thu, 18 Aug 2022 08:49:54 +0900 Subject: [PATCH 11/16] Update rfcs/interop_2023.md --- rfcs/interop_2023.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rfcs/interop_2023.md b/rfcs/interop_2023.md index ea3a385d..bcb93b29 100644 --- a/rfcs/interop_2023.md +++ b/rfcs/interop_2023.md @@ -4,7 +4,7 @@ Interop 2023 is an effort to improve interoperability in areas believed to be important to web developers and users. This is the next iteration of [Interop 2022](./interop_2022.md), an effort which is still ongoing at the time of this RFC. -The focus areas will be selected by a proposals period followed by a proposals review and selection process. The [Interop team](https://github.com/orgs/web-platform-tests/teams/interop-2022) will manage this process and make decisions based on consensus, see [governance](#governance). +The focus areas will be selected by a proposals period followed by a proposals-review-and-selection process. The [Interop team](https://github.com/orgs/web-platform-tests/teams/interop-2022) will manage this process and make decisions based on consensus; see [governance](#governance). There will be a dashboard at https://wpt.fyi/interop-2023. From 28b499b69aa1aa87348ebcff74dbea3dc41c70a7 Mon Sep 17 00:00:00 2001 From: "Michael[tm] Smith" Date: Thu, 18 Aug 2022 08:50:42 +0900 Subject: [PATCH 12/16] Update rfcs/interop_2023.md --- rfcs/interop_2023.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rfcs/interop_2023.md b/rfcs/interop_2023.md index bcb93b29..cc77686d 100644 --- a/rfcs/interop_2023.md +++ b/rfcs/interop_2023.md @@ -30,7 +30,7 @@ During 2023: - Complete announcement plans. Prepare dashboard for launch. - January 23 to January 27: Launch. -If necessary, additional changes to the test lists can be made throughout the year with the consensus of the team, see [updating the tests](#updating-the-tests). +If necessary, additional changes to the test lists can be made throughout the year with the consensus of the team; see [updating the tests](#updating-the-tests). ### Governance From 96743c519a1320c12a678b597acbd12747f70d84 Mon Sep 17 00:00:00 2001 From: "Michael[tm] Smith" Date: Thu, 18 Aug 2022 08:51:18 +0900 Subject: [PATCH 13/16] Update rfcs/interop_2023.md --- rfcs/interop_2023.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rfcs/interop_2023.md b/rfcs/interop_2023.md index cc77686d..d83ed608 100644 --- a/rfcs/interop_2023.md +++ b/rfcs/interop_2023.md @@ -36,7 +36,7 @@ If necessary, additional changes to the test lists can be made throughout the ye The [Interop team](https://github.com/orgs/web-platform-tests/teams/interop) will manage the overall Interop 2023 effort. The team will be formed by renaming the [’22 team](https://github.com/orgs/web-platform-tests/teams/interop-2022). -The team makes decisions based on consensus, which is defined as support from at least two participating organizations and no opposition. +The team makes decisions based on consensus, which is defined as support from at least two participating organizations, and no opposition. The team will meet regularly, with agenda issues created in the repo at least 48 hours in advance, and meeting minutes posted in the issue. Decisions can be made both in meetings and in the repository, as long as consensus can be established. From 85a1bef091bae46ad3e3ea0b33e44ad908691791 Mon Sep 17 00:00:00 2001 From: "Michael[tm] Smith" Date: Thu, 18 Aug 2022 08:52:26 +0900 Subject: [PATCH 14/16] Update rfcs/interop_2023.md --- rfcs/interop_2023.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rfcs/interop_2023.md b/rfcs/interop_2023.md index d83ed608..0f6690cb 100644 --- a/rfcs/interop_2023.md +++ b/rfcs/interop_2023.md @@ -48,7 +48,7 @@ During the proposals period (September 15 to October 15), proposals are submitte To make proposal scope unambiguous, accepted proposals should be fully documented in the repository. To this end, and to make proposal review easier, the team may require that proposals are submitted as pull requests. Whether and how discussions, issues and pull requests are used in the proposals process is left to the team to decide before the proposal period begins. -There are two kinds of proposals: focus areas where progress is measured using test results, and investigation efforts where progress is measuring against a task list. +There are two kinds of proposals: focus areas where progress is measured using test results, and investigation efforts where progress is measured against a task list. #### Focus areas From 18c869d5db2daadf4d3255ebc0352b26b5465ad1 Mon Sep 17 00:00:00 2001 From: "Michael[tm] Smith" Date: Thu, 18 Aug 2022 08:53:44 +0900 Subject: [PATCH 15/16] Update rfcs/interop_2023.md --- rfcs/interop_2023.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rfcs/interop_2023.md b/rfcs/interop_2023.md index 0f6690cb..85c142f9 100644 --- a/rfcs/interop_2023.md +++ b/rfcs/interop_2023.md @@ -64,7 +64,7 @@ The following information should be provided in a proposal: #### Investigation efforts -If an area doesn't have a good spec and test suite it's not possible to use wpt.fyi test results to judge progress. Instead, some other work is needed to bring the area to state where test results can be used. +If an area doesn't have a good spec and test suite, then it's not possible to use wpt.fyi test results to judge progress. Instead, some other work is needed to bring the area to state where test results can be used. The following information should be provided in a proposal: From f9233bb1d32cf52e3e7ad5b747e8e22286841ce0 Mon Sep 17 00:00:00 2001 From: "Michael[tm] Smith" Date: Thu, 18 Aug 2022 08:55:58 +0900 Subject: [PATCH 16/16] Update rfcs/interop_2023.md --- rfcs/interop_2023.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rfcs/interop_2023.md b/rfcs/interop_2023.md index 85c142f9..b19fe78a 100644 --- a/rfcs/interop_2023.md +++ b/rfcs/interop_2023.md @@ -99,4 +99,4 @@ A public dashboard tracking the metrics over time will be available at https://w ## Risks -No set of tests is without flaws, and trying to improve a metric based on test results can lead to bad outcomes such as shallow implementations that pass the tests but still isn't usable in practice. The main mitigation for this is a careful review of the tests for the proposed areas, and to include only tests that are judged to be high quality. Also, the tests are not frozen but can be updated or even removed during the year as issues are uncovered. +No set of tests is without flaws, and trying to improve a metric based on test results can lead to bad outcomes such as shallow implementations that pass the tests but still aren't usable in practice. The main mitigation for this is a careful review of the tests for the proposed areas, and to include only tests that are judged to be high quality. Also, the tests are not frozen but can be updated or even removed during the year as issues are uncovered.