-
Notifications
You must be signed in to change notification settings - Fork 132
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
Should the Process define Business and Community Groups? #17
Comments
Mike to discuss |
Yes, it's time to look at integrating all our xGs into the process, but not 2018 |
This shouldn't have been closed, must have done it by accident somehow. |
Moving the entire documentation of CGs and BGs into the process seems like a lot of work. There are some edge questions here (e.g. does the Director's authority to dismiss someone apply to CGs and BGs if they are not mentioned). perhaps a pointer admitting of their existence? |
I think the answer to the question posed is 'no', because CGs and BGs are open to non-members, and the process document is for running Member business. Having said that, I think that (a) CGs and BGs should be mentioned in the Process document, by adding to the end of Section (1) Introduction "The W3C also operates Business and Community Groups, which are open to non-members and do not produce normative Recommendations. They are described by the Business and Community Group [process https://www.w3.org/community/about/agreements/]. I also think that the CG/BG process should contain identical provisions in a few cases, and should be edited. That includes mirroring the provisions of 3.1, especially the material added in Process2018: The Director may suspend or remove for cause a participant in any group (including the AB and TAG), where cause includes failure to meet the requirements of this process, the membership agreement, or applicable laws." That's all I see, and it's mostly updating the CG/BG process rather than the process document. |
I agree that CGs and BGs should have their own process document, and that such process should be synched up with the WG process in certain areas. I also agree that this is now a Process 2019 candidate, but where should it go? |
So, in general we need to sort out which parts of the process actually ought to apply to CGs and BGs. For example, conforming to the code of ethics and professional conduct probably does, and the Director's ability to dismiss for cause. Section 3 says "These policies apply to participants in the following groups: Advisory Committee, Advisory Board, TAG, Working Groups, and Interest Groups." I think we need to say in the introduction at the end of section 1 "The W3C also operates Community and Business Groups, which are separately described in their own process document." and link to https://www.w3.org/community/about/agreements/. Those pages probably need an update to include "Dismissal from a community or business group" and allow the Director to dismiss for cause. Do we need conflict of interest policy links in the CG/BG process? |
see also #180 |
Transferred from https://www.w3.org/community/w3process/track/issues/130
State: Raised
The text was updated successfully, but these errors were encountered: