Jupyter Media Strategy Working Group#
The mission of the Jupyter Media Strategy Working Group (JMS) is to ensure that communications in Jupyter official channels are strategic and benefit Project Jupyter. The Jupyter governance model includes a distributed model of responsibilities. This means that by design Jupyter publications, social media posts, promotions and other media activity are meant to be community driven. The JMS is vendor neutral and will provide mechanisms to enable the community to speak publicly through the official Jupyter communication channels. The JMS will also help to improve Jupyter media activity by creating strategy and guidelines, serving as editors for existing public media channels, and overseeing creation/delegation of new media channels.
The JMS makes editorial decisions related to whether or not to accept/post content on our official channels based on the following principles:
Prioritize content about the work of Project Jupyter and its subprojects and is beneficial to the Jupyter community.
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. 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#
This Working Group is responsible for two types of communication channels (e.g., blog, social media accounts, discussion forums, etc.). The list of official Jupyter communication channels is maintained separately here [link] by this Working Group and is intentionally not included as part of the group’s charter to allow operational flexibility. Areas of responsibility for the JMS include:
Creation and implementation of Jupyter Media Strategy, associated processes and guidelines
Editorial oversight of channels where Project Jupyter is the primary stakeholder and editor (such as the blog).
Oversight and participation in channels that are community managed (such as a discussion forum).
Approve, create, manage, and delegate all existing and new official Jupyter engagement channels (blog, discussion forum, social media etc)
Manage all access and permissions to new official Jupyter engagement channels (blog, discussion forum, social media etc)
The focus of the JMS is to provide editorial guidance and oversight in these channels. This working group may create content and publicly use the official Jupyter voice (using Project Jupyter persona or speaking on behalf of Project Jupyter).
Media Strategy Operations#
The JMS will create and maintain a media strategy page on the Jupyter website that shares guidance for how the Jupyter voice is managed. Jupyter subprojects, working groups, standing committees and their communities are encouraged to actively build awareness of themselves and their activities through emails, blog posts, social media posts, and other means of outreach using the processes and guidelines as outlined on a media strategy page on the Jupyter.org .
The Jupyter Decision-Making Guide will be used to make official decisions.
The Jupyter Code of Conduct will be followed within this group.
To ensure active participation, a member who is unable to join for more than two thirds of regularly scheduled bi-weekly meetings in a 90 day period may be asked to step down from the committee.