- From: Benjamin Goering <ben@bengo.co>
- Date: Sun, 1 Oct 2023 12:19:23 -0500
- To: public-swicg@w3.org
- Message-ID: <CAN+OhBM2BZm2ZWjJ=-zYVbOuK=byC+zXz3V0Zg3wv=ds4Lz+3Q@mail.gmail.com>
As an FYI, there is a corresponding FEP-37f2 proposal that affords providing feedback via the SocialCG Forum for those that have participated there more so than this more recent email list: https://socialhub.activitypub.rocks/t/fep-37f2-a-policy-for-calls-for-consensus-on-swicg-group-decisions/3620 The rationale for this is to meet the recommendation of past SocialCG resolution/decision from 2021-01-09 overseen by Chair > *Resolution:* The SocialCG should support the FEP (Fediverse Enhancement > Proposal) process as a way of documenting extensions to the fediverse and > encourage bringing FEP proposals for discussion to the SocialCG. > https://www.w3.org/2021/01/09-social-minutes.html#r02 A related FYI, because I don't know about about you, but sometimes I find the jargon at W3C to be opaque and not always inclusive unless explained, but 'resolution' and 'group decision' are generally synonymous per W3C Process: > decisions taken by the Chair > <https://www.w3.org/2023/Process-20230612/#GeneralChairs> of a Working > Group <https://www.w3.org/2023/Process-20230612/#GroupsWG> or Interest > Group <https://www.w3.org/2023/Process-20230612/#GroupsIG> on the basis > of having assessed the consensus > <https://www.w3.org/2023/Process-20230612/#def-Consensus> of the group or > following a vote (see § 5.2.3 Deciding by Vote > <https://www.w3.org/2023/Process-20230612/#Votes>) are called group > decisions (also known as group “resolutions”). > https://www.w3.org/2023/Process-20230612/#decision-types happy sun day 🌞 - bengo On Thu, Sep 28, 2023 at 7:01 PM Benjamin Goering <ben@bengo.co> wrote: > 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 > <https://socialweb.coop/SWIP/37f2/a-policy-for-calls-for-consensus-on-swicg-group-decisions/SWICG> will > seek to make decisions through consensus and due process, per the W3C > Process Document, §5.2.1 Consensus > <https://www.w3.org/2023/Process-20230612/#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 > <https://lists.w3.org/Archives/Public/public-swicg/>). 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 <https://www.w3.org/community/about/process/>. > ContextW3C 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: > > - WebAssembly Community Group Charter > <https://webassembly.github.io/cg-charter/#decision> > - Credentials Community Group Charter > <https://www.w3.org/community/credentials/charter/> (see section > "Transparency") > - Web Extensions Community Group Charter > <https://github.com/w3c/webextensions/blob/main/charter.md#decision-process> > - Web of Things Interest Group Charter > <https://www.w3.org/2021/12/wot-ig-2021.html#decisions> > - HTML Working Group Charter > <https://www.w3.org/2022/06/html-wg-charter.html#decisions> > - Web Platform Working Group Charter > <https://www.w3.org/2017/08/webplatform-charter.html#decisions> > - Web Applications Working Group Charter > <https://www.w3.org/2022/04/webapps-wg-charter.html#decisions> > - Media Working Group Charter > <https://www.w3.org/2023/06/media-wg-charter.html#decisions> > - Web Performance Working Group Charter > <https://www.w3.org/2021/02/webperf.html#decisions> > - Service Workers Working Group Charter > <https://www.w3.org/2023/01/sw-charter.html#decisions> > - Verifiable Credentials Working Group Charter > <https://www.w3.org/2022/06/verifiable-credentials-wg-charter.html#decisions> > - JSON-LD Working Group Charter > <https://www.w3.org/2018/03/jsonld-wg-charter.html#decisions> > - WebAssembly Working Group Charter > <https://www.w3.org/2020/03/webassembly-wg-charter.html#decisions> > - Web Authentication Working Group Charter > <https://www.w3.org/2022/04/webauthn-wg-charter.html#decisions> > - Immersive Web Working Group Charter > <https://www.w3.org/2022/07/immersive-web-wg-charter.html#decisions> > - Web Payments Working Group Charter > <https://www.w3.org/2017/08/webplatform-charter.html#decisions> > - Devices and Sensors Working Group Charter > <https://www.w3.org/2022/11/das-wg-charter.html#decisions> > - Distributed Tracing Working Group Charter > <https://www.w3.org/2023/05/distributed-tracing-wg-charter.html#decisions> > - Web Editing Working Group Charter > <https://www.w3.org/2023/09/webediting-charter-2023.html#decisions> > - Internationalization Working Group Charter > <https://www.w3.org/International/groups/wg/charter.html#decisions> > - Publishing Maintenance Working Group Charter > <https://www.w3.org/2023/06/pmwg-charter.html#decisions> > - Solid Community Group Charter > <https://www.w3.org/community/solid/charter/> (see section "Decision > Policy") > - Decentralized Identifier Working Group Charter > <https://www.w3.org/2020/12/did-wg-charter.html#decisions> > > Proposal processes on SWICG Forum with identical response period: > > - FEP-a4ed: The Fediverse Enhancement Proposal Process > <https://socialhub.activitypub.rocks/t/fep-a4ed-the-fediverse-enhancement-proposal-process/1171/1> > > W3C Community Group Process > > W3C SWICG <https://www.w3.org/community/socialcg/> is a W3C Community > Group (CG). > > CGs are described in their process document > <https://www.w3.org/community/about/process/> 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: > > - They must be publicly documented. > - They must be fair and must not unreasonably favor or discriminate > against any group participant or their employer. > - They must not conflict with or modify this Community and Business > Group Process, the Community Contributor License Agreement (CLA) > <https://www.w3.org/community/about/process/cla/>, or the Final > Specification Agreement > <https://www.w3.org/community/about/process/final/>. … > > 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. > > Related Reading > > - IETF RFC7282 On Consensus and Humming in the IETF > <https://datatracker.ietf.org/doc/html/rfc7282> > - Doty, Nick, and Deirdre K. Mulligan. 2013. "Internet > Multistakeholder Processes and Techno-Policy Standards: Initial Reflections > on Privacy at the World Wide Web Consortium" > <http://www.jthtl.org/content/articles/V11I1/JTHTLv11i1_MulliganDoty.PDF> Journal > on Telecommunications and High Technology Law 11. > - Harmonization (standards), en.wikipedia.org > <https://en.wikipedia.org/wiki/Harmonization_(standards)> > > Editorial Notes > > The title of this proposal was generated in line with norms established by Content > addressed vocabulary for extensions > <https://socialhub.activitypub.rocks/t/content-addressed-vocabulary-for-extensions/539/1> > and FEP-a4ed: The Fediverse Enhancement Proposal Process > <https://socialhub.activitypub.rocks/t/fep-a4ed-the-fediverse-enhancement-proposal-process/1171#proposal-title-and-identifier-5> > . > > ⚡ 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: > > - > https://socialweb.coop/SWIP/37f2/a-policy-for-calls-for-consensus-on-swicg-group-decisions/ > > Copyright > > 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. >
Received on Sunday, 1 October 2023 17:19:42 UTC