-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Jupyter Media Strategy Charter #181
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
# Jupyter Media Strategy Working Group | ||
|
||
## Purpose | ||
|
||
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 ](https://jupyter.org/governance/standing_committees_and_working_groups.html)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. | ||
|
||
|
||
# Editorial Principles | ||
|
||
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: | ||
|
||
1. Creation and implementation of Jupyter Media Strategy, associated processes and guidelines | ||
2. Editorial oversight of channels where Project Jupyter is the primary stakeholder and editor (such as the blog). | ||
3. Oversight and participation in channels that are community managed (such as a discussion forum). | ||
4. Approve, create, manage, and delegate all existing and new official Jupyter engagement channels (blog, discussion forum, social media etc) | ||
5. 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 . | ||
|
||
|
||
## Meetings | ||
|
||
1. The [Jupyter Decision-Making Guide](https://jupyter.org/governance/decision_making.html) will be used to make official decisions. | ||
2. The Jupyter Code of Conduct will be followed within this group. | ||
3. 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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -29,3 +29,7 @@ Charter Summary: License, protect, and promote the trademarks and visual and tex | |
### Jupyter Community Building | ||
|
||
[Charter](communitybuildingworkinggroup.md) Summary: Grow, build, and connect the global Jupyter community of users and contributors. | ||
|
||
### Jupyter Media Strategy | ||
|
||
[Charter][charters/MediaStrategyCharter.md] Summary: Ensure that communications in Jupyter official channels are strategic and benefit Project Jupyter. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Misc on the gist you post.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does that preclude a later group to engage with users and reply to their questions on non-prefered channel ? Even if it's replying "this channel is not used for support, please reach out via " which is technically a two way communication.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This relates only to official public-facing official Jupyter accounts. The user profile will make it clear that it is considered broadcast only. Individual users in the Jupyter community are still free to interact on these channels.