-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make getting/staying involved in TIs easier #330
Comments
Thanks for linking #169 @sevansdell ! There's a lot of fantastic input in that issue that we can incorporate into the outcomes of this one. |
Seems related: #316 |
Will the architecture PR in security-baseline in some ways help with this issue? Plan to have another document on vulnerability management and incident response. had discussion with @sevansdell about the document location and review process #361 |
@Danajoyluck Good question! I don't think this issue is related to the security baseline or vuln management. This issue is about helping developers get involved and contributing to TIs, because it can be hard for contributors to know what are the open tasks or issues that a TI needs addressed in their code or spec. Practices like tagging issues as "Good first issue" are what's needed to address this issue. |
Several TIs have reported much lower participation than usual lately. While there are many external factors that are affecting participation at the moment, there's a general sense that there are several barriers to a sustained level of participation in TIs:
Some proposed ways to begin to lower these barriers:
These are comments/thoughts summarizing a discussion on the #tac Slack channel with @sevansdell @steiza @SecurityCRob and @mlieberman85 . Please add anything I might have missed from our original conversation, or any new concerns/ideas not mentioned yet.
The text was updated successfully, but these errors were encountered: