Hi Stack, I think the proposal sounds reasonable.
HBase is an integrated optional part of a Hadoop stack more than a standalone component, but other ASF TLPs build on top of other projects. I suppose HDFS and ZK are going to be TLPs at some point also, is that true? Leaving Hadoop as just the MR framework? Anyway, what I like is HBase will stand on its own merits. What are the risks of being a TLP? - Andy > From: Stack <st...@duboce.net> > Subject: [DISCUSS] HBase as Apache top-level project? > To: "HBase Dev List" <hbase-dev@hadoop.apache.org> > Date: Thursday, March 18, 2010, 9:58 AM > > I'd like to start a discussion about promoting HBase > from a Hadoop sub-project to a top-level Apache project > (TLP). > > This is not yet a vote. Once we have established > general understanding and agreement, I'll call a vote. > > I propose we move HBase from hadoop.apache.org/hbase to > hbase.apache.org. HBase would then have it's own > Project Management Committee (PMC) so that it can elect > committers and create releases on its own. Currently > these actions require votes by the Hadoop PMC. However > I think HBase now has a sufficiently large, diverse and > distinct community that it can fend for itself. > > I suggest that initial HBase PMC consist of all active > HBase committers at the time we make the formal proposal. [...] > I nominate myself as the initial chair of the HBase PMC, > with the proviso that we adopt a policy of regular chair > replacement. I suggest that HBase PMC chairs serve a > one or two-year term.
