Skip to content
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 e-mails for SSC and EC #222

Merged
merged 4 commits into from
May 22, 2024
Merged

Add e-mails for SSC and EC #222

merged 4 commits into from
May 22, 2024

Conversation

choldgraf
Copy link
Contributor

In a recent round of communication with the SSC, I couldn't find the listserv e-mail for the group. This adds brief information for how to get in touch with the SSC and the EC so that others aren't confused like I was.

@Ruv7
Copy link
Contributor

Ruv7 commented May 20, 2024

Hi Chris - I'm not familiar enough with GH to click about on this issue and figure out the exact spot where you're proposing to include this contact info but I would advise the thing to include would be a link pointing to the EC Team Compass which includes various ways to communicate with the EC including the EC email. https://executive-council-team-compass.readthedocs.io/en/latest/#contacting-the-executive-council

@jasongrout
Copy link
Member

FYI, for the EC, we already have a section on the team compass and it specifically mentions how to contact the EC:

The Executive Council Team Compass publishes information about the activities and operations of the EC, including how to contact the EC.

@choldgraf
Copy link
Contributor Author

Hmm - I'll just give you my perspective as an uninformed user of these docs:

  • the executive council page has a lot of information on it, and it's easy to miss things + kind of overwhelming.
  • so I searched for the words "email" and "listserv" and didn't see them
  • so I concluded the information was not there.

I'd recommend putting a bit button at the top of that page like "for general information about the executive council go to the team compass" rather than nesting it in a subsection. Would that be acceptable for folks?

@jasongrout
Copy link
Member

I'd recommend putting a bit button at the top of that page like "for general information about the executive council go to the team compass" rather than nesting it in a subsection. Would that be acceptable for folks?

Yes, putting the team compass link at the very top sounds great! We already have a note at the top that points to the list of EC members. How about moving that team compass sentence (or something similar) up to the top as the very first sentence, even before the pointer to the list of people?

There's nothing like debugging existing docs by having people try to use them to solve problems. Thanks for coming back and making things better for the next person!

@choldgraf
Copy link
Contributor Author

OK the latest push makes the EC docs a button. I didn't find any team compass information for the SSC so I left it as-is.

Here's what it looks like:

CleanShot 2024-05-20 at 15 48 12@2x

There's nothing like debugging existing docs by having people try to use them to solve problems. Thanks for coming back and making things better for the next person!

This describes like 90% of my contributions to the Jupyter project 😅

@jasongrout
Copy link
Member

Pinging @jupyter/software-steering-council for their approval

@jasongrout jasongrout merged commit d5a7907 into jupyter:main May 22, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants