As soon as I encounter a problem with a FOSS library or program I'm working with, I grab the code and start looking for a solution, and often my first communication with the project will be the patch that fixes the bug.
It takes practice to be able to dive into a codebase quickly and solve problems right away, but so does anything else worth doing.
@sir how do you understand a codebqse that you've never seen before? Would you have any advice?
@rbd make liberal use of git grep
Asking the developers directly also has helped me a lot. Just popping on IRC or similar and asking something like "What does function XYZ do?" can yield good results since free software developers tend to be pretty friendly, especially to prospective contributors.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!