On Fri, Apr 23, 2010 at 12:11 AM, Lars George <lars.geo...@gmail.com> wrote:
> +1 on all of the above. I think with becoming a TLP it is of utmost > importance to throw down a perfect start, i.e. clean code, clean > website (!), clean build process, and a clear strategy on versioning, > roadmap etc. We have all the passion and intricate knowledge to do > that. I suggest that the Bay Area devs all get together and establish > this in one fell swoop. +1 - I don't think we can accomplish all of the above all at once (clean code???) but it would be nice to have a hackathon day where we force ourselves to only do spring cleaning and roadmapping (and not talk about fun problems). Pretty sure we could host at the new Cloudera office in Palo Alto - we have a lot of space, and close to caltrain. > We have put of polishing way to long IMHO and > hopefully Ryan can get something moving with the site, if not it > should be organized differently now now. I am sure one of us the > contacts to make this happen, heck I throw in a hundred bucks if that > helps. I cannot imagine getting someone doing a current design while > integrating the established content is such a big thing. > > Let us show the world what a few determined "nerds" (in the positive > sense) can achieve! > > Lars > > On Fri, Apr 23, 2010 at 8:44 AM, Jonathan Gray <jg...@facebook.com> wrote: > > Yay HBase! > > > > I am also interested in this. > > > > Now might also be the time to think about breaking from hadoop numbering > (I think this idea has been floating around since the first version we > synced). > > > > We've already agreed to break client compatibility for 0.20.5 and it's > more than a minor revision. And I'm sure we'll have another release between > 0.20.5 and 0.21. > > > > It's also clear that this is going to be by far our most solid release to > date and so might be worthy of new shiny versioning/packaging as a TLP. > Website/docs/wiki refresher to boot. > > > > Changing the package names is way more invasive to client code but I'm > always +1 on making stuff shorter. > > > > > > Anyways, I'm not doing much production cluster maintenance these days so > these changes would impact me way less than others. Will welcome pushback > if you guys don't want to deal with this. > > > > JG > > > >> -----Original Message----- > >> From: Ryan Rawson [mailto:ryano...@gmail.com] > >> Sent: Thursday, April 22, 2010 11:20 PM > >> To: hbase-dev@hadoop.apache.org > >> Subject: Re: HBase move to Apache Top Level Project > >> > >> I am somewhat interested in this :-) > >> > >> But it can make life difficult for our users... thoughts people? > >> > >> On Thu, Apr 22, 2010 at 11:17 PM, Karthik K <oss....@gmail.com> wrote: > >> > This is great news. Congrats HBase team. > >> > > >> > (Does this mean, the packages would be refactored as o.a.hbase.* in > >> the > >> > trunk ? ). > >> > > >> > -- > >> > Karthik. > >> > > >> > > >> > On Thu, Apr 22, 2010 at 10:47 PM, Cosmin Lehene <cleh...@adobe.com> > >> wrote: > >> > > >> >> This is great news! > >> >> > >> >> On Apr 22, 2010, at 8:32 PM, Stack wrote: > >> >> > >> >> > The board yesterday passed a resolution making HBase a TLP. > >> >> > > >> >> > I filed an infrastructure issue to start the move: > >> >> > > >> >> > https://issues.apache.org/jira/browse/INFRA-2641 > >> >> > > >> >> > The primary disruption to developers will be when the subversion > >> >> > repository is renamed. We'll send out a note before we do this, > >> then > >> >> > developers can use 'svn switch' to update their repos (There is no > >> >> > apache git repo that I know of... I asked just in case) > >> >> > > >> >> We already use the apache git.apache.org mirror for HBase. I've also > >> seen > >> >> the GitHub mirror http://github.com/apache/hbase and thought there > >> might > >> >> be some plans for migration. > >> >> > >> >> > One other issue is the wiki. I don't think it's easy to rename a > >> >> > subtree from a Moin Moin wiki to a new wiki. Fortunately we don't > >> >> > have many wiki pages and could cut and paste them manually. > >> >> > Alternately, we could switch to using confluence for our wiki. > >> >> > Thoughts? > >> >> > > >> >> Confluence has a good integration with Jira (being both developed by > >> >> Atlassian). It's functionally advanced and looks better. So +1 for > >> that as > >> >> well. > >> >> > >> >> Cosmin > >> >> > >> >> > St.Ack > >> >> > (Above shamelessly a copy of Doug's mail to the Avro list) > >> >> > >> >> > >> > > > > -- Todd Lipcon Software Engineer, Cloudera
