<unlurk> Greetings.
While not a JBoss Developer myself, I regularly use JBoss, and have contributed a few testcases and a patch or two. I have been to JBossOne & JBossTwo, and know some of the principals involved.
The Jetty group are another open source group, several of whom have never to my knowledge actually been employed by JBoss LLG. My understanding of the Jetty group's relation to JBoss Group was that it was an independent consulting firm, whose main product was a slim servlet container, Jetty.
Jetty/JBoss has been a very potent combination, and very effective for me.
For it to be suddenly removed from JBoss, with all of their developer's access terminated, is going to lead to large problems down the line for me when I start my next JBoss project.
As to why there is a conflict between CDN and JBoss, I do not understand. CDN handles a suite of solutions, of which JBoss is only one. A partnership between JBoss LLC and CDN would be of benefit to many, including JBoss LLC & CDN. A war would hamper CDN, but heavily damage JBoss LLC's growth potential, and damage JBoss as well. There are too many good developers with CDN who were never part of JBoss LLC (the majority of the CDN group that I met at JavaOne2003, actually).
It would be best if this was resolved amicably ASAP. Marc F, as far as can be seen, this is just you flying off the deep end. If there is more going on, an official statement needs to be released explaining the termination of the access of non-JBoss LLC developers to JBoss.
Regards, Steve
</unlurk>
Colin Sampaleanu wrote:
I must agree. Perhaps I don't know all the facts, but from external appearances this was a somewhat shamefull way for the JBoss Group to act, considering all that these developers have put into JBoss. A statement from the JBoss group on what happened to Greg's and the other developer's access, and why they were removed from the project listing page, would hopefully go a long way towards stopping people from making their own interpretation. Certainly at this point, I have no choice but to interpret these events in a certain way, and this will colour all my future attittude towards JBoss and the JBoss Group...
Regards, Colin
Callies, Peter wrote:
I just wish JBoss Group would truly treat their company and the JBoss
Project as separate entities. Just because JBoss Group has issues with some
of their employees taking jobs with a different company is no reason to
undercut the JBoss Project.
Obviously the success of the JBoss Group is tied to the success of the JBoss
Project, but my understanding is that the JBoss Project is an open-source
project, not owned by JBoss Group. I understand that some small group of
people needs to decide who has commit privileges to the source tree to
ensure quality control. However, since the developers in question had
commit privileges at one time they apparently are skilled enough to
contribute quality code.
Perhaps JBoss Group has given up on community development or perhaps it is
now a closed community. If this is the truth, come out and say it. Quit
saying the change to Tomcat has nothing to do with political infighting.
Quit saying that the new emphasis on JDO has nothing to do with Dain leaving
JBoss Group for CDN.
-Peter
-- Java/J2EE Developer/Integrator 214-724-7741
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
