Add Media Strategy content #748
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
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,43 @@ | ||
| --- | ||
| layout: page | ||
| title: Blog Guidelines | ||
| tagline: Project Jupyter is committed to having a community-led official blog. | ||
| permalink: /blog_guidelines | ||
| --- | ||
|
|
||
| ## Content Guidelines | ||
| The Project Jupyter blog is designed for community members to share valuable and educational content about Jupyter. Blog posts can be about various topics, for example how you got started with Jupyter, the latest extension you built around Jupyter, a quick tutorial on how to use a specific feature, and more. This channel is powered by our community members so there are no particular requirements for how the blog post has to be written. | ||
|
|
||
| Here is an example of a potential structure: | ||
|
|
||
| - Title | ||
| - Subtitle (max 140 characters) – summary of what the blog post is about | ||
| - Provide one image that represents your project - it can also be a code snippet | ||
| - Introduce your topic | ||
| - Why is this topic important? What are the benefits for the Jupyter community? | ||
| - Do you have an interesting user story or usage example? Include this here. | ||
| - Pick a specific usage example and provide a step-by-step guide so the readers can follow along. Make sure to include visuals or | ||
| code examples so readers can follow along easily. | ||
| - Thank/acknowledge the people who helped make the work described in the blog post possible. This includes anyone who helped you | ||
| write the blog post itself. | ||
| - End the article with the forward-looking statement about your project or research | ||
|
|
||
| Blog Post Examples: | ||
| - Shorter post: European Commission Funds Jupyter Bug Bounty Program | ||
| - Longer post: Generative AI in Jupyter | ||
| - Post using the Jupyter Voice: JupyterLab is Ready for Users | ||
|
|
||
| ## Submission Process | ||
| - *Create a Medium account*. If you are new to Medium, create an account by following these instructions. | ||
| - *Request permissions*. Email the Jupyter Media Strategy working group (JMS) at jupyter-media-strategy at googlegroups dot com to have your Medium account to be added as the writer of the blog. Once you are added as the authorized writer, you should receive an email that allows you to upload your blog. | ||
|
There was a problem hiding this comment. That won't work in the long run, I believe we are already at the maximum number of writer. There was a problem hiding this comment. As far as I can tell, there is no limit on the number of writers. The number of editors will be reduced as part of this effort. If we do hit the limit on the number of writers, we'll have to start removing inactive writers, who can also be re-added through the submission process. |
||
| - *Submit your story*. For step by step instructions see the following Medium article. | ||
| - *Request review*. Email the JMS at jupyter-media-strategy at googlegroups dot com confirming you have submitted the story. and provide suggested social media text and image. | ||
|
|
||
| ## Social media amplification of blog post | ||
| If you would like to have a post about your work on Project Jupyter social media [LINK to the list of the official Jupyter social media], please provide the following: | ||
| - Post content (500 characters maximum) | ||
| - Github link (this will auto-generate an image) | ||
| - Or an image to use | ||
| - Social handles to include | ||
|
|
||
| Please note that we will vet this content against our current editorial review backlog, and follow up with you if there are any issues. | ||
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,29 @@ | ||
| --- | ||
| layout: page | ||
| title: Media Strategy | ||
| tagline: Project Jupyter is committed to ensuring communication in Jupyter's official channels is strategic and benefit Project Jupyter. | ||
| permalink: /news | ||
| --- | ||
|
|
||
| The Jupyter Media Strategy Working Group (JMS) exists to ensure that communications in Jupyter official channels are strategic and benefit Project Jupyter. | ||
|
|
||
| ## Jupyter Blog | ||
| The Jupyter blog (blog.jupyter.org) is designed for community members to share valuable, educational content, including news and tutorials, about Jupyter. Please see the Jupyter Blog Submission [Guidelines](./blog_guidelines) for details on creating a post. | ||
|
|
||
| ## Jupyter Discourse Forum | ||
| The Discourse forum (discourse.jupyter.org) is meant to be a welcoming place for discussion about Project Jupyter. Members are encouraged to ask and answer questions, and highlight wins. If you are interested to be a part of the Jupyter Discourse moderation team, please reach out to us at jupyter-media-strategy at googlegroups dot com. | ||
|
|
||
| ## Social Media Accounts | ||
| The JMS maintains a list of official Project Jupyter social media accounts to support and promote our organization's interests. We primarily use our Mastodon account for interactive social media engagement, but will also broadcast messages about the blog or Jupyter events on other channels. | ||
|
|
||
| If you are organizing a Jupyter event or have something Jupyter-related that should be boosted by the official Jupyter account, please reach out to us at jupyter-media-strategy at @googlegroups dot com. | ||
|
There was a problem hiding this comment. Obfuscating email addresses is not really necessary anymore. A sophisticated address harvesting bot's author has had 25 years to code that "foo at bar dot com" is an email address. Google Groups has spam filtering and moderation to keep spam out, when properly configured. It might be good to go beyond "please reach out to us". When should I reach out to JMS — how far in advance of the event? What should I include in the message? Should I draft a post or just ask if you can promote it? There was a problem hiding this comment. Thanks! We're going to add specific info to this PR about social media posts during our next meeting. |
||
|
|
||
| List of channels maintained by JMS in alphabetical order: | ||
| - Facebook: facebook.com/projectjupyter | ||
| - LinkedIn: linkedin.com/company/project-jupyter | ||
| - Mastodon: https://hachyderm.io/@ProjectJupyter | ||
| - Slack JupyterCon 2023: jupyterconworkspace.slack.com | ||
| - Slack JupyterLab: jupyterlabworkspace.slack.com | ||
| - X/Twitter Jupyter: twitter.com/ProjectJupyter | ||
| - X/Twitter JupyterCon: twitter.com/JupyterCon | ||
| - YouTube: youtube.com/@ipython | ||
|
There was a problem hiding this comment. Most of these are missing https:// We shouldn't be promoting the Slack JupyterCon 2023 or JupyterCon accounts until we have an upcoming conference to promote. If you want these to be in here for historical reasons, they should be in a section of their own. |
||
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.
These should be links to posts.
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.
👍🏼