On 10/11/2016 08:31 PM, Ron W wrote: > Sounds like something Google Docs does or could easily do (at least in > Google docs for Business).
I'm not familiar with any recent incarnation of Google Docs. A quick glance at my white board and I see four loops of interaction with the documentation system: 1. Developers - creation 2. Maintainers - modification 3. Users - annotation 4. SRC/runtime - verification Each of those loops [in my current view] would involve data collection and analysis with hooks into the [policy automation][1] system and ticket system. [1]: https://www.youtube.com/watch?v=B9pulMZwUUY "Checklists For Better Software" Item 4 in that list is rich with possibilities; e.g., examples & demonstrations within the documentation could be executed and assessed, there could be meta-data within the documentation expressing various dependency relations to sections or areas of the source code, etc. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
