Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Accumulo >> mail # dev >> Accumulo 1.6 and beyond feature summit


Copy link to this message
-
Re: Accumulo 1.6 and beyond feature summit
On Fri, Feb 1, 2013 at 7:22 AM, Adam Fuchs <[EMAIL PROTECTED]> wrote:

> How I read Benson's comment is that if anyone feels excluded by the online
> forum and voices that objection then we should not do it. This is not to
> say that the community has any power to forbid communication about Accumulo
> outside of email channels, but we should make things as accessible as
> possible and only make official decisions via approved channels (do we have
> by-laws to approve channels yet?).
>

We should work on our by-laws.  I believe the only channel we have to make
decisions is through the mailing list (and by extension JIRA, since it is
logged to the mailing list).

Billie

>
> Another way to think of this online forum is like a meetup. We're proposing
> to do a couple of things to be as inclusive as possible -- one is to record
> the presentations so that everyone can see them on their own schedule. The
> other is to refrain from any official decision making at this event. This
> is only intended to facilitate information exchange.
>
> Adam
>
>
>
> On Fri, Feb 1, 2013 at 10:04 AM, Aaron Cordova <[EMAIL PROTECTED]> wrote:
>
> > Benson,
> >
> > Just to be clear (I had to re-read your email a few times to understand)
> > you're saying a real-time online discussion such as Adam is proposing has
> > the potential to exclude some members of the dev community and that we
> > should be sure to stick to things like this email discussion to avoid
> those
> > problems?
> >
> >
> > Thanks,
> >
> > Aaron
> >
> >
> > On Feb 1, 2013, at 2:36 AM, Benson Margulies <[EMAIL PROTECTED]>
> > wrote:
> >
> > > I want to caution everyone that this process skates close to an edge
> > > of an Apache invariant. An online forum has the potential to exclude
> > > people in far-away time zones or with other constraints. At Apache, we
> > > try to maximize the use of email to avoid this problem.
> > >
> > > Nothing here is an absolute -- I'm not trying to torpedo this plan
> > altogether.
> > >
> > > Nothing, that is, except except that _decisions_ must be made on the
> > > mailing list afterwards.
> > >
> > > If anyone in the dev community feels excluded by this prospect, I
> > > would encourage you to speak up now, so that the planners can make
> > > adjustments to minimize that.
> > >
> > >
> > > On Thu, Jan 31, 2013 at 10:10 PM, Billie Rinaldi
> > > <[EMAIL PROTECTED]> wrote:
> > >> On Sun, Jan 27, 2013 at 12:43 PM, Eric Newton <[EMAIL PROTECTED]>
> > wrote:
> > >>
> > >>> What is CAS?
> > >>>
> > >>>   - Switch to Curator.
> > >>>   - Monitoring.  I'm hoping this will just be integration with an
> > existing
> > >>>   tool.
> > >>>   - Namespaces.
> > >>>   - A simple query language.  Perhaps there's something we can
> > collaborate
> > >>>   with some of the other NoSQL folks.
> > >>>   - Update the wiki search example.
> > >>>   - Automatic tablet merge.
> > >>>   - Scalable NN
> > >>>
> > >>
> > >> Is scalable NN == ACCUMULO-722?  I'd be excited about that for 1.6.
> > >>
> > >> Billie
> > >>
> > >>
> > >>
> > >>>
> > >>> Some of these don't need design documents, but some discussion of
> > >>> requirements would be nice.
> > >>>
> > >>> -Eric
> > >>>
> > >>>
> > >>>
> > >>> On Sun, Jan 27, 2013 at 12:26 PM, Keith Turner <[EMAIL PROTECTED]>
> > wrote:
> > >>>
> > >>>> This will be very useful.
> > >>>>
> > >>>> Some new features I am thinking about for 1.6 are replication, CAS,
> > >>>> and Percolator.  I would like to put together a bit of an initial
> > >>>> design document for each of these.  I'm thinking that a follow up
> > >>>> online deep dive on the design of each large new 1.6 feature would
> > >>>> also be very useful.
> > >>>>
> > >>>> In the coming week I plan to spend most of my time testing,
> > >>>> documenting, fixing bugs, and polishing 1.5.0.  I do not think this
> > >>>> would leave much time to work on 1.6.  So interleaving design
> > >>>> discussion about new 1.6 features while 1.5 is being polished would
> be
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB