add license infos and more (#503)

Author: gzussa

.github/CODEOWNERS

@@ -3,7 +3,8 @@
 # and another team can own the rest of the directory.
 
 # All your base
-*                   @DataDog/integrations-tools-and-libraries
+*                       @DataDog/integrations-tools-and-libraries
 
 # Documentation
-*.md                @DataDog/baklava
+*.md                    @DataDog/baklava @DataDog/integrations-tools-and-libraries
+LICENSE                 @DataDog/baklava @DataDog/integrations-tools-and-libraries

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,36 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: 'kind/bug'
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+Label the issue properly.
+- Add `severity/` label.
+- Add `documentation` label if this issue is related to documentation changes.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. 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 and Versions (please complete the following information):**
+A clear and precise description of your setup:
+  - version for this project in use.
+  - services, libraries, languages and tools list and versions. 
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,23 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: 'kind/feature-request'
+assignees: ''
+
+---
+
+**Note:** 
+If you have a feature request, you should [contact support](https://docs.datadoghq.com/help/) so the request can be properly tracked.
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is.
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,77 @@
+### Requirements for Contributing to this repository
+
+* Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
+* The pull request must only fix one issue, or add one feature, at the time.
+* The pull request must update the test suite to demonstrate the changed functionality.
+* After you create the pull request, all status checks must be pass before a maintainer reviews your contribution. For more details, please see [CONTRIBUTING](/CONTRIBUTING.md). 
+
+### What does this PR do?
+
+<!-- 
+
+What inspired you to submit this pull request?
+Link to the issue describing the bug that you're fixing.
+
+If there is not yet an issue for your bug, please open a new issue and then link to that issue in your pull request.
+Note: In some cases, one person's "bug" is another person's "feature." If the pull request does not address an existing issue with the "bug" label, the maintainers have the final say on whether the current behavior is a bug.
+
+-->
+
+### Description of the Change
+
+<!--
+
+A brief description of the change being made with this pull request. 
+
+We must be able to understand the design of your change from this description. 
+If we can't get a good idea of what the code will be doing from the description here, the pull request may be closed at the maintainers' discretion. 
+Keep in mind that the maintainer reviewing this PR may not be familiar with or have worked with the code here recently, so please walk us through the concepts.
+
+-->
+
+### Alternate Designs
+
+<!-- Explain what other alternates were considered and why the proposed version was selected -->
+
+### Possible Drawbacks
+
+<!-- What are the possible side-effects or negative impacts of the code change? -->
+
+### Verification Process
+
+<!--
+
+What process did you follow to verify that your change has the desired effects?
+
+- How did you verify that all new functionality works as expected?
+- How did you verify that all changed functionality works as expected?
+- How did you verify that the change has not introduced any regressions?
+
+Describe the actions you performed (including scripts, commands you ran, etc.), and describe the results you observed.
+
+-->
+
+### Additional Notes
+
+<!-- Anything else we should know when reviewing? -->
+
+### Release Notes
+
+<!--
+
+If the PR title is not enough to describe the changes in a single line that explains this improvement in
+terms that a user can understand. This text will be added in release notes.
+
+For example, you can provide additionnal notes about feature deprecation or backward incompatible changes.
+
+-->
+
+### Review checklist (to be filled by reviewers)
+
+- [ ] Feature or bug fix MUST have appropriate tests (unit, integration, etc...)
+- [ ] PR title must be written as a CHANGELOG entry [(see why)](/CONTRIBUTING.md#pull-request-title)
+- [ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
+- [ ] PR must have one `changelog/` label attached. If applicable it should have the `backward-incompatible` label attached.
+- [ ] PR should not have `do-not-merge/` label attached.
+- [ ] If Applicable, issue must have `kind/` and `severity/` labels attached at least.
+

.github/labeler.yml

@@ -0,0 +1,3 @@
+# Configuration for labeler - https://github.com/actions/labeler
+
+documentation: "**/*.md"

.github/workflows/labeler.yml

@@ -0,0 +1,11 @@
+name: "Pull Request Labeler"
+on:
+- pull_request
+
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: DataDog/labeler@glob-all
+      with:
+        repo-token: "${{ secrets.GITHUB_TOKEN }}"

.github/workflows/stale.yml

@@ -0,0 +1,38 @@
+# Configuration for https://github.com/actions/stale
+
+name: "Stale issues and pull requests"
+on:
+  schedule:
+  - cron: "0 0 * * *"
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/stale@v1
+      with:
+        repo-token: ${{ secrets.GITHUB_TOKEN }}
+        stale-issue-message: >-
+          Thanks for your contribution!
+
+
+          This issue has been automatically marked as stale because it has not had
+          activity in the last 30 days. Note that the issue will not be automatically
+          closed, but this notification will remind us to investigate why there's
+          been inactivity. Thank you for participating in the Datadog open source community.
+
+
+          If you would like this issue to remain open:
+
+            1. Verify that you can still reproduce the issue in the latest version of this project.
+
+            1. Comment that the issue is still reproducible and include updated details requested in the issue template.
+        days-before-stale: 30
+        stale-issue-label: 'stale'
+        exempt-issue-label: 'stale/exempt'
+        stale-pr-message: >-
+          This issue has been automatically marked as stale because it has not had activity in the last 30 days.
+
+          Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity.
+        stale-pr-label: 'stale'
+        exempt-pr-label: 'stale/exempt'