adds initial docs around funding and best practices #10
Conversation
This file contains 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
Signed-off-by: Nell Shamrell <nellshamrell@gmail.com>
Signed-off-by: Nell Shamrell <nellshamrell@gmail.com>
GabrielDosReis
approved these changes
Aug 10, 2023
| @@ -0,0 +1,10 @@ | |||
| # Best Practices - Non Memory-Safe By Default Languages | |||
|
|
|||
| This working group recommends switching to a memory-safe by default language whenever possible. However, when switching to a memory-safe by default language is not possible, there are developer practices that will improve memory safety, even if it is not the default. | |||
There was a problem hiding this comment.
suggestion: "whenever possible or practical"
Signed-off-by: Nell Shamrell <nellshamrell@gmail.com>
Signed-off-by: Nell Shamrell <nellshamrell@gmail.com>
balteravishay
approved these changes
Aug 10, 2023
| # Best Practices - Non Memory-Safe By Default Languages | ||
|
|
||
| This working group recommends switching to a memory-safe by default language whenever possible or practical. However, when switching to a memory-safe by default language is not possible or practical, there are developer practices that will improve memory safety, even if it is not the default. | ||
|
|
There was a problem hiding this comment.
should this also point to the BEST c/c++ hardening guide: https://github.com/ossf/wg-best-practices-os-developers/tree/main/docs/Compiler-Hardening-Guides
|
Suggest "This working group recommends using a memory-safe by default language whenever possible or practical." |
Signed-off-by: Nell Shamrell <nellshamrell@gmail.com>
|
Suggested edits have been made :) |
GabrielDosReis
approved these changes
Sep 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.