|
1 | 1 | ---
|
2 | 2 | RFC: RFC0000
|
3 |
| -Author: Steve Lee |
| 3 | +Author: Steve Lee, Joey Aiello |
4 | 4 | Status: Draft
|
5 | 5 | Area: Process
|
6 | 6 | Version: 1.4
|
@@ -35,13 +35,14 @@ RFC documents shall follow the following template:
|
35 | 35 |
|
36 | 36 | ```markdown
|
37 | 37 | ---
|
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> |
39 | 39 | Author: <First Last>
|
40 | 40 | Status: <Draft | Experimental | Accepted | Rejected | Withdrawn | Final>
|
41 | 41 | SupercededBy: <link to another RFC>
|
42 | 42 | Version: <Major>.<Minor>
|
43 | 43 | Area: <Area within the PowerShell language>
|
44 | 44 | Comments Due: <Date for submitting comments to current draft (minimum 1 month)>
|
| 45 | +Plan to implement: <Yes | No> |
45 | 46 | ---
|
46 | 47 |
|
47 | 48 | # Title
|
@@ -74,14 +75,15 @@ This is the initial draft of an RFC posted for comments and considered a work-in
|
74 | 75 | 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.
|
75 | 76 | * When the Committee closes the comment period, the Author should update the RFC and Pull Request with a new commit to address the comments.
|
76 | 77 | * 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. |
77 | 79 |
|
78 | 80 | ### Draft-Accepted
|
79 | 81 |
|
80 | 82 | The PowerShell Committee has reviewed the RFC and comments, and has voted to accept the RFC as a Draft.
|
81 | 83 |
|
82 | 84 | * New comments are not being sought.
|
83 | 85 | * 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. |
85 | 87 |
|
86 | 88 | ### Experimental
|
87 | 89 |
|
@@ -109,6 +111,7 @@ RFCs in the `Withdrawn` state were rescinded by the RFC Author.
|
109 | 111 |
|
110 | 112 | RFCs in the `Final` state are considered fully complete and implemented in PowerShell.
|
111 | 113 | 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. |
112 | 115 |
|
113 | 116 | ## History
|
114 | 117 | v1.1 - 5-20-2016 - Updated to enable RFCs for design changes that don't require code changes.
|
|
0 commit comments