Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Total Expenses dips into carryover, leaving $5K, not dipping into reserves.
PC is currently leading effort to expand engagement and membership which will increase income
Action items:
Craig to follow up with Wayne on next steps for Equinix
Kat confirming AWS costs with EBSCO to confirm both bugfest and performance testing are covered - will follow up with Mark Veksler
10 min.
Announcements/Updates from the Councils
Council Chairs
CC: @Simeon Warner
completed governance doc cleanup, the most substantive part of which was agreement on a uniform voting process
developed letters to folio institutions that are not members to encourage community participation and that is currently waiting on clarification of the mailing list
There was a Community Update along with PC and TC chairs and Jesse to describe Wolfcon a couple of weeks ago
Approved the budget last week as Kat just described, pending those clarifications on EBSCO support
Looking at renewing the DevOps support contract with index data, which will be discussed at the next CC meeting
PC: @Caitlin Stewart & @Alexis Manheim
Active working groups:
SIG Priorities working group
Community Driven Development
New PC Jira project to track evaluation of new functionality
councils will get an update on number of nominees May 29, 2025
nomination will run until Jun 6, 2025
election will run Jun 9, 2025 - Jun 27, 2025 may be extended through weekend
Terms start Jul 1, 2025
Recruiting new candidates
Please encourage people to self-nominate (especially from new organizations)
There are significant numbers of term-limited people rolling off councils
30 min
Eureka/Sunflower release contingencies
@Alexis Manheim@Jeremy Huff
Okapi support for Ramsons
Alexis:
Last Monday there was a discussion of Sunflower in release management meeting
Prompted a discussion a discussion of Eureka timeline
CC and PC approved Eureka with caveat that early adopters needed to feel comfortable. General consensus was that no one wants to release Sunflower or Trillium, but we also need to know that the early adopters are supported.
Tomorrow there is a meeting to discuss whether Sunflower can be released next week
Still discussing the support plan for Eureka
Jeremy:
TAMU has been working on getting Eureka set up since February. Working in parallel with GBV and Index Data with help from EPAM and EBSCO. The effort is progressing but current version does not represent something they can deploy to production yet
Currently planning to stay on Okapi until they feel confident moving onto Eureka, which will likely be sometime next year.
Will be upgrading to Ramsons soon, but this will be the last release with Okapi support.
Ultimate goal is to extend Ramsons support until early adopters are ready to move forward with Eureka.
How much would this cost?
What mechanism can we use to do that?
Multiple working groups are currently looking into community development.
Idea: tap community resources, in-kind develop contributions, to support Ramsons
This is a great opportunity to pilot community driven development in a context that is tightly scoped and urgently needed
formation of community driven development working group
Launch CDD model at WOLFCon
Preparations begin after WOLFCon, extend through March
Discussion:
Challenge: timeline - Sunflower Decision is predicated on decision around CDD
Support for a version of FOLIO impacts the entire community
If we are unable to secure adequate in-kind resources, we could pay
Trillium is an extra large release targeting October; traditionally these are quite late - may not be released until January. That means there will be support for Ramsons until that time. Theoretically there should not be P1s at this time
National Library of Sweden is dependent on this for go-live. They are working towards Eureka
Why not spend the CDD effort getting ready for Eureka? Eureka progress and Ramsons support are not mutually exclusive
Urgency of not going out of support - how big a deal is this? Many institutions choose to go out of support for a period.
Estimate may be low - need to be more specific about what is a P1, is this only P1s? Are P1s or security related? security related P1s require full Have to update and rerun tests, additional security oversight. Verifying in bugfest, communication, infrastructure (this as not accounted for in budget proposal), in addition to bugfest there must by a performance testing environment. Mark will follow up via email.
infrastructure could be in-kind contribution
Follow up on further questions will go to tri-council meeting
Sunflower go/no go decision is tomorrow - Kristin proposes going ahead with it
This is an opportunity to execute a timeboxed experiment in community development
Might be useful to do a
For some roles a minimum of 50% would be required, others 10%
Trillium needs to go out in late 2025; early adopters need until 2026 - we are already behind the eightball and if people are interested in community support regardless of council input
Action items
Decisions
, multiple selections available, Use left or right arrow keys to navigate selected items