First step: find the project you want to contribute. I would've picked a project which
1) I already use, so im already familiar with it
2) Has a little codebase so diving into it would be a little bit easier
3) Has an active development community
Second step is to use it, if you havent used it already. You wont be able to contribute to a software which you havent even used by now.
And when you use software, you will have little ideas to improve it. Or little bugs that annoy you.
Third step is diving into the source code, understanding the codebase and actually doing the changes. At this step, you might need to communicate the authors. This is an imporant part.
You can usually find developers on mailing lists and/or irc channels. Use these tools to contact authors and ask for their help.
Dont be afraid, you are not supposed to do it all by yourself without asking anything. On the conterary, asking developers assures that you're doing it the right way.
However, you should ask smart question. This one makes differrence. (Read Eric Reymond's article about this.)
Last step, is giving the patch to authors. if the project uses a proper SCM, you will be able to produce a patch easily. Send the patch to authors and wait for their response. Some projects have reviewboards which you can post your patch there and wait for their review.
Now, depending on the project, the path you go may differ. Dont bug developers too much. Dont hurry. Be friendly with them. Be Patience.
Second step is to use it, if you havent used it already. You wont be able to contribute to a software which you havent even used by now.
And when you use software, you will have little ideas to improve it. Or little bugs that annoy you.
Third step is diving into the source code, understanding the codebase and actually doing the changes. At this step, you might need to communicate the authors. This is an imporant part.
You can usually find developers on mailing lists and/or irc channels. Use these tools to contact authors and ask for their help. Dont be afraid, you are not supposed to do it all by yourself without asking anything. On the conterary, asking developers assures that you're doing it the right way. However, you should ask smart question. This one makes differrence. (Read Eric Reymond's article about this.)
Last step, is giving the patch to authors. if the project uses a proper SCM, you will be able to produce a patch easily. Send the patch to authors and wait for their response. Some projects have reviewboards which you can post your patch there and wait for their review.
Now, depending on the project, the path you go may differ. Dont bug developers too much. Dont hurry. Be friendly with them. Be Patience.
Also, this website is created for this exact purpose: http://openhatch.com
(Some projects have JuniorJobs, which are easy tasks for newcomers to start contributing, if you havent already found 'what' you want to do)