<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:11.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:2034065914;
mso-list-template-ids:-157760736;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Here’s the treasurer’s report for today
</span><span style="font-size:11.0pt;font-family:"Segoe UI Emoji",sans-serif">😊</span><span style="font-size:11.0pt">
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><a href="https://docs.google.com/document/d/1oq6UB0xOCJkxZ6RIrUMTfegWOoAQxGeH8JVuop9jphU/edit?usp=sharing">https://docs.google.com/document/d/1oq6UB0xOCJkxZ6RIrUMTfegWOoAQxGeH8JVuop9jphU/edit?usp=sharing</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Board <board-bounces@list.evergreen-ils.org>
<b>On Behalf Of </b>Lussier, Kathy via Board<br>
<b>Sent:</b> Thursday, June 20, 2024 8:00 AM<br>
<b>To:</b> Evergreen Project Board <board@list.evergreen-ils.org><br>
<b>Subject:</b> [Board] Report from release discussion<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi all,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">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.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The release discussion came about after a discussion at the February development meeting about the timing of releases. I
<a href="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=">
offered to facilitate</a> a big-picture discussion on ways the community could improve releases. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">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!).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">We also prioritized issues that need to be addressed during the release process. The top priorities, with the most urgent being listed first, are:<o:p></o:p></p>
</div>
<div>
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Streamline / automate the release process as much as possible.<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Documentation of the release process.<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Encourage feature merges throughout the cycle so that they don't pile up at release time. <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Communications & PR should be a dedicated release team role with a clear strategy and playbook.<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Stagnation in community growth (this one actually tied with #4.)<o:p></o:p></li></ol>
<div>
<p class="MsoNormal">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.<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">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.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">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.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">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.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thank you!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Kathy<o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">--<o:p></o:p></p>
</div>
<p class="MsoNormal">Kathy Lussier<o:p></o:p></p>
<div>
<p class="MsoNormal">she/her<o:p></o:p></p>
<div>
<p class="MsoNormal">Executive Director<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">NOBLE: North of Boston Library Exchange<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Danvers, MA<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">978-777-8844 x201<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="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=" target="_blank">www.noblenet.org</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>