User Tools

Site Tools


evergreen-docs:reorg_2014:agenda_2016-02-10

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
Next revisionBoth sides next revision
evergreen-docs:reorg_2014:agenda_2016-02-10 [2016/02/09 11:56] – created sandbergjaevergreen-docs:reorg_2014:agenda_2016-02-10 [2016/02/09 12:43] – [Ideas] sandbergja
Line 5: Line 5:
      
 ===== Develop consensus on project requirements ===== ===== Develop consensus on project requirements =====
-[[http://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:reorg_2014:requirements|Proposed project requirements]].+The following agenda items are based on the [[http://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:reorg_2014:requirements|Proposed project requirements document]].
 ==== Values check ==== ==== Values check ====
 +  * Do the [[http://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:reorg_2014:requirements#ideas_expressed_about_this_project|values listed in the requirements document]] work for everybody?
 ==== Specific goals ==== ==== Specific goals ====
 +  * Any discussion points here?
  
 ==== Requirements ==== ==== Requirements ====
 +  * Any discussion points here?
  
 ==== Ideas ==== ==== Ideas ====
 Specifically, let's talk about:  Specifically, let's talk about: 
  
-* Platform (Asciidoc vs. flossmanuals vs. something else)? +  * Platform (Asciidoc vs. flossmanuals vs. something else)? 
-* If consensus on Asciidoc, how to create crosslinks? +  * If consensus on Asciidoc, how to create crosslinks? 
-* Which audiences should we target?+  * Which audiences should we target?  For this discussion, we can use [[evergreen-docs:reorg_2014:audience_focused_layout|remingtron's draft as a starting place]]
  
-==== Identify compilers ====+===== Identify compilers =====
 These people would be responsible for individual "books" 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 [[http://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:reorg_2014:requirements#proposed_timeline|timeline on the requirements doc]].
evergreen-docs/reorg_2014/agenda_2016-02-10.txt · Last modified: 2022/02/10 13:34 by 127.0.0.1

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.