Proposal for pep process

[mattjmorrison]

• We will use Github Projects to facilitate the pep workflow and a github pages site for the approved & adopted peps
• A pep will be submitted as an issue in the peps repo in the peps project (we will have an issue template to facilitate the necessary inputs for a new pep)
  • New peps should include the following fields
    • title
    • description
    • appropriate labels
• Be default new peps will be in a "Draft" status, they can then be moved from "Draft" to "Submitted" which is where the Steering Committee will review.
• After the steering committee reviews it it will be moved into RFC (Request for Comment) and will be sent out to the group (via Discord - in a #pep channel)
  • Steering Committee will determine the if the pep is:
    • redundant and can be deleted
    • labeled correctly and is clearly defined
    • ready for immediate implementation (ie trivial spelling fixes, etc)
    • within the scope of our mission
• At the following steering committee meeting, after the pep has been in RFC for 1 week, the comments will be reviewed and the pep will be voted on and will then be moved to Accepted or Rejected
• Peps that have been accepted will be updated in the peps repo (which will appear on the peps website) and there will be a link added back to the original pep issue.
• There will be a pending status in case some action needs to be taken before a pep is able to be adopted.

[mattjmorrison]

Should we include what specific inputs that we would like all peps to include? I did create a template, but it's just a title and a description

[mattjmorrison]

A pep can be in a "draft" mode prior to being "submitted"

[Automatez]

Part of moving RFC over to Accepted will also include assigning someone to handle updating the peps repo (adding new or amending as needed)