Self Assessment: Comm Channels #128
Conversation
Signed-off-by: Min Lu <[email protected]>
| | Communication Channel | Usage | | ||
| | ------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | [Slack](https://cloud-native.slack.com/archives/C06F3PEPNBW) | Real-time chats and team collaboration. | | ||
| | [Google Group](https://groups.google.com/g/oscal-compass) | Formal email communications. Address is [email protected]. | |
There was a problem hiding this comment.
I don't thing google groups is used to communicate internally between teams. This is more for public announcements.
| | [Meeting Agenda & Notes](https://docs.google.com/document/d/1XTYM7xnWlIqd-8Nn5-qtgvgk8kH3NSmYle5yZvaS7qs/edit?usp=sharing) | Shared notes and agendas for meetings. | | ||
| | [Shared Calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/trestlegrc?view=week) | Schedule of upcoming meetings and events. | | ||
| | [YouTube Channel](https://www.youtube.com/@OSCAL-Compass) | Provides users access to video recordings, tutorials, and meeting recordings. | | ||
|
|
There was a problem hiding this comment.
Youtube channel is also for public/user communication rather than internal communication.
| | [Slack](https://cloud-native.slack.com/archives/C06F3PEPNBW) | Public channel for quick user questions. | | ||
| | [Google Group](https://groups.google.com/g/oscal-compass) | Forum for user discussions and support. Address is [email protected]. | | ||
| | [GitHub Issues](https://github.com/oscal-compass/community/issues) | Enables users to report issues and request features. | | ||
| | [YouTube Channel](https://www.youtube.com/@OSCAL-Compass) | Provides users access to video recordings, tutorials, and meeting recordings. | |
There was a problem hiding this comment.
youtube is only for disseminating information to users. They cannot use it to communicate with the OSCAL-Compass team. It is not for inbound communication.
jpower432
left a comment
jpower432
left a comment
There was a problem hiding this comment.
Just leaving one comment with additional Slack channels to add to the feedback @vikas-agarwal76 provided.
|
|
||
| | Communication Channel | Usage | | ||
| | ------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | [Slack](https://cloud-native.slack.com/archives/C06F3PEPNBW) | Real-time chats and team collaboration. | |
There was a problem hiding this comment.
We have two private channels in CNCF Slack oscal-compass-maintainers and oscal-compass-oversight-committee for internal communication that could be listed in the description.
There was a problem hiding this comment.
Should I also add instructions on how to get invited to those private channels? I believe I only got invited by contacting Jeff at Georgia Tech's OSPO office, but it doesn't seem to be clear anywhere else how to be added to the private channels?
There was a problem hiding this comment.
@minlu21 Access to these channels is contributor role-based. Becoming a maintainer of an OSCAL Compass sub-project includes access to the oscal-compass-maintainers channel. The oscal-compass-oversight-committee channel is for OSCAL Compass Oversight Committee member communication.
These channels are primarily for private communications between maintainers for team logistics and potentially sensitive matters. The public channel is the default for communication. All community coordination, engagement, and decision-making is conducted in public channels or through GitHub Issues.
3 participants
No description provided.