Likewise CEO Offers Suggestions on Minimizing Risks (and Taking Smart Ones)
by Kristin Shoemaker - Mar. 25, 2009Comments (1)- Related Blog Posts
- Open-Xchange and SugarCRM Join Forces to Integrate and Share Data
- Windows (L)users Are People, Too
- Military Medicine Foundation Opts for Open Solution With Bluenog
- The Great Software Freedom Debate, Part 368
- Sun Exec Proposes Software Freedom Definition and Vendor Scorecard
As OSBC kicks in to high gear, speakers, attendees, and organizers have been relaying information and insights from the event with those that couldn't make the trip to San Francisco. Barry Crist, of Likewise Software, is no exception.
After attending a session led by Google's Chris DiBona and Intel's Dirk Hohndel on the risks associated with migrating businesses to open source software, Crist offered some further thoughts on how to approach open source licenses.
Crist believes that many companies are intimidated by open source licensing because they are presented with legal minutia early in the adoption process. He says that while it's unacceptable to work with open source without putting any effort into learning how the licenses work, planning ahead and having knowledgeable resources on tap to field questions makes open source no more risky -- or perhaps considerably less hazardous -- than working with closed platforms. It's sometimes hard to get the process in motion, he says, and this is what prompted him to put together his list of "actionable advice."
A few points he makes are particularly worth noting. Migration to an open source environment shouldn't be done alone, especially if your company is completely inexperienced in this arena. He recommends at the very least consulting an attorney specializing in open source (one that will explain the risks, benefits, and things to be aware of, not one who simply points out risks). He also urges companies to call in an experienced open source project manager. The open source process is a different one, and consulting with someone experienced can ensure that your first open source project isn't your last.
Another point Crist mentions is uniquely open source: Develop and operate in good faith, and try to do the right thing. It will get you everywhere, or at the very least, make those rough spots a little easier. This has been mentioned by others in open source; when a company puts forth a good faith effort to rectify any compliance issues, there are rarely any legal repercussions. Crist's advice goes beyond the purely legal standpoint, however. Don't upset your development community, or the community behind the source code you're modifying -- while legal woes can be mitigated with capable lawyers, it isn't so easy to win back the trust of a community.
Understanding and embracing open source licensing in a conceptual sense is one thing, but applying those concepts to your business and charting a course forward is another matter completely. Crist has laid out a few solid, smart first steps in making this transition. His first two bits of advice -- obtaining help from open source-savvy lawyers and project managers -- can turn your company's smart baby steps into confident leaps forward.
