If I had to choose which part was most interesting to me, and there were plenty to choose from, I suppose the most interesting is his thinking on the Axis project at Apache.
"Then what happened is the project took off, people started contributing, IBM contributed a lot, and when it was stable and almost a product, then IBM forked back into IBM Corp. a proprietary version, which is allowed by the BSD-style license that the Apache Software Foundation has. That led me, my guys, our group, and all the other users that contributed to Axis in a void"Now, I don't really know if this happened. (I'd be surprised if it did in the way he describes) and I don't really know how many of his guys contributed to Axis - it's public information in the commit logs - but it's a good thought-experiment:
If someone stops contributing to an open source project and continues developing privately, does this actually harm other contributors, or is it just that they don't benefit from the work of others?
Since this could happen with non-BSD-derived licenses as well, is there anything that can be done?
How does this differ from the normal risk that you encounter when depending on a commercial software vendor to continue a product line? In this case, it appears that Marc was dependent upon the contributions of IBM, and now w/o IBM contributing, is JBoss stuck on their WebServices stack?
Read JBoss CEO Opposes Open-Source Java
Also read Transparent middleware, EJB3.0, Las Vegas TSS