User Tools

Site Tools


dev:meetings:2010-09:minutes

Differences

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

Link to this comparison view

Next revision
Previous revision
dev:meetings:2010-09:minutes [2010/09/07 19:08] – created aatredev:meetings:2010-09:minutes [2022/02/10 13:34] (current) – external edit 127.0.0.1
Line 10: Line 10:
     - Mike Rylander proposed that we forget 1.4 after 2.0 goes gold, that 1.6.0 is frozen, barring data-loss bugs and 1.6.1 gets cleanup bug fixes of all sorts, but no major functionality updates.     - Mike Rylander proposed that we forget 1.4 after 2.0 goes gold, that 1.6.0 is frozen, barring data-loss bugs and 1.6.1 gets cleanup bug fixes of all sorts, but no major functionality updates.
     - Jason Etheridge supported the idea that if someone wants to maintain these older branches, they're welcome to volunteer to do so.     - Jason Etheridge supported the idea that if someone wants to maintain these older branches, they're welcome to volunteer to do so.
-    - Dan Scott has backported some nice usability enhancements to rel_1_6, in case there ever is a 1.6.2.x, which Mike Rylander suggested could just be applied to 1.6.1  if they're 1.6.1 compatible and would be construed as "minor" functionality. 1.6.2 will be reelase if there is a strong 1.6.2 desire from users and a need.+    - Dan Scott has backported some nice usability enhancements to rel_1_6, in case there ever is a 1.6.2.x, which Mike Rylander suggested could just be applied to 1.6.1  if they're 1.6.1 compatible and would be construed as "minor" functionality. 1.6.2 will be released if there is a strong 1.6.2 desire from users and a need.
     - The proposals were voted on and accepted by the community.     - The proposals were voted on and accepted by the community.
-      * **ACTION ITEM:** Dan Scott will update http://evergreen-ils.org/dokuwiki/doku.php?id=versioning+      * **ACTION ITEM:** Dan Scott will update [[:versioning|versioning]]
   - ** Evergreen 2.0 alpha - status of release notes, features. **   - ** Evergreen 2.0 alpha - status of release notes, features. **
     - ESI is compiling 2.0 release notes they are scheduled to be available before 2.0 goes gold and will start putting stuff on the wiki as soon as there's stuff to show.     - ESI is compiling 2.0 release notes they are scheduled to be available before 2.0 goes gold and will start putting stuff on the wiki as soon as there's stuff to show.
     - Everything that's committed before 2.0 will be included in gold for/from KCLS.     - Everything that's committed before 2.0 will be included in gold for/from KCLS.
-    - Amy Teralga pointed out that there is a basic (not complete) roadmap/feature list available which James Fournie recently updated. [[http://open-ils.org/dokuwiki/doku.php?id=faqs:evergreen_roadmap | Evergreen Roadman/Feature List]]+    - Amy Terlaga pointed out that there is a basic (not complete) roadmap/feature list available which James Fournie recently updated. [[faqs:evergreen_roadmap | Evergreen Roadmap/Feature List]]
       * **ACTION ITEM:** Release notes and future expected features need to be separated out from roadmap.       * **ACTION ITEM:** Release notes and future expected features need to be separated out from roadmap.
-    - Dan Scott has some reasonably accurate notes for Debian Squeeze [[http://evergreen-ils.org/dokuwiki/doku.php?id=server:2.0:install | Installing 2.0 Alpha]]+    - Dan Scott has some reasonably accurate notes for Debian Squeeze [[zzz_archive:server:2.0:install| Installing 2.0 Alpha]]
     - With all the fixes going into rel_2_0 puches for an alpha2 release of 2.0 sometime soon.     - With all the fixes going into rel_2_0 puches for an alpha2 release of 2.0 sometime soon.
       * **ACTION ITEM:** 2.0 alpha2 release for testing next week - Bill Erickson       * **ACTION ITEM:** 2.0 alpha2 release for testing next week - Bill Erickson
     - Jason Etheridge needs help testing out the Windows client for 2.0, the version of xulrunner used is pretty different than what 1.6 is running and there are some issues with printing to certain printers.     - Jason Etheridge needs help testing out the Windows client for 2.0, the version of xulrunner used is pretty different than what 1.6 is running and there are some issues with printing to certain printers.
-    - KCLS will be using FGI to rework their web catalog screens so that they're more generic for others to use (Amy Teralga).+    - KCLS will be using FGI to rework their web catalog screens so that they're more generic for others to use (Amy Terlaga).
   - ** 2.0 alpha1 to 2.0 gold - works in progress, discuss of what will make it in for general release, hash out schedule. **   - ** 2.0 alpha1 to 2.0 gold - works in progress, discuss of what will make it in for general release, hash out schedule. **
     - Alpha to gold (Mike Rylander)     - Alpha to gold (Mike Rylander)
Line 42: Line 42:
     - KCLS will be going live on alpha2.5 so there will be further development they have funded which will get included into 2.0 gold.     - KCLS will be going live on alpha2.5 so there will be further development they have funded which will get included into 2.0 gold.
   - ** After Evergreen 2.0; roundup of projects that people are working on. **   - ** After Evergreen 2.0; roundup of projects that people are working on. **
-    - Mike Rylander:+    - (known to) Mike Rylander:
       * authority control sets       * authority control sets
       * MARC batch-edit template wizard       * MARC batch-edit template wizard
       * tiled MARC editor/merger       * tiled MARC editor/merger
-      * staff client auto-update 
-      * new tabbing implementation 
       * query set and field set (batch non-bib editing) UIs       * query set and field set (batch non-bib editing) UIs
       * hard due dates       * hard due dates
Line 54: Line 52:
       * Circulation Matrix project       * Circulation Matrix project
       * Staff client development       * Staff client development
 +      * staff client auto-update
 +      * new tabbing implementation
     - Bill Erickson: Serials and Acquisitions improvements.     - Bill Erickson: Serials and Acquisitions improvements.
-    - Amy Teralga: Kids' catalog project (long term project > 4-6 months) requested others who would like to get involved to contact her.+    - Amy Terlaga: Kids' catalog project (long term project > 4-6 months) requested others who would like to get involved to contact her.
     - Joe Atzberger: EDI (EDIFACT) support for message types: ORDERS, ORDRSP, INVOICE, OSTENQ, OSTRPT     - Joe Atzberger: EDI (EDIFACT) support for message types: ORDERS, ORDRSP, INVOICE, OSTENQ, OSTRPT
-    - Dan Scott/Conifer:+    - Dan Scott: University of Windsor is seconding him to work full time on Evergreen on behalf of [[http://projectconifer.ca|Project Conifer]] for the next year, plans are not yet concrete but features will likely include:
       * LDAP integration       * LDAP integration
-      * Drupal integration (long term > 4-6 months)+      * Drupal integration (long term > 4-6 months) (at this, a number of attendees announced that they too had Drupal/Evergreen integration working or were working on it - clearly we need to follow up on this and flush it out to avoid more duplicated efforts)
       * Recalls       * Recalls
-    - Jason Ethridge: We're going to need to give some serious thought to the staff client in the future; Mozilla is removing a feature we depend on currently (remote xul).  Could hold steady for the time being.+    - Jason Etheridge: We're going to need to give some serious thought to the staff client in the future; Mozilla is removing a feature we depend on currently (remote xul).  Could hold steady for the time being.
     - Jason Stephenson: Using lassos in the circ and hold matrices: https://bugs.launchpad.net/evergreen/+bug/620518     - Jason Stephenson: Using lassos in the circ and hold matrices: https://bugs.launchpad.net/evergreen/+bug/620518
       * **ACTION ITEM:** List projects in progress in a central location.       * **ACTION ITEM:** List projects in progress in a central location.
Line 68: Line 68:
       * ** 2.1 ... late winter **       * ** 2.1 ... late winter **
   - ** DIG report - Karen Collier **   - ** DIG report - Karen Collier **
- +    - The Documentation Interest Group (DIG) is working to find, update, and organize into a single document, the documentation that's been contributed by the community, as well as fill in any gaps. We have an outline of our plans for the overall organization of the documentation and what we hope to include.  The outline shows which parts are completed vs in progress: [[:evergreen-docs:outline|documentation outline]]
-    - The Documentation Interest Group (DIG) is working to find, update, and organize into a single document, the documentation that's been contributed by the community, as well as fill in any gaps. We have an outline of our plans for the overall organization of the documentation and what we hope to include.  The outline shows which parts are completed vs in progress: http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:outline+
     - Documentation is being converted to DocBook XML format and committed to a github repository set up by Robert Soulliere at http://github.com/rsoulliere/Evergreen-DocBook. Our work in progress document is available in [[http://libdog.mohawkcollege.ca/evergreen_documentation/draft/html/index.html | HTML format]] and in [[http://libdog.mohawkcollege.ca/evergreen_documentation/draft/pdf/Evergreen_Documentation.pdf | PDF format]].     - Documentation is being converted to DocBook XML format and committed to a github repository set up by Robert Soulliere at http://github.com/rsoulliere/Evergreen-DocBook. Our work in progress document is available in [[http://libdog.mohawkcollege.ca/evergreen_documentation/draft/html/index.html | HTML format]] and in [[http://libdog.mohawkcollege.ca/evergreen_documentation/draft/pdf/Evergreen_Documentation.pdf | PDF format]].
     - In an email to the documentation discussion list, Robert Souilliere raised some topics relating to DIG that he wanted to get input on from the larger development community.  The archive of his email is here:  http://list.georgialibraries.org/pipermail/open-ils-documentation/2010-September/000644.html     - In an email to the documentation discussion list, Robert Souilliere raised some topics relating to DIG that he wanted to get input on from the larger development community.  The archive of his email is here:  http://list.georgialibraries.org/pipermail/open-ils-documentation/2010-September/000644.html
Line 81: Line 80:
   - ** Reports taskforce report - Amy Terlaga and/or Jenny Turner **   - ** Reports taskforce report - Amy Terlaga and/or Jenny Turner **
     - **Jenny Turner:**     - **Jenny Turner:**
-      * First a bit of background...The Evergreen Reports Taskforce was established in April 2010 at the annual Evergreen International Conference. The goal of the taskforce is to establish a framework for sharing reports and improving the reporting system in Evergreen.  There are seven people on the taskforce and we meet approximately once per month.  Our activities can be tracked here: http://www.open-ils.org/dokuwiki/doku.php?id=evergreen-reports:taskforce.+      * First a bit of background...The Evergreen Reports Taskforce was established in April 2010 at the annual Evergreen International Conference. The goal of the taskforce is to establish a framework for sharing reports and improving the reporting system in Evergreen.  There are seven people on the taskforce and we meet approximately once per month.  Our activities can be tracked here: [[:evergreen-reports:taskforce|Evergreen reports taskforce]]
       * The primary accomplishment of the taskforce to date is the creation of a site to share SQL Reports, along with some general guidelines for posting. Next steps include: developing a mock-up for a reports interface and figuring out a way to share templates more easily.  PINES kindly shared their reports requirements with the group to use as a starting point.       * The primary accomplishment of the taskforce to date is the creation of a site to share SQL Reports, along with some general guidelines for posting. Next steps include: developing a mock-up for a reports interface and figuring out a way to share templates more easily.  PINES kindly shared their reports requirements with the group to use as a starting point.
       * Next meeting is tomorrow afternoon, if interested in listening in, contact Jenny Turner.       * Next meeting is tomorrow afternoon, if interested in listening in, contact Jenny Turner.
Line 90: Line 89:
       * **ACTION ITEM:** Reports taskforce needs to follow-up with Jeff and Ben on their efforts.       * **ACTION ITEM:** Reports taskforce needs to follow-up with Jeff and Ben on their efforts.
   - ** Website team report - Lori Ayre and/or Amy Terlaga **   - ** Website team report - Lori Ayre and/or Amy Terlaga **
-    - **Amy Teralga:**+    - **Amy Terlaga:**
       * The Evergreen Communications Committee was formed at the Evergreen 2010  Conference and has been charged with helping to organize (and possibly  develop) the online resources needed by the greater Evergreen community.    The Committee has decided that one of our priorities should be to  identify all the user groups, undertake a needs assessment process, and  perform a content inventory in order to develop a plan for revamping the  evergreen-ils.org website.       * The Evergreen Communications Committee was formed at the Evergreen 2010  Conference and has been charged with helping to organize (and possibly  develop) the online resources needed by the greater Evergreen community.    The Committee has decided that one of our priorities should be to  identify all the user groups, undertake a needs assessment process, and  perform a content inventory in order to develop a plan for revamping the  evergreen-ils.org website.
       * The Communications Committee has created a smaller Website Planning Team  to focus on this work.  The Website Planning Team is being led by Jim Craner (RSCEL website developer and a long time member of other open  source communities and community development projects).       * The Communications Committee has created a smaller Website Planning Team  to focus on this work.  The Website Planning Team is being led by Jim Craner (RSCEL website developer and a long time member of other open  source communities and community development projects).
-      * The notes of the web team meetings (weekly) can be found here: http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen_community_web_team_planning_committee_page+      * The notes of the web team meetings (weekly) can be found here: [[:evergreen_community_web_team_planning_committee_page|Evergreen community web team planning committee page]]
     - **Lori Ayre:**     - **Lori Ayre:**
       * Goal: Using a transparent and formal process of needs analysis and content inventory, develop a web-based framework for the growing Evergreen community.       * Goal: Using a transparent and formal process of needs analysis and content inventory, develop a web-based framework for the growing Evergreen community.
-      * Official web page: For now it is http://evergreen-ils.org/dokuwiki/doku.php?id=communications+      * Official web page: For now it is [[:communications|Communications]]
       * **Update:**       * **Update:**
       * Very much in the planning phase.  The team is working on a planning document which we will share with the community.  We hope to identify strategic goals for a Evergreen community website.  We intend to develop these requirements by identify all the user roles.  We'll develop user stories that inform how different types of users will use the site.  That's the hard part.  Then we'll figure out the content and information architecture that makes sense to support those users and their needs. Hoping to begin planning the content and info architecture before end of year.       * Very much in the planning phase.  The team is working on a planning document which we will share with the community.  We hope to identify strategic goals for a Evergreen community website.  We intend to develop these requirements by identify all the user roles.  We'll develop user stories that inform how different types of users will use the site.  That's the hard part.  Then we'll figure out the content and information architecture that makes sense to support those users and their needs. Hoping to begin planning the content and info architecture before end of year.
Line 112: Line 111:
     - **Amy Terlaga:**     - **Amy Terlaga:**
       * The EG Governance Committee meets monthly, you can follow our activities here:  http://www.rscel.org/taxonomy/term/154       * The EG Governance Committee meets monthly, you can follow our activities here:  http://www.rscel.org/taxonomy/term/154
-      * Dan Scott just submitted our application to the Software Freedom Conservancy. [ http://evergreen-ils.org/dokuwiki/doku.php?id=governance:software_freedom_conservancy_membership_application | Text of the Application ]+      * Dan Scott just submitted our application to the Software Freedom Conservancy. [[:governance:software_freedom_conservancy_membership_application | Text of the Application ]]
     - **Why/What is Software Freedom Conservancy? (Dan Scott)**     - **Why/What is Software Freedom Conservancy? (Dan Scott)**
       * The Software Freedom Conservancy is a 501 (c) (3) that acts as an umbrella for software projects (like Sugar Labs, Boost) so that those projects don't have to set up their own 501 (c)(3) and elect directors, etc. So - a quick way to provide a 501 (c)(3) structure for an "Evergreen Software Foundation" that can be trusted to hold and enforce (if necessary) legal collateral like trademarks and copyright, as well as assets such as donations to the foundation.       * The Software Freedom Conservancy is a 501 (c) (3) that acts as an umbrella for software projects (like Sugar Labs, Boost) so that those projects don't have to set up their own 501 (c)(3) and elect directors, etc. So - a quick way to provide a 501 (c)(3) structure for an "Evergreen Software Foundation" that can be trusted to hold and enforce (if necessary) legal collateral like trademarks and copyright, as well as assets such as donations to the foundation.
Line 119: Line 118:
       * The Committee is also working on developing governance documents, i.e. bylaws (jcorridan-isl), proposals for memberships, voting and who tells the conservancy how to spend donated funds, etc.       * The Committee is also working on developing governance documents, i.e. bylaws (jcorridan-isl), proposals for memberships, voting and who tells the conservancy how to spend donated funds, etc.
   - ** Schedule next meeting **   - ** Schedule next meeting **
-    - Galen Charelton proposed that we meet again in mid-October after alpha2, hopefully after alpha3 or just before beta1. +    - Galen Charlton proposed that we meet again in mid-October after alpha2, hopefully after alpha3 or just before beta1. 
-    - The community voted on Tuesday, 19 October [14:00 ETas the next meeting date.+    - The community voted on Tuesday, 19 October (14:00 ETas the next meeting date.
  
 **Meeting adjourned by Galen Charlton (gmcharlt) at 15:16:47 EST** **Meeting adjourned by Galen Charlton (gmcharlt) at 15:16:47 EST**
dev/meetings/2010-09/minutes.1283900907.txt.gz · Last modified: 2022/02/10 13:34 (external edit)

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.