-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Define methods and processes for communicating with all Service Providers #118
Comments
Eden - What other channels should we be using? |
@e0d - Would love your feedback on blog text, link above. |
Reviewed the blog, it looks great, just had a couple minor comments in the doc. |
@jmakowski1123 I can circulate the links on all of our social media channels (FB, Twitter, and LinkedIn). We can also leverage discourse, and an SF email marketing campaign. Additionally, there are several Slack channels you can circulate the link to: #general, #core-contributors, #frontend-working-group, #wg-build-test-release, (https://openedx.slack.com/archives/C02BMP2RD5Y), [#marketing] |
3/8 - done:
|
|
To do by end of week 3/11: -Jenna to reach out 1:1 to 15 providers |
I've shared the request with the TOC. |
We need to identify all public channels of communication for circulating links to the Survey with a Call To Action to complete by March 18.
As a starting point, here is draft text for a blog post: https://docs.google.com/document/d/1p_qAd_113rtKvHtJfepgMlPpGiwLCDW-L4dlS2a3O_M/edit
The text was updated successfully, but these errors were encountered: