Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Update RFC process, add blog post blurb section to RFC template #1750

Merged
merged 12 commits into from
Oct 30, 2018

Commits on Oct 19, 2018

  1. Update how-we-work to capture RFC process modifications discussed

    Co-Authored-By: Ash Wilson <smashwilson@gmail.com>
    Co-Authored-By: Vanessa Yuen <vanessayuenn@users.noreply.github.com>
    3 people committed Oct 19, 2018
    Configuration menu
    Copy the full SHA
    861410d View commit details
    Browse the repository at this point in the history
  2. State what goals of RFC are and are not

    Co-Authored-By: Ash Wilson <smashwilson@gmail.com>
    Co-Authored-By: Vanessa Yuen <vanessayuenn@users.noreply.github.com>
    3 people committed Oct 19, 2018
    Configuration menu
    Copy the full SHA
    bc1b2eb View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    4c3b0f3 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    0ad0ca1 View commit details
    Browse the repository at this point in the history

Commits on Oct 23, 2018

  1. Configuration menu
    Copy the full SHA
    a21fec9 View commit details
    Browse the repository at this point in the history

Commits on Oct 29, 2018

  1. Configuration menu
    Copy the full SHA
    04cb55a View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    0db18af View commit details
    Browse the repository at this point in the history

Commits on Oct 30, 2018

  1. Tweak merge criteria based on @smashwilson's comment

    > I'm kind of thinking of it as "we merge the RFC PR when we, the core team, move on to something else and aren't working on it directly for a while," rather than when we hit some "completeness" threshold? Put another way - I think that us starting to work on new things is a good, emergent, arbitrary way for us to call a feature "shipped", even if there's still stuff in the document that we haven't gotten to yet.
    
    Co-Authored-By: Ash Wilson <smashwilson@gmail.com>
    kuychaco and smashwilson committed Oct 30, 2018
    Configuration menu
    Copy the full SHA
    f73ba51 View commit details
    Browse the repository at this point in the history
  2. RFC --> Feature Request

    Co-Authored-By: Vanessa Yuen <vanessayuenn@users.noreply.github.com>
    kuychaco and vanessayuenn committed Oct 30, 2018
    1 Configuration menu
    Copy the full SHA
    cffb2b0 View commit details
    Browse the repository at this point in the history
  3. Emojify RFC template 😄

    Co-Authored-By: Vanessa Yuen <vanessayuenn@users.noreply.github.com>
    kuychaco and vanessayuenn committed Oct 30, 2018
    Configuration menu
    Copy the full SHA
    d626f7a View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    ce12fe8 View commit details
    Browse the repository at this point in the history
  5. Add why we use pull requests instead of issues for Feature Requests

    Co-Authored-By: Ash Wilson <smashwilson@gmail.com>
    kuychaco and smashwilson committed Oct 30, 2018
    Configuration menu
    Copy the full SHA
    1ae716f View commit details
    Browse the repository at this point in the history