| Recent
Articles |
The Transition's Happening
The introduction of consumer-driven Web 2.0 technologies into businesses is set to usher in a new phase of productivity growth that could surpass that achieved...
What Do You Want To See From An MSS
One of the hallway conversations we have been having lately is what would a customer want to see in a...
It's Good To Have Ajax And Ruby Skills
The San Jose Mercury News has an interesting viewpoint on the desirability of web developers that can both code, and understand the requirements or ways that...
Courts: It's Ok To "Google" Employees
More than ever, it is important for people to know what "Google has on them". A recent court ruling indicates that employers can use data pulled up in a Google...
Are There Enough Developers?
One of the things that was apparent in 1995 through 1999 was that developers, really good developers were hard to find. In 2007, we are facing the same crunch...
|
|
|
08.03.07
Time To Unleash Web 2.0 With Open Source
 By Ross Mayfield
Web 2.0 companies are largely built upon Open Source software. But how many of them do you consider significant contributors to Open Source?
In general, there is an open ethic, and communities demand (and reward) it. But somewhere along the way, the focus shifted to APIs and Open Source wasn't rationalized as part of the business model.
Some call them Open APIs or Open Data, but until there is a legal framework adhered to as community standard (word is OSI will work to address this), they are just APIs with unilateral rights. And with the focus on APIs, instead of contributing code back to the projects you leverage, or contributing your own projects, cooperation has been limited (save a handful of great standards efforts like Atom) Business models have also been held back by the gradual evolution of Open Source licensing, until now.
The Common Public Attribution License (CPAL) meets commercial needs for both attribution and network use (the SaaS loophole). My hope is to see:
• Web 2.0 companies seriously considering what portions of their codebase could be Open Source licensed for their own benefit. As well as taking an inventory of what they use for the purpose of what they should give back.
• MPL+Attribution companies adopting CPAL because they want to be Open Source and part of the community
• Enterprise 2.0 SaaS providers reconsidering their business model with the one Open Source license that closes the SaaS loophole
• Enterprises considering what portion of their erstwhile custom in-house codebase could now be made available under CPAL
• Portal companies thinking beyond how they have the coding power to write around attribution and consider which of their projects could be licensed with it
• New Commercial Open Source ventures
• Native Open Source projects address the SaaS loophole and bring attribution back to their community because of the positive incentives it provides for innovation.
Dan Bricklin has written a practical guide for applying CPAL to your product.
I should say my first paragraph is a generalization. There are lots of Web 2.0 companies that are great citizens of Open Source and some make it part of their business model, like Wordpress and recently Six Apart. Some Portals make great contributions, but again, my impression is that they have played into the API parlay. To defeat this generalization, there is almost a need for a wiki that lets people openly inventory the open source products leveraged, licenses used and contributions back.
Comments
About
the Author:
Ross Mayfield is CEO and co-founder of Socialtext, an emerging provider of Enterprise Social Software that dramatically increases group productivity and develops a group memory.
He also writes Ross Mayfield's Weblog which focuses on markets, technology and musings.
|
|
