Yes, but you may need to pick a different job as an intermediate step: find a job that will let you interact meaningfully with wider open source communities.
The recipe is deceptively simple: (1) build things, (2) tell people about it, (3) repeat. You need a job that lets you do step 2.
I will also add that projects around "20/hr or less" are not just quantitatively too low-paying, they are qualitatively the wrong kind of projects. A $300/hr consultant is not just a more expensive version of a $20/hr web developer -- it's an entirely different job.
The actual technology layer involved in either case might be the same, but the "interface" between you and your clients is different. The high-priced consultant exposes a much higher-level interface that is closer to the business problem domain.