...
In the past, Stanford has merged contributed code into SAMigo ; with the only condition was that it was in production at the contributor's school for a year without any problems and that it might be useful to other schools. While that condition criteria that the code had to be fully QAed and updated with trunk code. While these conditions might help prevent performance issues, we have found that sometimes contributed code introduces usability issues. In light of this, Stanford began implementing a new release process for SAMigo starting with SAMigo 2.7. This process is adapted from a process suggested for community development of SAMigo back in 2006 as well as what the OSP group is doing to insure that enhancements are desired and well-designed. As part of the release process, contributions will be undergoing a user experience (UX) review to insure that contributed code does not negatively affect user experience or come in conflict with other recent contributions. This process is described below.
...