[Template] New BSIP

[ryanRfox]

This Issue Description would become the default "New Issue" template within the BSIPS repo.

Instructions

• Review the BSIP Process Flow document
• Include a detailed Title above
• Complete the BSIP Template below be replacing the with your draft text
• Submit Your BSIP Draft

    BSIP: TBD
    Title: <BSIP title>
    Authors: <list of authors' real names and optionally, email address>
    Status: Draft
    Type: [ Informational | Protocol ]
    Created: <date created on, in ISO 8601 (yyyy-mm-dd) format>
    Discussion: <this Issue was created>
    Replaces: <BSIP number> (optional)
    Superseded-By: <BSIP number> (optional)
    Worker: <Id of worker proposal> (optional)

Abstract

<A short (~200 word) description of the technical issue being addressed.>

Motivation

# Rational # Specifications # Discussion # Summary for Voters # Copyright < Each BSIP must either be explicitly labelled as _placed in the public domain_ or licensed under the [Open Publication License](https://en.wikipedia.org/wiki/Open_Publication_License).> # See Also (optional) ### Submit Your BSIP Draft Finally, press the 'Submit new issue' button. The BSIP Review Team will work with the author and Community to progress thru their Task List below. ### BSIP Review Team Task List: - [ ] Draft BSIP - [ ] Discussion (add link to this Issue) - [ ] Approve/Deny Draft - [ ] Assign BSIP ID - [ ] Publish BSIP - [ ] Publish notification - [ ] Accept/Defer for Implementation - [ ] Notify relevant development team(s) - [ ] Prioritize on Backlog - [ ] Fund Implementation - [ ] Implement

[ryanRfox]

Regarding the Task List above: I feel performance of the Task List will be performed by these (roles):

BSIP Review Team Task List:

• [ ] Draft BSIP (author, Community, BSIP Review Team)
• [ ] Discussion (author, Community, BSIP Review Team)
• [ ] Approve/Deny Draft (BSIP Review Team)
  • [ ] Assign BSIP ID (BSIP Review Team)
  • [ ] Publish BSIP (BSIP Review Team)
  • [ ] Publish notification (BBF will create the WP and notify on their site. Author will promote elsewhere.)
• [ ] Accept/Defer for Implementation (Community Vote)
  • [ ] Notify relevant development team(s) (BSIP Review Team)
  • [ ] Prioritize on Backlog (Relevant development team(s))
• [ ] Fund Implementation (dev team(s) if they have capacity, else separate WP)
• [ ] Implement (dev team(s))

[ryanRfox]

Alternative workflow:

• [ ] Create Issue [BSIP Draft] (author)
  • [ ] Refine Draft (author, Community, BSIP Review Team)
  • [ ] Document Discussion (author, Community)
• [ ] Accept/Deny Draft (BSIP Review Team)
  • [ ] Assign BSIP ID (BSIP Review Team)
  • [ ] Create Pull Request [BSIP ID] (BSIP Review Team)
  • [ ] Finalize BSIP (author, Community, BSIP Review Team)
  • [ ] Document Discussion (author, Community) -[ ] Accept/Deny BSIP (BSIP Review Team)
  • [ ] Merge BSIP (BSIP Review Team)
  • [ ] Publish voting notification (BBF will create the WP and notify on their site. Author will promote elsewhere.)
• [ ] Accept/Defer for Implementation (Community Vote)
  • [ ] Notify relevant development team(s) (BSIP Review Team)
  • [ ] Prioritize on Backlog (Relevant development team(s))
• [ ] Fund Implementation (dev team(s) if they have capacity, else separate WP)
• [ ] Implement (dev team(s))