Interesting thread on InfoQ regarding open source business models:
http://www.infoq.com/news/2007/06/open-source-models
Rod Johnson and Stormy Peters are engaging in the debate of which model is better: "Create & Support" vs. "Pure Support". This topic has gone round and round in the past, and I think the heart of the debate lies in the definition of "Support".
The "Pure Support" model should actually be called "Technical Assistance" since it focuses on helping people get over technical issues, find workarounds, etc.
Technical assistance is important, but what happens when the issue requires a bug fix...or a refactoring of some of the code? Then what?
The code can be changed...but who manages that change? And if that code is part of a complicated stack of open source technologies...who is managing all the patches and branches of all those changes?
Also...who ensures that change is committed upstream so that future releases of the technology benefit from the change? If the changes are not committed upstream...then who will maintain that fork for the X-years lifecycle that enterprise customers demand?
Let's be real. While enterprise customers need technical assistance, they also need patches and updates to the versions of the software they have deployed today...and they want the peace of mind that comes with knowing that their fix today will still be there in future versions if/when they upgrade.
So, this explains why we at JBoss hire the key technical leaders from the projects that comprise our middleware portfolio. THIS is Professional Open Source.
Professional Open Source is not just Technical Assistance.
Thursday, June 21, 2007
Tuesday, May 15, 2007
So, How's Life After Marc Fleury?
I was at the Red Hat Summit in San Diego last week and we had a capacity crowd of attendees, with lots of press and analysts attending the event as well. There was a lot of interest in our Open Source Architecture and our Developer strategy.
A variety of people also asked the question: "So, how's life after Marc Fleury?"
My thoughts on Marc's departure remain unchanged from my JBoss Reloaded blog in March. "Marc was never shy to speak his mind, and that fact helped keep JBoss in the news as much as our great technology did. Marc's persona fueled love/hate feelings forever preserved on the Internet; if you Google "Marc Fleury", you will get hundreds of thousands of hits. Love him or hate him, you have to give Marc props for taking a huge risk in 1999 and creating a software business that was valued at $350M in June 2006."
The recent article by Tom Sanders accurately quotes me in some aspects but sums things up in a misleading way. I do not think that "Marc Fleury's oversised ego stood in the way of partnerships, according to JBoss vice president - product management. ". And I do not credit our continued growth to Marc's departure.
I believe my thoughts above are clearly stated in my JBoss Reloaded blog. Marc Fleury absolutely has a lightning rod personality, and that fact helped make JBoss the success it is today. As part of Red Hat, however, JBoss Reloaded is less about one person. Things are different because folks like Sacha Labourey and Bob McWhirter have their own way of doing things. The new look at JBoss.org is just one example.
While I am quite happy with the success JBoss is having as part of Red Hat, I do not credit that success to one person joining...or one person leaving. We've got a great team of folks focused on the success of JBoss.
So, how's life after Marc? Fast-paced, exciting, and in the eye of the open source storm. While some things have changed...other things remain the same.
A variety of people also asked the question: "So, how's life after Marc Fleury?"
My thoughts on Marc's departure remain unchanged from my JBoss Reloaded blog in March. "Marc was never shy to speak his mind, and that fact helped keep JBoss in the news as much as our great technology did. Marc's persona fueled love/hate feelings forever preserved on the Internet; if you Google "Marc Fleury", you will get hundreds of thousands of hits. Love him or hate him, you have to give Marc props for taking a huge risk in 1999 and creating a software business that was valued at $350M in June 2006."
The recent article by Tom Sanders accurately quotes me in some aspects but sums things up in a misleading way. I do not think that "Marc Fleury's oversised ego stood in the way of partnerships, according to JBoss vice president - product management. ". And I do not credit our continued growth to Marc's departure.
I believe my thoughts above are clearly stated in my JBoss Reloaded blog. Marc Fleury absolutely has a lightning rod personality, and that fact helped make JBoss the success it is today. As part of Red Hat, however, JBoss Reloaded is less about one person. Things are different because folks like Sacha Labourey and Bob McWhirter have their own way of doing things. The new look at JBoss.org is just one example.
While I am quite happy with the success JBoss is having as part of Red Hat, I do not credit that success to one person joining...or one person leaving. We've got a great team of folks focused on the success of JBoss.
So, how's life after Marc? Fast-paced, exciting, and in the eye of the open source storm. While some things have changed...other things remain the same.
Friday, April 27, 2007
JBoss Enterprise Application Platform 4.2 Beta is Available
On Tuesday, we announced our New Development, Distribution, and Support Model for JBoss. As followup to that announcement, we have released the JBoss Enterprise Application Platform 4.2 Beta. Congratulations to the development team and community for helping us pull this Beta together!
You can access the Beta download from the JBoss Enterprise Middleware Downloads page.JBoss Enterprise Application Platform integrates the following open source JBoss technologies for building, deploying and hosting enterprise Java applications and services:
- JBoss Application Server 4.2
- Apache Tomcat 6
- JavaServer Faces 1.2
- JBoss Clustering, Cache and Messaging
- JBoss Transactions JTA
- Hibernate
- JBoss Seam
This Beta Release represents an opportunity to evaluate the JBoss Enterprise Application Platform before its widespread production release. It is intended as a technology preview in order to allow users to explore its capabilities and evaluate its suitability for their needs. Please deploy it in testing and evaluation environments only.
Your feedback on this technology preview is valuable to us, and is an integral part of making this the most stable Enterprise Application Platform possible. Please raise any concerns that you have or issues that you encounter by opening an issue in our JIRA Issue Tracking System at http://jira.jboss.com/jira/browse/JBPAPP. Please bear in mind that the JBoss Enterprise Application Platform Beta is a technology preview and will not have a support SLA until its final release.
Tuesday, April 24, 2007
Driving Developer Preference
JBoss' success has hinged on grassroots adoption by developers and users of our open source technologies. Thank you for your support over the years! With our relaunch of JBoss.org, we are hoping to fuel that innovative spirit further and keep our users informed and excited about our new technologies and directions.
There are many types of developers, of course. While many will download our open source components and tools and support themselves via our forums and wikis, many corporate developers just want a set of solid tools they can use and a well tested platform to develop and deploy on. While they may think innovation is cool...and will factor it into future applications...stability is what gets deployed today. They have a job to do and want vendors like Red Hat to make their lives simpler.At Red Hat, we are focused on driving preference for our Open Source Architecture as early in the development lifecycle as possible. So, we are building on the grassroots relationship JBoss has with developers and consolidating our developer-related efforts into a single strategy across all of Red Hat.
Towards that end, we have launched the following new subscriptions:- Red Hat Developer Professional is designed for corporate developers and individuals.
- Red Hat Developer Enterprise is designed for Independent Software Vendors, larger development organizations and mission critical development projects.
- Red Hat Developer Studio is an Eclipse-based development tools environment that integrates tools for Linux, Java, and Web 2.0 application development.
The Red Hat Developer Studio subscription is due out in the summer timeframe and will integrate all of our Eclipse-based tools, including the Exadel Studio Pro and Ajax technologies, into a development environment that works well with and includes our certified platforms. So, developers will not only get the tools but also access to our certified JBoss and Red Hat Enterprise Linux platforms.
This is a first step, of course, and as always, if you have cool ideas for other things we should be doing to help developers, just let us know.Sunday, April 8, 2007
OFF TOPIC: Thank You Sir, May I Have Another
I had the pleasure of spring skiing with my family in Alta, Utah this past week. This was our first time skiing "for real"...meaning taking a lift that brings you up to 10,450 feet.
If you've never skied in April...do it! And if you are looking for a nice place to stay, check out Rustler Lodge in Alta, Utah.
Thank you Rustler...we look forward to our next trip to Alta.
Typical of any vacation, I returned to a ton of emails...but one email in particular caught my eye. The email was from Andy Oliver, longtime JBoss developer now doing his own thing at Buni.org.
Andy read the two blogs I posted on March 31 right before I headed out on vacation. Admittedly, those blogs could have used a bit more editing...but I had a plane to catch and slopes to conquer so I quickly wrote and posted them and put up my "On Vacation" sign.
Anyhow, Andy's email basically said: "Dude....write less!".
Good advice for bloggers in general...and I'd like to thank Andy for the Buni-slap...I really do appreciate the feedback.
Saturday, March 31, 2007
Building A Great Open Source Architecture
For the past 3 years, we have been busy building out JBoss Enterprise Middleware as the Open Source Platform for SOA. During this time, we have been very consistent in our stance that SOA needs to be Simple, Open, and Affordable. We contend that SOA technologies should be available to all, not just the privileged few who can afford the HUGE license costs.
This approach delivers real value to our customers. And since joining Red Hat last June, there are more and more people around the world who want to understand our strategy, product roadmap, etc.
I use a set of 3 graphics to describe our product strategy. These are designed to illustrate how I see the open source market - one graphic for last year, this year, and next year. The color coding on the slides is meant to illustrate the level of pain (threat level) that proprietary vendors are feeling due to open source competitors.
Needless to say, Operating Systems a la Red Hat, Web Servers a la Apache, Developer Tools a la Eclipse, and App Servers a la JBoss are causing high and severe alert levels for the proprietary vendors. Portal, Business Process Management (BPM), and Integration markets have been gaining ground and should generate strong momentum into 2008 and beyond.
I actually use these graphics for two purposes: 1) to explain to people how open source is penetrating software market areas that are relevant to Red Hat / JBoss, and 2) as a radar screen, of sorts, that I personally use to help identify strategic areas of opportunity/expansion.
For example, looking at the pace of BPM, Portal, and Integration, I ask myself: what things can I do to accelerate those areas. This is why you have seen JBoss spend considerable time and effort over the past two years on building out technologies such as JBoss jBPM, JBoss Rules, JBoss Portal, and JBoss ESB.
So, mapping all of this back to the bigger Red Hat Open Source Architecture strategy yields a product map that looks something like this:
This architecture, from left to right, covers the typical lifecycle areas of Develop, Deploy, Secure, and Manage. I believe we have a pretty impressive array of open source technologies in our architecture today, and I point you to the the recent reactions of some of the major sofware vendors in the industry as proof positive that the threat levels I illustrate above are accurate and real.
In my Open Source Strategy: Freeing Great Technology blog, I outlined the different approaches we take towards expanding our base of open source technologies. With this in mind, I encourage you to stay tuned over the course of 2007 and beyond as we continue to rollout new technologies and services focused on driving real customer value. The fact that this will have the net effect of turning up the heat on our proprietary competitors is icing on the cake.
What areas will we expand into next? Well...you'll just have to wait and see, now won't you? ;-)
This approach delivers real value to our customers. And since joining Red Hat last June, there are more and more people around the world who want to understand our strategy, product roadmap, etc.
I use a set of 3 graphics to describe our product strategy. These are designed to illustrate how I see the open source market - one graphic for last year, this year, and next year. The color coding on the slides is meant to illustrate the level of pain (threat level) that proprietary vendors are feeling due to open source competitors.
Needless to say, Operating Systems a la Red Hat, Web Servers a la Apache, Developer Tools a la Eclipse, and App Servers a la JBoss are causing high and severe alert levels for the proprietary vendors. Portal, Business Process Management (BPM), and Integration markets have been gaining ground and should generate strong momentum into 2008 and beyond.
I actually use these graphics for two purposes: 1) to explain to people how open source is penetrating software market areas that are relevant to Red Hat / JBoss, and 2) as a radar screen, of sorts, that I personally use to help identify strategic areas of opportunity/expansion.
For example, looking at the pace of BPM, Portal, and Integration, I ask myself: what things can I do to accelerate those areas. This is why you have seen JBoss spend considerable time and effort over the past two years on building out technologies such as JBoss jBPM, JBoss Rules, JBoss Portal, and JBoss ESB.
So, mapping all of this back to the bigger Red Hat Open Source Architecture strategy yields a product map that looks something like this:
This architecture, from left to right, covers the typical lifecycle areas of Develop, Deploy, Secure, and Manage. I believe we have a pretty impressive array of open source technologies in our architecture today, and I point you to the the recent reactions of some of the major sofware vendors in the industry as proof positive that the threat levels I illustrate above are accurate and real.In my Open Source Strategy: Freeing Great Technology blog, I outlined the different approaches we take towards expanding our base of open source technologies. With this in mind, I encourage you to stay tuned over the course of 2007 and beyond as we continue to rollout new technologies and services focused on driving real customer value. The fact that this will have the net effect of turning up the heat on our proprietary competitors is icing on the cake.
What areas will we expand into next? Well...you'll just have to wait and see, now won't you? ;-)
Then they fight you. Then you win.
Mohandas Gandhi's quote actually goes: "First they ignore you. Then they laugh at you. Then they fight you. Then you win."
This quote has been a rallying cry for many years at Red Hat, and is oh-so-appropriate given the shenanigans going on in the software market these days. Let's focus on two major proprietary software vendors shall we? In order to protect their identities, I will simply refer to them here as....Thing 1 and Thing 2.
Thing 1 says he will just take our technology and make it his own. He reasons that this will help him deliver more value to his customers. Hello!! The BIG COSTS for customers are in the layers on top. I suggest you read my Building A Great Open Source Architecture blog for an illustration of the technology areas I refer to and how open source is poised to deliver more value in those areas.
Now...let's talk about Thing 2. They offer an entry level product that is "based on open source" as an onramp to their complex, proprietary, and expensive stack of products that they are really focused on selling. And in the process....get this...this is the best part...they claim they are actually more open source than we are. Now THAT is great marketing folks! They have a tiny sliver of their stack "based on open source" and that makes them more open source than JBoss. Read my blog on Open Source Community for my thoughts on that topic.
Anyhow, the interesting news is that Thing 2 is spending time building and marketing what I call a bridge to the past. They have built some tools that help people move away from our innovative and fully featured open source platform for SOA to their low-end "children's edition" onramp. The problem is that their onramp only provides a thin sliver of the functionality that people need for their SOA initiatives....so....oh darn....I guess that means people will just need to buy the other complex proprietary stuff in their portfolio...for real license $$'s. This "bridge to the past" will truly be the gift that keeps giving....only their customers are not the ones receiving the gift, if you know what I mean.
So why are Thing 1 and Thing 2 fighting us so vigorously?
Because they are not happy that we are successfully building out a complete open source platform for SOA that not only encompasses the Operating System and Application Server...but also covers the market areas of Portal, BPM, and Integration among others.
They see our big picture. They see our great technology and services. And they will do whatever it takes to preserve the lock-in and huge license fees provided by their big proprietary stacks.
Thing 1 and Thing 2 are more focused on trying to slow us down, rather than on delivering increased value to their customers. And I believe customers and the market in general are smart enough to see that.
This quote has been a rallying cry for many years at Red Hat, and is oh-so-appropriate given the shenanigans going on in the software market these days. Let's focus on two major proprietary software vendors shall we? In order to protect their identities, I will simply refer to them here as....Thing 1 and Thing 2.
Thing 1 says he will just take our technology and make it his own. He reasons that this will help him deliver more value to his customers. Hello!! The BIG COSTS for customers are in the layers on top. I suggest you read my Building A Great Open Source Architecture blog for an illustration of the technology areas I refer to and how open source is poised to deliver more value in those areas.
Now...let's talk about Thing 2. They offer an entry level product that is "based on open source" as an onramp to their complex, proprietary, and expensive stack of products that they are really focused on selling. And in the process....get this...this is the best part...they claim they are actually more open source than we are. Now THAT is great marketing folks! They have a tiny sliver of their stack "based on open source" and that makes them more open source than JBoss. Read my blog on Open Source Community for my thoughts on that topic.
Anyhow, the interesting news is that Thing 2 is spending time building and marketing what I call a bridge to the past. They have built some tools that help people move away from our innovative and fully featured open source platform for SOA to their low-end "children's edition" onramp. The problem is that their onramp only provides a thin sliver of the functionality that people need for their SOA initiatives....so....oh darn....I guess that means people will just need to buy the other complex proprietary stuff in their portfolio...for real license $$'s. This "bridge to the past" will truly be the gift that keeps giving....only their customers are not the ones receiving the gift, if you know what I mean.
So why are Thing 1 and Thing 2 fighting us so vigorously?
Because they are not happy that we are successfully building out a complete open source platform for SOA that not only encompasses the Operating System and Application Server...but also covers the market areas of Portal, BPM, and Integration among others.
They see our big picture. They see our great technology and services. And they will do whatever it takes to preserve the lock-in and huge license fees provided by their big proprietary stacks.
Thing 1 and Thing 2 are more focused on trying to slow us down, rather than on delivering increased value to their customers. And I believe customers and the market in general are smart enough to see that.
Subscribe to:
Posts (Atom)
