Skip to content

Commit 4f4b1e7

Browse files
author
joeyaiello
committed
joeyaiello fixes to language and terms
1 parent 66a98d7 commit 4f4b1e7

File tree

1 file changed

+22
-19
lines changed

1 file changed

+22
-19
lines changed

RFC0000-RFC-Process.md

Lines changed: 22 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ RFC: RFC0000
33
Author: Steve Lee
44
Status: Draft
55
Area: Process
6-
Version: 1.3
6+
Version: 1.3.1
77
Feedback: https://github.com/PowerShell/PowerShell-Language-RFC/issues/5
88
---
99

@@ -18,9 +18,10 @@ This process was adapted from the Chef RFC process as well as from DMTF.org proc
1818

1919
## Roles
2020

21-
- **Author** - All members of the community are allowed to author new RFCs and can provide feedback to any RFC.
22-
- **Maintainer** - Owner of the RFC process.
23-
- **Maintainer's committee** - Committee of Maintainers to vote and to make conclusion about accept/reject RFC.
21+
* **Author**: All members of the community are allowed to author new RFCs and can provide feedback to any RFC.
22+
* **PowerShell Committee**: The design committe that votes to accept or reject an RFC.
23+
(Learn more about the PowerShell Committee [here](https://github.com/PowerShell/PowerShell/blob/master/docs/community/governance.md#powershell-committee).)
24+
* **Committee Member**: An individual member of the PowerShell Committee.
2425

2526
## RFC Naming Convention
2627

@@ -40,7 +41,7 @@ Status: <Draft | Experimental | Accepted | Rejected | Withdrawn | Final>
4041
SupercededBy: <link to another RFC>
4142
Version: <Major>.<Minor>
4243
Area: <Area within the PowerShell language>
43-
Comments Due: <Date for submitting comments to current draft. Minimum 1 month>
44+
Comments Due: <Date for submitting comments to current draft (minimum 1 month)>
4445
---
4546

4647
# Title
@@ -67,31 +68,31 @@ RFCs go through applicable stages:
6768

6869
This is the initial draft of a RFC posted for comments and considered a work-in-progress.
6970

70-
New proposed drafts should be submitted as a Pull Request from Author's fork.
71-
Author must ensure the 'modifiable by maintainers' is checked so that the Maintainers can assign the next RFC number.
71+
New proposed drafts should be submitted as a Pull Request from the Author's fork.
72+
The Author must ensure that 'Allow edits from maintainers' is checked so that a Committee Member can assign the next RFC number.
7273

73-
Maintainers only ensure that the RFC adheres to the template and the RFC process and then merge the PRPull Request.
74+
Committee Members also ensure that the RFC adheres to the template and the RFC process before merging the Pull Request.
7475

75-
After that Maintainers will ask the Author to create an issue for this RFC and used for collection and response to comments (Author creates it so that they get notified of new comments instead of the Maintainer).
76-
Typically, one or two months is allowed for comments (see above `Comments Due`).
76+
After the Pull Request is merged, Maintainers will ask the Author to create an issue for this RFC to collect and respond to feedback on the RFC.
77+
(The Author should create issue so that they get notified of new comments instead of the Committee Member.)
78+
Typically, one or two months is allowed for comments (see `Comments Due` above).
7779

78-
Community discuss the RFC.
80+
At this point, the community discusses the RFC.
7981

80-
After `Comments Due` date the Author summarizes comments, submit new Pull Request to make the final RFC Draft and ask the Maintainer's committee to vote.
82+
After the `Comments Due` date, the Author summarizes the comments, submits a new Pull Request to make the final RFC Draft, and asks the PowerShell Committee to vote.
8183

82-
Maintainers merge the Pull Request.
83-
84-
The Maintainer's committee vote for the RFC Draft and make a conclusion: reject, return for discussion, accept.
84+
Just before voting, the PowerShell Comittee merges the Pull Request.
85+
The PowerShell Committee then votes to accept or reject the RFC Draft.
8586

8687
* Draft-Accepted
8788

88-
The Maintainer's committee reviewed the RFC Draft and comments, voted and accepted the RFC Draft.
89+
The PowerShell Committee has reviewed the RFC Draft and comments, and has voted to accept the RFC Draft.
8990

90-
New comments are not being sought.
91+
At this point, new comments are not being sought.
9192

92-
Code work has not started/planned or not needed.
93+
Code work has not started and is not planned or not needed.
9394

94-
Community is invited to use and implement the RFC.
95+
The community is invited to implement the RFC.
9596

9697
* Experimental
9798

@@ -122,3 +123,5 @@ Added Draft-Accepted state and Version header property.
122123
v1.2 - 8-18-2016 - Open submitting RFCs to the community and update formatting.
123124

124125
v1.3 - 9-26-2016 - Added Withdrawn stage. Comments Due field to template. Updated guidance on RFC numbering.
126+
127+
v1.3.1 - 3-22-2017 - Cleaned up language and made explicit clarifications to process

0 commit comments

Comments
 (0)