Nice!
On Thu, Jul 10, 2014 at 12:05 PM, Clebert Suconic <[email protected]> wrote: > All the docs are part of the master.. being generated from XML... so they > are part of the donation as well.. > > > The docs are developed maintained, so I don't think there would be any > issues there. > > https://github.com/hornetq/hornetq/tree/master/docs > > > > these docs are later just ftp-ed to the hornetq website just to make it > easier for users to see it.. so git master includes it all. > > > > > On Thu, Jul 10, 2014 at 12:01 PM, Daniel Kulp <[email protected]> wrote: > >> >> One more thing: >> >> HornetQ has a lot of good docs and information on the web site. Is the >> intention to also donate some of that? If so, we’ll likely need a grant >> for that, but that obviously may be a bit more difficult to identify from >> git hash/tarball sha1/etc…. That wouldn’t need to be done immediately as >> that could be done via a separate grant, but something to consider as well >> while you are chasing things down inside RedHat. If you only have to do >> that once, you could make it a bit easier on yourself. :-) >> >> Dan >> >> >> >> On Jul 10, 2014, at 11:53 AM, Hiram Chirino <[email protected]> >> wrote: >> >> > Hi Clebert , >> > >> > This is a far as I've been able to get with the IP clearance form: >> > >> > >> http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/hornetq.xml >> > >> > I assumed that what you guys want to donate is the code that currently >> > exists on github master (commit >> > 90d43fbc158a0e6e3028c7179dbcf984757b88fb). >> > >> > Things we still need to do: >> > >> > 1) Get Red Hat to file a CCLA with Schedule B filled out >> > 2) Get a list of your active committers and make sure they have CLAs >> filed. >> > 3) "Check and make sure that for all items included with the >> > distribution that is not under the Apache license, we have the right >> > to combine with Apache-licensed code and redistribute" >> > 4) Check and make sure that all items depended upon by the project is >> > covered by one or more of the approved licenses. >> > 5) Run a VOTE thread to accept the code donation. >> > >> > I encourage the rest of the ActiveMQ PMC members to help check and >> > double check items #3 and #4 before doing #5. >> > >> > >> > On Thu, Jul 10, 2014 at 10:58 AM, Hiram Chirino <[email protected]> >> wrote: >> >> I'll start looking into filling out the ip-clearance from. >> >> >> >> On Tue, Jul 8, 2014 at 10:53 AM, Gary Tully <[email protected]> >> wrote: >> >>> Hi Clebert, >> >>> the hornetq specJMS numbers are very impressive so from my perspective >> >>> we would love to have the code base. >> >>> We can then evaluate how best to combine the relative strengths of >> >>> Apollo and HornetQ for the next gen ActiveMQ. >> >>> >> >>> Please start the process outlined at [1] and we can look at doing an >> import. >> >>> >> >>> [1] http://incubator.apache.org/ip-clearance/ >> >>> >> >>> >> >>> On 8 July 2014 15:37, Hiram Chirino <[email protected]> wrote: >> >>>> Hi Clebert, >> >>>> >> >>>> That sounds very interesting! Bringing the HornetQ community into >> >>>> ActiveMQ would be exciting for me. We could collaborate and bring >> >>>> together the best features of ActiveMQ, Apollo and HornetQ to create >> >>>> an amazing next generation messaging system AND grow our developer >> >>>> community at the same time. Lots of folks have been asking me when >> >>>> will ActiveMQ get JMS 2.0 support, so the fact that HornetQ has JMS >> >>>> 2.0 support already is big plus in my book! >> >>>> >> >>>> I was building up the Apollo codebase to be that next generation >> >>>> messaging backbone for ActiveMQ, but perhaps because it's mostly >> >>>> implemented using Scala, not too many developers got involved and >> >>>> that's a bit of a problem since the 'Apache Way' of building projects >> >>>> is more about community than code. I have been pondering porting >> >>>> Apollo to be just plain Java based. Since HornetQ is Java based but >> >>>> and has a similar fully async threading architecture like Apollo, >> >>>> perhaps this donation will save me lots of work. >> >>>> >> >>>> :) >> >>>> >> >>>> On Tue, Jul 8, 2014 at 10:31 AM, Clebert Suconic >> >>>> <[email protected]> wrote: >> >>>>> Hi all, >> >>>>> >> >>>>> My name is Clebert Suconic, I'm the project lead for the HornetQ JMS >> broker >> >>>>> (http://hornetq.jboss.org/). The HornetQ team is currently in the >> planning >> >>>>> phase for the next release of the broker and we've been thinking >> about >> >>>>> whether it would make sense for us to collaborate more closely with >> the >> >>>>> ActiveMQ community. >> >>>>> >> >>>>> There is a lot of overlap in the capabilities of the two brokers >> today and >> >>>>> it strikes us that it would be beneficial to both communities for us >> to join >> >>>>> forces to build one truly great JMS broker rather than spend our time >> >>>>> duplicating efforts on both brokers. ActiveMQ has a great community >> of >> >>>>> developers and users and it'd be great to be able to consolidate our >> work >> >>>>> there. >> >>>>> >> >>>>> My understanding is that the Apollo sub-project aimed to provide a >> basis for >> >>>>> the next generation of ActiveMQ, addressing some of the current >> limitations. >> >>>>> Perhaps HornetQ could be an alternative. HornetQ has some good >> performance >> >>>>> and scalability numbers as well as support for JMS 2.0. It already >> supports >> >>>>> STOMP today and adding support for OpenWire would be >> straight-forward and >> >>>>> would provide continuity for existing clients. Essentially, the goal >> could >> >>>>> be to combine the existing flexibility of ActiveMQ with the >> performance of >> >>>>> HornetQ. >> >>>>> >> >>>>> Anyway, these are just some initial ideas, for now I'm really just >> >>>>> interested to know how the ActiveMQ community would feel about a >> donation of >> >>>>> the HornetQ codebase. >> >>>>> >> >>>>> Thanks and best regards, >> >>>>> Clebert. >> >>>> >> >>>> >> >>>> >> >>>> -- >> >>>> Hiram Chirino >> >>>> Engineering | Red Hat, Inc. >> >>>> [email protected] | fusesource.com | redhat.com >> >>>> skype: hiramchirino | twitter: @hiramchirino >> >>> >> >>> >> >>> >> >>> -- >> >>> http://redhat.com >> >>> http://blog.garytully.com >> >> >> >> >> >> >> >> -- >> >> Hiram Chirino >> >> Engineering | Red Hat, Inc. >> >> [email protected] | fusesource.com | redhat.com >> >> skype: hiramchirino | twitter: @hiramchirino >> > >> > >> > >> > -- >> > Hiram Chirino >> > Engineering | Red Hat, Inc. >> > [email protected] | fusesource.com | redhat.com >> > skype: hiramchirino | twitter: @hiramchirino >> >> -- >> Daniel Kulp >> [email protected] - http://dankulp.com/blog >> Talend Community Coder - http://coders.talend.com >> >> > > > -- > Clebert Suconic > http://community.jboss.org/people/[email protected] > http://clebertsuconic.blogspot.com -- Hiram Chirino Engineering | Red Hat, Inc. [email protected] | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino
