-
Notifications
You must be signed in to change notification settings - Fork 33
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
Status change (approved) - follow up actions #100
Comments
References #81 |
I have an update from the last JupyterLab accessibility call! As the wider Jupyter governance coalesces, we're trying to get the accessibility council established. BackgroundThe governance bootstrapping docs don't account for the fact that we became a software project later than some of the others and did not have existing steering council members to start our council process. We also need to have a council soon to nominate our representative to the new SSC soon. ApproachAs we discussed in the latest JupyterLab accessibility meeting, we're going to pull together a starter group based on recent interactions so that we can kickstart the council and start the nomination process as described in the previously mentioned docs. I'm going to be inviting people to this starter group based on
Keep in mind this group is not set and is open to further nominations after. This approach is intended to reflect recently active people as best and transparently as possible. Please let me know if you have any questions! |
🎉 as y'all might have heard - this project is now officially a Jupyter Software Subproject 🎉
However, we need to complete a few tasks to align ourselves with the requirements set by Jupyter governance.
TODO:
🔗 Relevant resources:
The text was updated successfully, but these errors were encountered: