Hi Andy, > ------------------------------------------- > Getting Started > -------------------------------------------
I'm perhaps a minority voice in that I think our release docs are good, and line by line they describe exactly what needs to be done to setup Matterhorn. I don't think they could get more clear, except perhaps the "Install Across Multiple Servers" section, which is just tough because the software is flexible. Also, these docs are very version specific, and I think we've found a good way to represent that in the wiki. I don't think the structure for 1.3 worked out as well as 1.2, and the release manager should keep the ordering as it appears in trunk in the future. So, I prefer the section "Release Docs" to remain largely unchanged. It's well tested, and almost line by line what someone would have to run in a terminal to setup and configure Matterhorn. > ------------------------------------------- > Developing for Matterhorn > ------------------------------------------- > Developer System Set-up > A guide on how to get your development environment set-up > > Committing Code > A guide on how to contribute code/patches to trunk. > > Writing Unit Tests > A guide on writing unit tests > > Writing Integration Tests > A guide on writing integration tests > > Using Matterhorn Services > A guide to taking advantage of the Matterhorn Service Oriented > Architecture (SOA) I like this for the development side. I also thing we need to link in that page on all the different methods of calling the rest service since it's invaluable for a sys admin who just wants to play around. This could be a subsection of the last point: http://opencast.jira.com/wiki/display/MH/Remote+Services Where would you put the cookbook entries? Out of everything I use those the most. Also, lots of people have talked about the integration scenarios page on list, so that seems useful, where would that information appear? > ------------------------------------------- > Contributing to Matterhorn > ------------------------------------------- > How to Become a Committer > A guide for how/why you become a committer > > Committer Guidelines > The do's and don'ts of a committer > > Documentation Guidelines > A guide outlining the community framework for documentation and > expectations. > > QA/Testing Guidelines > A guide for how you and your institutions can help improve Matterhorn I assume this would be the place for the guidelines, and that the actual results of tests run, e.g. http://opencast.jira.com/wiki/display/MH/QA+Status would stay with the release documentation? Chris _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
