Tooling request issue template #336
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for safety-critical-rust-consortium canceled.
|
|
Note that this PR contains a lot of small commits because the only way to properly preview a GitHub issue template is on GitHub itself, necessitating lots of commits and pushes. A semi-rendered version of this template can be viewed here: |
PLeVasseur
approved these changes
Jun 7, 2025
There was a problem hiding this comment.
Seems like a good start to me @MerrimanInd! I'm in favor of merging and then we can try it out a little to see how we fell.
cc @alexandruradovici -- what do you think?
|
Looks good too see, do you think we should put this on the agenda for Friday and merge it afterwards? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an idea I had while sitting at the meeting in Utrecht. A member had mentioned that they were limited by a very specific and comparatively minor limitation with current Rust tooling, specifically that when their Rust code is passing all clippy lints there's no documentation generated of the code compliance to feed into the internal or external audit process. This seemed like a pretty minor issue to bring to the cargo/clippy teams now that it was identified.
This GitHub issue template is an attempt at capturing issues that safety-critical Rust users are finding with their tooling. The consortium can then bring these issues to the correct stakeholder. For example, issues with Rust projects (cargo, clippy, rustc, etc) can be brought directly to the maintainers. Issues that can be solved by commercial software companies working in the space can be broadcast within the consortium member companies. And lastly, issues that could be solved by the open-source community could be advertised across Rust channels.
This will likely be discussed at an upcoming Tooling Subcommittee meeting (attn @alexandruradovici) but this draft PR is to get some visibility and discussion going.