Re: [patcg.github.io] Adding a clear incubation process and flow (#7)

This seems like a topic best discussed at the meeting, so I'm going to keep my responses shortish.

> FWIW, I do agree that it's not clear why an incubation group would have a separate incubation process. However, I disagree about refusing to accept under the group's umbrella any work until it is proven to be entirely functional and agreeable to all involved; that's the end of the incubation stage, not the beginning. 

This is not the standard I am endorsing. Rather, I believe that the standard ought to be the one in the charter, namely "there is consensus amongst Community Group Participants that the work should be taken on and that the document is a good basis for a Community Group Report. What I'm opposed to is taking on documents where there is *not* consensus on that point.

> I'm concerned by comparisons to WICG. NOTHING in WICG is anything but an incubation, by definition; nothing there has proven broad support. Nothing there is a "standard". If something has reached the point of broad agreement, we (WICG co-chairs) try to move it out; to another CG with the right community for further incubation, or ideally to a WG that can turn it into a real standard.

And yet companies frequently ship specs that are only in WICG and we often get calls to implement those specs.


Re: personal repositories, ISTM that part of the problem is the distinction between a discussion forum (which I agree that the CG should sponsor, even for non-adopted drafts) and for where the drafts live. Github tends to blur those distinctions, but my concern is having documents appear on a piece of real estate which tends to indicate that they are work items of the CG, when they are merely being discussed but have not been adopted.







-- 
GitHub Notification of comment by ekr
Please view or discuss this issue at https://github.com/patcg/patcg.github.io/pull/7#issuecomment-1068388872 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 15 March 2022 19:36:19 UTC