================================================================================================================================================================================================================================ #evergreen: 2012-07-05 - DIG Monthly Meeting Evergreen Documentation Interest Group (DIG) Monthly Meeting. The agenda can be found here http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:dig_meeting_20120705-agenda ================================================================================================================================================================================================================================ Meeting started by yboston at 14:03:06 US/Eastern. The full logs are available at http://evergreen-ils.org/meetings/evergreen/2012/evergreen.2012-07-05-14.03.log.html . Meeting summary --------------- * Introductions (yboston, 14:03:19) * Updates from Content Coordinators (yboston, 14:06:01) * Conversion Coordinator Report (rsoulliere, 14:06:32) * this is a test report first post/line (yboston, 14:07:37) * this is a test report second post/line (yboston, 14:07:40) * I plan to create an outline for the EG 2.3 documentation in the next week for us to update in regards to what can be merged from 2.2. (rsoulliere, 14:07:49) * At this point, only developers might have the answers until others get a chance to play with 2.3. (rsoulliere, 14:08:04) * I submitted a pull request via launchpad a few weeks ago related to an update to the upgrade instructions for 2.2. See: https://bugs.launchpad.net/evergreen/+bug/1015248 (rsoulliere, 14:08:21) * I would like to get the upgrade instructions fixed up a bit for the latest edition of 2.2.0. (rsoulliere, 14:09:06) * I was also wondering of the install page could point the the official docs chapter on upgrading -- if it is fixed and cleaned up? (rsoulliere, 14:09:24) * Another question is whether we should have a section for upgrading from 2.1 to 2.2 and a separate for going from 2.0 to 2.2 since many might be jumping directly from 2.0 to 2.2? (rsoulliere, 14:10:08) * HELP: rsoulliere says: Another question is whether we should have a section for upgrading from 2.1 to 2.2 and a separate for going from 2.0 to 2.2 since many might be jumping directly from 2.0 to 2.2? (yboston, 14:11:04) * HELP: rsoulliere says: I was hoping for some checking and pulling or some feedback. I didn’t get any. [on] upgrade instructions for 2.2. See: https://bugs.launchpad.net/evergreen/+bug/1015248 (yboston, 14:12:02) * I am hoping to do some doc work in the next few weeks to fill in some 2.2 gaps. (rsoulliere, 14:13:05) * Are Devs. Comfortable with me doing lots of commits in the docs folder on the master or rel_2_2 branches in the next 2 weeks? I’ll try to follow proper procedure for commits. (rsoulliere, 14:13:29) * HELP: rsoulliere says: Are Devs. Comfortable with me doing lots of commits in the docs folder on the master or rel_2_2 branches in the next 2 weeks? I’ll try to follow proper procedure for commits. (yboston, 14:14:40) * Reports Coordinator Report (jenny, 14:16:35) * I reviewed the functional documentation for reports from 2.1 (folders, templates, outputs) and gave rsoulliere the go-ahead to move those to 2.2 (jenny, 14:17:27) * I need volunteers to review the admin side of reporting (jenny, 14:17:50) * HELP: jenny says: I need volunteers to review the admin side of reporting (yboston, 14:18:27) * IDEA: to rsoulliere and others: I was thinking that we might want to collaboratively write a letter to the DIG list mentioning the transition to 2.3, even if it is preliminary so we can get more feedback (yboston, 14:28:13) * ACTION: rsoulliere & yboston (& others) will write letters to DIG list to solicit comments and share ideas of how to handle the 2.3 transition (yboston, 14:30:17) * IDEA: I might also point out some of the critical 2.2 gaps we need to fill in a posting. (rsoulliere, 14:30:27) * ACTION: rsoulliere & yboston (& others) will write letters to DEV list to solicit help & ideas of how to handle the 2.3 transition (yboston, 14:30:54) * ACTION: new content outline has to be created for EG 2.3 (yboston, 14:33:41) Meeting ended at 14:37:33 US/Eastern. Action Items ------------ * rsoulliere & yboston (& others) will write letters to DIG list to solicit comments and share ideas of how to handle the 2.3 transition * rsoulliere & yboston (& others) will write letters to DEV list to solicit help & ideas of how to handle the 2.3 transition * new content outline has to be created for EG 2.3 Action Items, by person ----------------------- * rsoulliere * rsoulliere & yboston (& others) will write letters to DIG list to solicit comments and share ideas of how to handle the 2.3 transition * rsoulliere & yboston (& others) will write letters to DEV list to solicit help & ideas of how to handle the 2.3 transition * yboston * rsoulliere & yboston (& others) will write letters to DIG list to solicit comments and share ideas of how to handle the 2.3 transition * rsoulliere & yboston (& others) will write letters to DEV list to solicit help & ideas of how to handle the 2.3 transition * **UNASSIGNED** * new content outline has to be created for EG 2.3 People Present (lines said) --------------------------- * yboston (48) * rsoulliere (26) * jenny (12) * pinesol_green (4) * fortin (2) * hopkinsju (1) * glen_ (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot