...

• Ensure your communication answers the following questions:

  • Make sure all the details live in one place and all your announcements should link to that place.

    • Your details should have a summary that you can copy paste everywhere.

  • Be clear about where you want the discussion to happen.

    • For example, if you’re announcing in Slack and Discourse, but you want the discussion on the OEP pull request.

  • Is there a clear call-to-action? If so, what is it?

  • How does this impact the reader?

  • What are the “outcomes” that are planned/completed (as opposed to “activities” planned/completed)?

    • (Optionally) How will these outcomes be measured?

  • How/where can the reader follow-up with questions/feedback/etc?

Tips for tuning-in

...

In general, review the announcing table and configure notifications that work for you. This may include joining the listed Slack channels, or getting notified from GitHub or Discourse. See the following additional tips.

Notifications for Discourse Posts

• Click the relevant “Discourse Post” link from the announcement table that you wish to watch.

• Click the notification button with the bell icon, and choose “Watching First Post”, or your favorite option. This should watch an entire category of posts.

  • If you choose “Watching First Post”, and get notified about a post you want to continue to watch, us Visit Topic and again add a watch using the notification button with bell icon.

• Under Also, under email preferences (https://discuss.openedx.org/u/<username>/preferences/emails)

  • Choose “always” in place of “only when away” if you want more consistent email notifications.

ADR-ish notifications

There is a google group https://groups.google.com/g/adr-notifications that you can subscribe to to get emails from adr-notifications@googlegroups.com with notices about any doc related changes, like ADRs, OEPs, etc.

Times When This Table Was Not Helpful

...