Skip to end of banner
Go to start of banner

RFC Process

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Proposed Changes

  • Time bound Review Phases
  • Dedicated time slot for RFC review (Once every 2 weeks)
  • TC will vote at every stage to advance the RFC to the next stage
  • Phases
    • PRELIMINARY REVIEW (2 weeks)
      • RFC enters into PRELIMINARY REVIEW stage once the submitter creates a PR in https://github.com/folio-org/rfcs
      • Submitter works with the TC to get feedback related to the overall scope and the general direction of the RFC
      • Submitter will hold necessary discussions to resolve issues/concerns raised in the PR
      • Submitter will be responsible for resolving all the conversations in the PR
      • TC votes swiftly on whether there is any merit to the RFC
      • Any member of the TC will merge the PR in its current state to advance the PR to the next stage after ensuring that all conversations have been marked as resolved
      • RFC is likely to be rejected at this stage if there is significant misalignment
    • DRAFT REVIEW(2 weeks)
      • Submitter creates a new PR for the DRAFT REVIEW stage
      • A sub group is formed (must have community/TC members who are experts in the area addressed by the RFC)
      • Sub group to works with the submitter to refine the RFC by providing feedback
      • Submitter will be responsible for resolving all the conversations in the PR
      • TC will review the draft when it is ready
      • Any member of the TC will merge the PR in its current state to advance the PR to the next stage after ensuring that all conversations have been marked as resolved
      • TC votes to advance the RFC to the next stage
    • PUBLIC REVIEW (4 weeks)
      • Submitter creates a new PR for the PUBLIC REVIEW stage
      • RFC opened up for a community wide review
      • Community should really take this opportunity to weigh in on the changes
      • Create POCs/RI's to identify any gaps (Optional)
    • FINAL REVIEW (2-4 weeks)
      • TC will review and deliberate over the comments from the community and decide what should be included and what should be left out of the RFC 
      • Submitter prepares the final version of the RFC
      • TC does the final review and Sign Off
      • TC should really work towards getting a consensus on this final vote or at least have an overwhelming majority in favor of the RFC
  • No labels