Sam Newman's site, a Consultant at ThoughtWorks

Thanks to a friend for this heads up – seems Mark Fleury has responded to the creation of the Geronimo project in the latest newsletter on the JBoss mailing list:

First a bit of history. I offered JBoss when it was 4 month old to
Apache. The guys at Jakarta vote OK unanimously and their vote was
overridden by Brian Behlendorf. The reason from behlendorf was that they
‘were not the dust bin of open source projects’. I heard the Apache
crowd got offended for me calling them “a bunch of fat ladies drinking
tea” at a later date when they were running around telling us how to run
our project. We had reports that this was the non-official reason for
this “challenge”. Challenge accepted. More seriously as we overtake
them in corporate penetration and business model, I guess they are
finally looking beyond the HTTPD C co debase and imitation is the
sincerest form of flattery.

We are the real thing, all we have so far is talk and announcement, announcements are a dime a dozen. Apache code on this project has yet to be released and then production reached and then maturity bla bla bla. I have little comment on the project except to say that JBOSS IS NOT A PART OF IT. In a misleading announcement Apache chairman’s Greg Stein implied JBoss was participating and that JBOSS CODE WAS PART OF THE PROJECT. No current JBoss developers are participating in the Apache J2EE project and since JBoss is LGPL only full copyright holders can offer JBoss code under other licenses. Bottom line? JBoss can’t be forked by apache. As our customers know, we are a business, a serious one and we seriously believe in and defend “professional open source”. That includes legal protection of IP. Make no mistakes, JBoss will AGGRESIVELY defend its copyright and LGPL license.

Ouch! So, JBoss code will not be part of Geronimo unless Geronimo is offered ONLY under an LGPL license, which is highly unlikely to be the case given that its an Apache project. This leads me to believe that OpenEJB will likely form the basis for the EJB container inside Geronimo – OpenEJB developers are among those already signedup.

The Core Developers Network seems to be backing the Geronimo initiative quite strongly, and its intersting to note that the Core Developers Network’s consultants have all been heavily involved in JBoss development – beyond any contributions to the JBoss code base they also sell themselves as JBoss consultants, just as they did for JBoss itself before they left earlier this year.

It seems that JBoss’s reaction to the Geronimo project may not be limited to strongly worded emails – according to my friend on the JBoss mailing list one of the Jetty-JBoss developers has very recently had his commit rights revoked without warning and the only clue seems to of been this developers involvement with Geronimo. Its also important to note that in his email Mark Fleury states that no _current_ JBoss developers are involved in Geronimo, which must mean the guys at Core Developers have all had their commit rights revoked, despite their apparent heavy involvement with JBoss (check the members page for information concerning their apparent ongoing involvement ). Expect this to run and run…

One Response to “Mark Fleury’s response to Apache Geronimo”

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Basic HTML is allowed. Your email address will not be published.

Subscribe to this comment feed via RSS

%d bloggers like this: