Karanbir Singh wrote: > Not really, no. From your initial email you seemed to imply that it was > packaging and bug tracking that might be involved, but your reply here > implies something completely different. > > I dont see why one might need a new website or start a new project to do > this sort of a thing. Also why do you need to get 'some bits out there > for people to hack on', What is broken within the JBoss communities ? Or > are you saying that there are no JBoss communities and that its not open > source ? > > Perhaps I am missing the big-picture. Could someone clarify the > situation please ? Since Red Hat acquired JBoss in 2006, they extend their trademark policies to encompass not just JBoss, but Hibernate as well. What this means, is that for anyone who wishes to make a redistribution of JBoss with any modification must remove all mention of Red Hat trademarks, and logos; that is unless there is a signed agreement/partnership between Red Hat and the interested party. (All of this is covered in detail within the JBoss EULA and Red Hat trademark guidelines) The project we are proposing is a whiteboxed JBoss distribution; it simply takes a given release of JBoss, and makes the modifications necessary to comply with the Red Hat terms. This is very important; it allows other companies/organizations to distribute a modified version either as a service, or as a part of their product. -- Steven Stallion Senior Software Engineer Object Computing, Inc. http://www.ociweb.com