Versions Compared

Old Version 40

changes.mady.by.user Taras Spashchenko

Saved on

compared with

New Version Current

changes.mady.by.user Craig McNally

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Purpose:  The submitter prepares the RFC abstract and brings it to the attention of the Technical Council.

Timebox:  Approximately 16-17 weeks when incorporating review windows and accounting for administrative overhead, making adjustments, etc.

Steps:

  1. The submitter creates a PR in https://github.com/folio-org/rfcs but only populates the following sections:
    1. Metadata - Contributors, links to PRs, outcome, etc.
    2. Overview - An overview of what the RFC is about
    3. Scope - Defines the scope of what the RFC intends to cover/not cover
    4. Timing - Indicates a rough timeline of when the RFC might be ready
  2. The submitter updates the "RFC PRs" section of the metadata to link to the PRELIMINARY REVIEW pull request.
  3. The submitter should contact one of the Technical Council chairs and plan to attend a TC meeting in the near future to present the RFC Abstract.

...

Purpose: Final review and discussion by Technical Council, leading to a decision

Timebox:  This may not be needed. This stage seems to move quickly. If consistency is desired, a short duration (e.g., 1 week) could be chosen.

Steps:

  1. The Technical Council will review and deliberate over the comments from the community 
  2. The submitter creates a new PR for the FINAL REVIEW stage
  3. The Technical Council does the final review and votes on whether the RFC should be Accepted or Rejected
  4. The FINAL REVIEW pull request is updated with appropriate outcome.
  5. A message is sent to the public #tc-rfc slack channel announcing the outcome of the RFC.
  6. The Technical Council should really work towards getting a consensus on this final vote or at least have an overwhelming majority in favor of the RFC

...

  • To help us learn, a retrospective will be performed regardless of the outcome of the RFC.  
  • The submitter should work with the Technical Council to log a decision N.B. A formal decision should be logged in the Technical Council's Decision Log.  This is one of the primary deliverables of this process and should not be overlooked.  
    • If needed, the Technical Council can help the submitter with this.
    • Adding a list of keywords to the bottom of the DR would make it easier to find information via search.

...