You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: process/cg-transition.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,19 +3,19 @@ title: How to transition work from a Community Group to a Working Group
3
3
toc: yes
4
4
---
5
5
6
-
From time to time a Community Group that has been [incubating a technology](../incubation.html) seeks to advance it to the W3C Recommendation track in a Working Group. Our goal through this document is to ease that transition.
6
+
From time to time a Community Group that has been [incubating a technology](../incubation.md) seeks to advance it to the W3C Recommendation track in a Working Group. Our goal through this document is to ease that transition.
7
7
8
8
## Preparation
9
9
10
10
The following questions can help a Community Group to prepare for the transition of work to a Working Group.
11
11
12
12
### Is the work ready for standardization?
13
13
14
-
Please see elsewhere in the Guide: [W3C Recommendation Track Readiness Best Practices](https://www.w3.org/Guide/standards-track/).
14
+
Please see elsewhere in the Guide: [W3C Recommendation Track Readiness Best Practices](../standards-track/).
15
15
16
16
### What is the target Working Group and the relation to the CG?
17
17
18
-
If the Working Group does not yet exist, the Community Group can prepare by [drafting a Working Group charter](https://www.w3.org/Guide/process/charter.html). Otherwise, if the group exists but the new work is not within its scope W3C needs to [recharter the group](https://www.w3.org/Guide/process/charter.html) to accommodate the new work.
18
+
If the Working Group does not yet exist, the Community Group can prepare by [drafting a Working Group charter](charter.md). Otherwise, if the group exists but the new work is not within its scope W3C needs to [recharter the group](charter.md) to accommodate the new work.
19
19
20
20
The charter of the target Working Group should address two topics:
21
21
@@ -47,8 +47,8 @@ Once the work transitions to a Working Group, that Working Group's patent policy
47
47
48
48
In many cases, Community Group participants will want to continue their involvement in discussions about a work after it has been transferred to a Working Group.
49
49
50
-
- If a Community Group participant works for a [W3C Member](https://www.w3.org/Consortium/Member/list), the participant can ask their Advisory Committee Representative to join the Working Group.
51
-
- Otherwise, please contact [Member Relations](mailto:[email protected]) to explore [W3C Membership](https://www.w3.org/Consortium/membership). During that exploration, [Community Group participants may continue participating in the Working Group as Invited Experts](https://www.w3.org/community/about/faq/#how-do-community-groups-make-it-easier-to-move-to-the-standards-track).
50
+
- If a Community Group participant works for a [W3C Member](https://www.w3.org/membership/list/), the participant can ask their Advisory Committee Representative to join the Working Group.
51
+
- Otherwise, please contact [Member Relations](mailto:[email protected]) to explore [W3C Membership](https://www.w3.org/membership/). During that exploration, [Community Group participants may continue participating in the Working Group as Invited Experts](https://www.w3.org/community/about/faq/#how-do-community-groups-make-it-easier-to-move-to-the-standards-track).
52
52
53
53
## Operations
54
54
@@ -76,8 +76,8 @@ Other repository admin for the target Working Group:
76
76
Other repository admin for W3C staff.
77
77
78
78
- Request that the systems team back up the org repositories.
79
-
- Update or add LICENSE.md, CONTRIBUTING.md, CODE\_OF\_CONDUCT.md to reflect the new contribution framework.
80
-
- Configure the repository with the [labels used for tracking horizontal reviews](https://www.w3.org/Guide/documentreview/#working_with_horizontal_review_labels)
79
+
- Update or add `LICENSE.md`, `CONTRIBUTING.md`, `CODE_OF_CONDUCT.md` to reflect the new contribution framework.
80
+
- Configure the repository with the [labels used for tracking horizontal reviews](../documentreview/#working_with_horizontal_review_labels).
81
81
- If not already set up, make sure members of the `horizontal-admin` team have triage access to the repo.
82
82
- Make w3cbot a co-owner of the org (useful for integrating the IPR manager among other things).
83
83
- Update [validate-repo to monitor the repos of that org](https://github.com/w3c/validate-repos/blob/main/validate.js#L9).
0 commit comments