Update github templates and cutover to the Chef Foundation team

.expeditor/config.yml

@@ -2,7 +2,7 @@
 ---
 # Slack channel in Chef Software slack to send notifications about build failures, etc
 slack:
-  notify_channel: releng-notify
+  notify_channel: chef-found-notify
 
 # This publish is triggered by the `built_in:publish_rubygems` artifact_action.
 rubygems:
@@ -15,7 +15,10 @@ github:
   version_tag_format: "v{{version}}"
   # allow bumping the minor release via label
   minor_bump_labels:
-    - "Expeditor: Bump Minor Version"
+    - "Expeditor: Bump Version Minor"
+  # allow bumping the major release via label
+  major_bump_labels:
+    - "Expeditor: Bump Version Major"
 
 changelog:
   rollup_header: Changes not yet released to rubygems.org
@@ -30,7 +33,7 @@ merge_actions:
       only_if: built_in:bump_version
   - built_in:update_changelog:
       ignore_labels:
-        - "Expeditor: Exclude From Changelog"
+        - "Expeditor: Skip Changelog"
         - "Expeditor: Skip All"
   - built_in:build_gem:
       only_if: built_in:bump_version

.github/CODEOWNERS

@@ -1,3 +1,5 @@
 # Order is important. The last matching pattern has the most precedence.
 
-* @chef/jex-team
+*                 @chef/chef-foundation-reviewers
+.expeditor/**     @chef/jex-team
+*.md              @chef/docs-team

.github/ISSUE_TEMPLATE.md → .github/ISSUE_TEMPLATE/BUG_TEMPLATE.md

@@ -1,8 +1,16 @@
+---
+name: � Bug Report
+about: If something isn't working as expected �.
+labels: "Status: Untriaged"
+---
+
 # Version:
 
 [Version of the project installed]
 
-# Environment: [Details about the environment such as the Operating System, cookbook details, etc...]
+# Environment:
+
+[Details about the environment such as the Operating System, cookbook details, etc...]
 
 # Scenario:
 

.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.
+
+---
+
+<!---  Proposal description and rationale.  -->
+
+## Motivation
+
+<!---
+    As a <<user_profile>>,
+    I want to <<functionality>>,
+    so that <<benefit>>.
+ -->
+
+## Specification
+
+<!---  A detailed description of the planned implementation. -->
+
+## Downstream Impact
+
+<!---  Which other tools will be impacted by this work?  -->

.github/ISSUE_TEMPLATE/ENHANCEMENT_REQUEST_TEMPLATE.md

@@ -0,0 +1,17 @@
+---
+name: 🚀 Enhancement Request
+about: I have a suggestion (and may want to implement it 🙂)!
+labels: "Status: Untriaged"
+---
+
+### Describe the Enhancement:
+<!---  What you are trying to achieve that you can't? -->
+
+### Describe the Need:
+<!---  What kind of user do you believe would utilize this enhancement, and how many users might want this functionality -->
+
+### Current Alternative
+<!--- Is there a current alternative that you can utilize to workaround the lack of this enhancement -->
+
+### Can We Help You Implement This?:
+<!---  The best way to ensure your enhancement is built is to help implement the enhancement yourself. If you're interested in helping out we'd love to give you a hand to make this possible. Let us know if there's something you need. -->

.github/ISSUE_TEMPLATE/SUPPORT_QUESTION.md

@@ -0,0 +1,11 @@
+---
+name: 🤗 Support Question
+about: If you have a question 💬, please check out our Slack!
+---
+
+We use GitHub issues to track bugs and feature requests. If you need help please post to our Mailing List or join the Chef Community Slack.
+
+ * Chef Community Slack at http://community-slack.chef.io/.
+ * Chef Mailing List https://discourse.chef.io/
+
+ Support issues opened here will be closed and redirected to Slack or Discourse.

.github/PULL_REQUEST_TEMPLATE.md

@@ -5,10 +5,11 @@
 ### Issues Resolved
 
 [List any existing issues this PR resolves, or any Discourse or
-StackOverflow discussion that's relevant]
+StackOverflow discussions that are relevant]
 
 ### Check List
 
 - [ ] New functionality includes tests
 - [ ] All tests pass
 - [ ] All commits have been signed-off for the Developer Certificate of Origin. See <https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco>
+- [ ] PR title is a worthy inclusion in the CHANGELOG

.github/lock.yml

@@ -0,0 +1 @@
+daysUntilLock: 60

.travis.yml

@@ -1,11 +1,11 @@
-sudo: false
 language: ruby
 cache: bundler
+dist: xenial
 
 addons:
   apt:
     sources:
-      - chef-stable-trusty
+      - chef-stable-xenial
     packages:
       - chefdk
       - wget
@@ -14,25 +14,20 @@ addons:
 
 matrix:
   include:
-      # WE SUPPORT UPGRADES OF CHEF 11.x on RUBY 1.9.3 VIA chef_client_updater COOKBOOK
-    - rvm: 1.9.3
-      bundler_args: --without chefstyle functional development docs --jobs=3 --retry=3 --path=${BUNDLE_PATH:-vendor/bundle}
-      script:
-        - bundle exec rake unit
-        - bundle exec rake functional
     - rvm: 2.0
     - rvm: 2.1.10
     - rvm: 2.2.10
     - rvm: 2.3.8
     - rvm: 2.4.5
-    - rvm: 2.5.3
+    - rvm: 2.5.5
+    - rvm: 2.6.2
     - rvm: ruby-head
   allow_failures:
     - rvm: ruby-head
 
 branches:
   only:
-  - master
+    - master
 
 bundler_args: --without docs development
 

CONTRIBUTING.md

@@ -1,14 +1 @@
-This project is maintained by the contribution guidelines identified for
-  [chef](https://github.com/chef/chef) project. You can find the guidelines here:
-
-https://github.com/chef/chef/blob/master/CONTRIBUTING.md
-
-Pull requests in this project are merged when they have two :+1:s from maintainers.
-
-## Maintainers
-
-
-- [Thom May](https://github.com/thommay)
-- [Patrick Wright](https://github.com/patrick-wright)
-- [Serdar Sutay](https://github.com/sersut)
-- [Seth Chisamore](https://github.com/schisamo)
+Please refer to https://github.com/chef/chef/blob/master/CONTRIBUTING.md

Gemfile

@@ -12,8 +12,7 @@ group :test do
   gem "rake"
   gem "rspec"
   gem "vcr"
-  gem "webmock", "~> 2.3.2"      # ruby 1.9.3
-  gem "addressable", "~> 2.4.0"  # ruby 1.9.3
+  gem "webmock", "~> 3.4"
   gem "aruba", "~> 0.14"
   gem "cucumber", "~> 1.3.20"
   gem "climate_control"