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: docs/en/community/governance/schedule/change-process.md
+11-42Lines changed: 11 additions & 42 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,28 +1,29 @@
1
1
# Change Process
2
2
3
-
The specification change process guides how the community proposes, reviews, and adopts changes to the specification in the [GTFS Repository](https://github.com/google/transit/pulls).
3
+
## Overview
4
4
5
-
The specification change process is categorized into 3 tracks according to the three change types: functional changes, non-functional changes, and documentation maintenance. The change process is separated into 2 stages:
5
+
The specification change process guides how the community proposes, reviews, and adopts changes to the specification in the [GTFS Repository](https://github.com/google/transit/pulls).
6
6
7
-
* Issue Stage: New ideas are introduced, needs are identified, and the feasibility of changes is discussed.
8
-
* Pull Request Stage: Ideas from the Issue Stage are developed, tested, and approved for adoption.
7
+
The specification change process divided into 2 main stages and categorized into 3 tracks according to the three change types: functional changes, non-functional changes, and documentation maintenance.
9
8
10
9
<imgclass="center"width="100%"height="100%"src="../../../../assets/governance-process-overview.png"alt="GTFS Governance Change Process overview">
11
10
12
-
The issue stage is the same for all 3 tracks. The Pull Request stage differs in each of the 3 tracks.
13
-
14
-
## Stage 1: Issue
11
+
### Stage 1: Issue
15
12
16
13
The Issue Stage is meant for discussing new ideas, identifying needs, and proposing improvements to the specification. Issues help evaluate the necessity and support for a change, while organizing the resources required to proceed to the Pull Request Stage.
17
14
18
15
It’s recommended to start at the Issue stage to build consensus around new ideas. However, if the proposal’s scope is already well-defined, beginning directly at the Pull Request stage is appropriate.
19
16
20
-
## Stage 2: Pull Request
17
+
###Stage 2: Pull Request
21
18
22
19
The Pull Request Stage is where ideas from the Issue Stage are developed and implemented into the specification. This stage is divided into 3 tracks depending on the change type.
23
20
24
21
The entire process happens within the [GitHub google/transit repository](https://github.com/google/transit/pulls) and ensures that all changes are thoroughly evaluated before being adopted.
25
22
23
+
## Process Tracks
24
+
25
+
The issue stage is the same for all 3 tracks. The Pull Request stage differs in each of the 3 tracks.
26
+
26
27
### Track A: Functional Changes
27
28
28
29
<imgclass="center"width="100%"height="100%"src="../../../../assets/governance-process-functional.png"alt="GTFS Governance Change Process Track A">
@@ -72,38 +73,6 @@ All of the steps in the Issue and Pull Request Stages are highlighted below. Con
<imgclass="center"width="100%"height="100%"src="../../../../assets/governance-process-step-1.1.png"alt="GTFS Governance Change Process Step 1.1">
@@ -163,7 +132,7 @@ The community engages in discussions to help develop a proposal for modifying th
163
132
164
133
A proposal to change the specification is published by opening a Pull Request in [the GTFS Repository](https://github.com/google/transit/pulls). The Advocate who publishes the proposal must focus on a single change; anyone is welcome to propose a modification.
165
134
166
-
==**Actions**==
135
+
**<ins>Actions</ins>**
167
136
168
137
1.**Applying the Changes**
169
138
@@ -174,7 +143,7 @@ A proposal to change the specification is published by opening a Pull Request in
174
143
175
144
* The Advocate [creates a Pull Request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork) in the [GTFS Repository](https://github.com/google/transit/pulls) from their fork.
Copy file name to clipboardExpand all lines: docs/en/community/governance/schedule/test-process-overview.md
+50-41Lines changed: 50 additions & 41 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,10 @@ The specification change process guides how the community proposes, reviews, and
4
4
5
5
The specification change process is categorized into 3 tracks according to the three change types: functional changes, non-functional changes, and documentation maintenance. The change process is separated into 2 stages:
6
6
7
-
* Issue Stage: New ideas are introduced, needs are identified, and the feasibility of changes is discussed.
8
-
* Pull Request Stage: Ideas from the Issue Stage are developed, tested, and approved for adoption.
7
+
***Issue Stage:** New ideas are introduced, needs are identified, and the feasibility of changes is discussed.
8
+
***Pull Request Stage:** Ideas from the Issue Stage are developed, tested, and approved for adoption.
9
+
10
+
The entire process happens within the [GitHub google/transit repository](https://github.com/google/transit/pulls) and ensures that all changes are thoroughly evaluated before being adopted.
9
11
10
12
<imgclass="center"width="100%"height="100%"src="../../../../assets/governance-process-overview.png"alt="GTFS Governance Change Process overview">
11
13
@@ -17,65 +19,72 @@ The Issue Stage is meant for discussing new ideas, identifying needs, and propos
17
19
18
20
It’s recommended to start at the Issue stage to build consensus around new ideas. However, if the proposal’s scope is already well-defined, beginning directly at the Pull Request stage is appropriate.
19
21
20
-
## Stage 2: Pull Request
22
+
The Issue stage is composed of the following steps:
21
23
22
-
The Pull Request Stage is where ideas from the Issue Stage are developed and implemented into the specification. This stage is divided into 3 tracks depending on the change type.
24
+
* 1.1 Issue Publication
25
+
* 1.2 Issue Discussion
23
26
24
-
The entire process happens within the [GitHub google/transit repository](https://github.com/google/transit/pulls) and ensures that all changes are thoroughly evaluated before being adopted.
27
+
## Stage 2: Pull Request
28
+
29
+
The Pull Request Stage is where ideas from the Issue Stage are developed and implemented into the specification. This stage is divided into 3 tracks depending on the change type. Consider that only Track A: Functional changes utilizes all the steps. Track B: Non-Functional changes and Track C: Documentation Maintenance utilize a shortened version of the process
25
30
26
31
### Track A: Functional Changes
27
32
28
33
<imgclass="center"width="100%"height="100%"src="../../../../assets/governance-process-functional.png"alt="GTFS Governance Change Process Track A">
29
34
30
35
This process guides how the community proposes, reviews, and adopts Functional changes to the specification in the [GTFS Repository](https://github.com/google/transit/pulls).
31
36
32
-
* A proposal is submitted by opening a Pull Request in the GTFS Repository.
33
-
* The community engages in discussions to refine the proposal and reviews it before testing.
34
-
* After a preliminary vote, First Adopters test the proposed changes.
35
-
* The community votes to decide whether the changes should be officially adopted.
36
-
* Finally, changes are implemented into the specification.
37
+
1. A proposal is submitted by opening a Pull Request in the GTFS Repository.
38
+
2. The community engages in discussions to refine the proposal and reviews it before testing.
39
+
3. After a preliminary vote, First Adopters test the proposed changes.
40
+
4. The community votes to decide whether the changes should be officially adopted.
41
+
5. Finally, changes are implemented into the specification.
42
+
43
+
Track A: Functional Changes utilizes steps:
44
+
45
+
* 2.1 Pull Request Publication
46
+
* 2.2 Pull Request Discussion
47
+
* 2.3 Pull Request Review
48
+
* 2.4 Vote to test
49
+
* 2.5 Testing
50
+
* 2.6 Vote to Adopt
51
+
* 2.7 Adoption
37
52
38
53
### Track B: Non-Functional Changes
39
54
40
55
<imgclass="center"width="100%"height="100%"src="../../../../assets/governance-process-non-functional.png"alt="GTFS Governance Change Process Track B">
41
56
42
57
This process guides how the community proposes, reviews, and adopts Non-Functional changes to the specification in the [GTFS Repository](https://github.com/google/transit/pulls).
43
58
44
-
* A proposal is submitted by opening a Pull Request in the GTFS Repository.
45
-
* The community engages in discussions to refine the proposal.
46
-
* The community votes to decide whether the changes should be officially adopted.
47
-
* Finally, changes are implemented into the specification.
59
+
1. A proposal is submitted by opening a Pull Request in the GTFS Repository.
60
+
2. The community engages in discussions to refine the proposal.
61
+
3. The community votes to decide whether the changes should be officially adopted.
62
+
4. Finally, changes are implemented into the specification.
63
+
64
+
Track B: Non-Functional Changes utilizes steps:
65
+
66
+
* 2.1 Pull Request Publication
67
+
* 2.2 Pull Request Discussion
68
+
* 2.3 Pull Request Review
69
+
* 2.6 Vote to Adopt
70
+
* 2.7 Adoption
48
71
49
72
### Track C: Documentation Maintenance
50
73
51
74
<imgclass="center"width="100%"height="100%"src="../../../../assets/governance-process-documentation.png"alt="GTFS Governance Change Process Track C">
52
75
53
76
This process guides how the community proposes, reviews, and adopts changes to maintain the documentation in the [GTFS Repository](https://github.com/google/transit/pulls).
54
77
55
-
* A proposal is submitted by opening a Pull Request in the GTFS Repository.
56
-
* The community engages in discussions to refine the proposal
57
-
* Finally, changes are implemented into the specification.
58
-
59
-
### Pull Request Stage Steps
60
-
61
-
All of the steps in the Pull Request Stage are highlighted below. Consider that only Track A: Functional changes utilizes all the steps. Track B: Non-Functional changes and Track C: Documentation Maintenance utilize a shortened version of the process:
Copy file name to clipboardExpand all lines: docs/en/community/governance/schedule/test-process-steps.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,13 +10,13 @@ A Contributor shares their idea to improve the specification by opening an Issue
10
10
11
11
* Anyone can open an Issue to start a discussion.
12
12
13
-
**<ins>Actions</ins>**
13
+
**Actions**
14
14
15
15
1.**Issue Submission**
16
16
17
17
* A Contributor posts an Issue describing an idea and the problem it would solve.
18
18
19
-
**<ins>Suggestions</ins>**
19
+
**Suggestions**
20
20
21
21
| Suggestion | Details |
22
22
| :---- | :---- |
@@ -30,7 +30,7 @@ A Contributor shares their idea to improve the specification by opening an Issue
30
30
31
31
The community engages in discussions to help develop a proposal for modifying the specification, which will be submitted as a Pull Request in the next stage.
32
32
33
-
**<ins>Actions</ins>**
33
+
**ACTIONS**
34
34
35
35
1.**Issue Discussion**
36
36
@@ -42,7 +42,7 @@ The community engages in discussions to help develop a proposal for modifying th
42
42
* The Working Group can be organized by any contributor or the Maintainer.
43
43
* Discussions held in Working Group meetings should be summarized in the Issue comments.
0 commit comments