From 8328bb0a8eeedef1dcc1ff503aee26967360a3b4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Philip=20J=C3=A4genstedt?= Date: Wed, 3 Aug 2022 23:01:08 +0200 Subject: [PATCH 1/4] RFC 120: Interop Team Charter --- rfcs/interop_charter.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 rfcs/interop_charter.md diff --git a/rfcs/interop_charter.md b/rfcs/interop_charter.md new file mode 100644 index 00000000..d441a177 --- /dev/null +++ b/rfcs/interop_charter.md @@ -0,0 +1,17 @@ +# RFC 120: Interop Team Charter + +## Summary + +An Interop Team is created as part of the web-platform-tests project, defined by a charter [in the team repo](https://github.com/web-platform-tests/interop-2022/pull/102). The team is tasked with maintaining [Interop 2022](./interop_2022.md), [Interop 2023](./interop_2023.md) and future such efforts. + +## 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, as described in the [Interop 2023 RFC](./interop_2023.md). + +The [team charter](https://github.com/web-platform-tests/interop-2022/pull/102) is made official by this RFC and substantial changes can only be made through the web-platform-tests RFC process. + +The Interop Team can define additional public efforts/metrics beyond Interop 2022 and 2023. The process for doing that is decided by the Interop Team, may evolve over time, and is not defined by this RFC. + +## Risks + +This charter is not time limited. Yet, there is no guarantee that there will be enough interest to define a yearly effort/metric, or that participants will be able to find consensus. The outcome would simply be that there will be no new effort/metric announced. In such a case the Interop Team and/or the WPT core team should evaluate whether it's time for an official end to the charter. From 174d75c0602e3b7561d598594f2c88f007eba31d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Philip=20J=C3=A4genstedt?= Date: Thu, 18 Aug 2022 17:15:35 +0200 Subject: [PATCH 2/4] Reflect repo rename --- rfcs/interop_charter.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/rfcs/interop_charter.md b/rfcs/interop_charter.md index d441a177..0eb4c268 100644 --- a/rfcs/interop_charter.md +++ b/rfcs/interop_charter.md @@ -2,13 +2,11 @@ ## Summary -An Interop Team is created as part of the web-platform-tests project, defined by a charter [in the team repo](https://github.com/web-platform-tests/interop-2022/pull/102). The team is tasked with maintaining [Interop 2022](./interop_2022.md), [Interop 2023](./interop_2023.md) and future such efforts. +An Interop Team is created as part of the web-platform-tests project, defined by a charter [in the team repo](https://github.com/web-platform-tests/interop/pull/102). The team is tasked with maintaining [Interop 2022](./interop_2022.md), [Interop 2023](./interop_2023.md) and future such efforts. ## 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, as described in the [Interop 2023 RFC](./interop_2023.md). - -The [team charter](https://github.com/web-platform-tests/interop-2022/pull/102) is made official by this RFC and substantial changes can only be made through the web-platform-tests RFC process. +The [team charter](https://github.com/web-platform-tests/interop/pull/102) is made official by this RFC and substantial changes can only be made through the web-platform-tests RFC process. The Interop Team can define additional public efforts/metrics beyond Interop 2022 and 2023. The process for doing that is decided by the Interop Team, may evolve over time, and is not defined by this RFC. From a61ece08d8d66ac113ee9f68508ccbe080ec636d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Philip=20J=C3=A4genstedt?= Date: Thu, 18 Aug 2022 17:17:30 +0200 Subject: [PATCH 3/4] Put BSF in scope --- rfcs/interop_charter.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/rfcs/interop_charter.md b/rfcs/interop_charter.md index 0eb4c268..dba06a1e 100644 --- a/rfcs/interop_charter.md +++ b/rfcs/interop_charter.md @@ -10,6 +10,8 @@ The [team charter](https://github.com/web-platform-tests/interop/pull/102) is ma The Interop Team can define additional public efforts/metrics beyond Interop 2022 and 2023. The process for doing that is decided by the Interop Team, may evolve over time, and is not defined by this RFC. +The Interop Team also maintains the "Browser Specific Failures" metric on [wpt.fyi](https://wpt.fyi/). + ## Risks This charter is not time limited. Yet, there is no guarantee that there will be enough interest to define a yearly effort/metric, or that participants will be able to find consensus. The outcome would simply be that there will be no new effort/metric announced. In such a case the Interop Team and/or the WPT core team should evaluate whether it's time for an official end to the charter. From a4f289b8074112245aaf869828aa6cc186e604a9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Philip=20J=C3=A4genstedt?= Date: Tue, 20 Sep 2022 22:48:54 +0200 Subject: [PATCH 4/4] Update rfcs/interop_charter.md --- rfcs/interop_charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rfcs/interop_charter.md b/rfcs/interop_charter.md index dba06a1e..67d89c3b 100644 --- a/rfcs/interop_charter.md +++ b/rfcs/interop_charter.md @@ -10,7 +10,7 @@ The [team charter](https://github.com/web-platform-tests/interop/pull/102) is ma The Interop Team can define additional public efforts/metrics beyond Interop 2022 and 2023. The process for doing that is decided by the Interop Team, may evolve over time, and is not defined by this RFC. -The Interop Team also maintains the "Browser Specific Failures" metric on [wpt.fyi](https://wpt.fyi/). +The Interop team will take ownership of the existing Browser Specific Failures metric, and manage it according to the rules in its charter. ## Risks