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
@@ -31,11 +31,9 @@ This RFC covers four main stages of how we tackle large scale work, referred to
31
31
32
32
## Proposal
33
33
34
-
Anyone may propose a large scale project to be worked on. Projects are proposed by opening an issue that is tagged with the `project` tag on the [Issue Tracker].
34
+
Anyone may propose a large scale project to be worked on. Projects are proposed by opening an PR that copies the project template from `0000-project-template.md` to `projects/in-progress/0000-your-project-name.md`.
All proposals should contain the following information:
36
+
All proposals should contain the following information in the template file:
39
37
40
38
1. What is the current problem/shortcoming?
41
39
2. What is the relevance to the Rust Embedded Ecosystem?
@@ -48,17 +46,6 @@ Once a potential sponsor has been found, the project may be selected.
48
46
49
47
## Selection
50
48
51
-
In order to move an issue from "proposed" to "selected", the proposer and sponsor should open a PR to add the project to the `projects/` folder in this repo. Items in this folder should be named `0000-project-name.md`, and should contain the following information:
52
-
53
-
1. All contents from the proposal
54
-
* Original problem
55
-
* Relevance
56
-
* Desired Outcome
57
-
* What will be done?
58
-
2. Who is the WG sponsor for this issue?
59
-
3. Who else is working on this issue?
60
-
4. If relevant, a link to the repository where work on this project is being done
61
-
62
49
A project does not require full WG approval to be selected, only the sponsorship of one or more WG members. This member will be expected to provide status updates at the weekly Matrix meeting on the status of this project. If the WG member is unable to attend, they can delegate this responsibility as necessary.
63
50
64
51
A project moves to the tracking state once the PR adding the project to the `projects/` folder has been approved by the sponsoring WG member.
@@ -83,13 +70,13 @@ Once a project has been completed, the WG sponsor is no longer required to provi
83
70
84
71
### Finished
85
72
86
-
If the work has completed successfully by meeting the current or revised goals, and does not require ongoing focus, this can be signified by submitting a PR to move the project file from `projects/` to `projects/completed/`. This move only requires the approval of the sponsoring WG member.
73
+
If the work has completed successfully by meeting the current or revised goals, and does not require ongoing focus, this can be signified by submitting a PR to move the project file from `projects/in-progress/` to `projects/completed/`. This move only requires the approval of the sponsoring WG member.
87
74
88
75
It is recommended to add a section to the project file summarizing the outcome of the project, and what was achieved.
89
76
90
77
### On-Hold
91
78
92
-
If the work need to be put on hold due to availability or technical reasons, this can be signified by submitting a PR to move the project file from `projects/` to `projects/on-hold/`. This move only requires the approval of the sponsoring WG member.
79
+
If the work need to be put on hold due to availability or technical reasons, this can be signified by submitting a PR to move the project file from `projects/in-progress/` to `projects/on-hold/`. This move only requires the approval of the sponsoring WG member.
93
80
94
81
If a project is not expected to make progress, or hasn't made progress, for one month or more it is recommended that it be moved to the on-hold state.
95
82
@@ -128,4 +115,4 @@ What other designs have been considered? What is the impact of not doing this?
0 commit comments