That makes a lot of sense. If I look at any project I've contributed to, it always started out with something small. Taking the time to make a small PR that makes a tiny improvement:
- shows you care about improving the project; you took the time to improve something small that others would ignore
- lets you test the waters. Are the project owners receptive of changes? Is it pleasant trying to contribute to the project? Or do they ignore your patch and don't reply for 2 weeks. You wouldn't want to spend a lot of effort just to find that out.
- gives you a chance to become familiar with the process, the tools, gain practice, and hopefully get rewarded with your change being accepted
For example, my first CL to Go was a trivial change:
But without having done that (and having a good experience) I couldn't have been working on more complicated changes like https://codereview.appspot.com/142360043/ now.
- shows you care about improving the project; you took the time to improve something small that others would ignore
- lets you test the waters. Are the project owners receptive of changes? Is it pleasant trying to contribute to the project? Or do they ignore your patch and don't reply for 2 weeks. You wouldn't want to spend a lot of effort just to find that out.
- gives you a chance to become familiar with the process, the tools, gain practice, and hopefully get rewarded with your change being accepted
For example, my first CL to Go was a trivial change:
https://codereview.appspot.com/97280043/patch/40001/50001
But without having done that (and having a good experience) I couldn't have been working on more complicated changes like https://codereview.appspot.com/142360043/ now.