From bd61ff1aaecfe115894d9d7ff2dc959da0837dac Mon Sep 17 00:00:00 2001 From: Zach Sailer Date: Mon, 16 Oct 2023 13:25:32 -0700 Subject: [PATCH 1/3] (re)add a section to our README about async/sync style operations --- README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/README.md b/README.md index 8788c78..ccc95c3 100644 --- a/README.md +++ b/README.md @@ -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 From 7496ca69e86d59e8624150c732f5e1252c291565 Mon Sep 17 00:00:00 2001 From: Zachary Sailer Date: Tue, 17 Oct 2023 09:48:36 -0700 Subject: [PATCH 2/3] Remove unnecessary comma --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ccc95c3..47b60cc 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ This repository is **NOT** for opening or discussing JEPs. This can be done in t ## 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). +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. From cb57b27a9c111e38180b1e32bdef33ae639d90f3 Mon Sep 17 00:00:00 2001 From: Zachary Sailer Date: Tue, 17 Oct 2023 09:48:47 -0700 Subject: [PATCH 3/3] Fix comma space --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 47b60cc..9760fd6 100644 --- a/README.md +++ b/README.md @@ -12,7 +12,7 @@ That said, we recognize that some "synchronous" time is beneficial to grow our r 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: +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.