Business - Written by Guest Blogger on Wednesday, June 3, 2009 14:05 - 4 Comments
Collaborating with competitors
(Editor’s Note: Kevin Cochrane is Chief Marketing Officer for Day Software. He joins us to share Day’s experience of collaborating with competitors on an open source platform for the benefit of an industry as a whole.)
From ancient philosophers to modern day journalists, the rules of engagement for discourse and collaboration have always been hot topics. In ancient times mass collaboration was limited to communities building churches, discussion in public squares, or monks taking turns to painstakingly write text. Today, in addition to facilitating public debate online, mass collaboration has the ability to build robust and super efficient software. Collaboration is central to Day Software’s ethos. Not only is Day Software born through mass collaboration but its software has social collaboration central to its user experience. We also embrace collaboration with our competitors. The last area is one I want to focus on for this post.
Last month we collaborated with one of our key competitors, Nuxeo, in order to advance an industry standard, which will benefit the content management industry as a whole. We used the Apache Software Foundation (ASF) as our neutral “workspace”. The Apache Software Foundation provides support for the Apache community of Open Source software projects.
That word “community” is key.We teamed up with Nuxeo to advance the Content Management Interoperability Services (CMIS) standard via Apache. CMIS is designed to benefit the growing number companies that need to securely manage a wide variety of online and offline content from different applications in a central hub. This is just one of many projects that Day collaborates with their peers via Apache. On the Jackrabbit project, numerous vendors leverage the community-driven efforts of building a standardized Enterprise Content Management (ECM) repository based on open standards
Despite our competitive differences, both Nuxeo and Day share the same collaborative Open Source mindset that is central and unique to the ASF. In contrast to the more onerous General Public Licence (GPL) model, The ASF model lowers the legal and creative barriers for commercial collaboration and innovation. When you sign up to Apache your day job (excuse the pun) is irrelevant. It’s an environment ancient philosophers would be proud of; the Apache community is working together, openly, equally, without bias and everyone’s contribution is valid.
Open Source is beneficial specifically because it is not proprietary. That means that the user is not locked in to any one vendor. In community Open Source, if a given vendor were to stop innovating, the community can take the product forward. Apache enforces a simple rule: new concepts under incubation do not graduate until there is a proper community that is not beholden to any one vendor. Apache also enforces the principle benefit of Open Source: no one vendor is responsible for driving or inhibiting innovation. Innovation happens.
Commercial Open Source firms – the ones driving much press these days – do not always follow this model. For many commercial Open Source firms, community and collaboration with their peers does not happen. This limits the benefits of the Open Source model, because while the software is accessible, true participation and joint collaboration does not happen.
Contrary to conventional wisdom, collaboration actually helps us to win marketshare and revenue. By serving up the basic product interoperability that developers and customers demand, collaboration frees up our time to focus on unique customer and market driven product innovations and invest more time in services and support. We are not afraid to say we are reaping the rewards of being a collaborative company. Open Source can provide the basis for a robust and profitable business model.
For us Open Source is proving to be a very strong, yet flexible backbone for our business. This should serve as an example to other technology companies that being Open Source is of benefit both to your customers, product development and profitability. The more competitors that join the Open Source community, the better all our products and services will be.
4 Comments
Arvind Gupta
Links 07/06/2009: More Migrations to GNU/Linux in Schools, Shop | Boycott Novell
[...] Collaborating with competitors From ancient philosophers to modern day journalists, the rules of engagement for discourse and collaboration have always been hot topics. In ancient times mass collaboration was limited to communities building churches, discussion in public squares, or monks taking turns to painstakingly write text. Today, in addition to facilitating public debate online, mass collaboration has the ability to build robust and super efficient software. Collaboration is central to Day Software’s ethos. Not only is Day Software born through mass collaboration but its software has social collaboration central to its user experience. We also embrace collaboration with our competitors. The last area is one I want to focus on for this post. [...]
Arvind: great question. Today, a web developer building a new application may typically download various components like an open source database and application server and directly build his/her app directly against the RDBMS. All of the core content services the developer will have to implement atop the RBDMS – versioning, observation, access control, search, and more. And then for the next application, rebuild the entirety of that bespoke functionality again for the next app. This is inefficient.
As a backend persistance manager, RDBMSes will not go away. However, as Jackrabbit adoption grows, directly building apps atop the RDBMS will shift as developers increasingly build their content applications directly atop Jackrabbit to eliminate the need for building bespoke content services again and again and instead take advantage of the pre-built capabilities and higher level API afforded by Jackrabbit or any other JCR implementation.
Will all content applications one day be based on a standardized content repository infrastructure? Here at Day and at many other of the newer, JCR-based CMS vendors, we certainly think so.
It’s good business but too bad most competitors don’t see eye to eye on this. You tap into a source of very VERY targeted leads and create a win/win situation!
Business - Oct 5, 2010 12:00 - 0 Comments
DRM and us
More In Business
- Facebook, Facebook, Facebook
- Survey: How are you using Facebook, Twitter, smart phones, and other technology platforms?
- Will Facebook be your CRM provider?
- Wiki Banking
- The importance of being competent
Entertainment - Aug 3, 2010 13:14 - 2 Comments
Want to see the future? Look to the games
More In Entertainment
- Lessons in collaboration from B.B. King’s
- CL!CK – LEGO’s fun social product development platform
- Peer Pressure 2.0: Farmville
- Online gaming more than just fun
- The NFL – The most protective league, attempting to control the uncontrollable
Society - Aug 6, 2010 8:19 - 4 Comments
The Empire strikes a light
More In Society
- Balance: customer receptivity vs. customer revulsion
- The Net Gen: Too plugged-in for parenting?
- Are you addicted to social media?
- The privacy discussion we need to have
- “The Data-Driven Life”: Who’s not interested in discovery?

Coming soon in paperback! Help rename the paperback version of Macrowikinomics and win a one-hour webinar for you and your colleagues with Don Tapscott. Ends 5:00pm ET, August 31.
As jackrabbit evolves application will be able to collabarate more with each other. How do you see roles of database at that time?