dev:meetings:2010-09:minutes
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
dev:meetings:2010-09:minutes [2010/09/10 09:23] – Proper crediting of planned work miker | dev:meetings:2010-09:minutes [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 12: | Line 12: | ||
- 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' | - 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' | ||
- 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 | + | * **ACTION ITEM:** Dan Scott will update |
- ** 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' | - 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' | ||
- 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 Terlaga pointed out that there is a basic (not complete) roadmap/ | + | - Amy Terlaga pointed out that there is a basic (not complete) roadmap/ |
* **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:// | + | - Dan Scott has some reasonably accurate notes for Debian Squeeze [[zzz_archive: |
- 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' | + | - KCLS will be using FGI to rework their web catalog screens so that they' |
- ** 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 57: | Line 57: | ||
- Amy Terlaga: 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/ | + | - Dan Scott: University of Windsor is seconding him to work full time on Evergreen on behalf of [[http:// |
* 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/ |
* 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:// | - Jason Stephenson: Using lassos in the circ and hold matrices: https:// | ||
* **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 ** | ||
- | + | | |
- | | + | |
- Documentation is being converted to DocBook XML format and committed to a github repository set up by Robert Soulliere at http:// | - Documentation is being converted to DocBook XML format and committed to a github repository set up by Robert Soulliere at http:// | ||
- 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. | - 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. | ||
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:// | + | * 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: [[: |
* 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 93: | Line 92: | ||
* The Evergreen Communications Committee was formed at the Evergreen 2010 Conference and has been charged with helping to organize (and possibly | * The Evergreen Communications Committee was formed at the Evergreen 2010 Conference and has been charged with helping to organize (and possibly | ||
* 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:// | + | * The notes of the web team meetings (weekly) can be found here: [[: |
- **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:// | + | * Official web page: For now it is [[: |
* **Update:** | * **Update:** | ||
* Very much in the planning phase. | * Very much in the planning phase. | ||
Line 112: | Line 111: | ||
- **Amy Terlaga:** | - **Amy Terlaga:** | ||
* The EG Governance Committee meets monthly, you can follow our activities here: http:// | * The EG Governance Committee meets monthly, you can follow our activities here: http:// | ||
- | * Dan Scott just submitted our application to the Software Freedom Conservancy. [ http:// | + | * Dan Scott just submitted our application to the Software Freedom Conservancy. [[: |
- **Why/What is Software Freedom Conservancy? | - **Why/What is Software Freedom Conservancy? | ||
* 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 " | * 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 " |
dev/meetings/2010-09/minutes.1284125027.txt.gz · Last modified: 2022/02/10 13:34 (external edit)