(shifting discussion to dev@) Brian,
That’s a good question. There’s been some discussion in this respect, specifically with regard to storm-kafka, since that is a widely used module within the storm community. The short answer is we don’t know quite yet. I think the near-term goal is to get Storm aligned with the Apache Way, get a first (Apache) release out, and then deal with these types of inquiries/contributions. I think it’s still up in the air how we’re going to deal with “contrib”-type modules. So if you (or any other community members) have ideas in that respect, now would be a good time to chime in. Hopefully some of our Apache mentors are listening, and can chime in, but from my understanding: 1. IP clearance is very important — you could start by changing the license/license headers so all IP is transferred to the ASF. 2. I’m not sure on this, but you may need to chase down all contributors and get CLAs. Since I was involved with establishing and/or maintaining many of the projects you mentioned. I’d be happy to help out with transition in any way I can. I’d also like to applaud Health Market Science for their commitment to and support of Storm and open source in general. - Taylor On Nov 27, 2013, at 5:37 AM, Brian O'Neill <[email protected]> wrote: > > Given the move to Apache, what is the plan for storm-contrib? > (and other bolt, function, and state implementations) > > We are looking for a home for: > https://github.com/hmsonline/storm-cassandra > https://github.com/hmsonline/storm-elastic-search > > We also have a state implementation for graph databases, storm-graph, which > we are about to release. > > Do we bother consolidating or should they just remain in their current homes? > > -brian > > > --- > Brian O'Neill > Chief Architect > Health Market Science > The Science of Better Results > 2700 Horizon Drive • King of Prussia, PA • 19406 > M: 215.588.6024 • @boneill42 • > healthmarketscience.com > > This information transmitted in this email message is for the intended > recipient only and may contain confidential and/or privileged material. If > you received this email in error and are not the intended recipient, or the > person responsible to deliver it to the intended recipient, please contact > the sender at the email above and delete this email and any attachments and > destroy any copies thereof. Any review, retransmission, dissemination, > copying or other use of, or taking any action in reliance upon, this > information by persons or entities other than the intended recipient is > strictly prohibited. > >
signature.asc
Description: Message signed with OpenPGP using GPGMail
