Project Incubation: Jupyter FS - APPROVED

### Entry Path

Direct Entry (Advanced Contribution)

### Labs Compliance

- [x] I confirm that the codebase continues to meet [Labs Acceptance Requirements](https://community.finos.org/docs/governance/lifecycle-stages/labs/#labs-acceptance-requirements)
- [x] I confirm that the codebase meets [Labs Ongoing Maintenance Requirements](https://community.finos.org/docs/governance/lifecycle-stages/labs/#labs-ongoing-maintenance-requirements)

### Acceptance Checklist

- [x] At least two maintainers from different organizations (one must be a FINOS member)
- [x] Active use by at least two financial services organizations
- [x] At least one detailed end-user adoption story provided
- [x] Consistent adherence to the contribution workflow in CONTRIBUTING.md
- [x] Public roadmap/backlog with target outcomes and timelines is available

### Incubating Acceptance - Evidence

Maintainer list on PyPI: https://pypi.org/project/jupyter-fs/
Contributor history: https://github.com/jpmorganchase/jupyter-fs/graphs/contributors?all=1
Code of conduct: https://github.com/jpmorganchase/jupyter-fs?tab=coc-ov-file
End-user adoption story will be sent to TOC privately to avoid approvals for publishing.
The current backlog is the issue list: https://github.com/jpmorganchase/jupyter-fs/issues

### Maintenance & Health Commitment

- [x] The Project Team commits to public tracking of all activity using GitHub Issues
- [x] The Project Team commits to maintaining an up-to-date shortlist of 'Good First Issues' or 'Help Wanted'
- [x] The Project Team commits to replying to all community inquiries and issues with reasonable promptness
- [x] The Project Team commits to publicly visible adherence and updates to the project roadmap
- [x] The Project Team commits to pre-release integration with a FINOS-approved dependency and license scanner
- [x] The Project Team commits to build and release processes that use NO private or undocumented steps
- [x] The Project Team commits to presenting a project update once every six months at a public TOC meeting
- [x] The Project Team commits to adhering to Maturity Level 2 of the [OSPS Baseline](https://baseline.openssf.org/)

### Maintenance Readiness - Evidence

Most of these will be enforced/implemented on org/repo level once repository is transferred to Finos. Help wanted tag is already in use here: https://github.com/jpmorganchase/jupyter-fs/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22help%20wanted%22

### Status Badging

- [x] Project Team commits to adopt the [FINOS Incubating badge](https://community.finos.org/docs/governance/lifecycle-stages/incubating#badge) in the README.md once approved