Please introduce yourself using the #info command. For example:

#info tay_tay is Taylor Swift, Wyomissing Public Library

The following agenda items are based on the Proposed project requirements document.

• Do the values listed in the requirements document work for everybody?

• Any discussion points here?

• Any discussion points here?
• (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?

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

These people would be responsible for individual "books"

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.

If we have time, it would also be nice to start filling in the timeline on the requirements doc.