Skip to content

Commit 1e6500b

Browse files
author
joeyaiello
committed
addressed last round of comments from Committee
1 parent c55700d commit 1e6500b

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

RFC0000-RFC-Process.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
RFC: RFC0000
3-
Author: Steve Lee
3+
Author: Steve Lee, Joey Aiello
44
Status: Draft
55
Area: Process
66
Version: 1.4
@@ -35,13 +35,14 @@ RFC documents shall follow the following template:
3535

3636
```markdown
3737
---
38-
RFC: RFC<four digit unique incrementing number assigned by Committee, this should be left blank by the author>
38+
RFC: RFC<four digit unique incrementing number assigned by Committee, this shall be left blank by the author>
3939
Author: <First Last>
4040
Status: <Draft | Experimental | Accepted | Rejected | Withdrawn | Final>
4141
SupercededBy: <link to another RFC>
4242
Version: <Major>.<Minor>
4343
Area: <Area within the PowerShell language>
4444
Comments Due: <Date for submitting comments to current draft (minimum 1 month)>
45+
Plan to implement: <Yes | No>
4546
---
4647

4748
# Title
@@ -74,14 +75,15 @@ This is the initial draft of an RFC posted for comments and considered a work-in
7475
Typically, one or two months is allowed for comments, though this may be extended if a submission is particularly contentious or hasn't received enough feedback for the Committee to feel comfortable making a decision.
7576
* When the Committee closes the comment period, the Author should update the RFC and Pull Request with a new commit to address the comments.
7677
* The Committee shall vote to merge or reject the RFC.
78+
Note: the Comittee may be slower to respond to RFCs where the Author has indicated that they do not plan to implement the RFC.
7779

7880
### Draft-Accepted
7981

8082
The PowerShell Committee has reviewed the RFC and comments, and has voted to accept the RFC as a Draft.
8183

8284
* New comments are not being sought.
8385
* No one has begun implementing the RFC, and there are no current plans to implement the RFC.
84-
* The community is invited to implement the RFC (unless explicitly stated in the RFC).
86+
In this case, the Comittee will create `up-for-grabs` Issues in the [PowerShell](https://github.com/PowerShell/PowerShell) repository.
8587

8688
### Experimental
8789

@@ -109,6 +111,7 @@ RFCs in the `Withdrawn` state were rescinded by the RFC Author.
109111

110112
RFCs in the `Final` state are considered fully complete and implemented in PowerShell.
111113
Any proposed changes should be made through a new RFC or via an Issue in the [PowerShell/PowerShell repository](https://github.com/powershell/powershell).
114+
New RFCs should reference old RFCs where applicable.
112115

113116
## History
114117
v1.1 - 5-20-2016 - Updated to enable RFCs for design changes that don't require code changes.

0 commit comments

Comments
 (0)