-
Notifications
You must be signed in to change notification settings - Fork 18
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
Update SIG & Code of Contact Info #16
Conversation
original Issue: slsa-framework/slsa#453 Added 1.6. Special Interest Group Members to Governance.md Added Reporting Violations section with associated contacts to Code_of_Conduct.md Added 3 files for SIG charters as they stand today. Added Special Interest Groups section to Readme Updated Readme.md Related issues, PRs, docs: slsa-framework/slsa#384 https://github.com/slsa-framework/slsa-proposals/tree/main/0002 https://docs.google.com/document/d/1L1gEJMBIvE0IbpFi23FOUByDYlItSYPPJmKdhvJQYsg/edit#
Signed-off-by: Melba <[email protected]>
original Issue: slsa-framework/slsa#453 Added 1.6. Special Interest Group Members to Governance.md Added Reporting Violations section with associated contacts to Code_of_Conduct.md Added 3 files for SIG charters as they stand today. Added Special Interest Groups section to Readme Updated Readme.md Related issues, PRs, docs: slsa-framework/slsa#384 https://github.com/slsa-framework/slsa-proposals/tree/main/0002 https://docs.google.com/document/d/1L1gEJMBIvE0IbpFi23FOUByDYlItSYPPJmKdhvJQYsg/edit#
Co-Authored-By: Mark Lodato <[email protected]>
Sorry for the PR messyness @MarkLodato --- the "main" branch + gpg issues made me rename/get rid of gpg signing; will have to add ssh signing for future commits. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks again, Melba. It would be great to hear from other reviewers as well.
|
||
* [Joshua Lock](https://github.com/joshuagl) - VMware | ||
* [Melba Lopez](https://github.com/melba-lopez) - IBM | ||
* Or any [Steering Committee Member](README.md#steering-committee) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops, it's Readme.md
(not README.md
)
@@ -22,3 +22,27 @@ To contact the steering committee: | |||
|
|||
- On GitHub: `@slsa-framework/slsa-steering-committee` | |||
- Via email: [email protected] | |||
|
|||
## Special Interest Groups | |||
If you would like to participate in a SIG, come join a meeting or reach out directly via slack/email (see information below)! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: could you add blank lines here too? (After the heading and before each bulleted list?) That makes it easier to read in source form. Thanks!
## Mission | ||
|
||
* Educate the open source community, global industry, and standards/regulatory bodies on SLSA | ||
* Evangelize SLSA to increase adoption |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Copied from #15)
Can we use a more precise term than "adoption"? I interpret it as getting projects to actually do SLSA, which I think is more in scope for the future Adoption SIG. My understanding is that the Positioning SIG is more focused on higher-level recognition and recommendation by organizations, governments, and standards. Is that right?
If so, would it make sense to combine with the bullet above?
Educate and evangelize SLSA across the open source community, global industry, and standards/regulatory bodies
Same goes for the Vision. There, maybe just remove "adoption and" from the sentence?
|
||
## Values | ||
|
||
Please see [Code of Conduct](8._Code_of_Conduct.md)for more information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: missing space after )
Alternatively, should we just drop this section it will be the same in all three charters?
[Specification](9._SIG_Charter_-_Specification.md) | ||
- [Mark Lodato](https://github.com/MarkLodato) - Google | ||
- [Joshua Lock](https://github.com/joshuagl) - VMware | ||
- Via slack: [#slsa-specification](https://openssf.slack.com/archives/C03NUSAPKC6) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per slsa-framework/slsa#499, this link fails if the user does not already have an account. Unfortunately we need to write this out as #slsa-specification on https://slack.openssf.org
.
Same below.
Original PR: #15
original Issue: slsa-framework/slsa#453
Added 1.6. Special Interest Group Members to Governance.md
Added Reporting Violations section with associated contacts to Code_of_Conduct.md
Added 3 files for SIG charters as they stand today.
Added Special Interest Groups section to Readme
Updated Readme.md
Related issues, PRs, docs:
slsa-framework/slsa#384
https://github.com/slsa-framework/slsa-proposals/tree/main/0002
https://docs.google.com/document/d/1L1gEJMBIvE0IbpFi23FOUByDYlItSYPPJmKdhvJQYsg/edit#
@melba-lopez