Paul Frields wrote:
A CMS is good for a document like a general QA guide for users -- i.e.
something that helps people get started with the team, understand the
terminology, how to set up a testing environment, and so on. Those
details largely won't change between releases so it's easy enough to
keep the document in sync with reality, especially if you give broad
editing rights to the QA group so that people can help.
As long as this model is limited to canonical docs with a very low
rate of change, this should work OK.
Totally agree! I've nothing against open collaboration until it makes
information harder to get or impossible to use.
Leam
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
