I was going through the repos in https://github.com/jupyter looking for “good first issue”, check this query for details. There are 72 repos with 41 open issues in total.
Where should I start from? Familiarity with both repository and programming language could be a good lead right?
The Contributor Guides says to get in touch with the community. We could add a line there pointing newcomers to “good first issue”. Also what about submitting repos to https://www.codetriage.com?
It would be great to improve some of those getting started pages! We just recently added one for jupyterhub (https://jupyterhub-team-compass.readthedocs.io/en/latest/contributing.html) but would love to think about ways to improve this kind of thing for the whole project!
The method I used back in the day to figure out where to start contributing was that I wanted to use JupyterHub for an event and got interested in it. Then in the process of using it I found a few little corners that didn’t quite do what I wanted. So I opened issues and asked for advice on how to fix them.
This means that I think you should pick a project that you are using already as a tool as that means you have a high chance of already having a few small things that you’d like to see changed. As well as some familiarity with the thing.
Overall we should work on making it more obvious for where people can get started.
And because one GitHub organisation isn’t enough: there is also JupyterHub · GitHub and JupyterLab · GitHub 
Do you know how it works from the point of view of a project maintainer? I clicked around a bit but couldn’t find much docs on the website and most buttons directly ask me to sign up/inn with my GitHub credentials.
Not sure how it works, but after the login, I’ve managed to add repo2docker. However, it doesn’t display any entry in the Help Out section. I guess they periodically pull them from github since other repose have some entries (eg ipython).
Maybe it looks for a specific tag or something?
I think after some hours it pulled the issues from GitHub, see https://www.codetriage.com/jupyter/repo2docker