Yea, resources become the issue, and it helps to have someone with experience in dealing with specific implementations.
My opinion is put the project up on freshmeat/slashdot with an open call to new developers. Not that the current team isnt doing great, but expanding the team will make it easier to delegate work out, and you might be able to pull some developers who have prior experience dealing with those issues/coding problems.
Yes, you flood the project with new people, but you also open it up to alot of new development talent.
Oh course, you'll probably have to have someone assume the mantle of full time 'project/systems manager' and start to
develop some design strategies to keep everyone working in the same direction.
I've noticed this team will do that, grow, then shrink down to a few folks, but not actively recruit new developers. Thats the beauty of opensource projects is how easy it is to pull in new development blood when you have a project thats interesting, and this one is one of the more fascinating ones I've seen. Hell, I'd love to be more actively involved in the development of eqemu, but it seems you need to be knighted by King Arthur first to get access to the developer channel..... LOL
I think if you want to spur the development of the project, you need to first have a more open way to recruit new developers on a constant basis, not just when you get down to 1 or 2 people.
There should be a developer application form right on the front page, or some method for pulling new blood in.
Also, sceheduling a weekly design/development meeting thats open to the public will go a long way (IRC would work), at least you make a scheduled attempt to hear what the community has to say and get new ideas.
Hows that sound? I think a weekly/biweekly design meeting on an IRC channel would be an awesome idea...
|