Hi all, I'd like to throw my hat in the ring for co-release manager for the Evergreen 3.5 release.
About me: I've been administering Evergreen in the Georgia PINES consortium since 2008 and have been actively involved in support, training, informal consulting, and software development in the Evergreen Community ever since. I have contributed to the release build team since 2018. Also in 2018, I was named a core committer for the Evergreen project and in 2019 I was named Evergreen Contributor of the Month. In my position at Georgia PINES, I have an end-user-centric perspective for both library patrons and staff, and bring a broad knowledge of public library operations, from circulation to cataloging, admin, and reports. This would be my first time as release manager. My proposal: I would like to serve as a co-release manager to someone who has been release manager before, so I can learn the process and hopefully become more skilled to be a lead release manager in the future. I would want to help shepherd in major upcoming features, such as acquisitions search improvements, Angular 8, and third-party integration (e.g. OpenAthens, RBDigital), but also smaller bugfixes that may have been neglected over the past few cycles. I hope you will seriously consider me for this role. I'm excited to get started! Sincerely, Chris On Mon, Oct 21, 2019 at 9:55 AM Galen Charlton <g...@equinoxinitiative.org> wrote: > Hi, > > It's now time to decide who will be Release Manager for the spring 2020 > release of Evergreen, Evergreen 3.5. > > The Release Manager does not have to be a core committer, but does need > to be familiar with Git and have already contributed substantially to the > Evergreen project whether it be code or documentation. > > For this release, I would like to especially encourage people to put in > proposals to be co-RMs. A pair of people acting as RM can of course help > spread out the work, but it would also be a mechanism for somebody who has > previously acted as RM to help mentor somebody who is acting as RM for the > first time. > > Nominations (including self-nominations) are due by 11:59 PM EDT on > Friday, 25 October 2019. Nominations should be made by email to > open-ils-...@list.georgialibraries.org with a Cc: to > email@example.com. Replying to all on this email > will also work. > > Nominees should send an email to both of the above mailing lists a > statement about their relationship to the Evergreen community and their > goals for the next release. The elected release manager will be expected > to follow the typical schedule for a spring release but should provide > information on when they intend to set specific milestones such as the beta > release. > > If more than one candidate is nominated, an election will be held in the > #evergreen IRC channel on freenode.net on 30 October at 15:00 EDT / 12:00 > PDT. > > Everyone is invited to participate in the voting. Evergreen core > committers who cannot make the meeting may submit their vote via email to > the open-ils-dev mailing list. > > Regards, > > Galen > -- > Galen Charlton > Implementation and Services Manager > Equinox Open Library Initiative > phone: 1-877-OPEN-ILS (673-6457) > email: g...@equinoxinitiative.org > web: https://equinoxInitiative.org > direct: +1 770-709-5581 > cell: +1 404-984-4366 > -- Chris Sharp, PINES System Administrator ------------------------------ Georgia Public Library Service 2872 Woodcock Blvd, Suite 250 | Atlanta, GA 30341 (404) 235-7147 | csh...@georgialibraries.org <https://www.facebook.com/georgialibraries> <https://www.twitter.com/georgialibs> Join our email list <http://georgialibraries.org/subscription/> for stories of Georgia libraries making an impact in our communities.