|
|
Given the nature of how this software is developed over time, I see it as being more important to have a manual for it, that is available instead of no manual at all.
The book needs to be listed as as being subject to updates - at the outset.
The chapters or parts of them need to be qualified under 3 criteria.
1. Current with version XYZ.
2. Under Revision.
3. Needs Documentation - submissions requested.
Then apply monthly updates and releases of the same manual.
A reasonably current manual, with qualifications, is much better than NO manual.
Especially for new users (important) and users considering incorporating this into their software array, or for teaching it.
This is a fundamental "deal maker / deal breaker"issue.
Rather than just whine about it, I'd be prepared to help out and do it myself - as a collaborative effort.
|
Locked
