Improve Communication channels #114
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -144,6 +144,42 @@ vulnerabilities, etc.---> | |
|
|
||
| ### Communication Channels | ||
|
|
||
| #### Internal | ||
|
Member
There was a problem hiding this comment. We use the CNCF Slack workspace for internal communication and we have an internal Oversight Committee meeting every two weeks. |
||
|
|
||
| ##### Scheduled meetings | ||
|
Member
There was a problem hiding this comment. We can probably keep this a bit more generic so the exact information is not duplicated and doesn't get stale as quickly. A good example could be this self assessment. |
||
|
|
||
| Please attend! All are invited. | ||
|
|
||
| | | When | Where | | ||
| | -------- | ------- | -------- | | ||
| | **Global** | Every other Tuesday starting on April 23, 2024 · 11:00 – 12:00pm ET [convert to your local time.](https://mytime.io/11am/ET) | [Zoom](https://zoom-lfx.platform.linuxfoundation.org/meeting/91709345128?password=5510325d-895f-4932-a843-df728dc3028d) | | ||
| | **APAC friendly** | Every other following Thursday starting on November 30, 2024 - 05:00 GMT / 16:00 AEDT / 1030 IST [convert to your local time.](https://mytime.io/5am/GMT) |[Zoom](https://zoom-lfx.platform.linuxfoundation.org/meeting/97945872533?password=abad1bfe-cc9a-49d8-9aa6-99bb469a434d) | | ||
|
|
||
|
|
||
| Meeting agenda and notes [Google Docs](https://docs.google.com/document/d/1XTYM7xnWlIqd-8Nn5-qtgvgk8kH3NSmYle5yZvaS7qs/edit?usp=sharing) | ||
|
|
||
| We also have a [shared calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/trestlegrc?view=week). | ||
|
|
||
| #### Outbound | ||
|
|
||
| ##### Recordings | ||
|
|
||
| All of our meeting recordings are available for review on our YouTube [channel](https://www.youtube.com/@OSCAL-Compass). | ||
|
|
||
| #### Inbound | ||
|
|
||
|
|
||
| Google Group: [oscal-compass](https://groups.google.com/g/oscal-compass)\ | ||
| [email protected] | ||
|
|
||
| #### Chat anytime | ||
|
|
||
| Slack: [#oscal-compass-trestle-agileauthoring-c2p](https://cloud-native.slack.com/archives/C06F3PEPNBW) | ||
|
|
||
| - **Note**: You can login to Slack using another account like Google, Apple | ||
|
|
||
|
|
||
| <!--Reference where you document how to reach your team or | ||
| describe in corresponding section. | ||
| * Internal. How do team members communicate with each other? | ||
|
|
@@ -180,11 +216,12 @@ patching/update availability.---> | |
| record in catching issues in code review or automated testing.--> | ||
| ### [Open SSF Best Practices](https://www.bestpractices.dev/en) | ||
|
|
||
| OSCAL Compass is making great progress towards earning OpenSSF Best Practices badges across all repositories! | ||
| 🚀 The team has focused on the most mature components, and we are excited to share that Trestle has already met the passing level criteria! | ||
| ✅ We're on track to achieve full compliance soon! 🎯 | ||
|
|
||
| <!---* Case Studies. Provide context for reviewers by detailing 2-3 scenarios of | ||
| real-world use cases. | ||
| * Related Projects / Vendors. Reflect on times prospective users have asked | ||
| about the differences between your project and projectX. Reviewers will have | ||
| the same question.--> | ||
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.
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.
I think leaving the information in the README.md is important for discoverability even though the information will be duplicated somewhat.