I see you included a KDE4 tag. (edit, I swear when I started writing this, there was a kde4 tag)
Getting into the Community
If you are interested in contributing to KDE4, I recommend picking a KDE application or two that interests you, then join that application's IRC channel on freenode. Most developers are more than happy to point out a few bugs or simple features you could work on, if you ask in the channel (or on the mailing list).
I am an Amarok developer, and we have great community of members who will help dedicated new contribuors find your way around the codebase, and help find simple tasks to complete.
Also check out the KDE List of Junior Jobs, which are small bugs/features that have been tagged for a new contributor to work on so they might ease in to the KDE developer community.
Speaking for the KDE community, you won't be "branded" a developer straight away, that takes a little bit of time. You'll get direct commit access after submitting a few patches, and having your code reviewed. In Amarok if you submit several solid patches over the period of a month or so we'll likely give you commit access.
Important KDE IRC channels ( on irc.freenode.net
):
#kde-devel
for developer questions
#kde
for user questions
#amarok
for amarok
#kontact
for anything in kdepim
#qt
For Qt related questions
Technical Information
KDE has a large codebase, and is broken down into many many submodules/programs. The Techbase is the first place you should investigate before diving into KDE code. Individual projects may have other websites/wikis with more information, so you should ask in that projects IRC channel or mailing list.
Important Techbase links:
After Thoughts
It is important to note that in KDE's case -- and I suspect many other open source communities -- becoming a developer is something that takes time and dedication. Most of all, you have to understand you are joining a community of people. Open source development doesn't take place in isolation (usually). In some ways it is like having a job, in that you have colleagues you have to work with. Without a doubt, at times, there is drama and politics, but that comes with any human community.
Sure, I suppose, you could show up every now and then, contribute some code then disappear, and the community would accept it (assuming the code was of acceptable quality), but then, IMHO, you're missing out on 99% of what the Open Source community has to offer.