Details

    • Type: Task Task
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      We need to spread the word more on HBase to advance adoption.

      I took the first step and create a HBase Twitter account that talks about itself as it "sees" itself being mentioned on the intertubes. Here the URL:

      http://twitter.com/HBase

      We should discuss further means of a combines effort given our limited advertisement budget.

      While I created the account for Twitter, I suggest we share the details and set the email address to a central account, so that more than one person can post updates. BTW, other projects on Apache.org follow the same approach, so this is more or less a working concept. And avoids someone else hogging the HBase account name.

        Activity

        Hide
        stack added a comment -

        Resolving as won't fix inside. Lets open specific issues rather than this general umbrella issue.

        Show
        stack added a comment - Resolving as won't fix inside. Lets open specific issues rather than this general umbrella issue.
        Hide
        Lars George added a comment -

        The only other effort I know of is the "fan of hbase" on facebook. Who created that one? What is its goal? Can we somehow combined efforts or even consolidate them? For example, the Twitter updates could be cross posted to Facebook's status of the HBase account (if that is actually an account?) using TweetDeck etc.

        Just on Stack's comment, the thing I see is that we need to tackle two audience mainly, the developers and the management. While we are starting to have good documentation on the Wiki for developers I think we could improve to pitch HBase on an "executive white paper" level - so that it will be considered by the decision makers in selection processes.

        We have so many "Powered by" entries - there ought to be a lot of material we could use to build case studies. And as Stack says, I think we should not answer the religious question "Why HBase? Why not database A or storage solution B?" - we need to explain why we use it for our particular projects. That alone will show off HBase's features and how someone could make use of it.

        I am also suggesting we create a army of volunteers, the "Ambassadors of HBase". I am a - self proclaimed, mind you - European Ambassador for HBase where I offer any company or institution to have me present and advise on HBase. Just for the cost of travel (and accommodation if to far away). Not sure if anyone will make use of this, but it is one more step towards advocating HBase to everyone who is even remotely interested.

        The first step is of course selling us through our site. It must answer all preliminary questions a developer or decision maker may ask. Maybe divide the sections into two separate ones, have a generic FAQ, case studies and white paper section and then a developers corner with API documentation, samples, advice etc.

        One more issue - and please this is not to blame anyone, you are all outstanding guys - I would suggest to clean up the Javadocs starting with the direct API (or client) classes and then traversing down. That way a new developer has a much better support from say within Eclipse as the documentation of the classes already gets them what they need quick. The lower classes are important too as that will give more people access to the gory details and we may gain more contributors and eventually committers.

        If I am off here, please let me know too. I am just trying to get a revolution going.

        Show
        Lars George added a comment - The only other effort I know of is the "fan of hbase" on facebook. Who created that one? What is its goal? Can we somehow combined efforts or even consolidate them? For example, the Twitter updates could be cross posted to Facebook's status of the HBase account (if that is actually an account?) using TweetDeck etc. Just on Stack's comment, the thing I see is that we need to tackle two audience mainly, the developers and the management. While we are starting to have good documentation on the Wiki for developers I think we could improve to pitch HBase on an "executive white paper" level - so that it will be considered by the decision makers in selection processes. We have so many "Powered by" entries - there ought to be a lot of material we could use to build case studies. And as Stack says, I think we should not answer the religious question "Why HBase? Why not database A or storage solution B?" - we need to explain why we use it for our particular projects. That alone will show off HBase's features and how someone could make use of it. I am also suggesting we create a army of volunteers, the "Ambassadors of HBase". I am a - self proclaimed, mind you - European Ambassador for HBase where I offer any company or institution to have me present and advise on HBase. Just for the cost of travel (and accommodation if to far away). Not sure if anyone will make use of this, but it is one more step towards advocating HBase to everyone who is even remotely interested. The first step is of course selling us through our site. It must answer all preliminary questions a developer or decision maker may ask. Maybe divide the sections into two separate ones, have a generic FAQ, case studies and white paper section and then a developers corner with API documentation, samples, advice etc. One more issue - and please this is not to blame anyone, you are all outstanding guys - I would suggest to clean up the Javadocs starting with the direct API (or client) classes and then traversing down. That way a new developer has a much better support from say within Eclipse as the documentation of the classes already gets them what they need quick. The lower classes are important too as that will give more people access to the gory details and we may gain more contributors and eventually committers. If I am off here, please let me know too. I am just trying to get a revolution going.
        Hide
        stack added a comment -

        I made this issue 'critical', rather than 'major', since its a means to broader community – broad community is what hbase needs to be successful.

        Other comments:

        Lars also suggested that we work on the home page and on the wiki layout to clean them up and make them more presentable. In particular, he suggested – which I liked – that on the home page that we link to use case, descriptions of how hbase is being used in deployment. These use cases would include detail and most importantly, why hbase is being used rather than some other tech (Lars also made the point that we shouldn't be about hbase being only possible soln., just about why it in particular works in the described use case).

        Lars also suggested that we should choose a few stats that we might want to monitor over time as fit criteria for how well we're doing on this issue such as mentions in blogosphere, numbers on irc channel, mailing list numbers, etc.

        Show
        stack added a comment - I made this issue 'critical', rather than 'major', since its a means to broader community – broad community is what hbase needs to be successful. Other comments: Lars also suggested that we work on the home page and on the wiki layout to clean them up and make them more presentable. In particular, he suggested – which I liked – that on the home page that we link to use case, descriptions of how hbase is being used in deployment. These use cases would include detail and most importantly, why hbase is being used rather than some other tech (Lars also made the point that we shouldn't be about hbase being only possible soln., just about why it in particular works in the described use case). Lars also suggested that we should choose a few stats that we might want to monitor over time as fit criteria for how well we're doing on this issue such as mentions in blogosphere, numbers on irc channel, mailing list numbers, etc.

          People

          • Assignee:
            Unassigned
            Reporter:
            Lars George
          • Votes:
            2 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development