This effort was organized on the Help Files and Documentation Process Redesign page.
Participants
- Name a moderator and a minute-taker
Agenda
1. Introductions/Expectations/Skills/Availability of participants
2. Current Status
- Study of Samigo, at Stanford: Current Status of Tests & Quizzes Documentation (R. Hill)
- Why is it so hard to document the portfolio tools? (R. Hill, relying on S. Keesler)
- Because we're too lazy to learn the skills clearly designated as necessary; we want documentation to reveal the effort-free path.
- Because the Help files are written to an audience, trained faculty, that enjoys an environment of expert support.
- Because Sean's comprehensive documents on Confluence are found in different branches of the hierarchy.
- Because some Confluence pages have lost their context and suffer from neglect: http://confluence.sakaiproject.org/display/OSPDOC/Data+warehouse
- Because there is no visible intermediate result that affords the author a self-check of progress.
- Because there are assumed procedures and scenarios that hide restrictions.
- Because portfolios, insofar as they capture the essence of learning, are inherently complex objects.
3. Define goals
- Scope (redistributable KB or wiki, prioritized list of docs needed)
- Exploration of different levels of documentation for different audiences
- SDK documentation for developers
- Official policy for developers' institutions' submittal of documentation