Skip to content

Commit 2cd9bc8

Browse files
MerrimanIndalexandruradoviciPLeVasseur
authored
Sc tool suggestion GitHub issue template (#337)
* Added submit tool GitHub issue template * Fixed typo * Added more text to intro section and changed heading title for submittor role * Update .github/ISSUE_TEMPLATE/submit_tool.yml Co-authored-by: Pete LeVasseur <plevasseur@gmail.com> * Update .github/ISSUE_TEMPLATE/submit_tool.yml Co-authored-by: Pete LeVasseur <plevasseur@gmail.com> --------- Co-authored-by: Alexandru Radovici <msg4alex@gmail.com> Co-authored-by: Pete LeVasseur <plevasseur@gmail.com>
1 parent bce675c commit 2cd9bc8

1 file changed

Lines changed: 61 additions & 0 deletions

File tree

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
name: Submit Safety Critical Tool
2+
description: Submit a safety-critical tool to the consortium
3+
title: Safety-Critical Tool Submission
4+
labels: ["submit tooling"]
5+
assignees:
6+
- joelmarcey, alexandruradovici
7+
body:
8+
- type: markdown
9+
attributes:
10+
value: |
11+
## Submit a Tool to the Consortium
12+
If you maintain, sell, or use a software tool that would be useful to the safety-critical Rust community we want to hear about it. This might include statis analysis, hardware deployment, compilers, or libraries/crates.
13+
14+
The consortium may publicize this tool on email publications, websites ([Are We Safety Critical Yet](www.arewesafetycriticalyet.com)), or at meetings. If we decide to move ahead with featuring the tool we will request more information about the specific uses of the tool as well as ask for a point-of-contact.
15+
16+
However, we may also deem the tool as not safety-critical, not mature enough (yet), or unmaintained and decline to publish it. In that case we would be happy to reconsider the tool in the future as it develops.
17+
- type: input
18+
id: tool_name
19+
attributes:
20+
label: What is the name of the tool?
21+
validations:
22+
required: true
23+
- type: textarea
24+
id: tool_description
25+
attributes:
26+
label: What is a description of the tool, what it does, how it would be used?
27+
validations:
28+
required: true
29+
- type: input
30+
id: tool_link
31+
attributes:
32+
label: Link to the tool repo or homepage
33+
validations:
34+
required: true
35+
- type: dropdown
36+
id: submitter_role
37+
attributes:
38+
label: What is your role/connection to this tool?
39+
description: What do you do for/with this tool
40+
options:
41+
- 'User or Customer'
42+
- 'Creator/Maintainer (open source)'
43+
- 'Product Manager/Owner (commercial)'
44+
- 'Other'
45+
validations:
46+
required: true
47+
- type: dropdown
48+
id: tool_type
49+
attributes:
50+
label: Tool category
51+
description: Specific use and type of this tool
52+
options:
53+
- "coverage"
54+
- "requirements-traceability"
55+
- "qualified-compiler"
56+
- "test-runner"
57+
- "formal-verification"
58+
- "static-analysis"
59+
- "tests-generation"
60+
validations:
61+
required: false

0 commit comments

Comments
 (0)