Added License Files and Initial Setup

Signed-off-by: David Deal <[email protected]>

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,68 @@
+---
+name: Bug Report
+about: Create a report to help us improve
+title: 'EasyCLA Bug Report'
+labels: 'bug'
+assignees: ''
+---
+
+## Summary
+
+Describe the bug - a clear and concise description of what the bug is.
+
+## Background
+
+Provide context to the issue - provide steps to reproduce the behavior, such as:
+
+1. Go to '...'
+1. Click on '....'
+1. Scroll down to '....'
+1. See error
+
+## Expected behavior
+
+A clear and concise description of what you expected to happen.
+
+## Screenshots
+
+If applicable, add screenshots to help explain your problem.
+
+## Environment
+
+Please complete the following information:
+
+* Environment: STAGING and PROD 
+* OS: \[e.g. iOS\]
+* Browser \[e.g. chrome, safari\]
+* Version \[e.g. 22\]
+
+## Additional Context
+
+Add any other context about the problem here.
+
+## Assumptions
+
+If you are assuming certain facts or scenarios, list them so we have a baseline to understand your request.
+
+- [...] Assumption 1
+- [...] Assumption 2
+
+## Questions
+
+List any questions or clarifications that are needed to addressed to satisfy this request.
+
+1. [...] Question 1...
+1. [...] Question 2...
+
+## Acceptance Criteria
+
+The "done" criteria when this feature or problem is resolved. Such as:
+
+1. Unit Tests added and running in CI
+1. Functional Tests updated to cover feature, if applicable
+1. Demonstrate the set of capabilities to the product team while the code is running in the STAGING environment.
+
+## References
+
+\(Optional\) Provide any code or specification references that would be helpful for the developer implementing this feature.
+

.github/ISSUE_TEMPLATE/docs_update.md

@@ -0,0 +1,37 @@
+---
+name: Documentation Update
+about: Suggest an update for the project documentation
+title: ''
+labels: 'documentation'
+assignees: ''
+---
+
+## Impacted Docs
+
+Describe what has changed and which documents need updating
+
+* [/docs/doc-to-update.md](https://github.com/communitybridge/easycla/blob/master/docs/)
+
+## Tasks
+
+* [ ] Review help documents for impacts beyond what this issue explicitly calls out
+* [ ] Task 2
+* [ ] Task 3
+* [ ] Comment on any additional changes made relating to this issue, provide help doc link\(s\)
+
+## Verbiage
+
+Provide applicable markdown/text.
+
+## Acceptance Criteria
+
+The "done" criteria when this feature or problem is resolved. Such as:
+
+1. Documentation changes submitted as a Pull Request
+1. Pull Request Reviewed and Approved by Product Owner
+1. Documentation changes merged to 'master' branch
+
+## Images
+
+Attach any images or screenshots related to this documentation update.
+

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,54 @@
+---
+name: Feature Request
+about: Suggest an idea for this project
+title: ''
+labels: 'enhancement'
+assignees: ''
+---
+
+## Summary
+
+Describe the feature - a clear and concise description of what the feature is.
+
+## Background
+
+Provide context to the feature request - provide steps to indicate how this feature would be realized, such as:
+
+1. Go to '...'
+1. Click on '....'
+1. Scroll down to '....'
+1. See updated feature...
+
+## User Story
+
+A description from a user's perspective.
+
+For example:
+
+- As a project manager, I want to see the list of project sorted alphabetically when I select this button...
+
+## Assumptions
+
+If you are assuming certain facts or scenarios, list them so we have a baseline to understand your request.
+
+- [...] Assumption 1
+- [...] Assumption 2
+
+## Questions
+
+List any questions or clarifications that are needed to addressed to satisfy this request.
+
+1. [...] Question 1...
+1. [...] Question 2...
+
+## Acceptance Criteria
+
+The "done" criteria when this feature or problem is resolved. Such as:
+
+1. Unit Tests added and running in CI
+1. Functional Tests updated to cover feature, if applicable
+1. Demonstrate the set of capabilities to the product team while the code is running in the STAGING environment.
+
+## References
+
+\(Optional\) Provide any code or specification references that would be helpful for the developer implementing this feature.

.github/auto-merge.yml

@@ -0,0 +1,20 @@
+# Configuration for probot-auto-merge - https://github.com/bobvanderlinden/probot-auto-merge
+
+updateBranch: true
+deleteBranchAfterMerge: true
+reportStatus: true
+
+minApprovals:
+  COLLABORATOR: 1
+maxRequestedChanges:
+  NONE: 0
+blockingLabels:
+- blocked
+
+# Will merge whenever the above conditions are met, but also
+# the owner has approved or merge label was added.
+rules:
+- minApprovals:
+    CONTRIBUTOR: 1
+- requiredLabels:
+  - merge

LICENSE

@@ -1,21 +1,18 @@
-MIT License
+Copyright The Linux Foundation and each contributor to CommunityBridge.
 
-Copyright (c) 2020 CommunityBridge
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+the Software, and to permit persons to whom the Software is furnished to do so,
+subject to the following conditions:
 
 The above copyright notice and this permission notice shall be included in all
 copies or substantial portions of the Software.
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.