Hi, > 2. While recognizing that Entwine is taking the initiative here, it's > conceivable that in the future other commercial partners may also > offer QA resources or get involved in various ways. So I think it > would be most appropriate to define a community process with specific
And it's not just up to commercial partners! Consider this a call to arms to adopters of Matterhorn to get involved not only in the QA but in the development efforts! By getting involved as a developer your team grows and: - develops contacts in the project that are invaluable for local support issues - learns best practices for production deployment, and better understands what the product can and cannot do - understands the system from an architectural perspective which gives insight into better development of integration - gains skills in the environment that matterhorn runs in Developers who have commit access to the Matterhorn codebase have agreed to give back to the community in the form of mentoring, advising, and giving code reviews. And there are ways to contribute for every skill level and background; from non-coding to expert coder, from interface designer or pedagogical expert to software developer. So, please introduce yourself on the development list ([email protected]) and start asking for ways to contribute. We're not only open source, but an open community! Chris -- Christopher Brooks, BSc, MSc ARIES Laboratory, University of Saskatchewan Web: http://www.cs.usask.ca/~cab938 Phone: 1.306.966.1442 Mail: Advanced Research in Intelligent Educational Systems Laboratory Department of Computer Science University of Saskatchewan 176 Thorvaldson Building 110 Science Place Saskatoon, SK S7N 5C9 _______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
