That pretty much sounds like... everything! Like most things in open source, new code/docs/service get to users of Jupyter when:
- someone has an itch to scratch (might be a person, company, or bot)
- someone can do the work to scratch it (maybe the first someone, maybe someone else)
- someone reviews the work (usually, initially by a bot, but then a person)
- someone merges the work (maybe the reviewer, maybe someone else)
- someone cuts a release containing the new work (sometimes a person, sometimes a bot)
Concretely, as most development on Jupyter happens on GitHub, you can take your pick of "good first issue" issues on the respective repositories. Here's a random smattering of repos:
-
https://github.com/jupyter/notebook/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22
If none of those sound interesting, you may wish to watch/star some repos and and start watching the issues that crop up, and see if something takes your fancy. Ocotobox.io is very handy for this, as you can search across many repos.
Once you find a thing you want to work on, It's "good form" to announce that you intend to work on an issue, but few projects will turn down good code on a drive-by PR if is:
- fixing a known issue
- small
- well-written
- tested
- documented
in roughly that order of importance.