1. Bigtop Working Group
6/30/2013
DC: Group Intro, Detailed history
Roman: Bigtop

2. History
● 6 months 2 years ago for group to get to project delivery
● Too long/took too much time from Roman,DC. We had to go to every
meeting
● Got fantastic projects; mostly focused around builds b/c we spend all our
time here
● We used the same structure at work. Didn't know any better
● High turnover, ~70->7. 90% drop out rate.
– Not enough time, people dropped out after getting behind
– Too much like work, reduce scope of projects, used to meet weekly. Lots of all
nighters
– People use it to switch careers

3. What you get out of joining the
working group: Hadoop/HBase
●
More detailed than anything you get from a 3 day training session.
Costs to hire people to create material. They HAVE to charge
$800-1k/day.
●
We aren't a class. Work hard to make sure we don't turn into one.
Have to respect people who have full time jobs and do this on the
side. No Sponsorship can fix this.
● People will use this as a class anyway. 40->7 people at the end
● Goal to get create Apache Contributors. Too ambitious. Got
Impressive code contributions. Projects<->Builds

4. Structure Modifications
● 3 prescheduled sessions only. Once that is over
we see who is left
● Groups, split the work and help to keep people
motivated in the group
● First goal deeper dive into Hadoop*
components

5. Bigtop Install and Build (too much)
● Bigtop Install on wiki, 0.5.0 documented. Work
on 0.6.0 and document?
● Install the components, all of them? Develop
component flows. Can start by running the
individual tests in the components then
combining them. Must haves HBase, Hadoop,
Pig or Hive, Oozie, Zookeeper. More?

6. Bigtop Build(0.5.0)
● Build instructions and test
● Adding a new component
– Mongodb (doesn't count)
– Storm (into Hadoop, modify after Ted's talk)

7. Bigtop Build(0.5.0)
● Build instructions and test
● Adding a new component
– Mongodb (doesn't count)
– Storm (into Hadoop, modify after Ted's talk)