evergreen-docs:reorg_2014:agenda_2016-02-10
This is an old revision of the document!
Table of Contents
Agenda
Introductions
Please introduce yourself using the #info command. For example:
#info tay_tay is Taylor Swift, Wyomissing Public Library
Develop consensus on project requirements
The following agenda items are based on the Proposed project requirements document.
Values check
- Do the values listed in the requirements document work for everybody?
Specific goals
- Any discussion points here?
Requirements
- Any discussion points here?
- Gather requirements from users (idea from remingtron)
- Let's consider getting feedback from documentation users to help guide our efforts. Maybe a broad survey to understand general needs, with questions like:
- How do you use Evergreen? (sys admin, staff client admin, circ superuser, circ normal user)
- How often while using Evergreen do you want help?
- Where is the first place you go for help? (supervisor, coworker, IRC, printed/handwritten notes, online documentation, youtube, my library's training documentation)
- Have you used the documentation available at docs.evergreen-ils.org?
- How useful has it been to you?
Ideas
Specifically, let's talk about:
- Platform (Asciidoc vs. flossmanuals vs. something else)?
- If consensus on Asciidoc, how to create crosslinks?
- Which audiences should we target? For this discussion, we can use remingtron's draft as a starting place
Identify compilers
These people would be responsible for individual "books"
Testing and assessment plan
If we have time, it would be great to come up with a plan for testing these reorganized docs on end-users. It would also be good to work towards a plan for assessing this work.
Timeline
If we have time, it would also be nice to start filling in the timeline on the requirements doc.
evergreen-docs/reorg_2014/agenda_2016-02-10.1455121406.txt.gz · Last modified: 2022/02/10 13:34 (external edit)