The whole development process does not feel very welcoming to casual contributors. On most open source projects you have a development mailing list where you can send patches to. Then they decide if they want to include that patch or not. Usually they do include it but tell you to change some things first, so it better fits their overall design. I think that is the better approach to hook up new developers as someone who has already spend hours developing a patch is more likely to make a few changes to get it accepted. Once one of your patches is accepted you already have some knowledge about the system and are more likely to develop another one.
actually that's what the bugtracker is for (and crystal space uses the same development process. they are actually more strict you must always make a ticket to submit a patch even if the committer is talking with you, then it's commited it and the ticket closed if the patch is appropriate) make a bug with the patch and see if it gets approved obviously it can happen we don't accept it like in any opensource project so doing a patch without asking first is a risk for who does it.
The whole problem is less about the bug tracker but the communication process in itself. It does not matter if you finally have to create a bug report to get the patch into the game, but there is no real place to discuss your changes and send your first trys to. The forums are nice but most of the time developers do not participate in the forum threads - you weltall are an exception of this rule. When you post something on a forum you never know if a developer did not read the forums or if just noone did know the answer. On a mailing list you at least know that everyone got your message (even if they might not read it).
An example: In June last year, I thought about getting into PS development. As I didn't want to apply for the team (the recruitement page scared me away), I thought I start with something simple - adding some documentation. Adding documentation is always good because you help other newcomers and you get into the code as you have to read it to write the documentation. So I checked the "requested documents" page on the wiki and started by adding a guide how to add a spell to the database
http://www.hydlaaplaza.com/doc/index.php?title=HowtoAddASpellToTheDatabase and did some other database documentation.
To find something to work on where you do not need a complete overview of the whole system, I decided that it might be worth looking into effects, as all magic effects are pretty much ugly and they all look the same. So I added the effects manual to the Wiki to get into effects development:
http://www.hydlaaplaza.com/doc/index.php?title=EffectsManual. The effects manual was btw not my own work but I moved it from a PDF file into the wiki so I could improve it while experimenting with effects. The effects manual contained lots of images which I wanted to add to the wiki page as well, so I just asked if someone could add image support to the wiki:
http://www.hydlaaplaza.com/smf/index.php?topic=33083.0Well I didn't get any answer to that simple question which really is demoralizing. Did noone read that question or did noone know the answer? On a mailing list I would have at least known that all the developers received my request. Still they might not read it but chances would have been probably much higher that someone responds. The whole development process seems to lack some central communication hub where absolutely all developers of all departements come together.
I could go on describing my attempts to participate in PS development, but why that never happened is a story for another post/thread.