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.

Sign up for GitHub

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 a section to our README about async/sync style operations #16

Merged
merged 3 commits into from
Oct 23, 2023
Merged

Add a section to our README about async/sync style operations #16

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bd61ff1
(re)add a section to our README about async/sync style operations
Zsailer Oct 16, 2023
7496ca6
Remove unnecessary comma
Zsailer Oct 17, 2023
cb57b27
Fix comma space
Zsailer Oct 17, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,19 @@ the Jupyter Software Steering Council.

This repository is **NOT** for opening or discussing JEPs. This can be done in the [dedicated repository](https://github.com/jupyter/enhancement-proposals).

## How the Software Steering Council operates

The Software Steering Council (SSC) is an asynchronous-first council. We do our best not to _require_ synchronous meetings with the whole council since we span various timezones and aim to keep a robust record of all communications. To facilitate this style, we organize our work and track in-flight tasks using a [Github project board](https://github.com/orgs/jupyter/projects/10/views/1).

That said, we recognize that some "synchronous" time is beneficial to grow our relationships on the council and offer a place for the community to meet the council members.

Thus, we host a weekly, public "office hour" where available SSC members gather to review JEPs, refine process, and triage/organize tasks. No decisions should be made in these meetings; rather, it's a place to meet-and-greet, answer questions, and organize ourselves for the coming week.

Finally, we use two channels for all of our communication:
1. For private discussion, we use a google group, jupyter-software-steering-council@googlegroups.com
2. For public discussion, we use a [team-compass repository](https://github.com/jupyter/software-steering-council-team-compass) on Github.

Anyone is welcome to open an issue or email thread on these two channels to engage the SSC.

## Code of Conduct
As an official part of Project Jupyter, all communication across all
Expand Down