From 81ea20bbb6e4da0a0f143b6d4160a391b89fb3fd Mon Sep 17 00:00:00 2001 From: Tim Smith Date: Tue, 23 Apr 2019 11:57:44 -0700 Subject: Add back Ruby 2.4 support / update testing Add back Ruby 2.4 support Test on more versions in Appveyor Test on the latest ruby versions in Travis Add our full set of GitHub templates Enable issue locking Add a contributing file Signed-off-by: Tim Smith --- .github/ISSUE_TEMPLATE/DESIGN_PROPOSAL.md | 40 +++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/DESIGN_PROPOSAL.md (limited to '.github/ISSUE_TEMPLATE/DESIGN_PROPOSAL.md') diff --git a/.github/ISSUE_TEMPLATE/DESIGN_PROPOSAL.md b/.github/ISSUE_TEMPLATE/DESIGN_PROPOSAL.md new file mode 100644 index 0000000..9f4a958 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/DESIGN_PROPOSAL.md @@ -0,0 +1,40 @@ +--- +name: Design Proposal +about: I have a significant change I would like to propose and discuss before starting +labels: "Status: Untriaged" +--- + +### When a Change Needs a Design Proposal + +A design proposal should be opened any time a change meets one of the following qualifications: + +- Significantly changes the user experience of a project in a way that impacts users. +- Significantly changes the underlying architecture of the project in a way that impacts other developers. +- Changes the development or testing process of the project such as a change of CI systems or test frameworks. + +### Why We Use This Process + +- Allows all interested parties (including any community member) to discuss large impact changes to a project. +- Serves as a durable paper trail for discussions regarding project architecture. +- Forces design discussions to occur before PRs are created. +- Reduces PR refactoring and rejected PRs. + +--- + + + +## Motivation + + + +## Specification + + + +## Downstream Impact + + -- cgit v1.2.1