87c2ec02e4
Since project is hosted on GitHub, it makes sense to first attempt to file issues there. Even ones that should be submitted as part of CVE process. This will help guide submitters to proper channels. Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: I1be5f8fb009ce06c71520675055801c392f3acfe Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1602 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
9 lines
343 B
YAML
9 lines
343 B
YAML
blank_issues_enabled: false
|
|
contact_links:
|
|
- name: SPDK Community
|
|
url: https://spdk.io/community/
|
|
about: Please ask and answer questions here.
|
|
- name: SPDK Common Vulnerabilities and Exposures (CVE) Process
|
|
url: https://spdk.io/cve_threat/
|
|
about: Please follow CVE process to responsibly disclose security vulnerabilities.
|