In the 2U Slack workspace, the connected channels to the Open edX Slack are (unfortunately) private and not easily discoverable without an explicit invite.
Why? The 2U InfoSec team is concerned about phishing attacks via the Open edX connected Slack channels.
Ideally, 2U staff would use the connected Paragon channel for any Paragon-related questions and/or announcements.
Why? Questions/answers/announcements posted in the connected Slack channel benefit both 2U and Open edX, rather than having to potentially duplicate messages across multiple Slack channels.
Today, we now have a 2U-specific #paragon-working-group channel and a private #openedx-wg-paragon channel.
[discuss] How can we make the private, connected channels like openedx-wg-paragon more discoverable/obvious so that they are used over 2U-specific channels?
E.g., as a new engineer who has a question about using a Paragon component and searches Slack for the appropriate channel to ask the question, how can we ensure they are aware of and choose to use the private connected channel instead?
Documentation about Slack makes sense to live in Slack.
Can we expose private shared WG channels from the open 2U-specific channel? E.g., channel topic, pinned message, etc.
Action items
Add action items to close the loop on open questions or discussion topics:
Decisions
Type /decision to record the decisions you make in this meeting:
Date