As one who has used the BGE numerous times before, I have a vested interest in seeing this engine expand in terms of features and usability. However, it seems that we are starting to lose control of one thing, the number of bugs reported in the BGE tracker.
As you can see, there’s a lot of unfixed bugs as well as no indication on whether or not a developer is aware of it, so I would start by suggesting a few things.
1). - The first thing is that Moguri, Dfelinto, and the other developers should try find the spare time they need to comb through the tracker and make a reply that they are now aware of the problem and that sooner or later they will be able to get around to fix it, this will at least give assurance that we have dev. activity surrounding the BGE’s issues.
2). The developers, if possible, should try to take some time every week to hunt down some of these bugs and fix them, because chances are some of these might require just a few lines of code to fix. It would also be nice if some of them that currently have BGE-related projects would at least try to help with this, so as to make the BGE as issue-free as possible as early as the 2.68 release.
3). There should also be an effort to make sure that all of these bugs are assigned to someone once confirmed, this will ensure that every developer has a list that he can work on that plays to the parts of the code he knows best.
4). Bugfixing would also be a good way for prospective developers learning C++ to show that they have the skills needed to develop fully-fledged BGE features, so if you’re interested in writing patches, here’s a bunch of items that you can pick from to help hone your skills. Now I’m not saying that this should be a required thing, but it would be a nice thing to do.
That’s all I can think of for now when it comes to how all of us will be able to enjoy a BGE with less bugs and prevent the BGE from even getting close to the broken state it was in early in the 2.4x series, what are your thoughts?