-
Notifications
You must be signed in to change notification settings - Fork 65
Steering Committee 201804 Minutes
CORAL Steering Committee Meeting
Minutes
April 10, 2018
Xiaoyan Song, Heather Wilson, Jeffrey Mudge, Scott Vieira, Remington Steed, Tommy Keswick; Eric Hartnett; Carla Clark, Matthias Meusburger
There are three remaining pull requests, that need to be merged. Committee members were unsure how they might test the Oauth feature. An agreement made that Jeff would read through the code, and the main concern is that this does not break anything.
Tommy volunteered to test the feature regarding licensing.
The goal is to announce that the beta release is available after these three requests are merged, on Wednesday, April 11. The release notes are still being refined. The draft release notes will be available on GitHub. Once beta is released, Heather will create a press release and post on the CORAL site. We will not post a link to download beta, anyone interested download through GitHub. The link to download will be posted after GA.
Heather will be sure to call out that the documentation and release notes are still being polished. A fresh install should work as usual. Tommy has been testing the upgrade and it has been working fine. Tommy will create some brief notes about upgrading. For the time being, the instructions for upgrading to 2.01 should be sufficient.
If sites have questions, they should refer to GitHub for now, or post general questions to the mailing list. If someone finds a bug, they can go to GitHub, and open an issue.
Also, there is a chat room available in IRC.
The committee agreed to have a review call two weeks after beta is released. Assuming no major blockers, then a release candidate will be available for one week, and then GA.
Carla asked if Texas A&M would update the demo instance on the web site and point people to that one for testing. Matthias observed that without an API key, it will be difficult to test the EBSCO integration. Carla will ask EBSCO for a temp key.
The committee also discussed the labels on issues. Are the labels “SC Review” and “SC Approved” still providing value? The consensus was that if you are a developer/creator, then you should add the tag when the story merits SC review, and you are responsible for alerting the SC. If an issue was created by a non-developer, then the devs who are active in GitHub may decide to add the “SC Review” label, and once you add the label you are also responsible for alerting the SC. The committee agreed that the labels are still desirable if a process for reviewing and approving is defined and followed.
Yan suggested that we consider adding a column to the project board that captured any issues with the “SC Review” tag, but there was no final decision to try this approach.
The committee agreed that we should continue to refine the roadmap, and to encourage new developers to address roadmap items when they are good candidates for newer devs.
BibLibre and SD are working on ILS processes to move acquisitions data to and from an ILS. BibLibre is focused on Koha, SirsiDynix is working on Symphony and Horizon. SirsiDynix is considering an integration with the ProQuest KB, but Carla will need to get approval from her executives, so no promises yet.
Tommy is going to pitch a project to a UX class at Cal Tech to look at CORAL. If you have any comments or questions that might be useful for Tommy when he visits the class, please contact him.
*My notes are too sketchy to add anything meaningful here
(From Remington) On April 9, 2018, Paul Poulain emailed the coral-admin list that BibLibre will be hiring an intern to work on CORAL from June to August of this year. The focus will be merging the separate module databases into a single CORAL database (removing duplicate tables, etc.). (There is a related GitHub issue: https://github.com/coral-erm/coral/issues/65)
Yan reported that Eastern Carolina University is interested in joining the Steering Committee. They have a new e-resources librarian, and they have IT staff, and would like to have the e-resources librarian and one dev on the SC if possible. They do use CORAL currently.
Yan will send a letter of introduction to Steve for the SC to consider.
Scott added that we should need new members on the Web Committee, so please consider serving.
Yan mentioned the NASIG webinar on April 26th.
Meeting adjourned