Log in Sign up
1 Matching Annotations
  1. Nov 2020
  2. github.com github.com
    Governance · Issue #274 · yarnpkg/yarn
    1
    1. TylerRick 12 Nov 2020
      in Public
      In Rust, we use the "No New Rationale" rule, which says that the decision to merge (or not merge) an RFC is based only on rationale that was presented and debated in public. This avoids accidents where the community feels blindsided by a decision.
      open-source projects: allowing community (who are not on core team) to influence/affect/steer the direction of the project feeling blindsided allowing sufficient time for discussion/feedback/debate before a final decision is made have discussion/feedback/debate in public (transparency)
    Visit annotations in context

    Tags

    • feeling blindsided
    • open-source projects: allowing community (who are not on core team) to influence/affect/steer the direction of the project
    • have discussion/feedback/debate in public (transparency)
    • allowing sufficient time for discussion/feedback/debate before a final decision is made

    Annotators

    • TylerRick

    URL

    github.com/yarnpkg/yarn/issues/274
Share:
Group. Only group members will be able to view this annotation.
Only me. No one else will be able to view this annotation.
Hypothes.is
  • About
  • Blog
  • Bioscience
  • Education
  • Jobs
  • Help
  • Contact
  • Terms of Service
  • Privacy Policy