User Tools

Site Tools


evergreen-docs:dig_meetings:20110711-minutes

DIG Meeting minutes, July 11, 2:30 EST

Participants

Karen Collier, Kent County Public Library; Robert Soulliere, Mohawk College; Jenny Turner, PALS (MN); Jason Etheridge, Equinox; Mike Rylander, Equinox; Glen Modell, Ann Arbor District Library; Yamil Suarez - Berklee College of Music; Kathy Lussier, MassLNC; Shauna Borger, Evergreen Indiana

Updates from groups

Content coordinators

Yamil Suarez is working on bumping up the EG & OSRF version numbers/link in the official documentation. He asks for DIG members to notify him of any spots or mistakes with regards to version numbers and links in the official documentation. Suarez reports that he is done with fixing an installation documentation bug and is trying to find new documentation bugs. He needs to follow up on a couple more potential bugs in documentation that came up recently on the lists.

Jenny Turner has confirmed that the 1.6 documentation works for 2.0, at least on a very basic level. If anyone notices anything in 2.0 that needs to be changed, she asks to please let her know. Nothing to discuss from the reports group.

Robert Soulliere has nothing new to report since last meeting with regards to the DocBook Conversion Coordinator Report.

Kathy Lussier spent some time pulling together some 2.1 documentation recently and needs to take a second look at it to see if it can be made generic for DIG purposes.

Old Business

No old business discussed.

New Business

Yamil Suarez has been part of the discussion to have a single source of installation instructions. No final decision has been made. Right now there are three sources for installation instructions:

1) README file within the EG/OSRF source code 2) Docuwiki based instructions linked from the downloads page 3) Official documentation

It has been noted that having three separate sources of instructions at times causes confusion when helping new Evergreen users with installation problems.

Having a single source would be good but there are some technical issues since some instructions are in ASCIIdoc and some in DocBook. Also, we might end up eliminating installation content that was contributed by some.

There was discussion about how to improve the installation instructions but it was reported that we are not ready for a fully automated solution. There was a suggestion by Suarez to manually synchronize at least two of the three sources. Dbs has been fleshing out the AsciiDoc install instructions in master - still not quite caught up to the wiki, but almost there - and includes Debian / Ubuntu + Fedora

There was a suggestion to consider defining links manually from the AsciiDoc into other parts of the manual, and vice versa, once we have stable enough targets to point to and consider how it might affect several documentation pages but keep in mind that some submitted content might be eliminated in the process.

Robert Soulliere asked whether we should start thinking about 2.1 documentation at the RC12 stage and release. He volunteered to create a wiki content outline to get started.

Kathy Lussier has content to add for 2.1 but just needs time to adapt it.

Yamil Suarez asks whether in the future, we intend to plan to have three separate versions if the documentation: 1.6.x, 2.0.x, and 2.1x or 1.6.x and a combined 2.0.x with 2.1.x?

Robert Soulierre states that he thinks we need separate docs for 2.0 and 2.1 since this release include new features. Kathly Lussier agrees with Soulierre. A reminder that 1.6 loses support once 2.1 comes out is made. Soulierre states that while 1.6 will not be officially supported, DIG can keep the documentation up but discontinue updating it.

Meeting was concluded at 3:19 EST on July 11, 2011.

Next meeting will be Monday, August 1, Freenode IRC network (http://evergreen-ils.org/irc.php) @ 2:30pm EST.

evergreen-docs/dig_meetings/20110711-minutes.txt · Last modified: 2018/04/24 15:27 by rjs7

© 2008-2017 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a member of Software Freedom Conservancy.