What was the reason for playing with the board software? :S
Maybe switch to the new phpBB 3 once it hits Gold and it could cure the 500 errors and also allow Rats or Zothos to have whatever it is they wanted the board to do. All in all, I think we need to look at existing successful open source projects and see how they manage these intra-team issues as well as development approach.
A good example that comes to mind is Drupal. One or two main guys who have overall control. Then one leader per branch. A new and final release every 1 year. But the development HEAD is always constant and changing. I was even thinking of suggesting Drupal itself as the software to power the frontend of ispCP? It's modular, secure, commented code and quick to develop for. The perfect tool to help Raphael to carry out his work FAST? That way, we can shift some of the load as we are not reinventing the wheel.
Another solution is to define absolute and final development roadmaps and assign key dates for when a code freeze is hit and how long to fix bugs. And work your way backwards from the deadline. Ubuntu, Fedora etc seem to be very successful using this method. It also helps the entire community get involved as they know the short time involved in each phase before it's out.
Just my .02
Search
Member List
Calendar
Help
