Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Challenges with Incubation #45

Open
cwilso opened this issue Aug 22, 2023 · 5 comments
Open

Challenges with Incubation #45

cwilso opened this issue Aug 22, 2023 · 5 comments
Labels
session Breakout session proposal track: getting work done

Comments

@cwilso
Copy link

cwilso commented Aug 22, 2023

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)

@cwilso cwilso added the session Breakout session proposal label Aug 22, 2023
@AramZS
Copy link
Member

AramZS commented Aug 28, 2023

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.

@egekorkan
Copy link

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".

@cwilso
Copy link
Author

cwilso commented Aug 31, 2023

@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 ??

@egekorkan
Copy link

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".

@cwilso
Copy link
Author

cwilso commented Aug 31, 2023

Oh, no, I wasn't looking for names; just trying to understand the concerns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
session Breakout session proposal track: getting work done
Projects
Status: No status
Development

No branches or pull requests

4 participants