diff options
author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2019-04-17 17:57:35 +0000 |
---|---|---|
committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2019-04-17 17:57:35 +0000 |
commit | 3b95e5be69c199a2a195c57aba12d88c242225ac (patch) | |
tree | 137b72ffaefe7f34bf21e975ccc9cc9ec0474564 /.github | |
parent | Adding upstream version 1.13.0. (diff) | |
download | netdata-3b95e5be69c199a2a195c57aba12d88c242225ac.tar.xz netdata-3b95e5be69c199a2a195c57aba12d88c242225ac.zip |
Adding upstream version 1.14.0~rc0.upstream/1.14.0_rc0
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to '.github')
-rw-r--r-- | .github/CODEOWNERS | 4 | ||||
-rw-r--r-- | .github/ISSUE_TEMPLATE.md | 10 | ||||
-rw-r--r-- | .github/ISSUE_TEMPLATE/bug_report.md | 34 | ||||
-rw-r--r-- | .github/ISSUE_TEMPLATE/feature_request.md | 16 | ||||
-rw-r--r-- | .github/ISSUE_TEMPLATE/question.md | 25 | ||||
-rw-r--r-- | .github/PULL_REQUEST_TEMPLATE.md | 19 | ||||
-rw-r--r-- | .github/stale.yml | 19 |
7 files changed, 125 insertions, 2 deletions
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index 6345a7f04..b199780da 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -5,8 +5,8 @@ * @ktsaou # Ownership by directory structure -.travis/ @paufantom @cakrit -.github/ @paufantom @cakrit +.travis/ @paulkatsoulakis @cakrit +.github/ @paulkatsoulakis @cakrit backends/ @ktsaou @vlvkobal backends/graphite/ @ktsaou @vlvkobal backends/json/ @ktsaou @vlvkobal diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md new file mode 100644 index 000000000..4fe94ad65 --- /dev/null +++ b/.github/ISSUE_TEMPLATE.md @@ -0,0 +1,10 @@ +<!--- +This is a generic issue template. We usually prefer contributors to use one +of 3 other specific issue templates (bug report, feature request, question) +to allow our automation classify those so you can get response faster. +However if your issue doesn't fall into either one of those 3 categories +use this generic template. +---> + +#### Summary + diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md new file mode 100644 index 000000000..fbd69a2f6 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -0,0 +1,34 @@ +--- +name: Bug report +about: Create a bug report to help us improve + +--- + +<!--- +When creating a bug report please: +- Verify first that your issue is not already reported on GitHub +- Test if the latest release and master branch are affected too. +- Provide a clear and concise description of what the bug is in "Bug report + summary" section. +- Try to provide as much information about your environment (OS distribution, + running in container, etc.) as possible to allow us reproduce this bug faster. +- Write which component is affected. We group our components the same way our + code is structured so basically: + component name = dir in top level directory of repository +- Describe how you found this bug and how we can reproduce it. Preferable with + a minimal test-case scenario. You can paste gist.github.com links for larger + files +- Provide a clear and concise description of what you expected to happen. +--> + +##### Bug report summary + +##### OS / Environment + +##### Netdata version (ouput of `netdata -V`) + +##### Component Name + +##### Steps To Reproduce + +##### Expected behavior diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md new file mode 100644 index 000000000..b27ba2653 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -0,0 +1,16 @@ +--- +name: Feature request +about: Suggest an idea for our project + +--- + +<!--- +When creating a feature request please: +- Verify first that your issue is not already reported on GitHub +- Explain new feature briefly in "Feature idea summary" section +- Provide a clear and concise description of what you expect to happen. +---> + +##### Feature idea summary + +##### Expected behavior diff --git a/.github/ISSUE_TEMPLATE/question.md b/.github/ISSUE_TEMPLATE/question.md new file mode 100644 index 000000000..9bdf6f14e --- /dev/null +++ b/.github/ISSUE_TEMPLATE/question.md @@ -0,0 +1,25 @@ +--- +name: Question +about: You just want to ask a question? Go on. +--- + +<!--- +When asking a new question please: +- Verify first that your question wasn't asked before on GitHub. + HINT: Use label "question" when searching for such issues. +- Briefly explain what is the problem you are having +- Try to provide as much information about your environment (OS distribution, + running in container, etc.) as possible to allow us reproduce this bug faster. +- Write which component is affected. We group our components the same way our + code is structured so basically: + component name = dir in top level directory of repository +- Provide a clear and concise description of what you expected to happen. +--> + +##### Question summary + +##### OS / Environment + +##### Component Name + +##### Expected results diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md new file mode 100644 index 000000000..b4932f9c5 --- /dev/null +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -0,0 +1,19 @@ +<!-- +Describe the change in summary section, including rationale and degin decisions. +Include "Fixes #nnn" if you are fixing an existing issue. + +In "Component Name" section write which component is changed in this PR. This +will help us review your PR quicker. + +If you have more information you want to add, write them in "Additional +Information" section. This is usually used to help others understand your +motivation behind this change. A step-by-step reproduction of the problem is +helpful if there is no related issue. +--> + +##### Summary + +##### Component Name + +##### Additional Information + diff --git a/.github/stale.yml b/.github/stale.yml new file mode 100644 index 000000000..dfa5ce2c0 --- /dev/null +++ b/.github/stale.yml @@ -0,0 +1,19 @@ +--- +only: issues +limitPerRun: 30 +daysUntilStale: 45 +daysUntilClose: 60 +exemptLabels: + - bug + - help wanted + - feature request +exemptProjects: true +exemptMilestones: true +staleLabel: stale +markComment: > + Currently netdata team doesn't have enough capacity to work on this issue. + We will be more than glad to accept a pull request with a solution to problem described here. + This issue will be closed after another 60 days of inactivity. +closeComment: > + This issue has been automatically closed due to extended period of inactivity. + Please reopen if it is still valid. Thank you for your contributions. |