From eaec5a35dc3382c4655957a3dca0caca188533d4 Mon Sep 17 00:00:00 2001 From: George Joseph Date: Fri, 28 Apr 2023 11:17:21 -0600 Subject: [PATCH] Initial GitHub Issue Templates --- .github/ISSUE_TEMPLATE/bug-report.yml | 85 ++++++++++++++++++++++++++ .github/ISSUE_TEMPLATE/config.yml | 5 ++ .github/ISSUE_TEMPLATE/improvement.yml | 24 ++++++++ .github/ISSUE_TEMPLATE/new-feature.yml | 24 ++++++++ .github/workflows/IssueOpened.yml | 15 +++++ SECURITY.md | 9 +++ 6 files changed, 162 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml create mode 100644 .github/ISSUE_TEMPLATE/config.yml create mode 100644 .github/ISSUE_TEMPLATE/improvement.yml create mode 100644 .github/ISSUE_TEMPLATE/new-feature.yml create mode 100644 .github/workflows/IssueOpened.yml create mode 100644 SECURITY.md diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml new file mode 100644 index 0000000000..a8e968fd34 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug-report.yml @@ -0,0 +1,85 @@ +name: Bug +description: File a bug report +title: "[Bug]: " +labels: ["Bug", "triage"] +#assignees: +# - octocat +body: + - type: markdown + attributes: + value: | + Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. + + A good first step is for you to review the Asterisk Issue Guidelines if you haven't already. The guidelines detail what is expected from an Asterisk issue report. + + Then, if you are submitting a patch, please review the Patch Contribution Process. + + Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. + + Please note that by submitting data, code, or documentation to Sangoma through GitHub, you accept the Terms of Use present at + https://www.asterisk.org/terms-of-use/. + Thanks for taking the time to fill out this bug report! + - type: dropdown + id: severity + attributes: + label: Severity + options: + - Trivial + - Minor + - Major + - Critical + - Blocker + validations: + required: true + - type: input + id: versions + attributes: + label: Versions + description: Enter one or more versions separated by commas. + validations: + required: true + - type: input + id: components + attributes: + label: Components/Modules + description: Enter one or more components or modules separated by commas. + validations: + required: true + - type: textarea + id: environment + attributes: + label: Operating Environment + description: OS, Disribution, Version, etc. + validations: + required: true + - type: dropdown + id: frequency + attributes: + label: Frequency of Occurrence + options: + - "Never" + - "One Time" + - "Occasional" + - "Frequent" + - "Constant" + - type: textarea + id: description + attributes: + label: Issue Description + - type: textarea + id: logs + attributes: + label: Relevant log output + description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks. + render: shell + - type: markdown + attributes: + value: | + [Asterisk Issue Guidelines](https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines) + - type: checkboxes + id: guidelines + attributes: + label: Asterisk Issue Guidelines + options: + - label: Yes, I have read the Asterisk Issue Guidelines + required: true diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml new file mode 100644 index 0000000000..ce54a75bf4 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -0,0 +1,5 @@ +blank_issues_enabled: false +contact_links: + - name: Asterisk Community Support + url: https://community.asterisk.org + about: Please ask and answer questions here. diff --git a/.github/ISSUE_TEMPLATE/improvement.yml b/.github/ISSUE_TEMPLATE/improvement.yml new file mode 100644 index 0000000000..7243499be2 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/improvement.yml @@ -0,0 +1,24 @@ +name: Improvement +description: Request an improvement to existing functionality +title: "[Improvement]: " +labels: ["Improvement", "triage"] +body: + - type: markdown + attributes: + value: | + Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. + + A good first step is for you to review the Asterisk Issue Guidelines if you haven't already. The guidelines detail what is expected from an Asterisk issue report. + + Then, if you are submitting a patch, please review the Patch Contribution Process. + + Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. + + Please note that by submitting data, code, or documentation to Sangoma through GitHub, you accept the Terms of Use present at + https://www.asterisk.org/terms-of-use/. + Thanks for taking the time to fill out this bug report! + - type: textarea + id: description + attributes: + label: Improvement Description + description: Describe the improvement requested in as much detail as possible diff --git a/.github/ISSUE_TEMPLATE/new-feature.yml b/.github/ISSUE_TEMPLATE/new-feature.yml new file mode 100644 index 0000000000..2e475d286e --- /dev/null +++ b/.github/ISSUE_TEMPLATE/new-feature.yml @@ -0,0 +1,24 @@ +name: New Feature +description: Request a New Feature +title: "[New Feature]: " +labels: ["New Feature", "triage"] +body: + - type: markdown + attributes: + value: | + Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. + + A good first step is for you to review the Asterisk Issue Guidelines if you haven't already. The guidelines detail what is expected from an Asterisk issue report. + + Then, if you are submitting a patch, please review the Patch Contribution Process. + + Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. + + Please note that by submitting data, code, or documentation to Sangoma through GitHub, you accept the Terms of Use present at + https://www.asterisk.org/terms-of-use/. + Thanks for taking the time to fill out this bug report! + - type: textarea + id: description + attributes: + label: Feature Description + description: Describe the new feature requested in as much detail as possible diff --git a/.github/workflows/IssueOpened.yml b/.github/workflows/IssueOpened.yml new file mode 100644 index 0000000000..74cef00b4d --- /dev/null +++ b/.github/workflows/IssueOpened.yml @@ -0,0 +1,15 @@ +name: Issue Opened +run-name: "Issue ${{github.event.number}} ${{github.event.action}} by ${{github.actor}}" +on: + issues: + types: opened + +jobs: + triage: + runs-on: ubuntu-latest + steps: + - name: initial labeling + uses: andymckay/labeler@master + with: + add-labels: "triage" + ignore-if-labeled: true diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000000..5386952efc --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,9 @@ +# Security Policy + +## Supported Versions + +The Asterisk project maintains a [wiki page](https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions) of releases. Each version is listed with its release date, security fix only date, and end of life date. Consult this wiki page to see if the version of Asterisk you are reporting a security vulnerability against is still supported. + +## Reporting a Vulnerability + +To report a vulnerability use the "Report a vulnerability" button under the "Security" tab of this project.