Merge pull request PowerShell#11 from PowerShell/lzybkr-update-rfc

Open RFCs to the community

Author: lzybkr

RFC0000-RFC-Process.md

@@ -3,29 +3,26 @@ RFC: 0000
 Author: Steve Lee
 Status: Draft
 Area: Process
-Version: 1.1
+Version: 1.2
 Feedback: https://github.com/PowerShell/PowerShell-Language-RFC/issues/5
 ---
 
 # PowerShell RFC Process and Guidelines
 
-A PowerShell RFC (Request for Comments) is a publication to propose 
-design changes and improvements to PowerShell.  This provides the community an opportunity 
-to provide feedback before code is written where it becomes harder to change at the risk of 
-compatibility. The complete list of RFCs are available at
-https://github.com/powershell/powershell-rfc
+A PowerShell RFC (Request for Comments) is a publication to propose design changes and improvements to PowerShell.
+This provides the community an opportunity to provide feedback before code is written where it becomes harder to change at the risk of 
+compatibility.
+The complete list of RFCs are available at https://github.com/powershell/powershell-rfc
 
-This process was adapted from the Chef RFC process as well as from DMTF.org process
+This process was adapted from the Chef RFC process as well as from DMTF.org process.
 
 ## Roles
 
-Currently, only members of the PowerShell Core team are allowed to author
-new RFCs.  All members of the community can provide feedback to any RFC.
+All members of the community are allowed to author new RFCs and can provide feedback to any RFC.
 
 ## RFC Naming Convention
 
-RFC documents shall follow the naming convention of "RFC####-Title.md" where #### is 
-the RFC number and Title is the title of the document.
+RFC documents shall follow the naming convention of "RFC####-Title.md" where #### is the RFC number and Title is the title of the document.
 
 ## RFC Template
 
@@ -62,34 +59,34 @@ RFCs go through applicable stages:
 
 * Draft
 
-This is the initial draft of a RFC posted for comments and considered a
-work-in-progress.  Typically, two months is allowed for comments.
+This is the initial draft of a RFC posted for comments and considered a work-in-progress.
+Typically, two months is allowed for comments.
 
 * Draft-Accepted
 
-Comments have been reviewed and new comments are not being sought.  Code
-work has not started/planned or not needed.
+Comments have been reviewed and new comments are not being sought.
+Code work has not started/planned or not needed.
 
 * Experimental
 
-Comments have been reviewed and code is being written to provide an working
-example of the proposed design change to get further feedback.
+Comments have been reviewed and code is being written to provide an working example of the proposed design change to get further feedback.
 
 * Experimental-Accepted
 
 Feedback from the experimental implementation and RFC have been reviewed.
-Engineering team will work towards final implementation in code to match
-the RFC.
+Engineering team will work towards final implementation in code to match the RFC.
 
 * Rejected
 
 Based on community feedback, this RFC was decided to not proceed any further.
 
 * Final
 
-Design and implementation is considered complete.  Any proposed changes 
-would be through a new RFC.
+Design and implementation is considered complete.
+Any proposed changes would be through a new RFC.
 
----
-History:
-v1.1 - 5-20-2016 - Updated to enable RFCs for design changes that don't require code changes.  Added Draft-Accepted state and Version header property.
+## History
+v1.1 - 5-20-2016 - Updated to enable RFCs for design changes that don't require code changes.
+Added Draft-Accepted state and Version header property.
+
+v1.2 - 8-18-2016 - Open submitting RFCs to the community and update formatting.