SWIP-37f2: a policy for calls for consensus on SWICG group decisions

Introduction

The Social Web Incubation Community Group is missing an explicit decision-making policy, which essentially all other W3C community groups have to ensure asynchronous and healthy consensus mechanisms across timezones and participatory modes.

Proposal

W3C SWICG will seek to make decisions through consensus and due process, per the W3C Process Document, §5.2.1 Consensus.

To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional.

A call for consensus (CFC) will be issued for all resolutions via email to public-swicg@w3.org (archives). The presence of formal resolutions will be indicated by a "CFC" prefix in the subject line of the email. Additional outreach to community venues for more affirmative consent is strongly encouraged. There will be a response period of 14 days. If no sustained objections are raised by the end of the response period, the resolution will be considered to have consensus as a resolution of the Community Group, i.e. a group decision.

All decisions made by the group should be considered resolved unless and until new information becomes available or unless reopened at the discretion of the Chairs or the Director.

This policy is an operational agreement per the W3C Community and Business Group Process.

Context

W3C Groups with Similar Decision Policies

These community groups and working groups have similar decision policies with tentative meeting resolutions and confirmation of calls for consensus via email:

Other Processes

Proposal process on SWICG Forum with identical response period:

W3C Community Group Process

W3C SWICG is a W3C Community Group (CG).

CGs are described in their process document as follows (excerpted for concision):

This document defines W3C Community Groups, where anyone may develop Specifications, hold discussions, develop tests, and so on, with no participation fee. …

Community Groups that develop specifications do so under policies designed to strike a balance between ease of participation and safety for implementers and patent holders …

A Community Group may adopt operational agreements… that establish the group’s scope of work, decision-making processes, communications preferences, and other operations. …

The following rules govern Community Group operational agreements:

the Chair determines the means by which the group adopts and modifies operational agreements. The Chair must give actual notice to the participants of any material changes to the agreements. Participants may resign from the group if they do not wish to participate under the new agreements. …

Note: W3C encourages groups adopt decision-making policies that promote consensus. …

Each Community Group must have at least one Chair who is responsible for ensuring the group fulfills the requirements of this document as well as the group’s operational agreements.

Editorial Notes

The title of this proposal was generated in line with norms established by Content addressed vocabulary for extensions and FEP-a4ed: The Fediverse Enhancement Proposal Process.

⚡ P='a policy for calls for consensus on SWICG group decisions'
⚡ echo "SWIP-$(echo -n "$P" | sha256sum | cut -c-4): $P"
SWIP-37f2: a policy for calls for consensus on group decisions

The 'SW' in 'SWIP' stands for 'Social Web'.

This proposal was initially published at:

CC0 1.0 Universal (CC0 1.0) Public Domain Dedication

To the extent possible under law, the authors of this Proposal have waived all copyright and related or neighboring rights to this work.