| | | |
|---|
5 min | Welcome & Announcements | @Jeremy Huff | A revised Trillium release, for the end of May, has been announced. It is recommended that PC members listen to the RMS recording, so we can address this topic in a future meeting. No PC Meetings Next 2 Week
|
3 - 5 min | Liaison Updates | @Tod Olson , @Alexis Manheim , @Jennifer Eustis | CC: no meeting TC: Pilot for review of existing modules: reviewers have been selected for mod-ebsconet and ui-export-manager Ebsconet is EBSCO’s subscription management tool, this module does the integration Charlotte: Has the linked data app been approved? Plan is to include it into T => Christie: will be evaluated next.
Discussed calendar calming proposal. There is interest in piloting that, but also some concern about the last week of the month interfering with other processes that kick off at the beginning of the month for developers. No dedicated topic meeting this week
RMS: Just a reminder that Ramsons CSP 9 will be released Jan. 14. Sunflower CSP 4 will be released Dec. 22, testing is in progress now. Proposed timeline for Trillium is to consider a functional date. Public release date of May 29th with a code freeze of April 10th. Some considerations: Sunflower is just only beginning to be adopted and need to settle with that release; libraries might have more availability to test; allows alignment with fiscal year rollovers; allows hosting organizations to ramp up and target upgrades for late summer/fall. Recording. Charlotte asked in RMS group whether Umbrellaleaf would be scheduled for fall 2026. Mark Veksler explained that flower releases are very expensive, indicated that there may be a shift to an incremental release schedule. A new release strategy should be communicated to the dev teams. A lot of teams are already done with T and they should know what they have to expect. Jeremy: Will Kong be replaced by APISIX within T? Charlotte: Work on APISIX will not hold back T if it is delayed.
|
Housekeeping |
3 - 5 min | New Topic Calendar 2026, and meeting dates | All | Alexis created calendar page for 2026. On Jan 22 2026 is Tri-Council meeting |
5 - 10 min | SIG Reports Are Due | All | Report page Jeremy reminds that there was a plan to focus more on the PC reporting to the SIGs Alexis: Community Priorities Dashboard (CPD) WG is discussing SIG update cadence Jennifer: When to review SIG prios for next year? Alexis: CPD WG covers this.
SIG prio updates take several weeks, streamline process. Charlotte: Biggest potential of priority updates is informing dev work. Cadence of prio updates should align with release cycle
|
3 - 5 min | Action Item Review | @Jeremy Huff | |
Updates on Active Initiatives |
5 - 10 min | Working Group Check-in | All | Working Groups
Charlotte reports that at the PO meeting Anne E. presented new way how to communicate implemented features more human-friendly instead of list of UXPROD tickets (recording) Community Priorities Dashboard WG: |
New Topics |
10 - 15 min | Calendar Calming Feedback | @Charlotte Whitt | Proposal: Update and Next Steps A discussion evolves on the feedback given. Feedback is mainly on new groups already having problems finding meeting slots. Charlotte proposes to see this as two different things. Some groups are already switching from weekly to biweekly.
TC has concerns regarding dev processes, but are wlling to go further.
Jennifer: Data Import SIG will alternate business meetings and working labs
Kristin: Alternating SIG meetings and working sessions (for subgroups etc.) may be a good way to go
Christie: Hopefully getting groups to be more efficient than blocking more of people’s time.
The discussions on he proposal are mixing two different goals: Jeremy proposes to implement proposal for PC’s meetings on January-March PC decides that in January, February, and March there will be no PC-owned meetings (business, agenda planning, working groups) during the last week of each month
|
– discussed up to here – |
10 - 15 min | Identification of Integrating Tools | All | |
Planning |
5 min | Newsletter topics | All | |
10 min | Define agendas for next 2 meetings | All | |