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

create JupyterHealth team #755

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

create JupyterHealth team #755

wants to merge 1 commit into from

Conversation

minrk
Copy link
Member

@minrk minrk commented Jan 21, 2025

implementation of #752 which has more details on the proposal. Feel free to ask questions here or there if there are any questions or concerns with (or especially objections to!) the proposal.

If this is merged, I'll go ahead and add jupyterhealth to the Jupyter GitHub Enterprise and consider the process complete

Any more tasks to take?

@minrk
Copy link
Member Author

minrk commented Jan 22, 2025

Thanks for the approvals!

Following our consensus-seeking approach, I'll merge this with existing approvals after 2 weeks (February 4) unless anyone asks for changes or more time. I'd particularly like review from folks who asked questions in #752 (@choldgraf @manics) to make sure those questions really are addressed. I didn't put the check-in after a year suggestion in the docs, because I figure it can be more of an Issue than documentation.

@minrk
Copy link
Member Author

minrk commented Jan 22, 2025

I can do calendar math, I promise. I meant February 4, not January 28.

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