JupyterHealth update #807
Description
checking in here on the JupyterHealth activity (sub-subproject?). We’re a bit less than a year since the proposed check-in in #752, but I think now is a good time for some updates.
We’ve done some development, including quite a bit of work especially by TCP on the JupyterHealth Exchange and now starting a new Sync project. These currently reside under TCP, but we plan to bring them under the JupyterHealth org for some clearer boundaries around the project.
We are working this fall to build capacity for more open community process, and plan to do a kind of launch at JupyterCon in November to signal that we’re really ready for folks to participate.
Key activities in the near term:
- improve community-facing documentation, contributor resources
- start holding open community meetings
- bringing Exchange, Sync (projects in development with the JupyterHealth name on them) under the JupyterHealth org
- public launch at JupyterCon
One thing that has updated in how we see the future is promoting JupyterHealth to a full Jupyter subproject (out of JupyterHub), so treating this time under JupyterHub as a kind of incubation process. We aren’t ready for that yet (maybe next year?), but we are trying to structure things with that in mind. While we are under JupyterHub, everything remains subordinate to JupyterHub of course, but it would be good to have the structure in place to be able to move to an independent subproject in the future more seamlessly. That means setting up things like a team compass, etc. That would mean the JupyterHealth team on the JupyterHub council would be ‘representatives’ on JupyterHub itself, while we could add more folks working on JupyterHealth without needing to add them here.
Does that sound like a reasonable path forward for other JupyterHub folks? Any questions or suggestions from the JupyterHub team?