Skip to content

Commit

Permalink
Merge pull request #240 from jupyter/revert-239-update-charter
Browse files Browse the repository at this point in the history
Revert "Clarify social media posting guideline"
  • Loading branch information
jasongrout authored Oct 24, 2024
2 parents 8492818 + 91b2f59 commit a1118f2
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion charters/MediaStrategyCharter.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,8 @@ The JMS makes editorial decisions related to whether or not to accept/post conte
- Ensure that any third party content is beneficial to the Jupyter community.
- Content may be written in any language, provided it has been vetted by a member of the Jupyter Union of Councils.
- The Jupyter blog is the primary channel with which Jupyter communicates with the community.
- Social media channels will be used to amplify the reach of the blog and to share content that we deem should reach as large an audience as possible. The working group will designate a preferred channel that it determines best reflects the values of Project Jupyter. Posting on a particular platform is not an endorsement of that platform by Project Jupyter, but a means to communicate news to the Jupyter Community.
- Social media channels will be used to amplify the reach of the blog. Posting on a particular platform is not an endorsement of that platform by Project Jupyter, but a means to communicate news to the Jupyter Community. With the exception of our preferred channel, we will use these channels to broadcast messages only, and will therefore not engage in two-way communication with users on said channels.
- The working group will designate a preferred channel that it determines best reflects the values of Project Jupyter. This channel will be used for high bandwidth interactions such as event promotion and interacting with members of the community.

## Areas of responsibility

Expand Down

0 comments on commit a1118f2

Please sign in to comment.