From 9552ca6cb4d6c793dfb79ebe547ae07bfb04ed10 Mon Sep 17 00:00:00 2001 From: Keith Miller Date: Wed, 10 Dec 2025 14:23:16 -0500 Subject: [PATCH 1/2] Add an Open Governance Policy The terms are nearly identical to the ones in Speedometer. This is the same text I shared offline / in the sync. --- Governance.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 Governance.md diff --git a/Governance.md b/Governance.md new file mode 100644 index 00000000..2141505b --- /dev/null +++ b/Governance.md @@ -0,0 +1,15 @@ +# JetStream Governance Policy + +JetStream uses multi-stakeholder governance. This will allow us to share work, and build a collaborative understanding of performance on the web in order to drive resourcing towards appropriate areas. This also provides a structure that can endure to provide maintenance and adapt to the future web. + +An eligible “browser project” is a core end-to-end web browser engine with an integrated JavaScript engine which distributes implementations widely. The project may delegate decision making within JetStream to multiple representatives (for example, to review code commits or to provide consensus for major changes). The participating browser projects at this time are Blink/V8, Gecko/SpiderMonkey, and WebKit/JavaScriptCore. + +The intent is that the working team should be able to move quickly for most changes, with a higher level of process and consensus expected based on the impact of the change. + +Trivial change - This is a change that has no effect on the official benchmark and includes changes to whitespaces, comments, documentation outside policies and governance model, and unofficial test cases. A trivial change requires approval by a reviewer, who is not the author of the change, from one of the participating browser projects. The intent is to ensure basic code quality & license compatibility, not to reach agreement. For example, one participating browser project might be both writing and reviewing a new benchmark in a subfolder to test in their own CI, or reviewing code written by an external contributor. + +Non-trivial change - This is a change that has small impact on the official benchmark and includes changes to official test cases, test runners, bug fixes, and the appearance of the benchmark. A non-trivial change requires approval by at least two of the participating browser projects (including either authoring or reviewing the change) and none other strongly opposed to the change within 10 business days. + +Major change - This is a change that has major implications on the official benchmark such as releasing of a new version of the benchmark or any revisions to governance policies and processes, including changes to the participating browser projects. A major change requires a consensus, meaning approvals by each of the participating browser projects. + +This governance policy and associated code will be hosted inside the JetStream repository within the WebKit GitHub organization under the 2-clause BSD license. \ No newline at end of file From f3f935b898d1f53ee92bfa03c21bec8b3c247814 Mon Sep 17 00:00:00 2001 From: Keith Miller Date: Thu, 11 Dec 2025 12:18:44 -0500 Subject: [PATCH 2/2] Add formatting back. --- Governance.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Governance.md b/Governance.md index 2141505b..4a36a787 100644 --- a/Governance.md +++ b/Governance.md @@ -6,10 +6,10 @@ An eligible “browser project” is a core end-to-end web browser engine with a The intent is that the working team should be able to move quickly for most changes, with a higher level of process and consensus expected based on the impact of the change. -Trivial change - This is a change that has no effect on the official benchmark and includes changes to whitespaces, comments, documentation outside policies and governance model, and unofficial test cases. A trivial change requires approval by a reviewer, who is not the author of the change, from one of the participating browser projects. The intent is to ensure basic code quality & license compatibility, not to reach agreement. For example, one participating browser project might be both writing and reviewing a new benchmark in a subfolder to test in their own CI, or reviewing code written by an external contributor. +- **Trivial change** This is a change that has no effect on the official benchmark and includes changes to whitespaces, comments, documentation outside policies and governance model, and unofficial test cases. A trivial change requires approval by a reviewer, who is not the author of the change, from one of the participating browser projects. The intent is to ensure basic code quality & license compatibility, not to reach agreement. For example, one participating browser project might be both writing and reviewing a new benchmark in a subfolder to test in their own CI, or reviewing code written by an external contributor. -Non-trivial change - This is a change that has small impact on the official benchmark and includes changes to official test cases, test runners, bug fixes, and the appearance of the benchmark. A non-trivial change requires approval by at least two of the participating browser projects (including either authoring or reviewing the change) and none other strongly opposed to the change within 10 business days. +- **Non-trivial change** This is a change that has small impact on the official benchmark and includes changes to official test cases, test runners, bug fixes, and the appearance of the benchmark. A non-trivial change requires approval by at least two of the participating browser projects (including either authoring or reviewing the change) and none other strongly opposed to the change within 10 business days. -Major change - This is a change that has major implications on the official benchmark such as releasing of a new version of the benchmark or any revisions to governance policies and processes, including changes to the participating browser projects. A major change requires a consensus, meaning approvals by each of the participating browser projects. +- **Major change** This is a change that has major implications on the official benchmark such as releasing of a new version of the benchmark or any revisions to governance policies and processes, including changes to the participating browser projects. A major change requires a consensus, meaning approvals by each of the participating browser projects. This governance policy and associated code will be hosted inside the JetStream repository within the WebKit GitHub organization under the 2-clause BSD license. \ No newline at end of file