Open cwilso opened 1 year ago
I'm very interested in this topic, as we had some complexity around PATCG and incubation where we basically have set up our own incubation space with specific language around it.
I am also interested in this topic, especially for "How should CGs be used at the W3C?". We also see CGs being useful past initial incubation (see JSON-LD CG, WoT CG). It is not clear how CG participants who are not members can provide input to existing WG documents without any legal issues. A CG report becoming a WG is covered under clause 9 of the CLA but there is nothing else showcasing the relationship between the two types of groups.
Another small point is that we see some companies struggling even with the CLA from the legal point of view since their organisation is not set up to tackle this kind of groups or "licenses for things that they do not buy".
@egekorkan I'm curious for elaboration on "some companies struggling even with the CLA from the legal point of view since their organisation is not set up to tackle this kind of groups or 'licenses for things that they do not buy'." Could you elaborate?
Is it that some companies don't have the ability to analyze their legal commitment, or have struggles with it, or ??
I cannot give names and I don't know the exact details but it is exactly"some companies don't have the ability to analyze their legal commitment".
Oh, no, I wasn't looking for names; just trying to understand the concerns.
Session description
This session is to define expectations & guidance for advancing work in incubation and when to move it out (both to a WG or to a closing report), and how we need to adjust various practices and Process (e.g. WG chartering) to support this. Also in scope is the topic of "how should CGs be used at the W3c?" More background to be found at https://github.com/w3c/AB-memberonly/issues/81.
Session goal
Consensus on role of CGs in incubation, and general expectations for how to advance work.
Additional session chairs (Optional)
No response
IRC channel (Optional)
incubation
Who can attend
Anyone may attend (Default)
Session duration
60 minutes (Default)
Other sessions where we should avoid scheduling conflicts (Optional)
No response
Estimated number of in-person attendees
Don't know (Default)
Instructions for meeting planners (Optional)
No response
Agenda, minutes, slides, etc. (Optional)