Archive for the ‘Evergreen’ Category

h1

“Of things to come”, the TL;DR version

2014-01-22

My colleague and former coworker Mike Rylander wrote a blog post about Equinox Software’s new services. The writing was a little bit formal, so I’m rewriting it in the spirit of a friendly amendment. What I think he meant was:

Equinox Software solves problems for libraries using Open Source software. We use Open Source because it’s powerful, and because it lets us help a lot of libraries. Open Source is not just a way of making software—Open Source is also a way of making communities of people who can help each other. That’s how people make Android phones, Google Chrome, and Ubuntu Linux. Open Source also means working together to create projects that benefit many people, and libraries love working together to create projects like that! So it’s a great fit.

Making Open Source software is exciting, but after the excitement fades, we have to work together to keep it in good shape. Sometimes volunteers will help out. When there aren’t enough volunteers, it’s important to know that there are people who find and fix bugs, and add new features. It’s important to be able to rely on the fact that someone out there will continue to improve Open Source software. Service providers—companies that do Open Source for a living—are a good way of being sure that community software will stay healthy.

Volunteers are crucial to Open Source. Most volunteers use the software and discover something they want to improve. Volunteers rarely have enough free time to see the big picture. Usually, volunteers study the part of the software they want to improve, then work on that part. When software gets complicated—and library software is complicated—some of the people working on it need to have enough time to see the big picture. All the parts have to work together smoothly. You don’t want anyone to have to reinvent the wheel. (Unless it’s a really awesome new wheel, in which case, go for it!) It’s better and cheaper to work with a good plan. So we need people who have enough time in their day to think about the big picture. Service providers can pay programmers who learn the software in depth, who can suggest plans for the community to consider.

We at Equinox Software have been thinking about the big picture. We know that Open Source software communities need to solve some long-term challenges. We’re going to be announcing some new services at ALA Midwinter that we hope will help the Evergreen and Koha communities to thrive for a long time. Stop by booth 541.

TL;DR: Long-range plans are a big deal for Open Source, and service providers like us can help.

Mike, is that more or less what you meant?

h1

My new job: Horizon vs. Evergreen cage match

2007-10-04

I’ve been hired as a consultant for the University of Utah for a one-year gig. (Actually, it’ll be a little less than a year, since the LSTA money has to be spent by September 1, 2008.)

They’ve been using SirsiDynix’s Horizon ILS for a while now, and they’ve asked me to conduct a feasibility study on using Evergreen. I’m going to be figuring out how well it works with their data, their workflows, and their business needs, and identifying any potential trouble spots.

I’m thrilled that Evergreen is being seriously considered by large university libraries. I’m not a zealot, though; for example, my preference for a desktop operating system is “whatever seems to work pretty well in the given situation”. I won’t hesitate to burninate Evergreen’s faults, whatever they may be. After all, my report is only valuable to the extent that it corresponds with reality.

In that spirit, I welcome propaganda from all sides. If you’re a SirsiDynix fan (or employee), and you want to point out Evergreen’s most serious flaws, please do. I’ll be glad to verify your comments in the course of forming a well-informed opinion. Similarly, if you’re an Evergreen fan and you want to point out its features or defend it against defamation, I’d love to hear tips about how to verify the truth.