Proposal for Process Experimentation #1189

New issue

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

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

Already on GitHub? Sign in to your account

Open

ianbjacobs wants to merge 31 commits into main from process-experiments

index.bs

-Original file line number
+Diff line change
@@ Expand Up / @@ -5322,6 +5322,93 @@ Process Evolution</h2> @@
     	the [[COC|Code of Conduct]] in the <a href="https://www.w3.org/community/pwe/">Positive Work Environment Community Group</a>,
     	and the Process in the <a href="https://www.w3.org/community/w3process/">W3C Process Community Group</a>.
+    <h2 id="process-experimentation">
+    Process Experimentation</h2>
+    	The Advisory Board may authorize Process Experiments.
+    	An <dfn id="authorized-process-experiment" export>Authorized Process Experiment</dfn> modifies or replaces
+    	one or more provisions of an operative policy for the authorized duration and scope of the experiment.
+    	Authorized Process Experiments may be conducted over the Process Document
+    	subject to the scope limitations defined below.
+    <h3 id="experiment-notification">
+    Notification</h3>
+    	The Advisory Boards must notify the Membership and public
+    	of its decision to authorize a Process Experiment
+    	no less than three weeks before the planned start of the experiment.
+    	Provided the experiment remains within <a href="#experiment-scope">scope limitations</a>,
+    	the authorization itself is not subject to the usual Formal Objection mechanisms,
+    	but it is subject to Advisory Committee Appeal.
+    	The usual Process safeguards (objections, appeals),
+    	to the extent they are not themselves modified by the experiment,
+    	remain in place for decisions made during the course of an experiment.
+    	Notification of a Process Experiment Authorization must:
+    	* Describe what problem(s) the experiment seeks to address.
+    	* Include hypotheses for how the experiment will address these problems
+    		and what success would look like.
+    	* Identify the policy provisions that are temporarily suspended during the experiment,
+    		and include the language that temporarily replaces those provisions.
+    	* Identify explicitly the parties affected by the experiment.
+    	        When an experiment is designed to affect a limited audience
+    		(e.g., one Working Group),
+    	        the Advisory Board must socialize the experiment with them
+    	        before issuing the the formal notification.
+    	        When an experiment affects a large audience
+    		(e.g., all Working Groups),
+    	        the Advisory Board must provide rationale for the more expansive scope.
+    	* Specify an end date that may not be more than 1 year after the start date of the experiment.
+    <h3 id="experiment-scope">
+    Scope limitations</h3>
+    	Authorized Process Experiments must not:
+    	* Extend to policies included by reference in the Process Document.
+    	* Alter the rules that give the Advisory Board the authority to conduct experiments
+    		or permanently change a policy.
+    	* Alter patent policy commitments.
+    	* Have retroactive effect.
+    <h3 id="experiment-extensions">
+    Extensions</h3>
+    	An Authorized Process Experiment expires automatically on its specified end date
+    	but may be extended at most one time for up to one year.
+    	If the Advisory Board wishes to extend an experiment:
+    	* the Advisory Board must issue a [=Process Experiment Report=]
+    	* the extension must be approved by majority vote of the Advisory Committee
+    		by a ballot open for two weeks at a minimum.
+    <h3 id="experiment-reports">
+    Process Experiment Reports</h3>
+    	Upon conclusion or termination of a Process Experiment and prior to any extension,
+    	the Advisory Board must share a <dfn id="process-experiment-report">Process Experiment Report</dfn>
+    	with the Membership and public.
+    	A Process Experiment Report must:
+    	* Describe at a high level what happened, what was learned, and what evidence was gathered.
+    	* Indicate whether the hypotheses in the Process Experiment Authorization were supported,
+    		and what unexpected events occurred.
+    	* Advise whether the experiment be extended, modified, or proposed for permanent adoption,
+    		or should no further action be taken.
+    <h3 id="experiment-outcomes">
+    Experiment outcomes</h3>
+    	Not all experiments will be deemed successful or lead to permanent changes to the Process Document.
+    	The validity of actions or decisions taken as part of an authorized Process Experiment
+    	does not depend on the outcome of the experiment.
+    	An Authorized Process Experiment does not amend the operational policy permanently;
+    	making any change permanent requires the usual approval process.
     <h2 id="old-terms" class="non-normative nonum">
     Appendix A: Retired Terminology</h2>
@@ Expand Down @@

Navigation Menu

Proposal for Process Experimentation #1189

Uh oh!

Diff view

Diff view

There are no files selected for viewing

Uh oh!

Proposal for Process Experimentation #1189

Are you sure you want to change the base?

Uh oh!

Proposal for Process Experimentation #1189

Uh oh!

Uh oh!

Diff view

Diff view

There are no files selected for viewing

Uh oh!