This past Thrusday, October 10, was the second Equinox Community Day. I introduced Community Day last month, and this month was just as big of a success. There was some follow up from the work done in September and several new projects, too.
Interestingly, I received several private requests from other community members to direct some attention at their favorite bugs. That’s good, if somewhat unexpected — I personally welcome such requests, and I’ll keep them in mind when community day rolls around — but I would also encourage discussion on the -dev and -general lists. Bugs that are causing your site pain will almost always benefit from a public champion, and you may find that others are in the same boat with you. It’s possible they think they’re the only ones suffering from a particular problem, and it may be the same issue you’re experiencing.
Again this month my coworkers exhibited the kind of enthusiasm that makes me so proud to be at Equinox. In an effort to highlight those efforts without further delay, I’m forgoing the silly titles portion of this Community Day update. Here are some of the highlights, without further ado:
- Erica Rohlfs worked on wrangling some of the Evergreen wiki, with an assist from Jason Etheridge.
- Jason also preformed some refactoring of the Debian Wheezy installer for Evergreen, moving us closer to the day when we will have fully-automated CI testing.
- Lebbeous Fogle-Weekley completed pre-testing work on the new Stripe payment processor for online billing that he began at the hack-a-way last month.
- Galen Charlton, release manager for Koha 3.14, reviewed and pushed a large set of patches for Koha, integrating work from Mathieu Saby, Frédéric Demians, Janusz Kaczmarek, and Jared Camins-Esakov. These improve UNIMARC support in Koha and provide the ability to merge authority records. Galen also revamped Koha’s test cases for Zebra indexing and searching, setting the stage for future work that can include adding tests for NORMARC indexes as well as adding more test records.
- Grace Dunbar created two new design mockups to help improve the Evergreen downloads page on the community site, forwarding them on the the Evergreen Web Team, and also began revamping the FulfILLment web site.
- Steve Callender produced a patch to address complaints of pre-cat copies retaining their “dummy” title and author info after becoming fully-cataloged items.
- Dale Rigney worked on confirming bug 1227344 was still an issue in 2.3, and it’s since been fixed via backport by Dan Wells.
- Brad LaJeunesse identified a sponsorship opportunity for Equinox to assist the Evergreen community, specifically for the annual Evergreen conference.
- Bill Erickson merged a set of integration tests that Jason Etheridge had previously created, and then created a set of unit tests of his own for bibliographic record retrieval and overlay.
- I worked with Bill to finish up the work we started last month on a new SIPServer implementation based on IO::Multiplex. This has both Evergreen and SIPServer components, each of which is needed to take advantage of the new server personality. We’re pretty happy with where it is now, and feel it’s ready for broader testing.
- I spent a chunk of time looking over one of the final 2.5 bugs relating to the Authority-enhanced Bib Browse that Lebbeous spearheaded and that I had the chance to contribute to. That ended, the next day, in consensus that the current approach to the fix is good enough for 2.5, which is great news for folks wanting proper browse functionality.
- The Evergreen community is starting to see some contributions from folks at OmniTI, and I worked to bring one of their proposed optimizations up to feature parity with the existing code. There’s more to do, and much testing will follow because the changes I needed to make were relatively substantial, but I’m heartened to see others putting work into database micro-(and sometimes not-micro)-optimization efforts!
- Several ESI’ers, myself included, also spent some time doing bug triage and providing feedback on some of the Lauchpad entries that each felt they could contribute to usefully.
As I mentioned last month, I plan to publish an update along these lines after each Community Day. We’re still scheduling Community Day for the second Thursday of each month, so look for the next update soon after November 14th.
We’re each individually proud to be part of these great Open Source communities, and I’m excited by all of the hard work that my coworkers do in support of the projects we’re involved with. Their contributions deserve mention, and so you will be seeing more of this from us.
Also as before, I want to encourage other organizations to highlight the contributions of their staff, especially when it is self-directed and for the love of the software. What have your folks been up to recently?