On issue with that approach is that Trevor is the only one who really knows all of the code, and quite a lot of it is (especially the stuff dealing with VBL, light, vision, etc). Combine that with the fact the some of the contributors are not full time java coders(myself for example), so it take a bit of time to figure out what's going on in many parts of the code. So yea... you can say, only fix bugs here, but I think that would be doing the project and the community a great disservice by doing so.biodude wrote: Would it be possible to restrict contributions in one area for a particular build, fix some bugs, then add new material in another area? The main reason I suggest this is to avoid the problem of "I really want to use new feature X, but bugs in feature Y are prohibitive". I'm not a contributor, so I have no idea how feasible this is - just a thought.
In the end, an open source project should not restrict contributors in the area they wish to work on based on their skill level (though I have no problem with Trevor saying "no, don't do that because I have some major plans in that section in the near future and what your going to do will be replaced real soon"). I have had a few things I thought might be easy, but after talking to Trevor he noted they were fairly complex and offered a few alternative smallish code patches I could do that he would like done but did not have time to get to. This also helps new people get involved with the code without overwhelming and getting confused and giving up.
