- From: Lisa Dusseault <lisa@dtinit.org>
- Date: Fri, 1 Nov 2024 10:40:37 -0700
- To: dzagidulin@gmail.com
- Cc: Social Web Incubator Community Group <public-swicg@w3.org>
- Message-ID: <CAH212UP27y4VUkoXRywbh16tWfp0ZaifpBTj1wvcV_pytwiJwQ@mail.gmail.com>
Early feedback even though we'll discuss next week - especially because the 1st point is all about readiness for next week 1. The proposed CG charter at https://github.com/swicg/potential-charters/blob/main/CGCharter-1727386911.html is fine as far as it goes, but the scope section is still "TBD: describe topics that are in scope..." nor do I see where out-of-scope topics are actually listed, nor do I see any report topics that would be in scope (just that specifications on all topics are out of scope). Is this something we could iterate on before the next meeting? Otherwise I don't think we'll be ready to adopt it, just discuss the parts that are there. 2. I'm still thinking about the incubation/staging process. It's got a lot of good stuff but there's something about the scale of "proposal" and "problem space" that got me concerned. I'd love it if the intent of what scale of things this process is intended to apply for was clearer in the doc even if it's not normative and not perfect. Is a *proposal* intended to be "a whole feature document" and the *problem space* is "why do we want a whole new feature" ? To give an example at the probably-ridiculous other extreme, does a *proposal* include "I propose we should decide in ActivityPub what servers do when they receive a Move for an actor that has supposedly already moved" and does *problem space* include "The problem space here is that ActivityPub servers behave differently when receiving conflicting Moves"? I think the authors have the incubation process in mind more for new features and new whole-ass specs, but when first I read it, my brain was thinking about all levels of changes proposed from tiny modifications of mature specs, on up the scale. Maybe this was obvious to folks who've used this incubation process elsewhere? 3. I think https://github.com/swicg/potential-charters/blob/main/ap-maintenance-wg-charter.html is ready for us to talk about adopting, and I like it. Lisa On Thu, Oct 31, 2024 at 12:12 PM Dmitri Zagidulin <dzagidulin@gmail.com> wrote: > Hi all, > > Apologies for short notice, but I'd like to postpone the monthly SocialWeb > CG community call for one week, to be now on November 8, 2024, instead. > > Partly for high holiday reasons :) but mostly to give the group more time > to engage with the potential charter documents and PRs over in > https://github.com/swicg/potential-charters > > Specifically, during the November call, we'd like to discuss: > > 1. Adopting a CG Charter (current proposed version: > https://github.com/swicg/potential-charters/blob/main/CGCharter-1727386911.html > ) > 2. Adopting an Incubation / Staging process (currently at > https://github.com/swicg/potential-charters/blob/main/stage-process.md ) > 3. Discuss Working Group charter options > - option 1: Focused AP+AS2 1.1 WG (current proposed charter at > https://github.com/swicg/potential-charters/blob/main/ap-maintenance-wg-charter.html > ) > - option 2: Wider SocialWeb WG, which includes AP+AS2, but also all the > other specs produced by the original WG. > > So, everybody has an extra week to read the proposals, make PRs, open > issues, and discuss here on the list! > > > 3. >
Received on Friday, 1 November 2024 17:40:52 UTC