Just an idle thought on a Friday evening: I always find it confusing
that we have two "hbase books".
- There's the wonderful one that Doug primarily maintains in SVN:
http://hbase.apache.org/book.html
- and the other wonderful one that Lars wrote:
http://shop.oreilly.com/product/0636920014348.do

Given that the one we build from our code tree isn't actually a
physical book, maybe we could rename it to the "HBase manual" instead?
Then we'd have less overloading and better SEO for both resources, to
boot. Of course we should live a redirect in place from the old URL to
the new so we don't break all those old links.

-Todd
--
Todd Lipcon
Software Engineer, Cloudera

+1

On Dec 2, 2011, at 6:29 PM, Todd Lipcon <[EMAIL PROTECTED]> wrote:

> Just an idle thought on a Friday evening: I always find it confusing
> that we have two "hbase books".
> - There's the wonderful one that Doug primarily maintains in SVN:
> http://hbase.apache.org/book.html
> - and the other wonderful one that Lars wrote:
> http://shop.oreilly.com/product/0636920014348.do
>
> Given that the one we build from our code tree isn't actually a
> physical book, maybe we could rename it to the "HBase manual" instead?
> Then we'd have less overloading and better SEO for both resources, to
> boot. Of course we should live a redirect in place from the old URL to
> the new so we don't break all those old links.
>
> -Todd
> --
> Todd Lipcon
> Software Engineer, Cloudera

+1
On Dec 2, 2011 6:47 PM, "Jonathan Gray" <[EMAIL PROTECTED]> wrote:

> +1
>
> On Dec 2, 2011, at 6:29 PM, Todd Lipcon <[EMAIL PROTECTED]> wrote:
>
> > Just an idle thought on a Friday evening: I always find it confusing
> > that we have two "hbase books".
> > - There's the wonderful one that Doug primarily maintains in SVN:
> > http://hbase.apache.org/book.html
> > - and the other wonderful one that Lars wrote:
> > http://shop.oreilly.com/product/0636920014348.do
> >
> > Given that the one we build from our code tree isn't actually a
> > physical book, maybe we could rename it to the "HBase manual" instead?
> > Then we'd have less overloading and better SEO for both resources, to
> > boot. Of course we should live a redirect in place from the old URL to
> > the new so we don't break all those old links.
> >
> > -Todd
> > --
> > Todd Lipcon
> > Software Engineer, Cloudera
>

+one

On Fri, Dec 2, 2011 at 6:29 PM, Todd Lipcon <[EMAIL PROTECTED]> wrote:
> Just an idle thought on a Friday evening: I always find it confusing
> that we have two "hbase books".
> - There's the wonderful one that Doug primarily maintains in SVN:
> http://hbase.apache.org/book.html
> - and the other wonderful one that Lars wrote:
> http://shop.oreilly.com/product/0636920014348.do
>
> Given that the one we build from our code tree isn't actually a
> physical book, maybe we could rename it to the "HBase manual" instead?
> Then we'd have less overloading and better SEO for both resources, to
> boot. Of course we should live a redirect in place from the old URL to
> the new so we don't break all those old links.
>
> -Todd
> --
> Todd Lipcon
> Software Engineer, Cloudera

+1

And one of them is starting to get almost as long as the Bible (too competitive of a SEO term)

Otis
----

Sematext :: http://sematext.com/ :: Solr - Lucene - Hadoop - HBase
Hadoop ecosystem search :: http://search-hadoop.com/
----- Original Message -----
> From: Todd Lipcon <[EMAIL PROTECTED]>
> To: dev <[EMAIL PROTECTED]>
> Cc:
> Sent: Friday, December 2, 2011 9:29 PM
> Subject: rename "book" to "manual"?
>
> Just an idle thought on a Friday evening: I always find it confusing
> that we have two "hbase books".
> - There's the wonderful one that Doug primarily maintains in SVN:
> http://hbase.apache.org/book.html
> - and the other wonderful one that Lars wrote:
> http://shop.oreilly.com/product/0636920014348.do
>
> Given that the one we build from our code tree isn't actually a
> physical book, maybe we could rename it to the "HBase manual" instead?
> Then we'd have less overloading and better SEO for both resources, to
> boot. Of course we should live a redirect in place from the old URL to
> the new so we don't break all those old links.
>
> -Todd
> --
> Todd Lipcon
> Software Engineer, Cloudera
>

+1

On Dec 3, 2011, at 3:29 AM, Todd Lipcon wrote:

> Just an idle thought on a Friday evening: I always find it confusing
> that we have two "hbase books".
> - There's the wonderful one that Doug primarily maintains in SVN:
> http://hbase.apache.org/book.html
> - and the other wonderful one that Lars wrote:
> http://shop.oreilly.com/product/0636920014348.do
>
> Given that the one we build from our code tree isn't actually a
> physical book, maybe we could rename it to the "HBase manual" instead?
> Then we'd have less overloading and better SEO for both resources, to
> boot. Of course we should live a redirect in place from the old URL to
> the new so we don't break all those old links.
>
> -Todd
> --
> Todd Lipcon
> Software Engineer, Cloudera

+1
On 12/3/11 3:31 AM, "Lars George" <[EMAIL PROTECTED]> wrote:

>+1
>
>On Dec 3, 2011, at 3:29 AM, Todd Lipcon wrote:
>
>> Just an idle thought on a Friday evening: I always find it confusing
>> that we have two "hbase books".
>> - There's the wonderful one that Doug primarily maintains in SVN:
>> http://hbase.apache.org/book.html
>> - and the other wonderful one that Lars wrote:
>> http://shop.oreilly.com/product/0636920014348.do
>>
>> Given that the one we build from our code tree isn't actually a
>> physical book, maybe we could rename it to the "HBase manual" instead?
>> Then we'd have less overloading and better SEO for both resources, to
>> boot. Of course we should live a redirect in place from the old URL to
>> the new so we don't break all those old links.
>>
>> -Todd
>> --
>> Todd Lipcon
>> Software Engineer, Cloudera
>
>