I too find it difficult to contribute to the Subsonic code base. It seems to me that there are just too many ways to report issues and provide fixes which hampers progress on the project.
First, there's the forum where users post issues in a rather unstructured fashion. This is great at times, e.g., when users announce a new GUI or client implementation. Then again, it's barely usable for bug and feature reporting as you cannot assign tasks to different people, mark issues as duplicates, and many other things that you take for granted when dealing with collaborative software engineering.
There's also Sourceforge which people use once in a while. Unfortunately, no one but Sindre seems to be in charge of managing the Sourceforge tracker: The number of closed bugs and feature requests is 2(!) which may simply be the case due to lack of management. (I suppose a lot of bugs which have been fixed in the code are not marked in the tracker accordingly.)
Finally, there's Launchpad. I am not sure why it's there, there's just a single issue reported; overall, it seems to be unused and obsolete.
In consequence, I think the Subsonic infrastructure needs some cleanup and redundancy elimination. Besides the points described there are further issues, such as having both an FAQ forum and an FAQ section in the wiki. These things just make it very hard to guarantee the kind of quality level that the project deserves.
I've gone ahead and started a Subsonic project fork called Supersonic
that I have pushed to Github
I plan to automatically track Sindre's SVN trunk on the upstream
branch, while providing my own changes and features on master
branches. As of today, to get started you would have to clone the repo and run Maven to build the project, but I plan on publishing the generated project artifacts directly to Github using their Maven plugin.
I'm really looking forward to making this more collaborative effort so we can learn and benefit from each other rather than always relying on Sindre.
Seeing you forking of a branch off Subsonic into github gives me mixed feelings. It's good to be able to work with git on the Subsonic code due to, well, its apparent strengths (branching, merging, you name it). In my opinion, working with Subversion effectively in a collaborative fashion is very hard, there are just too many restrictions. Not sure how much experience Sindre has with git, I'd be fine with Mercurial or even Bazaar just as well as long as we're going DCVS.
On the downside, getting to use a nice DCVS by means of having to fork is not a preferable option to me. It'll make everything even more difficult, first and foremost synchronisation of new features and bug fixes. I'd much rather see a single Subsonic project making the necessary changes to its infrastructure and workflow that will allow for a great collaborative work.
I can't tell whether Sindre would agree with opening up the project more so that people other than him can take important roles as well. All I can say is that if distributing work load among additional people is desired I'd be glad to join the party.