Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Received-SPF: pass (nike.apache.org: domain of billie.rinaldi@gmail.com
 designates 209.85.219.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPCL_Bzhtc23QKbnG3uUs8cMkOMF993TOkM-uiXVah19Cae_wQ@mail.gmail.com>
References: 
 <CAPCL_ByjiO8p=Qer=JAwoVbyT2Qn3E8i6cjAVVeNEKY7XvaUag@mail.gmail.com>
	<CAGHyZ6JJVqavdkwpeYhUeT_UKG+1W2mxgyS=3T7Hhj_3XZXDBg@mail.gmail.com>
	<CAOiJXP7ne7eYoMSRHdT3+yLuWY4znz89OmYxAyP0uZBEcNUYXA@mail.gmail.com>
	<410374FA-50BE-462F-BB44-AF3F73BCFE68@clearedgeit.com>
	<CAPCL_Bzhtc23QKbnG3uUs8cMkOMF993TOkM-uiXVah19Cae_wQ@mail.gmail.com>
Date: Mon, 22 Jul 2013 14:37:38 -0700
Message-ID: 
 <CAF1jEfAUM-mSyfLWHtNnCq+eYEJXOfeTEjo9UWZ4iBbH2_c4Bw@mail.gmail.com>
Subject: Re: QA
From: Billie Rinaldi <billie.rinaldi@gmail.com>
To: dev@accumulo.apache.org
Content-Type: multipart/alternative; boundary=047d7b2e44024d34ab04e2207c21

--047d7b2e44024d34ab04e2207c21
Content-Type: text/plain; charset=ISO-8859-1

We could experimentally subscribe our existing notifications list to the
accumulo tag.

Billie


On Mon, Jul 22, 2013 at 2:26 PM, Miguel Pereira
<miguelapereira1@gmail.com>wrote:

> On stackoverflow there is a way to subscribe an email to a tag set, is it
> possible to create something like: soqa@accumulo.apache.org and send all
> qa
> notifcations to subscribers that way? I was thinking the seperate email for
> those subscribed to dev that dont want to participate.
>
>
>
> On Mon, Jul 22, 2013 at 2:02 PM, Donald Miner <dminer@clearedgeit.com
> >wrote:
>
> > Im an avid user of stackoverflow and contribute a lot to the hadoop and
> > pig tag. And i think it is the right place, but we do need to work at it
> a
> > bit.
> >
> > There is a bit of a problem with smaller tags in terms of momentum. If
> > someone asks an accumulo question and it takes a long time to get a
> > response, they wont use it again. Also, if they don't see many questions
> > about accumulo already, it gives the impression they shouldnt waste their
> > time. I wonder if there is something out there that could notify the list
> > when a new question on SO is asked so we as a group can answer it
> quickly.
> >
> > The next thing is editing the questions. When we see an accumulo
> question,
> > we should make sure that hadoop and anything else is tagged that needs to
> > be tagged so it gets more eyes. For example, i use the pig tag a lot, but
> > always tag hadoop, too. Any other tags from a SEO perspective should be
> > added if the person doesn't know what they are asking. E.g., chaning
> > "server thingy not starting" to "TabletServer not starting".
> >
> > Finally, we need to get some volume in there. Maybe it's sending people
> > there or maybe it is "seeding" FAQ there and answering it ourselves
> (e.g.,
> > sean posts the faq, then I answer it with the predetermined answer). Not
> > sure how kosher that is.
> >
> > On Jul 22, 2013,i at 1:04 PM, David Medinets <david.medinets@gmail.com>
> > wrote:
> >
> > > +1 for stackoverflow and other links for simplicity and duplication
> > > avoidance.
> > > On Jul 22, 2013 9:45 AM, "Sean Busbey" <busbey@cloudera.com> wrote:
> > >
> > >> Or perhaps just a pointer to an appropriate tag on StackOverflow and
> > >> ServerFault?
> > >>
> > >> --
> > >> Sean
> > >> On Jul 22, 2013 8:55 AM, "Miguel Pereira" <miguelapereira1@gmail.com>
> > >> wrote:
> > >>
> > >>> Maybe consider putting up a Q & A page on the site for accumulo
> > specific
> > >>> topics?
> > >>> With the ability to post / reply
> > >>> I believe this will help new people quite a bit, and will serve as a
> > >>> reference so the same questions are not asked multiple times.
> > >>>
> > >>> Cheers,
> > >>> Miguel
> > >>
> >
> > --
> >  This communication is the property of ClearEdge IT Solutions, LLC and
> may
> > contain confidential and/or privileged information. Any review,
> > retransmissions, dissemination or other use of or taking of any action in
> > reliance upon this information by persons or entities other than the
> > intended recipient is prohibited. If you receive this communication in
> > error, please immediately notify the sender and destroy all copies of the
> > communication and any attachments.
> >
>

--047d7b2e44024d34ab04e2207c21--