[Board] June 2024 TEP Treasurer's report

[Katie Greenleaf Martin]

Here’s the treasurer’s report for today 😊
https://docs.google.com/document/d/1oq6UB0xOCJkxZ6RIrUMTfegWOoAQxGeH8JVuop9jphU/edit?usp=sharing

From: Board <board-bounces at list.evergreen-ils.org> On Behalf Of Lussier, Kathy via Board
Sent: Thursday, June 20, 2024 8:00 AM
To: Evergreen Project Board <board at list.evergreen-ils.org>
Subject: [Board] Report from release discussion

Hi all,

I am unable to attend the Project Board meeting today, but I told the developers during last week's release discussion that I would send a report of the discussion to the Project Board.

The release discussion came about after a discussion at the February development meeting about the timing of releases. I offered to facilitate<https://urldefense.proofpoint.com/v2/url?u=http-3A__list.evergreen-2Dils.org_pipermail_evergreen-2Ddev_2024-2DFebruary_000740.html&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=hkUaV5oeez5hwc81VrmIUg&m=5m59YmnOvyJbHRkgTldW_zNbUq0Dvvd7yuC4tC5RBIB6pey6Y7eGceYhItftQgUv&s=K3z6SEoVJr-vg3ZPuqdQpSIYtWnBkgdSRF5R44LkEPc&e=> a big-picture discussion on ways the community could improve releases.

As far as timing of releases, the group agreed that the community should continue with two time-based feature releases per year. Ruth Davis also volunteered to be the person to nudge people when a bug-fix release is due (thanks Ruth!).

We also prioritized issues that need to be addressed during the release process. The top priorities, with the most urgent being listed first, are:

  1.  Streamline / automate the release process as much as possible.
  2.  Documentation of the release process.
  3.  Encourage feature merges throughout the cycle so that they don't pile up at release time.
  4.  Communications & PR should be a dedicated release team role with a clear strategy and playbook.
  5.  Stagnation in community growth (this one actually tied with #4.)
Although automating the process was the highest priority, the group agreed that #2 - documentation - needs to come first. There was also broad consensus that the current developer community cannot address these issues on its own. What is needed is funding to pay people so that documentation and then automation are prioritized.

Stepping outside of my facilitator role for a second, I will say that I've heard the developer community talk about these two needs for years, and I firmly believe that automating the process will relieve some pressure felt by our contributors while keeping our releases on schedule.

Several Project Board members attended the session, and I'm hoping they can share their perspectives during today's meeting.I will be sharing my notes and the recording from the session with the developer community soon so that we can get feedback from those who were unable to attend.

On another somewhat related topic, I will also soon be calling the final meeting for the Membership Model Subcommittee. Apologies for the delay. May and June were somewhat busy on my end, but I expect time to free up once ALA is over.

Thank you!
Kathy
--
Kathy Lussier
she/her
Executive Director
NOBLE: North of Boston Library Exchange
Danvers, MA
978-777-8844 x201
www.noblenet.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.noblenet.org&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=hkUaV5oeez5hwc81VrmIUg&m=5m59YmnOvyJbHRkgTldW_zNbUq0Dvvd7yuC4tC5RBIB6pey6Y7eGceYhItftQgUv&s=QElIhnyGqVvnHTt7T13Ioooum40UtpEWqWWjf2cAHzo&e=>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/board/attachments/20240620/51b821c3/attachment.htm>