Hi Derek,

In my opinion, documentation issues are a great place to start your contribution streak. I would suggest make two list of projects/repositories

• You purely want to contribute to documentation and you know how to use it but, you don’t see yourself contributing in the form of code i.e. Docker (Let’s say you know how docker works but, you will never see yourself write Golang).
• You wish to start contributing to documentation for the long-term vision of contributing code. This would be a listing of projects that you know both the language (i.e. java or javascript) as well as how the projects work and you could easily set it up and play with it

I started with Option two (2) only. I picked Spring Security because I knew both the how framework works (don’t have to be an expert) as well as know Java programming language.

The benefit of Option one (1) is that, you do not have to worry about knowing the programming language and it gets you hooked into open source contribution as soon as your brain start to taste the joy of contributing to open source then you are all set to contribute in any form.

You can also play around with new features of your favourite open source projects to find bugs, performance issues and new feature requests and start a new github issue to start a discussion around that.

All in all, the above should give you some options to get started with. All the best Derek.