-
Notifications
You must be signed in to change notification settings - Fork 28
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
Moved Wording from MEET3.1v0.1 Policy Statement to Rationale #126
Conversation
baselines/Google Meet Minimum Viable Secure Configuration Baseline v0.1.md
Outdated
Show resolved
Hide resolved
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.
Suggested one minor edit to ln 124. Otherwise LGTM.
…line v0.1.md Co-authored-by: Thomas Comeau (MITRE) <[email protected]>
@LaurenBassett Feel free to review. We can merge once we have concurrence from you and @buidav. |
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.
These request changes apply for Pull Requests #127, #128, #130, #133, #138, #140 as well.
- Follow the PR template directions for adding description, linking and closing issues etc. Adding in and filling out the PR template greatly helps the going back to read PRs in the future. Also, helps reviewers know what they are reviewing without having to dig too much for context. https://github.com/cisagov/ScubaGoggles/blob/main/.github/pull_request_template.md
- That goes for the titles as well.
Made the changes for issue 125, 126,
etc. are not informative titles. This hampers generating automatically generating release notes in the future. When auto generating the release notes GitHub pull takes directly from the Pull Request titles. First checkbox of the PR template.This PR has an informative and human-readable title.
https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
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.
One last thing for this PR before merging.
baselines/Google Meet Minimum Viable Secure Configuration Baseline v0.1.md
Outdated
Show resolved
Hide resolved
… Configuration Baseline v0.1.md Co-authored-by: David Bui <[email protected]>
🗣 Description
Moved "so that they are available by default when a host starts their meeting." from the MEET.3.1v0.1 policy statement to the rationale section in order to keep the policy statement concise.
Fixes #125