Add Jupyter Media Strategy Charter

[blink1073]

Questions to answer ❓

Background or context to help others understand the change.

We (@Ruv7 and @blink1073, as representatives of the EC), are proposing to create a Jupyter Media Strategy Working Group.
We have notionally formed a team along with @andrii-i and Jake Diamond-Reivich.

A draft of the new web page that is mentioned in the charter can be found in this gist, for context.

A brief summary of the change.

Add a charter and listed working group for Jupyter Media Strategy.

What is the reason for this change?

Addressing the overall media strategy of Jupyter, including which channels to use and how.

Related: #170, #146, #175

Alternatives to making this change and other considerations.

Continue to rely on the EC to make decisions regarding media strategy, with its limited bandwidth.

The process ❗

The process for changing the governance pages is as follows:

• Open a pull request in draft state. This triggers a discussion and iteration phase
  for your proposed changes.
• When you believe enough discussion has happened,
  move the pull request to an active state. This triggers a vote.
• During the voting phase, no substantive changes may be made to the pull request.
• The Executive Council and Software Steering Council will vote, and at the end of voting the pull request is merged or closed.

The discussion phase is meant to gather input and multiple perspectives from the community.
Make sure that the community has had an opportunity to weigh in on
the change before calling a vote. A good rule of thumb is to ask several Council
members if they believe that it is time for a vote, and to let at least one person review
the pull request for structural quality and typos.

Please vote by 25 October 2023.

Executive Council

• @afshin
  • Yes
  • No
  • Abstain
• @ellisonbg
  • Yes
  • No
  • Abstain
• @jasongrout
  • Yes
  • No
  • Abstain
• @fperez
  • Yes
  • No
  • Abstain
• @Ruv7
  • Yes
  • No
  • Abstain
• @blink1073
  • Yes
  • No
  • Abstain

[Carreau]

communications in Jupyter official

Nitpicking and It's obvious I think from the context, this is outward-facing channels, i.e we don't consider thigns like slack, or internal communicatino channels. I don't think this is needed, but you may want to clarify ?

[blink1073]

Thanks, we added "public" in front of media channels.

[Carreau]

we will use these channels to broadcast messages only, and will therefore not engage in two-way communication with users on said channels.

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.

[blink1073]

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.

[Carreau]

Misc on the gist you post.

1. I would be worry of a google group, it's one more channel to manage WRT credential and access, can this be a GH team and github discussion?
2. missing Twitter/@IPythonDev ? And we used to have IRC... should we try to re-get access, and jupytercon.slack.com as well.

[blink1073]

• We prefer the use of a Google Group for communication because it allows for us to have non-public conversations if needed before making it public, and it follows the pattern used by other working groups and subprojects.
• We added Twitter/@ipythondev, thanks!
• We have no intention of handling IRC on this group, and aren't aware of any existing accounts or who would have credentials.
• We have deferred considering Slack as a long term solution due to the cost. We may consider Discord or Zulip.

[westurner]

Is there another list of these in YAML somewhere?
https://gist.github.com/blink1073/ffb41d5dcfef410614c614e875c24934#social-media-accounts

# This is almost JSON-LD/YAML-LD (without @context/$context, @type/$type, @id/$id,)

- name: 
  url: 
- name:
  url:

  $type: https://schema.org/Thing
  $id: 

[westurner]

"Jupyter Media Strategy" jms_page.md https://gist.github.com/blink1073/ffb41d5dcfef410614c614e875c24934 :

Project Jupyter Media and Blog Post Request Form

Could be a heading with a permalink

• https://github.com/ml-tooling/best-of-jupyter
  • github-topics:
    • https://github.com/topics/jupyter
    • https://github.com/topics/jupyter-extension
    • https://github.com/topics/jupyter-kernels
    • https://github.com/topics/jupyter-notebook
    • https://github.com/topics/jupyter-notebook-extension
    • https://github.com/topics/jupyter-widget
    • https://github.com/topics/jupyterhub
    • https://github.com/topics/jupyterhub-authenticator
    • https://github.com/topics/jupyterhub-spawner
    • https://github.com/topics/jupyterlab
    • https://github.com/topics/jupyterlab-extension
    • https://github.com/topics/jupyterlab-extensions
    • https://github.com/topics/notebook
  • https://github.com/jupyter/jupyter/wiki#a-gallery-of-interesting-jupyter-notebooks
    • try to find this page with a search engine
  • https://github.com/search?q=language%3A"Jupyter+Notebook"&type=Repositories&ref=advsearch
    • type: Jupyter Notebook OR (e.g Python,)
• /? site:github.com inurl:awesome jupyter
  https://www.google.com/search?q=site%3Agithub.com+inurl%3Aawesome+jupyter
• https://github.com/quobit/awesome-python-in-education#jupyter

[blink1073]

cc @jupyter/executive-council @jupyter/software-steering-council

[andrii-i]

Also realted:

• New chat-based communication channel to replace Gitter/Matrix jupyterlab/frontends-team-compass#213

[rpwagner]

@blink1073 while this Working Group is forming and starting up, is there an interim mechanism to request something to be posted by Project Jupyter? Specifically, we would like to this blog post by Trusted CI about upcoming workshops announced and there's at least one blog post we intend to draft. Thanks

[Carreau]

@blink1073 while this Working Group is forming and starting up, is there an interim mechanism to request something to be posted by Project Jupyter? Specifically, we would like to this blog post by Trusted CI about upcoming workshops announced and there's at least one blog post we intend to draft. Thanks

I've send a reuquest to the email which is mentioned in the gist at the top of the page.

[andrii-i]

@rpwagner please send a request to [email protected] as @Carreau suggests

[blink1073]

It has been two weeks, I'm opening up the voting for this proposal.

[Carreau]

And thanks @blink1073 for promoting ! https://twitter.com/ProjectJupyter/status/1707108823524114627?s=20

[blink1073]

A point of clarification: since this is a Working Group and not a Standing Committee, only the EC are required to vote.

[Carreau]

A point of clarification: since this is a Working Group and not a Standing Committee, only the EC are required to vote.

I've requested review from all member of the EC except you as you are the OP I can't request your review. I'm guessing you can vote and check your own checkbox, and I'm guessing @Ruv7 will also approve.

[westurner]

A potential additional process for the Media Strategy:

• Create a PR to add at least the :name/:url pair to [the YAML file in which repo] and then update the Jupyter Media Strategy Charter, and then standard PR merge procedure
  • Add Jupyter Media Strategy Charter #181 (comment)

[krassowski]

Hi @Ruv7 @blink1073 @andrii-i I just wanted to confirm whether you saw my emails (we wanted to promote a call for JupyterLab 4.1 testing but ended up posting from private accounts). I asked about this yesterday during lab call where at least one JMS member was present but did not get a reply.

I am not asking specifically about lack of response to my emails (absolutely fine - I am not expecting a reply on such a short notice) but because I noticed that you are using "@googlegroups.com" email address which are notorious for (a) getting things flagged as spam when they are forwarded to private gmail mailboxes (b) prone to misconfiguration by not allowing external mails. I also noticed a public comment on your Medium post added yesterday from a Medium product manager saying that they tried to reach you out via email but did not get a reply (https://arielist.medium.com/hey-jupyter-friends-9c43088ffc45).

If there is indeed a technical issue rather than a bandwidth issue, did you consider using a Google form/GitHub issue template or similar for submissions? Do you have a team compass?

[blink1073]

Hi @krassowski, yes, we got your message and are waiting for one more person to weigh in to reach quorum on how to proceed. Dear all, please bear with us as we get up to speed with handling requests. 😄