To grow the influence of bigtop, engaging vendors might be u= seful. For those pursuing an open strategy or open core strategy then commo= ditizing and amortizing the costs of baseline packaging and integration con= cerns makes sense. Everybody wins because more bandwidth is available to fo= cus on differentiators. Such vendors typically employ committers for commun= ity based development. If some of these=A0vendors can publicly=A0get behind= bigtop and invest in its credibility, then as an emergent consequence ther= e will be more community engagement on integration issues under its umbrell= a. Everyone will win.=A0

On some of the specific points, my humble opinion:

2. Hadoop 2 is the only long term viable option even i= f some parts may be still unstable in terms of API.=A0

3. This seems a case of "build it and they will come". Itera= te on a BOM that (mostly) works. Publicize it. For integration blockers, tr= ack the respective JIRAs on the bigtop wiki. Be polite. Be proactive. Mail = the respective dev lists with gentle reminders, but not too frequently.=A0<= /div>

4. See above.=A0

5. You can= 9;t.=A0

On Thursday, March 7, 2013, Roman Shaposhnik wrote:
On Wed, Mar 6, 2013 at 10:10 AM, Konstantin Boudnik <cos@a= pache.org> wrote:
> I believe there's not much more to say about it, except that this = is,
> in my opinion, a good way to establish our project as de-facto go-to > place for community driven Hadoop based stacks and a focal point for > the integration in the ASF storage and analytics projects.

I like this idea very much! A couple of things that I'd love to hear ot= her
chime in on:
=A0 #1 I think it is too late to change the focus of Bigtop 0.6.0
=A0 #2 Do we have a reasonable conviction that the beta
=A0 =A0 =A0 =A0release of Hadoop 2.X is withing reach?
=A0 #3 How do we influence Hadoop community to help us
=A0 =A0 =A0 =A0produce the first ever LTS of Bigtop?
=A0 #4 How do we get the downstream communities (pig, oozie, etc)
=A0 =A0 =A0 =A0on-board so that we can all work towards this common goal? =A0 #5 Suppose we do all the work in all of the downstream components,
=A0 =A0 =A0 =A0how can we at least make sure that there will be patch
=A0 =A0 =A0 =A0releases incorporating all the changes we've done?

Now, Bigtop (well, me personally at least ;-)) would be more than
willing to help on all of these with automation, testing, etc. But
we *have* to get all of the communities involved on-board with this.

Thanks,
Roman.

--
Best regards,

=A0 =A0- Andy=

Problems worthy of attack prove their worth by hitting back. - Piet= Hein (via Tom White)

--089e011841a0479bdd04d74e47a3--