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

> Perhaps, then, our disagreement is on the meaning of the word
> "basis". Because I think something that is a good start, but may not
> graduate to actually BEING a CGR (if subsequent incubation proves it
> is not a good idea), meets that bar. It SHOULD be made clear that's
> not the same as the CG making a statement (like a CGR does) that "this
> is what the CG thinks is the right solution".

This is the situation for any document that has not yet become a CGR.
Hence I don't see the need for a separate incubation stage.


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

> Indeed, and companies frequently ship specs that are not even in WICG (e.g. https://blog.mozilla.org/netpolicy/2021/10/28/implementing-global-privacy-control/), and we get calls to implement such specs also.

Note that we do not expose any UI for this feature, and you have to enable 
it in about:config, in large part because GPC does not have any standards status. 
shipped any WICG-only features behind chrome:flags that seems like it would go
 a long way towards addressing this concern.


> My concern is that asking for engagement and contributions to a
> document that does not have clear IP commitments is a Bad Idea; this
> is one of the reasons WHY we try to move out from personal repos
> asap. If the guidance from this discussion is that THIS CG wants to
> hold them at arm's length until they reach some finish line of
> acceptability, that's the CG's prerogative, but that doesn't change
> that we will need to put them somewhere that is not just a personal
> repo. (That's likely to be WICG as a placeholder - again, presuming
> such proposals pass the WICG bar of having some other entity agree
> it's worth incubating).

Yes, I understand this need, and I'd be open to some creative
thinking here. Perhaps some kind of patcg-individual-drafts
organization that had no access control, like IETF individual
submissions.


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


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

Received on Monday, 21 March 2022 19:14:13 UTC