Hey Nils, I don't mean to be a pain, perhaps I'm misunderstood. I mean, lets quit talking about how we should talk about this, and instead just start talking about changes we could make.
For instance, should we have all committers sign off that the docs are correct? Should subtrees of the docs be assigned to certain people? Should we have some sort of unit test to catch URLS to test for the existance of trunk before a doc is published? Should we form a group of adopters who verify the docs for us? Is the distributed install documentation the only configuration we want to verify (because you can distribute differently), etc? In otherwords, I agree we need process changes to catch these errors, so can we get on with trying to make those changes instead of trying to figure out who is to blame for the bugs? 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
