3. Updates to code:
If someone wants to correct an issue or correct a feature, this person would need to be plugged into either the PRB or community leader in order to be assigned via the TRAC system and have access to the latest build to update.
In terms of code updates, I've got a few questions. (sorry if TRAC does this already, but I'm not familiar with it)
What is in place currently to review changes to the codebase? Is there a system in place to do group reviews of code (before it is submitted to the svn)?
I believe that it is always good to have more eyes on code. It would probably be good to lay down a method to review all changes before they are submitted. The company I work for uses Review Board (http://review-board.org/
). We find it very useful to keep track of what is being submitted to the code base, and catching small errors before they get entered into the SVN.
I think that going forward, and as more people (who may be inexperienced) join LinuxMCE. That LinuxMCE would benefit from a code review process.