jupyter / jupyter/accessibility

Status change (approved) - follow up actions

Open
#100 2 comments 0 reactions 0 assignees View on GitHub
area: governance 🚀 status: work in progress 🏗 type: enhancement 💅🏼
Dominant language
Python
Stars
71
Forks
32
PR merge metrics
No merged PRs in 30d

Description

🎉 as y'all might have heard - this project is now officially a [Jupyter Software Subproject](https://jupyter.org/governance/software_subprojects.html) 🎉

However, we need to complete a few tasks to align ourselves with the requirements set by Jupyter governance.

TODO:

- [ ] [Decision making](https://jupyter.org/governance/decision_making.html)
- [ ] Establish an internal council (and decision-making processes)
- [ ] Document the above in this repository
- [x] Nominate a single representative to the SSC (though I think this is covered already by @isabela-pf, let me know if I am wrong)
- [ ] Update this repo to take the form of our team compass (see resources below)
- [x] Align with the licensing guidelines and practices of the Project Jupyter https://github.com/jupyter/accessibility/pull/101
- [x] Follow Jupyter’s trademark, branding, and intellectual property guidelines. (done - we do not modify the logo, and the one we use is fair use)


🔗 Relevant resources:

- [JupyterHub team compass](https://jupyterhub-team-compass.readthedocs.io/en/latest/)
- [Governance docs on SSC representation)(https://jupyter.org/governance/software_subprojects.html#ssc-representation)
- [useRknowledge base - proposed governance](https://gitlab.com/rconf/userknowledgebase/-/issues/78) based on the [scikit-learn governance model](https://scikit-learn.org/stable/governance.html)

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the Jupyter decision-making guidance, the JupyterHub team compass, and the linked governance resources. Done means establishing an internal council and decision-making process, documenting them in this repository, and updating the repository to follow the team compass format.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.