Re: [VOTE] Accept Tephra into the Apache Incubator

[Andrew Purtell]

+1 (binding)

> On Mar 3, 2016, at 5:29 PM, Poorna Chandra  wrote:
> 
> Hi All,
> 
> Tephra proposal was sent out for discussion last week. The proposal is
> available at https://wiki.apache.org/incubator/TephraProposal
> 
> Please vote to accept Tephra into the Apache Incubator. The vote will be
> open for the next 72 hours.
> 
> [ ] +1 Accept Tephra as an Apache Incubator podling.
> [ ] +0 Abstain.
> [ ] -1 Don’t accept Tephra as an Apache Incubator podling because ...
> 
> Thanks,
> Poorna.
> 
> --
> 
> = Abstract =
> 
> Tephra is a system for providing globally consistent transactions on
> top of Apache HBase and other storage engines.
> 
> = Proposal =
> 
> Tephra is a transaction engine for distributed data stores like Apache HBase.
> It provides ACID semantics for concurrent data operations that span over 
> region
> boundaries in HBase using Optimistic Concurrency Control.
> 
> = Background =
> 
> HBase provides strong consistency with row- or region-level ACID
> operations. However, it sacrifices cross-region and cross-table
> consistency in favor of scalability. This trade-off requires application
> developers to handle  the complexity of ensuring consistency when their
> modifications span region boundaries. By providing support for global
> transactions that span regions, tables, or multiple RPCs,
> Tephra simplifies application development on top of HBase, without a
> significant impact on performance or scalability for many workloads.
> 
> Tephra leverages HBase’s native data versioning to provide multi-versioned
> concurrency control (MVCC) for transactional reads and writes.
> With MVCC capability, each transaction sees its own consistent “snapshot” of
> data, providing snapshot isolation of concurrent transactions.
> MVCC along with conflict detection and handling enables Optimistic Concurrency
> Control.
> 
> Tephra consists of three main components:
> * Transaction Server – maintains global view of transaction state, assigns
>   new transaction IDs and performs conflict detection;
> * Transaction Client – coordinates start, commit, and rollback of
> transactions; and
> * Transaction Processor Coprocessor – applies filtering to the data read 
> (based
>   on a given transaction’s state) and cleans up any data from old
>   (no longer visible) transactions.
> 
> Although Tephra only supports HBase now, it can be extended to support
> transactions on any store that has multi-versioning and rollback
> support. The transactions
> can span over multiple stores and storage paradigms.
> 
> = Rationale =
> 
> Tephra has simple abstractions which can be used by an application to
> add transaction support over HBase. By abstracting away transaction
> handling using Tephra, the application is freed of
> transaction logic, and the application developer can focus on the use case.
> Also, Tephra can be extended to support transactions on data sources other
> than HBase.
> 
> By making Tephra an Apache open source project, we believe that there will
> be wider adoption and more opportunities for Tephra to be integrated
> into other Apache projects.
> 
> = Current Status =
> 
> Tephra was built at Cask Data Inc. initially as part of
> open-source framework Cask Data Application Platform (CDAP)
> [[http://cdap.io/]].
> It was later converted into an independent open source project with
> Apache 2.0 License [[https://github.com/caskdata/tephra]].
> 
> Tephra is used in CDAP as the transaction engine. As part of CDAP, Tephra
> has been deployed at multiple companies.
> 
> Apache Phoenix is using Tephra as transaction engine in the next release.
> 
> == Meritocracy ==
> 
> Our intent with this incubator proposal is to start building a diverse
> developer community around Tephra following the Apache meritocracy model.
> Since Tephra was initially developed in early 2013, we have had fast
> adoption and contributions within Cask Data. We are looking forward to
> new contributors. We wish to build a community based on Apache's
> meritocracy principles, working with those who contribute significantly to
> the project and welcoming them to be committers both during the incubation
> process and beyond.
> 
> == Community ==
> 
> Core developers of Tephra are at Cask Data. Recently the developer community
> has expanded to include folks from Apache Phoenix. We hope to extend our
> contributor base significantly and we will invite all who are interested
> in working on distributed transaction engine.
> 
> == Core Developers ==
> 
> A few engineers from Cask Data and outside have developed Tephra:
> Andreas Neumann, Terence Yim, Gary Helmling, Andrew Purtell and
> Poorna Chandra.
> 
> 
> == Alignment ==
> 
> The ASF is the natural choice to host the Tephra project as its goal of
> encouraging community-driven open source projects fits with our vision for
> Tephra.
> 
> Additionally, many other projects with which we are familiar and expect
> Tephra to integrate with, such as Phoenix, Zookeeper, 

Re: [VOTE] Accept Tephra into the Apache Incubator

[James Taylor]

+1 (binding)

On Thursday, March 3, 2016, Henry Saputra  wrote:

> +1 (binding)
>
> On Thu, Mar 3, 2016 at 5:29 PM, Poorna Chandra  > wrote:
>
> > Hi All,
> >
> > Tephra proposal was sent out for discussion last week. The proposal is
> > available at https://wiki.apache.org/incubator/TephraProposal
> >
> > Please vote to accept Tephra into the Apache Incubator. The vote will be
> > open for the next 72 hours.
> >
> > [ ] +1 Accept Tephra as an Apache Incubator podling.
> > [ ] +0 Abstain.
> > [ ] -1 Don’t accept Tephra as an Apache Incubator podling because ...
> >
> > Thanks,
> > Poorna.
> >
> > --
> >
> > = Abstract =
> >
> > Tephra is a system for providing globally consistent transactions on
> > top of Apache HBase and other storage engines.
> >
> > = Proposal =
> >
> > Tephra is a transaction engine for distributed data stores like Apache
> > HBase.
> > It provides ACID semantics for concurrent data operations that span over
> > region
> > boundaries in HBase using Optimistic Concurrency Control.
> >
> > = Background =
> >
> > HBase provides strong consistency with row- or region-level ACID
> > operations. However, it sacrifices cross-region and cross-table
> > consistency in favor of scalability. This trade-off requires application
> > developers to handle  the complexity of ensuring consistency when their
> > modifications span region boundaries. By providing support for global
> > transactions that span regions, tables, or multiple RPCs,
> > Tephra simplifies application development on top of HBase, without a
> > significant impact on performance or scalability for many workloads.
> >
> > Tephra leverages HBase’s native data versioning to provide
> multi-versioned
> > concurrency control (MVCC) for transactional reads and writes.
> > With MVCC capability, each transaction sees its own consistent “snapshot”
> > of
> > data, providing snapshot isolation of concurrent transactions.
> > MVCC along with conflict detection and handling enables Optimistic
> > Concurrency
> > Control.
> >
> > Tephra consists of three main components:
> >  * Transaction Server – maintains global view of transaction state,
> assigns
> >new transaction IDs and performs conflict detection;
> >  * Transaction Client – coordinates start, commit, and rollback of
> > transactions; and
> >  * Transaction Processor Coprocessor – applies filtering to the data read
> > (based
> >on a given transaction’s state) and cleans up any data from old
> >(no longer visible) transactions.
> >
> > Although Tephra only supports HBase now, it can be extended to support
> > transactions on any store that has multi-versioning and rollback
> > support. The transactions
> > can span over multiple stores and storage paradigms.
> >
> > = Rationale =
> >
> > Tephra has simple abstractions which can be used by an application to
> > add transaction support over HBase. By abstracting away transaction
> > handling using Tephra, the application is freed of
> > transaction logic, and the application developer can focus on the use
> case.
> > Also, Tephra can be extended to support transactions on data sources
> other
> > than HBase.
> >
> > By making Tephra an Apache open source project, we believe that there
> will
> > be wider adoption and more opportunities for Tephra to be integrated
> > into other Apache projects.
> >
> > = Current Status =
> >
> > Tephra was built at Cask Data Inc. initially as part of
> > open-source framework Cask Data Application Platform (CDAP)
> > [[http://cdap.io/]].
> > It was later converted into an independent open source project with
> > Apache 2.0 License [[https://github.com/caskdata/tephra]].
> >
> > Tephra is used in CDAP as the transaction engine. As part of CDAP, Tephra
> > has been deployed at multiple companies.
> >
> > Apache Phoenix is using Tephra as transaction engine in the next release.
> >
> > == Meritocracy ==
> >
> > Our intent with this incubator proposal is to start building a diverse
> > developer community around Tephra following the Apache meritocracy model.
> > Since Tephra was initially developed in early 2013, we have had fast
> > adoption and contributions within Cask Data. We are looking forward to
> > new contributors. We wish to build a community based on Apache's
> > meritocracy principles, working with those who contribute significantly
> to
> > the project and welcoming them to be committers both during the
> incubation
> > process and beyond.
> >
> > == Community ==
> >
> > Core developers of Tephra are at Cask Data. Recently the developer
> > community
> > has expanded to include folks from Apache Phoenix. We hope to extend our
> > contributor base significantly and we will invite all who are interested
> > in working on distributed transaction engine.
> >
> > == Core Developers ==
> >
> > A few engineers from Cask Data and outside have developed Tephra:
> > Andreas Neumann, Terence Yim, Gary Helmling, Andrew Purtell and

Re: [VOTE] Accept Tephra into the Apache Incubator

[Henry Saputra]

+1 (binding)

On Thu, Mar 3, 2016 at 5:29 PM, Poorna Chandra  wrote:

> Hi All,
>
> Tephra proposal was sent out for discussion last week. The proposal is
> available at https://wiki.apache.org/incubator/TephraProposal
>
> Please vote to accept Tephra into the Apache Incubator. The vote will be
> open for the next 72 hours.
>
> [ ] +1 Accept Tephra as an Apache Incubator podling.
> [ ] +0 Abstain.
> [ ] -1 Don’t accept Tephra as an Apache Incubator podling because ...
>
> Thanks,
> Poorna.
>
> --
>
> = Abstract =
>
> Tephra is a system for providing globally consistent transactions on
> top of Apache HBase and other storage engines.
>
> = Proposal =
>
> Tephra is a transaction engine for distributed data stores like Apache
> HBase.
> It provides ACID semantics for concurrent data operations that span over
> region
> boundaries in HBase using Optimistic Concurrency Control.
>
> = Background =
>
> HBase provides strong consistency with row- or region-level ACID
> operations. However, it sacrifices cross-region and cross-table
> consistency in favor of scalability. This trade-off requires application
> developers to handle  the complexity of ensuring consistency when their
> modifications span region boundaries. By providing support for global
> transactions that span regions, tables, or multiple RPCs,
> Tephra simplifies application development on top of HBase, without a
> significant impact on performance or scalability for many workloads.
>
> Tephra leverages HBase’s native data versioning to provide multi-versioned
> concurrency control (MVCC) for transactional reads and writes.
> With MVCC capability, each transaction sees its own consistent “snapshot”
> of
> data, providing snapshot isolation of concurrent transactions.
> MVCC along with conflict detection and handling enables Optimistic
> Concurrency
> Control.
>
> Tephra consists of three main components:
>  * Transaction Server – maintains global view of transaction state, assigns
>new transaction IDs and performs conflict detection;
>  * Transaction Client – coordinates start, commit, and rollback of
> transactions; and
>  * Transaction Processor Coprocessor – applies filtering to the data read
> (based
>on a given transaction’s state) and cleans up any data from old
>(no longer visible) transactions.
>
> Although Tephra only supports HBase now, it can be extended to support
> transactions on any store that has multi-versioning and rollback
> support. The transactions
> can span over multiple stores and storage paradigms.
>
> = Rationale =
>
> Tephra has simple abstractions which can be used by an application to
> add transaction support over HBase. By abstracting away transaction
> handling using Tephra, the application is freed of
> transaction logic, and the application developer can focus on the use case.
> Also, Tephra can be extended to support transactions on data sources other
> than HBase.
>
> By making Tephra an Apache open source project, we believe that there will
> be wider adoption and more opportunities for Tephra to be integrated
> into other Apache projects.
>
> = Current Status =
>
> Tephra was built at Cask Data Inc. initially as part of
> open-source framework Cask Data Application Platform (CDAP)
> [[http://cdap.io/]].
> It was later converted into an independent open source project with
> Apache 2.0 License [[https://github.com/caskdata/tephra]].
>
> Tephra is used in CDAP as the transaction engine. As part of CDAP, Tephra
> has been deployed at multiple companies.
>
> Apache Phoenix is using Tephra as transaction engine in the next release.
>
> == Meritocracy ==
>
> Our intent with this incubator proposal is to start building a diverse
> developer community around Tephra following the Apache meritocracy model.
> Since Tephra was initially developed in early 2013, we have had fast
> adoption and contributions within Cask Data. We are looking forward to
> new contributors. We wish to build a community based on Apache's
> meritocracy principles, working with those who contribute significantly to
> the project and welcoming them to be committers both during the incubation
> process and beyond.
>
> == Community ==
>
> Core developers of Tephra are at Cask Data. Recently the developer
> community
> has expanded to include folks from Apache Phoenix. We hope to extend our
> contributor base significantly and we will invite all who are interested
> in working on distributed transaction engine.
>
> == Core Developers ==
>
> A few engineers from Cask Data and outside have developed Tephra:
> Andreas Neumann, Terence Yim, Gary Helmling, Andrew Purtell and
> Poorna Chandra.
>
>
> == Alignment ==
>
> The ASF is the natural choice to host the Tephra project as its goal of
> encouraging community-driven open source projects fits with our vision for
> Tephra.
>
> Additionally, many other projects with which we are familiar and expect
> Tephra to integrate with, such as Phoenix, Zookeeper, HDFS, log4j, and
> 

[VOTE] Accept Tephra into the Apache Incubator

[Poorna Chandra]

Hi All,

Tephra proposal was sent out for discussion last week. The proposal is
available at https://wiki.apache.org/incubator/TephraProposal

Please vote to accept Tephra into the Apache Incubator. The vote will be
open for the next 72 hours.

[ ] +1 Accept Tephra as an Apache Incubator podling.
[ ] +0 Abstain.
[ ] -1 Don’t accept Tephra as an Apache Incubator podling because ...

Thanks,
Poorna.

--

= Abstract =

Tephra is a system for providing globally consistent transactions on
top of Apache HBase and other storage engines.

= Proposal =

Tephra is a transaction engine for distributed data stores like Apache HBase.
It provides ACID semantics for concurrent data operations that span over region
boundaries in HBase using Optimistic Concurrency Control.

= Background =

HBase provides strong consistency with row- or region-level ACID
operations. However, it sacrifices cross-region and cross-table
consistency in favor of scalability. This trade-off requires application
developers to handle  the complexity of ensuring consistency when their
modifications span region boundaries. By providing support for global
transactions that span regions, tables, or multiple RPCs,
Tephra simplifies application development on top of HBase, without a
significant impact on performance or scalability for many workloads.

Tephra leverages HBase’s native data versioning to provide multi-versioned
concurrency control (MVCC) for transactional reads and writes.
With MVCC capability, each transaction sees its own consistent “snapshot” of
data, providing snapshot isolation of concurrent transactions.
MVCC along with conflict detection and handling enables Optimistic Concurrency
Control.

Tephra consists of three main components:
 * Transaction Server – maintains global view of transaction state, assigns
   new transaction IDs and performs conflict detection;
 * Transaction Client – coordinates start, commit, and rollback of
transactions; and
 * Transaction Processor Coprocessor – applies filtering to the data read (based
   on a given transaction’s state) and cleans up any data from old
   (no longer visible) transactions.

Although Tephra only supports HBase now, it can be extended to support
transactions on any store that has multi-versioning and rollback
support. The transactions
can span over multiple stores and storage paradigms.

= Rationale =

Tephra has simple abstractions which can be used by an application to
add transaction support over HBase. By abstracting away transaction
handling using Tephra, the application is freed of
transaction logic, and the application developer can focus on the use case.
Also, Tephra can be extended to support transactions on data sources other
than HBase.

By making Tephra an Apache open source project, we believe that there will
be wider adoption and more opportunities for Tephra to be integrated
into other Apache projects.

= Current Status =

Tephra was built at Cask Data Inc. initially as part of
open-source framework Cask Data Application Platform (CDAP)
[[http://cdap.io/]].
It was later converted into an independent open source project with
Apache 2.0 License [[https://github.com/caskdata/tephra]].

Tephra is used in CDAP as the transaction engine. As part of CDAP, Tephra
has been deployed at multiple companies.

Apache Phoenix is using Tephra as transaction engine in the next release.

== Meritocracy ==

Our intent with this incubator proposal is to start building a diverse
developer community around Tephra following the Apache meritocracy model.
Since Tephra was initially developed in early 2013, we have had fast
adoption and contributions within Cask Data. We are looking forward to
new contributors. We wish to build a community based on Apache's
meritocracy principles, working with those who contribute significantly to
the project and welcoming them to be committers both during the incubation
process and beyond.

== Community ==

Core developers of Tephra are at Cask Data. Recently the developer community
has expanded to include folks from Apache Phoenix. We hope to extend our
contributor base significantly and we will invite all who are interested
in working on distributed transaction engine.

== Core Developers ==

A few engineers from Cask Data and outside have developed Tephra:
Andreas Neumann, Terence Yim, Gary Helmling, Andrew Purtell and
Poorna Chandra.


== Alignment ==

The ASF is the natural choice to host the Tephra project as its goal of
encouraging community-driven open source projects fits with our vision for
Tephra.

Additionally, many other projects with which we are familiar and expect
Tephra to integrate with, such as Phoenix, Zookeeper, HDFS, log4j, and others
mentioned in the External Dependencies section are Apache projects, and
Tephra will benefit by close proximity to them.

= Known Risks =

== Orphaned Products ==

There is very little risk of Tephra being orphaned, as it is a key part of
Cask Data’s products. The core Tephra developers plan to continue 

Re: HTrace 4.1 release

[Lewis John Mcgibbney]

Hi Colin,

Apologies for late response. Yes, I re-cheked the RC and I am +1 for this.
My VOTE is binding.
Thank you, good to see HTrace releasing again.
Lewis

On Thu, Mar 3, 2016 at 4:40 PM, 
wrote:

>
> From: "Colin P. McCabe" 
> To: general@incubator.apache.org
> Cc:
> Date: Thu, 3 Mar 2016 15:08:50 -0800
> Subject: Re: VOTE: HTrace 4.1 release
> Thanks, Marvin.  I'll send out the announce emails shortly.  And
> thanks for voting, everyone!
>
> best,
> Colin
>
> On Wed, Mar 2, 2016 at 1:00 PM, Marvin Humphrey 
> wrote:
> > On Wed, Mar 2, 2016 at 11:45 AM, Colin P. McCabe 
> wrote:
> >> Thanks for the comments so far, guys.
> >>
> >> Porting over the votes from the HTrace development list:
> >> Michael Stack: +1
> >> Lewis John McGibbney: +1
> >> Masatake Iwasaki: +1
> >> Elliot Clark: +1
> >> and of course myself, +1.
> >>
> >> It seems like we need another IPMC vote on this; does anyone have time
> >> to take a look?
> >
> > Justin Mclean, Lewis John McGibbney, and Michael Stack are all IPMC
> > members who have cast +1 votes in this thread.  You should be all set!
> >
> > Marvin Humphrey
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
>
> -- Forwarded message --
> From: Tsuyoshi Ozawa 
> To: general@incubator.apache.org
> Cc:
> Date: Fri, 4 Mar 2016 09:28:38 +0900
> Subject: Re: [VOTE] Accept Gearpump into the Apache Incubator
> +1(non-binding)
>
> - Tsuyoshi
>
> On Fri, Mar 4, 2016 at 4:44 AM, Ted Dunning  wrote:
> > +1 (binding)
> >
> >
> >
> > On Thu, Mar 3, 2016 at 9:30 AM, Hao Chen  wrote:
> >
> >> +1 (non-binding)
> >>
> >> Regards,
> >> Hao
> >>
> >> On Thu, Mar 3, 2016 at 9:18 AM, Felix Cheung 
> >> wrote:
> >>
> >> > +1 (non-binding)
> >> >
> >> > On Thu, Mar 3, 2016 at 9:03 AM Vasudevan, Ramkrishna S <
> >> > ramkrishna.s.vasude...@intel.com> wrote:
> >> >
> >> > > +1 (non-binding)
> >> > >
> >> > > Regards
> >> > > Ram
> >> > >
> >> > > -Original Message-
> >> > > From: Zheng, Kai [mailto:kai.zh...@intel.com]
> >> > > Sent: Wednesday, March 2, 2016 1:54 PM
> >> > > To: general@incubator.apache.org
> >> > > Subject: RE: [VOTE] Accept Gearpump into the Apache Incubator
> >> > >
> >> > > +1 (non-binding).
> >> > >
> >> > > Regards,
> >> > > Kai
> >> > >
> >> > > -Original Message-
> >> > > From: JiangAlan [mailto:whji...@outlook.com]
> >> > > Sent: Wednesday, March 02, 2016 3:21 PM
> >> > > To: general@incubator.apache.org
> >> > > Subject: RE: [VOTE] Accept Gearpump into the Apache Incubator
> >> > >
> >> > > +1 (non-binding)
> >> > >
> >> > > > From: r...@databricks.com
> >> > > > Date: Tue, 1 Mar 2016 23:14:30 -0800
> >> > > > Subject: Re: [VOTE] Accept Gearpump into the Apache Incubator
> >> > > > To: general@incubator.apache.org
> >> > > >
> >> > > > +1 (binding)
> >> > > >
> >> > > >
> >> > > > On Tue, Mar 1, 2016 at 5:05 PM, James Taylor <
> jamestay...@apache.org
> >> >
> >> > > wrote:
> >> > > >
> >> > > > > +1 (binding)
> >> > > > >
> >> > > > > On Tue, Mar 1, 2016 at 4:53 PM, Andrew Purtell <
> >> apurt...@apache.org>
> >> > > > > wrote:
> >> > > > >
> >> > > > > > Greetings,
> >> > > > > >
> >> > > > > > The discussion of the Gearpump proposal has concluded. Please
> >> vote
> >> > > > > > to accept Gearpump into the Apache Incubator. I will leave
> this
> >> > > > > > vote open
> >> > > > > for
> >> > > > > > at least the next 72 hours and will aim to close it Monday the
> >> 7th
> >> > > > > > of March, 2016 at midnight PT. Gearpump is a flexible,
> efficient,
> >> > > > > > and
> >> > > > > scalable
> >> > > > > > micro-service based real-time big data streaming engine. The
> text
> >> > > > > > of the proposal is included below and is also available at
> >> > > > > > https://wiki.apache.org/incubator/GearpumpProposal
> >> > > > > >
> >> > > > > > [ ] +1 Accept Gearpump as an Apache Incubator podling.
> >> > > > > > [ ] +0 Abstain.
> >> > > > > > [ ] -1 Don’t accept Gearpump as an Apache Incubator podling
> >> because
> >> > > ...
> >> > > > > >
> >> > > > > > Note that while votes from Incubator PMC members are binding,
> all
> >> > > > > > are
> >> > > > > most
> >> > > > > > definitely welcome to vote!
> >> > > > > >
> >> > > > > > I am +1 (binding).
> >> > > > > >
> >> > > > > > Best regards,
> >> > > > > >
> >> > > > > >- Andy
> >> > > > > >
> >> > > > > > -
> >> > > > > >
> >> > > > > > = Gearpump Proposal =
> >> > > > > >
> >> > > > > > === Abstract ===
> >> > > > > > Gearpump is a flexible, efficient and scalable micro-service
> >> based
> >> > > > > > real-time big data streaming engine developed by Intel
> >> Corporation
> >> > > > > > which has been licensed by Intel 

Re: [VOTE] Accept Gearpump into the Apache Incubator

[Jakob Homan]

+1 (binding)

On 3 March 2016 at 16:28, Tsuyoshi Ozawa  wrote:
> +1(non-binding)
>
> - Tsuyoshi
>
> On Fri, Mar 4, 2016 at 4:44 AM, Ted Dunning  wrote:
>> +1 (binding)
>>
>>
>>
>> On Thu, Mar 3, 2016 at 9:30 AM, Hao Chen  wrote:
>>
>>> +1 (non-binding)
>>>
>>> Regards,
>>> Hao
>>>
>>> On Thu, Mar 3, 2016 at 9:18 AM, Felix Cheung 
>>> wrote:
>>>
>>> > +1 (non-binding)
>>> >
>>> > On Thu, Mar 3, 2016 at 9:03 AM Vasudevan, Ramkrishna S <
>>> > ramkrishna.s.vasude...@intel.com> wrote:
>>> >
>>> > > +1 (non-binding)
>>> > >
>>> > > Regards
>>> > > Ram
>>> > >
>>> > > -Original Message-
>>> > > From: Zheng, Kai [mailto:kai.zh...@intel.com]
>>> > > Sent: Wednesday, March 2, 2016 1:54 PM
>>> > > To: general@incubator.apache.org
>>> > > Subject: RE: [VOTE] Accept Gearpump into the Apache Incubator
>>> > >
>>> > > +1 (non-binding).
>>> > >
>>> > > Regards,
>>> > > Kai
>>> > >
>>> > > -Original Message-
>>> > > From: JiangAlan [mailto:whji...@outlook.com]
>>> > > Sent: Wednesday, March 02, 2016 3:21 PM
>>> > > To: general@incubator.apache.org
>>> > > Subject: RE: [VOTE] Accept Gearpump into the Apache Incubator
>>> > >
>>> > > +1 (non-binding)
>>> > >
>>> > > > From: r...@databricks.com
>>> > > > Date: Tue, 1 Mar 2016 23:14:30 -0800
>>> > > > Subject: Re: [VOTE] Accept Gearpump into the Apache Incubator
>>> > > > To: general@incubator.apache.org
>>> > > >
>>> > > > +1 (binding)
>>> > > >
>>> > > >
>>> > > > On Tue, Mar 1, 2016 at 5:05 PM, James Taylor >> >
>>> > > wrote:
>>> > > >
>>> > > > > +1 (binding)
>>> > > > >
>>> > > > > On Tue, Mar 1, 2016 at 4:53 PM, Andrew Purtell <
>>> apurt...@apache.org>
>>> > > > > wrote:
>>> > > > >
>>> > > > > > Greetings,
>>> > > > > >
>>> > > > > > The discussion of the Gearpump proposal has concluded. Please
>>> vote
>>> > > > > > to accept Gearpump into the Apache Incubator. I will leave this
>>> > > > > > vote open
>>> > > > > for
>>> > > > > > at least the next 72 hours and will aim to close it Monday the
>>> 7th
>>> > > > > > of March, 2016 at midnight PT. Gearpump is a flexible, efficient,
>>> > > > > > and
>>> > > > > scalable
>>> > > > > > micro-service based real-time big data streaming engine. The text
>>> > > > > > of the proposal is included below and is also available at
>>> > > > > > https://wiki.apache.org/incubator/GearpumpProposal
>>> > > > > >
>>> > > > > > [ ] +1 Accept Gearpump as an Apache Incubator podling.
>>> > > > > > [ ] +0 Abstain.
>>> > > > > > [ ] -1 Don’t accept Gearpump as an Apache Incubator podling
>>> because
>>> > > ...
>>> > > > > >
>>> > > > > > Note that while votes from Incubator PMC members are binding, all
>>> > > > > > are
>>> > > > > most
>>> > > > > > definitely welcome to vote!
>>> > > > > >
>>> > > > > > I am +1 (binding).
>>> > > > > >
>>> > > > > > Best regards,
>>> > > > > >
>>> > > > > >- Andy
>>> > > > > >
>>> > > > > > -
>>> > > > > >
>>> > > > > > = Gearpump Proposal =
>>> > > > > >
>>> > > > > > === Abstract ===
>>> > > > > > Gearpump is a flexible, efficient and scalable micro-service
>>> based
>>> > > > > > real-time big data streaming engine developed by Intel
>>> Corporation
>>> > > > > > which has been licensed by Intel under the Apache License 2.0.
>>> > > > > >
>>> > > > > > === Proposal ===
>>> > > > > > Gearpump is a reactive real-time streaming engine; completely
>>> > > > > > based on
>>> > > > > the
>>> > > > > > micro-service Actor model. Gearpump provides extremely high
>>> > > > > > performance stream processing while maintaining millisecond
>>> latency
>>> > > message delivery.
>>> > > > > > It enables reusable, composable flows or partial graphs that can
>>> > > > > > be remotely deployed and executed in a diverse set of
>>> > > > > > environments,
>>> > > > > including
>>> > > > > > IoT edge devices. These flows may be deployed and modified at
>>> > > > > > runtime --
>>> > > > > a
>>> > > > > > capability few real time streaming frameworks provide today.
>>> > > > > >
>>> > > > > > The goal of this proposal is to incubate Gearpump as an Apache
>>> > > > > > project in order to build a diverse, healthy, and self-governed
>>> > > > > > open source
>>> > > > > community
>>> > > > > > around this project.
>>> > > > > >
>>> > > > > > === Background ===
>>> > > > > > In past decade, there have been many advances within real-time
>>> > > > > > streaming frameworks. Despite many advances, users of streaming
>>> > > > > > frameworks often complain about flexibility, efficiency, and
>>> > > > > > scalability. Gearpump
>>> > > > > endeavors
>>> > > > > > to solve these challenges by adopting the micro-service Actor
>>> > > > > > model. The Actor model was proposed by Carl Hewitt in 1973. In
>>> the
>>> > > > > > Actor model, each actor is a message driven micro-service; actors
>>> > > > > > are the basic building blocks of concurrent computation. By
>>> > > > > > leveraging Actor Model’s 

RE: [VOTE] Accept Mnemonic into the Apache Incubator

[Cheng, Hao]

+1 (binding)

Hao

-Original Message-
From: Ted Dunning [mailto:ted.dunn...@gmail.com] 
Sent: Friday, March 4, 2016 5:32 AM
To: general@incubator.apache.org
Subject: Re: [VOTE] Accept Mnemonic into the Apache Incubator

I thought I sent a vote in earlier today but I may have hit the wrong thread.

Please accept this vote.

+1 (binding)



On Thu, Mar 3, 2016 at 11:19 AM, P. Taylor Goetz  wrote:

> +1 (binding)
>
> -Taylor
>
> > On Feb 29, 2016, at 12:37 PM, Patrick Hunt  wrote:
> >
> > Hi folks,
> >
> > OK the discussion is now completed. Please VOTE to accept Mnemonic 
> > into the Apache Incubator. I’ll leave the VOTE open for at least the 
> > next 72 hours, with hopes to close it Thursday the 3rd of March, 
> > 2016 at 10am PT.
> > https://wiki.apache.org/incubator/MnemonicProposal
> >
> > [ ] +1 Accept Mnemonic as an Apache Incubator podling.
> > [ ] +0 Abstain.
> > [ ] -1 Don’t accept Mnemonic as an Apache Incubator podling because..
> >
> > Of course, I am +1 on this. Please note VOTEs from Incubator PMC 
> > members are binding but all are welcome to VOTE!
> >
> > Regards,
> >
> > Patrick
> >
> > 
> > = Mnemonic Proposal =
> > === Abstract ===
> > Mnemonic is a Java based non-volatile memory library for in-place 
> > structured data processing and computing. It is a solution for 
> > generic object and block persistence on heterogeneous block and 
> > byte-addressable devices, such as DRAM, persistent memory, NVMe, 
> > SSD, and cloud network storage.
> >
> > === Proposal ===
> > Mnemonic is a structured data persistence in-memory in-place library 
> > for Java-based applications and frameworks. It provides unified 
> > interfaces for data manipulation on heterogeneous 
> > block/byte-addressable devices, such as DRAM, persistent memory, 
> > NVMe, SSD, and cloud network devices.
> >
> > The design motivation for this project is to create a non-volatile 
> > programming paradigm for in-memory data object persistence, 
> > in-memory data objects caching, and JNI-less IPC.
> > Mnemonic simplifies the usage of data object caching, persistence, 
> > and JNI-less IPC for massive object oriented structural datasets.
> >
> > Mnemonic defines Non-Volatile Java objects that store data fields in 
> > persistent memory and storage. During the program runtime, only 
> > methods and volatile fields are instantiated in Java heap, 
> > Non-Volatile data fields are directly accessed via GET/SET operation 
> > to and from persistent memory and storage. Mnemonic avoids SerDes 
> > and significantly reduces amount of garbage in Java heap.
> >
> > Major features of Mnemonic:
> > * Provides an abstract level of viewpoint to utilize heterogeneous 
> > block/byte-addressable device as a whole (e.g., DRAM, persistent 
> > memory, NVMe, SSD, HD, cloud network Storage).
> >
> > * Provides seamless support object oriented design and programming 
> > without adding burden to transfer object data to different form.
> >
> > * Avoids the object data serialization/de-serialization for data 
> > retrieval, caching and storage.
> >
> > * Reduces the consumption of on-heap memory and in turn to reduce 
> > and stabilize Java Garbage Collection (GC) pauses for latency 
> > sensitive applications.
> >
> > * Overcomes current limitations of Java GC to manage much larger 
> > memory resources for massive dataset processing and computing.
> >
> > * Supports the migration data usage model from traditional 
> > NVMe/SSD/HD to non-volatile memory with ease.
> >
> > * Uses lazy loading mechanism to avoid unnecessary memory 
> > consumption if some data does not need to use for computing immediately.
> >
> > * Bypasses JNI call for the interaction between Java runtime 
> > application and its native code.
> >
> > * Provides an allocation aware auto-reclaim mechanism to prevent 
> > external memory resource leaking.
> >
> >
> > === Background ===
> > Big Data and Cloud applications increasingly require both high 
> > throughput and low latency processing. Java-based applications 
> > targeting the Big Data and Cloud space should be tuned for better 
> > throughput, lower latency, and more predictable response time.
> > Typically, there are some issues that impact BigData applications'
> > performance and scalability:
> >
> > 1) The Complexity of Data Transformation/Organization: In most 
> > cases, during data processing, applications use their own 
> > complicated data caching mechanism for SerDes data objects, spilling 
> > to different storage and eviction large amount of data. Some data 
> > objects contains complex values and structure that will make it much 
> > more difficulty for data organization. To load and then parse/decode 
> > its datasets from storage consumes high system resource and computation 
> > power.
> >
> > 2) Lack of Caching, Burst Temporary Object Creation/Destruction 
> > Causes Frequent Long GC Pauses: Big Data computing/syntax generates 
> > large 

Re: [VOTE] Accept Gearpump into the Apache Incubator

[Tsuyoshi Ozawa]

+1(non-binding)

- Tsuyoshi

On Fri, Mar 4, 2016 at 4:44 AM, Ted Dunning  wrote:
> +1 (binding)
>
>
>
> On Thu, Mar 3, 2016 at 9:30 AM, Hao Chen  wrote:
>
>> +1 (non-binding)
>>
>> Regards,
>> Hao
>>
>> On Thu, Mar 3, 2016 at 9:18 AM, Felix Cheung 
>> wrote:
>>
>> > +1 (non-binding)
>> >
>> > On Thu, Mar 3, 2016 at 9:03 AM Vasudevan, Ramkrishna S <
>> > ramkrishna.s.vasude...@intel.com> wrote:
>> >
>> > > +1 (non-binding)
>> > >
>> > > Regards
>> > > Ram
>> > >
>> > > -Original Message-
>> > > From: Zheng, Kai [mailto:kai.zh...@intel.com]
>> > > Sent: Wednesday, March 2, 2016 1:54 PM
>> > > To: general@incubator.apache.org
>> > > Subject: RE: [VOTE] Accept Gearpump into the Apache Incubator
>> > >
>> > > +1 (non-binding).
>> > >
>> > > Regards,
>> > > Kai
>> > >
>> > > -Original Message-
>> > > From: JiangAlan [mailto:whji...@outlook.com]
>> > > Sent: Wednesday, March 02, 2016 3:21 PM
>> > > To: general@incubator.apache.org
>> > > Subject: RE: [VOTE] Accept Gearpump into the Apache Incubator
>> > >
>> > > +1 (non-binding)
>> > >
>> > > > From: r...@databricks.com
>> > > > Date: Tue, 1 Mar 2016 23:14:30 -0800
>> > > > Subject: Re: [VOTE] Accept Gearpump into the Apache Incubator
>> > > > To: general@incubator.apache.org
>> > > >
>> > > > +1 (binding)
>> > > >
>> > > >
>> > > > On Tue, Mar 1, 2016 at 5:05 PM, James Taylor > >
>> > > wrote:
>> > > >
>> > > > > +1 (binding)
>> > > > >
>> > > > > On Tue, Mar 1, 2016 at 4:53 PM, Andrew Purtell <
>> apurt...@apache.org>
>> > > > > wrote:
>> > > > >
>> > > > > > Greetings,
>> > > > > >
>> > > > > > The discussion of the Gearpump proposal has concluded. Please
>> vote
>> > > > > > to accept Gearpump into the Apache Incubator. I will leave this
>> > > > > > vote open
>> > > > > for
>> > > > > > at least the next 72 hours and will aim to close it Monday the
>> 7th
>> > > > > > of March, 2016 at midnight PT. Gearpump is a flexible, efficient,
>> > > > > > and
>> > > > > scalable
>> > > > > > micro-service based real-time big data streaming engine. The text
>> > > > > > of the proposal is included below and is also available at
>> > > > > > https://wiki.apache.org/incubator/GearpumpProposal
>> > > > > >
>> > > > > > [ ] +1 Accept Gearpump as an Apache Incubator podling.
>> > > > > > [ ] +0 Abstain.
>> > > > > > [ ] -1 Don’t accept Gearpump as an Apache Incubator podling
>> because
>> > > ...
>> > > > > >
>> > > > > > Note that while votes from Incubator PMC members are binding, all
>> > > > > > are
>> > > > > most
>> > > > > > definitely welcome to vote!
>> > > > > >
>> > > > > > I am +1 (binding).
>> > > > > >
>> > > > > > Best regards,
>> > > > > >
>> > > > > >- Andy
>> > > > > >
>> > > > > > -
>> > > > > >
>> > > > > > = Gearpump Proposal =
>> > > > > >
>> > > > > > === Abstract ===
>> > > > > > Gearpump is a flexible, efficient and scalable micro-service
>> based
>> > > > > > real-time big data streaming engine developed by Intel
>> Corporation
>> > > > > > which has been licensed by Intel under the Apache License 2.0.
>> > > > > >
>> > > > > > === Proposal ===
>> > > > > > Gearpump is a reactive real-time streaming engine; completely
>> > > > > > based on
>> > > > > the
>> > > > > > micro-service Actor model. Gearpump provides extremely high
>> > > > > > performance stream processing while maintaining millisecond
>> latency
>> > > message delivery.
>> > > > > > It enables reusable, composable flows or partial graphs that can
>> > > > > > be remotely deployed and executed in a diverse set of
>> > > > > > environments,
>> > > > > including
>> > > > > > IoT edge devices. These flows may be deployed and modified at
>> > > > > > runtime --
>> > > > > a
>> > > > > > capability few real time streaming frameworks provide today.
>> > > > > >
>> > > > > > The goal of this proposal is to incubate Gearpump as an Apache
>> > > > > > project in order to build a diverse, healthy, and self-governed
>> > > > > > open source
>> > > > > community
>> > > > > > around this project.
>> > > > > >
>> > > > > > === Background ===
>> > > > > > In past decade, there have been many advances within real-time
>> > > > > > streaming frameworks. Despite many advances, users of streaming
>> > > > > > frameworks often complain about flexibility, efficiency, and
>> > > > > > scalability. Gearpump
>> > > > > endeavors
>> > > > > > to solve these challenges by adopting the micro-service Actor
>> > > > > > model. The Actor model was proposed by Carl Hewitt in 1973. In
>> the
>> > > > > > Actor model, each actor is a message driven micro-service; actors
>> > > > > > are the basic building blocks of concurrent computation. By
>> > > > > > leveraging Actor Model’s location transparency feature,Gearpump
>> > > > > > allows a graph to be composed of several partial graphs, where,
>> > > > > > for example, some parts may be deployed to remote IoT edge
>> > > > > > devices, and other parts to a 

Re: Possible ASF Incubator Project transfer..

[John D. Ament]

You need to start with convincing oracle to provide an SGA for the entire
glassfish codebase.  Your best bet is to start that before you leave
oracle.

John

On Thu, Mar 3, 2016 at 4:08 PM Reza Rahman  wrote:

> Obviously I need to take this up in earnest after Friday. In the meanwhile
> let me know what I need to do in order to get myself setup for this.
>
> Anything that is worth it is never easy. This matters enough to try and
> there are many that will be with us, even inside Oracle.
>
> On Mar 3, 2016, at 3:57 PM, John D. Ament  wrote:
>
> Hi Martin, Reza,
>
> The biggest hurdle would likely be Oracle signing an SGA for the glassfish
> codebase.  Not to mention that all dependencies are currently GPL/CDDL dual
> licensed.
>
> John
>
> On Thu, Mar 3, 2016 at 3:17 PM Martin Gainty  wrote:
>
>> Looking for procedures for transferring control of currently
>> un-maintained glassfish J2EE Server from Oracle to ASF incubator project
>>
>> Thanks and Regards
>> Martin Gainty
>>
>>
>> Subject: Re: [gf-users] Re: Farewell to Oracle
>> To: mgai...@hotmail.com
>> From: reza_rah...@lycos.com
>> Date: Thu, 3 Mar 2016 13:56:02 -0500
>>
>>
>>
>>
>>
>>
>> That sounds just about right. How can I
>>   get involved?
>>
>>
>>
>>   On 3/3/2016 1:53 PM, Martin Gainty wrote:
>>
>>
>>
>>
>>   Feel free to join Marcus and myself to transfer
>> Glassfish to ASF  ..
>>
>>
>>
>>
>>
>>
>>   > To: us...@glassfish.java.net
>>
>> > From: reza_rah...@lycos.com
>>
>> > Date: Thu, 3 Mar 2016 12:51:49 -0500
>>
>> > Subject: [gf-users] Farewell to Oracle
>>
>> >
>>
>> > Folks,
>>
>> >
>>
>> > I am leaving Oracle behind on Friday. I have no doubt
>> whatsoever that
>>
>> > this was one of the top five hardest decisions of my
>> life. I am also at
>>
>> > this stage equally certain that this is the way I
>> personally can best
>>
>> > help continue to advance the Java and Java EE
>> communities. I will be
>>
>> > resuming the community work I have been part of for the
>> better part of a
>>
>> > decade in earnest as soon as possible post-Oracle.
>>
>> >
>>
>> > At Oracle folks like my colleagues David Delabassee and
>> Bruno Borges
>>
>> > will continue their roles in the Java EE ecosystem. I
>> certainly wish the
>>
>> > many good folks at Oracle nothing but the best of luck.
>> They have a very
>>
>> > hard job to do and they will continue to need our
>> support, perhaps now
>>
>> > more than ever.
>>
>> >
>>
>> > As always anyone is absolutely welcome to reach out to
>> me on just about
>>
>> > anything. Below are all my contact points.
>>
>> >
>>
>> > Cheers,
>>
>> > Reza
>>
>> >
>>
>> > Email: reza_rah...@lycos.com
>>
>> > Cell: 717-329-8149
>>
>> > Home Office: 215-736-1208
>>
>> > Google/Skype: m.reza.rahman
>>
>> > Twitter: @reza_rahman
>>
>> > https://www.linkedin.com/in/javareza
>>
>> > http://blog.rahmannet.net/
>>
>> > http://cargotracker.java.net
>>
>>
>>
>>
>>
>>
>>
>
>

Re: VOTE: HTrace 4.1 release

[Colin P. McCabe]

Thanks, Marvin.  I'll send out the announce emails shortly.  And
thanks for voting, everyone!

best,
Colin

On Wed, Mar 2, 2016 at 1:00 PM, Marvin Humphrey  wrote:
> On Wed, Mar 2, 2016 at 11:45 AM, Colin P. McCabe  wrote:
>> Thanks for the comments so far, guys.
>>
>> Porting over the votes from the HTrace development list:
>> Michael Stack: +1
>> Lewis John McGibbney: +1
>> Masatake Iwasaki: +1
>> Elliot Clark: +1
>> and of course myself, +1.
>>
>> It seems like we need another IPMC vote on this; does anyone have time
>> to take a look?
>
> Justin Mclean, Lewis John McGibbney, and Michael Stack are all IPMC
> members who have cast +1 votes in this thread.  You should be all set!
>
> Marvin Humphrey
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT] [VOTE] Accept Mnemonic as an Apache Incubator Podling

[Patrick Hunt]

This vote has PASSED with the following tallies:

+1 Binding total 9
Patrick Hunt
Jacques Nadeau
Henry Saputra
James Taylor
Andrew Purtell
Chris Nauroth
Arvind Prabhakar
P. Taylor Goetz
Ted Dunning

+1 No-binding, total 11
Phillip Rhodes
Ramkrishna S Vasudevan
Uma Gangumalla
Debo Dutta
Tsuyoshi Ozawa
Kai Zheng
Liang Chen
Dapeng Sun
Priyank Ashok Rastogi
Sravya Tirukkovalur
Hao Hao

No other votes were submitted.

Thanks to everyone who voted. The mentors will now assist in getting
the project bootstrapped.

Regards,

Patrick

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Possible ASF Incubator Project transfer..

[David Blevins]

The procedure would be identical to the OpenOffice donation from Oracle to
Apache.  Oracle would have to sign a software grant to Apache and
contributors would have to iCLAs. Apache requires copyright owners to vouch
they are the original authors and have given permission for their IP to be
licensed under the Apache Software License.

It would not be possible to "fork" to Apache without sign-off from Oracle.


-David

On Thu, Mar 3, 2016 at 12:17 PM, Martin Gainty  wrote:

> Looking for procedures for transferring control of currently un-maintained
> glassfish J2EE Server from Oracle to ASF incubator project
>
> Thanks and Regards
> Martin Gainty
>
>
> Subject: Re: [gf-users] Re: Farewell to Oracle
> To: mgai...@hotmail.com
> From: reza_rah...@lycos.com
> Date: Thu, 3 Mar 2016 13:56:02 -0500
>
>
>
>
>
>
> That sounds just about right. How can I
>   get involved?
>
>
>
>   On 3/3/2016 1:53 PM, Martin Gainty wrote:
>
>
>
>
>   Feel free to join Marcus and myself to transfer
> Glassfish to ASF  ..
>
>
>
>
>
>
>   > To: us...@glassfish.java.net
>
> > From: reza_rah...@lycos.com
>
> > Date: Thu, 3 Mar 2016 12:51:49 -0500
>
> > Subject: [gf-users] Farewell to Oracle
>
> >
>
> > Folks,
>
> >
>
> > I am leaving Oracle behind on Friday. I have no doubt
> whatsoever that
>
> > this was one of the top five hardest decisions of my
> life. I am also at
>
> > this stage equally certain that this is the way I
> personally can best
>
> > help continue to advance the Java and Java EE
> communities. I will be
>
> > resuming the community work I have been part of for the
> better part of a
>
> > decade in earnest as soon as possible post-Oracle.
>
> >
>
> > At Oracle folks like my colleagues David Delabassee and
> Bruno Borges
>
> > will continue their roles in the Java EE ecosystem. I
> certainly wish the
>
> > many good folks at Oracle nothing but the best of luck.
> They have a very
>
> > hard job to do and they will continue to need our
> support, perhaps now
>
> > more than ever.
>
> >
>
> > As always anyone is absolutely welcome to reach out to
> me on just about
>
> > anything. Below are all my contact points.
>
> >
>
> > Cheers,
>
> > Reza
>
> >
>
> > Email: reza_rah...@lycos.com
>
> > Cell: 717-329-8149
>
> > Home Office: 215-736-1208
>
> > Google/Skype: m.reza.rahman
>
> > Twitter: @reza_rahman
>
> > https://www.linkedin.com/in/javareza
>
> > http://blog.rahmannet.net/
>
> > http://cargotracker.java.net
>
>
>
>
>
>
>

Re: [VOTE] Accept Mnemonic into the Apache Incubator

[Ted Dunning]

I thought I sent a vote in earlier today but I may have hit the wrong
thread.

Please accept this vote.

+1 (binding)



On Thu, Mar 3, 2016 at 11:19 AM, P. Taylor Goetz  wrote:

> +1 (binding)
>
> -Taylor
>
> > On Feb 29, 2016, at 12:37 PM, Patrick Hunt  wrote:
> >
> > Hi folks,
> >
> > OK the discussion is now completed. Please VOTE to accept Mnemonic
> > into the Apache Incubator. I’ll leave the VOTE open for at least
> > the next 72 hours, with hopes to close it Thursday the 3rd of
> > March, 2016 at 10am PT.
> > https://wiki.apache.org/incubator/MnemonicProposal
> >
> > [ ] +1 Accept Mnemonic as an Apache Incubator podling.
> > [ ] +0 Abstain.
> > [ ] -1 Don’t accept Mnemonic as an Apache Incubator podling because..
> >
> > Of course, I am +1 on this. Please note VOTEs from Incubator PMC
> > members are binding but all are welcome to VOTE!
> >
> > Regards,
> >
> > Patrick
> >
> > 
> > = Mnemonic Proposal =
> > === Abstract ===
> > Mnemonic is a Java based non-volatile memory library for in-place
> > structured data processing and computing. It is a solution for generic
> > object and block persistence on heterogeneous block and
> > byte-addressable devices, such as DRAM, persistent memory, NVMe, SSD,
> > and cloud network storage.
> >
> > === Proposal ===
> > Mnemonic is a structured data persistence in-memory in-place library
> > for Java-based applications and frameworks. It provides unified
> > interfaces for data manipulation on heterogeneous
> > block/byte-addressable devices, such as DRAM, persistent memory, NVMe,
> > SSD, and cloud network devices.
> >
> > The design motivation for this project is to create a non-volatile
> > programming paradigm for in-memory data object persistence, in-memory
> > data objects caching, and JNI-less IPC.
> > Mnemonic simplifies the usage of data object caching, persistence, and
> > JNI-less IPC for massive object oriented structural datasets.
> >
> > Mnemonic defines Non-Volatile Java objects that store data fields in
> > persistent memory and storage. During the program runtime, only
> > methods and volatile fields are instantiated in Java heap,
> > Non-Volatile data fields are directly accessed via GET/SET operation
> > to and from persistent memory and storage. Mnemonic avoids SerDes and
> > significantly reduces amount of garbage in Java heap.
> >
> > Major features of Mnemonic:
> > * Provides an abstract level of viewpoint to utilize heterogeneous
> > block/byte-addressable device as a whole (e.g., DRAM, persistent
> > memory, NVMe, SSD, HD, cloud network Storage).
> >
> > * Provides seamless support object oriented design and programming
> > without adding burden to transfer object data to different form.
> >
> > * Avoids the object data serialization/de-serialization for data
> > retrieval, caching and storage.
> >
> > * Reduces the consumption of on-heap memory and in turn to reduce and
> > stabilize Java Garbage Collection (GC) pauses for latency sensitive
> > applications.
> >
> > * Overcomes current limitations of Java GC to manage much larger
> > memory resources for massive dataset processing and computing.
> >
> > * Supports the migration data usage model from traditional NVMe/SSD/HD
> > to non-volatile memory with ease.
> >
> > * Uses lazy loading mechanism to avoid unnecessary memory consumption
> > if some data does not need to use for computing immediately.
> >
> > * Bypasses JNI call for the interaction between Java runtime
> > application and its native code.
> >
> > * Provides an allocation aware auto-reclaim mechanism to prevent
> > external memory resource leaking.
> >
> >
> > === Background ===
> > Big Data and Cloud applications increasingly require both high
> > throughput and low latency processing. Java-based applications
> > targeting the Big Data and Cloud space should be tuned for better
> > throughput, lower latency, and more predictable response time.
> > Typically, there are some issues that impact BigData applications'
> > performance and scalability:
> >
> > 1) The Complexity of Data Transformation/Organization: In most cases,
> > during data processing, applications use their own complicated data
> > caching mechanism for SerDes data objects, spilling to different
> > storage and eviction large amount of data. Some data objects contains
> > complex values and structure that will make it much more difficulty
> > for data organization. To load and then parse/decode its datasets from
> > storage consumes high system resource and computation power.
> >
> > 2) Lack of Caching, Burst Temporary Object Creation/Destruction Causes
> > Frequent Long GC Pauses: Big Data computing/syntax generates large
> > amount of temporary objects during processing, e.g. lambda, SerDes,
> > copying and etc. This will trigger frequent long Java GC pause to scan
> > references, to update references lists, and to copy live objects from
> > one memory location to another blindly.
> >
> > 3) The 

Re: [VOTE] Release taverna-language-0.15.1-incubating-RC5 and taverna-osgi-0.2.1-incubating-RC5

[Pierce, Marlon]

+1 (binding) for all three release components.




On 3/2/16, 12:07 PM, "Stian Soiland-Reyes"  wrote:

>I am pleased to be calling this vote for the source release of
>
>  Apache Taverna Maven Parent 2-incubating
>  Apache Taverna Language 0.15.1-incubating
>  Apache Taverna OSGi plugin system 0.2.1-incubating
>
>The Apache Taverna IPMC has voted in favour of this release with 5 IPMC votes:
>
>http://markmail.org/message/346xxkywuexw6z52
>http://mail-archives.apache.org/mod_mbox/taverna-dev/201603.mbox/
>
>We now ask for the Incubator PMC to vote on this release candidate.
>
>
>Apache Taverna Language is a set of APIs for workflow definitions
>(SCUFL2) and workflow inputs/outputs/run (DataBundle), as consumed and
>produced by the Apache Taverna workflow system. The API includes
>support for working with Research Object Bundles, and loading/saving
>Taverna workflows in different formats.
>
>Apache Taverna OSGi is a plugin system for OSGi with support for
>online updates, which can be used by Java desktop and command line
>applications.
>
>
>The release candidates to be voted over are available at:
>
>  
> https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-parent-2-incubating-RC5/
>  
> https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-language-0.15.1-incubating-RC5/
>  
> https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-osgi-0.2.1-incubating-RC5/
>
>
>Checksums:
>
>md5sum:
>8e7ee332896d314877af481b348dbf51
>apache-taverna-parent-2-incubating-source-release.zip
>
>6bd8ae9e2b1bc2e675e5573b87feaa2a
>apache-taverna-language-0.15.1-incubating-source-release.zip
>
>4d595212a813f62a0c16a31d3a872af4
>apache-taverna-osgi-0.2.1-incubating-source-release.zip
>
>
>sha1sum:
>d4b675763eb03bc5a9863db27779d725e1209af6
>apache-taverna-parent-2-incubating-source-release.zip
>
>af3a14ec6d9386e9aa97309275f7b147be6f0a38
>apache-taverna-language-0.15.1-incubating-source-release.zip
>
>2e91b5176322c0e029e1a856f0752159b1564158
>apache-taverna-osgi-0.2.1-incubating-source-release.zip
>
>
>sha512sum:
>d5787ba7066d0d3b7c3b292434eb3de909c8ebaf43f0a3ea5e9dd25f0f19b5c1b7d508ffde97c0e6afd53265835d1aa4f22bb3187011b50b7f5aac99892bd0aa
>apache-taverna-parent-2-incubating-source-release.zip
>
>7cb4860abb4c57b91e81703a0d362d2824f10f1d2abe62c3df028fdca4f3ce33c4fe572c3349e629c8d409a7b25f3c86b79487d840c642a4b39e84432aa86c04
>apache-taverna-language-0.15.1-incubating-source-release.zip
>
>31b50a87243a01f3a5a657643d0f3b7f56d86fcc309df74392df3915ef8a787948ff8c74bc6a7684e6f9049b6430324373c50959ff658803dbc2d67d8a3dc45c
>apache-taverna-osgi-0.2.1-incubating-source-release.zip
>
>
>
>To build the release candidates you need Apache Maven 3 and Java 8.
>
>
>Build the release candidate, in the above order, using:
>
>mvn clean install
>
>
>The release candidates correspond to the following git commits:
>
>  
> https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-maven-parent.git;a=commit;h=d34dd67fcfa11caead08008d37279b1ea546e3ec
>
>  
> https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-language.git;a=commit;h=66866a5454ed23262c055f65155d7a195c68a17d
>
>  
> https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-osgi.git;a=commit;h=0b7da331e81febade5ce2f4cf1f068013002b7aa
>
>
>Release candidates are signed with a GPG key available at:
>
>  https://dist.apache.org/repos/dist/release/incubator/taverna/KEYS
>
>A staged Maven repository is available for review at:
>
>  https://repository.apache.org/content/repositories/orgapachetaverna-1011/
>
>The changelog for this release is available from JIRA:
>
>  
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333249=12318322
>  
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333250=12318322
>  
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12332248=12318322
>
>
>Please vote on releasing these packages as:
>
>  Apache Taverna Maven Parent 2-incubating
>  Apache Taverna Language 0.15.1-incubating
>  Apache Taverna OSGi plugin system 0.2.1-incubating
>
>
>The vote is open for at least 72 hours
>(let's say Monday 2016-03-07 17:00 GMT)
>and passes if a majority of at least
>three +1 Incubator PMC votes are cast.
>
>[ ] +1 Release this package
>[ ]  0 I don't feel strongly about it, but don't object
>[ ] -1 Do not release this package because...
>
>Anyone can participate in testing and voting, not just Incubator PMC
>members, please feel free to try out the release candidate and provide
>your votes.
>
>
>--
>Stian Soiland-Reyes
>Apache Taverna (incubating), Apache Commons RDF (incubating)
>http://orcid.org/-0001-9842-9718
>
>-
>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>For additional commands, e-mail: general-h...@incubator.apache.org
>

Re: Possible ASF Incubator Project transfer..

[John D. Ament]

Hi Martin, Reza,

The biggest hurdle would likely be Oracle signing an SGA for the glassfish
codebase.  Not to mention that all dependencies are currently GPL/CDDL dual
licensed.

John

On Thu, Mar 3, 2016 at 3:17 PM Martin Gainty  wrote:

> Looking for procedures for transferring control of currently un-maintained
> glassfish J2EE Server from Oracle to ASF incubator project
>
> Thanks and Regards
> Martin Gainty
>
>
> Subject: Re: [gf-users] Re: Farewell to Oracle
> To: mgai...@hotmail.com
> From: reza_rah...@lycos.com
> Date: Thu, 3 Mar 2016 13:56:02 -0500
>
>
>
>
>
>
> That sounds just about right. How can I
>   get involved?
>
>
>
>   On 3/3/2016 1:53 PM, Martin Gainty wrote:
>
>
>
>
>   Feel free to join Marcus and myself to transfer
> Glassfish to ASF  ..
>
>
>
>
>
>
>   > To: us...@glassfish.java.net
>
> > From: reza_rah...@lycos.com
>
> > Date: Thu, 3 Mar 2016 12:51:49 -0500
>
> > Subject: [gf-users] Farewell to Oracle
>
> >
>
> > Folks,
>
> >
>
> > I am leaving Oracle behind on Friday. I have no doubt
> whatsoever that
>
> > this was one of the top five hardest decisions of my
> life. I am also at
>
> > this stage equally certain that this is the way I
> personally can best
>
> > help continue to advance the Java and Java EE
> communities. I will be
>
> > resuming the community work I have been part of for the
> better part of a
>
> > decade in earnest as soon as possible post-Oracle.
>
> >
>
> > At Oracle folks like my colleagues David Delabassee and
> Bruno Borges
>
> > will continue their roles in the Java EE ecosystem. I
> certainly wish the
>
> > many good folks at Oracle nothing but the best of luck.
> They have a very
>
> > hard job to do and they will continue to need our
> support, perhaps now
>
> > more than ever.
>
> >
>
> > As always anyone is absolutely welcome to reach out to
> me on just about
>
> > anything. Below are all my contact points.
>
> >
>
> > Cheers,
>
> > Reza
>
> >
>
> > Email: reza_rah...@lycos.com
>
> > Cell: 717-329-8149
>
> > Home Office: 215-736-1208
>
> > Google/Skype: m.reza.rahman
>
> > Twitter: @reza_rahman
>
> > https://www.linkedin.com/in/javareza
>
> > http://blog.rahmannet.net/
>
> > http://cargotracker.java.net
>
>
>
>
>
>
>

Possible ASF Incubator Project transfer..

[Martin Gainty]

Looking for procedures for transferring control of currently un-maintained 
glassfish J2EE Server from Oracle to ASF incubator project
 
Thanks and Regards
Martin Gainty 


Subject: Re: [gf-users] Re: Farewell to Oracle
To: mgai...@hotmail.com
From: reza_rah...@lycos.com
Date: Thu, 3 Mar 2016 13:56:02 -0500


  

  
  
That sounds just about right. How can I
  get involved?

  

  On 3/3/2016 1:53 PM, Martin Gainty wrote:



  
  Feel free to join Marcus and myself to transfer
Glassfish to ASF  ..
  

  

  

  > To: us...@glassfish.java.net

> From: reza_rah...@lycos.com

> Date: Thu, 3 Mar 2016 12:51:49 -0500

> Subject: [gf-users] Farewell to Oracle

> 

> Folks,

> 

> I am leaving Oracle behind on Friday. I have no doubt
whatsoever that 

> this was one of the top five hardest decisions of my
life. I am also at 

> this stage equally certain that this is the way I
personally can best 

> help continue to advance the Java and Java EE
communities. I will be 

> resuming the community work I have been part of for the
better part of a 

> decade in earnest as soon as possible post-Oracle.

> 

> At Oracle folks like my colleagues David Delabassee and
Bruno Borges 

> will continue their roles in the Java EE ecosystem. I
certainly wish the 

> many good folks at Oracle nothing but the best of luck.
They have a very 

> hard job to do and they will continue to need our
support, perhaps now 

> more than ever.

> 

> As always anyone is absolutely welcome to reach out to
me on just about 

> anything. Below are all my contact points.

> 

> Cheers,

> Reza

> 

> Email: reza_rah...@lycos.com

> Cell: 717-329-8149

> Home Office: 215-736-1208

> Google/Skype: m.reza.rahman

> Twitter: @reza_rahman

> https://www.linkedin.com/in/javareza

> http://blog.rahmannet.net/

> http://cargotracker.java.net

  

  


  

Re: [VOTE] Accept Gearpump into the Apache Incubator

[Ted Dunning]

+1 (binding)



On Thu, Mar 3, 2016 at 9:30 AM, Hao Chen  wrote:

> +1 (non-binding)
>
> Regards,
> Hao
>
> On Thu, Mar 3, 2016 at 9:18 AM, Felix Cheung 
> wrote:
>
> > +1 (non-binding)
> >
> > On Thu, Mar 3, 2016 at 9:03 AM Vasudevan, Ramkrishna S <
> > ramkrishna.s.vasude...@intel.com> wrote:
> >
> > > +1 (non-binding)
> > >
> > > Regards
> > > Ram
> > >
> > > -Original Message-
> > > From: Zheng, Kai [mailto:kai.zh...@intel.com]
> > > Sent: Wednesday, March 2, 2016 1:54 PM
> > > To: general@incubator.apache.org
> > > Subject: RE: [VOTE] Accept Gearpump into the Apache Incubator
> > >
> > > +1 (non-binding).
> > >
> > > Regards,
> > > Kai
> > >
> > > -Original Message-
> > > From: JiangAlan [mailto:whji...@outlook.com]
> > > Sent: Wednesday, March 02, 2016 3:21 PM
> > > To: general@incubator.apache.org
> > > Subject: RE: [VOTE] Accept Gearpump into the Apache Incubator
> > >
> > > +1 (non-binding)
> > >
> > > > From: r...@databricks.com
> > > > Date: Tue, 1 Mar 2016 23:14:30 -0800
> > > > Subject: Re: [VOTE] Accept Gearpump into the Apache Incubator
> > > > To: general@incubator.apache.org
> > > >
> > > > +1 (binding)
> > > >
> > > >
> > > > On Tue, Mar 1, 2016 at 5:05 PM, James Taylor  >
> > > wrote:
> > > >
> > > > > +1 (binding)
> > > > >
> > > > > On Tue, Mar 1, 2016 at 4:53 PM, Andrew Purtell <
> apurt...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Greetings,
> > > > > >
> > > > > > The discussion of the Gearpump proposal has concluded. Please
> vote
> > > > > > to accept Gearpump into the Apache Incubator. I will leave this
> > > > > > vote open
> > > > > for
> > > > > > at least the next 72 hours and will aim to close it Monday the
> 7th
> > > > > > of March, 2016 at midnight PT. Gearpump is a flexible, efficient,
> > > > > > and
> > > > > scalable
> > > > > > micro-service based real-time big data streaming engine. The text
> > > > > > of the proposal is included below and is also available at
> > > > > > https://wiki.apache.org/incubator/GearpumpProposal
> > > > > >
> > > > > > [ ] +1 Accept Gearpump as an Apache Incubator podling.
> > > > > > [ ] +0 Abstain.
> > > > > > [ ] -1 Don’t accept Gearpump as an Apache Incubator podling
> because
> > > ...
> > > > > >
> > > > > > Note that while votes from Incubator PMC members are binding, all
> > > > > > are
> > > > > most
> > > > > > definitely welcome to vote!
> > > > > >
> > > > > > I am +1 (binding).
> > > > > >
> > > > > > Best regards,
> > > > > >
> > > > > >- Andy
> > > > > >
> > > > > > ​-
> > > > > >
> > > > > > = Gearpump Proposal =
> > > > > >
> > > > > > === Abstract ===
> > > > > > Gearpump is a flexible, efficient and scalable micro-service
> based
> > > > > > real-time big data streaming engine developed by Intel
> Corporation
> > > > > > which has been licensed by Intel under the Apache License 2.0.
> > > > > >
> > > > > > === Proposal ===
> > > > > > Gearpump is a reactive real-time streaming engine; completely
> > > > > > based on
> > > > > the
> > > > > > micro-service Actor model. Gearpump provides extremely high
> > > > > > performance stream processing while maintaining millisecond
> latency
> > > message delivery.
> > > > > > It enables reusable, composable flows or partial graphs that can
> > > > > > be remotely deployed and executed in a diverse set of
> > > > > > environments,
> > > > > including
> > > > > > IoT edge devices. These flows may be deployed and modified at
> > > > > > runtime --
> > > > > a
> > > > > > capability few real time streaming frameworks provide today.
> > > > > >
> > > > > > The goal of this proposal is to incubate Gearpump as an Apache
> > > > > > project in order to build a diverse, healthy, and self-governed
> > > > > > open source
> > > > > community
> > > > > > around this project.
> > > > > >
> > > > > > === Background ===
> > > > > > In past decade, there have been many advances within real-time
> > > > > > streaming frameworks. Despite many advances, users of streaming
> > > > > > frameworks often complain about flexibility, efficiency, and
> > > > > > scalability. Gearpump
> > > > > endeavors
> > > > > > to solve these challenges by adopting the micro-service Actor
> > > > > > model. The Actor model was proposed by Carl Hewitt in 1973. In
> the
> > > > > > Actor model, each actor is a message driven micro-service; actors
> > > > > > are the basic building blocks of concurrent computation. By
> > > > > > leveraging Actor Model’s location transparency feature,Gearpump
> > > > > > allows a graph to be composed of several partial graphs, where,
> > > > > > for example, some parts may be deployed to remote IoT edge
> > > > > > devices, and other parts to a data center. This division and
> > > > > > deployment model can be changed at runtime to adapt to a changing
> > > > > physical
> > > > > > environment, providing extreme flexibility and elasticity in
> > > > > > solving various ingestion and 

Re: [VOTE] Accept Mnemonic into the Apache Incubator

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Feb 29, 2016, at 12:37 PM, Patrick Hunt  wrote:
> 
> Hi folks,
> 
> OK the discussion is now completed. Please VOTE to accept Mnemonic
> into the Apache Incubator. I’ll leave the VOTE open for at least
> the next 72 hours, with hopes to close it Thursday the 3rd of
> March, 2016 at 10am PT.
> https://wiki.apache.org/incubator/MnemonicProposal
> 
> [ ] +1 Accept Mnemonic as an Apache Incubator podling.
> [ ] +0 Abstain.
> [ ] -1 Don’t accept Mnemonic as an Apache Incubator podling because..
> 
> Of course, I am +1 on this. Please note VOTEs from Incubator PMC
> members are binding but all are welcome to VOTE!
> 
> Regards,
> 
> Patrick
> 
> 
> = Mnemonic Proposal =
> === Abstract ===
> Mnemonic is a Java based non-volatile memory library for in-place
> structured data processing and computing. It is a solution for generic
> object and block persistence on heterogeneous block and
> byte-addressable devices, such as DRAM, persistent memory, NVMe, SSD,
> and cloud network storage.
> 
> === Proposal ===
> Mnemonic is a structured data persistence in-memory in-place library
> for Java-based applications and frameworks. It provides unified
> interfaces for data manipulation on heterogeneous
> block/byte-addressable devices, such as DRAM, persistent memory, NVMe,
> SSD, and cloud network devices.
> 
> The design motivation for this project is to create a non-volatile
> programming paradigm for in-memory data object persistence, in-memory
> data objects caching, and JNI-less IPC.
> Mnemonic simplifies the usage of data object caching, persistence, and
> JNI-less IPC for massive object oriented structural datasets.
> 
> Mnemonic defines Non-Volatile Java objects that store data fields in
> persistent memory and storage. During the program runtime, only
> methods and volatile fields are instantiated in Java heap,
> Non-Volatile data fields are directly accessed via GET/SET operation
> to and from persistent memory and storage. Mnemonic avoids SerDes and
> significantly reduces amount of garbage in Java heap.
> 
> Major features of Mnemonic:
> * Provides an abstract level of viewpoint to utilize heterogeneous
> block/byte-addressable device as a whole (e.g., DRAM, persistent
> memory, NVMe, SSD, HD, cloud network Storage).
> 
> * Provides seamless support object oriented design and programming
> without adding burden to transfer object data to different form.
> 
> * Avoids the object data serialization/de-serialization for data
> retrieval, caching and storage.
> 
> * Reduces the consumption of on-heap memory and in turn to reduce and
> stabilize Java Garbage Collection (GC) pauses for latency sensitive
> applications.
> 
> * Overcomes current limitations of Java GC to manage much larger
> memory resources for massive dataset processing and computing.
> 
> * Supports the migration data usage model from traditional NVMe/SSD/HD
> to non-volatile memory with ease.
> 
> * Uses lazy loading mechanism to avoid unnecessary memory consumption
> if some data does not need to use for computing immediately.
> 
> * Bypasses JNI call for the interaction between Java runtime
> application and its native code.
> 
> * Provides an allocation aware auto-reclaim mechanism to prevent
> external memory resource leaking.
> 
> 
> === Background ===
> Big Data and Cloud applications increasingly require both high
> throughput and low latency processing. Java-based applications
> targeting the Big Data and Cloud space should be tuned for better
> throughput, lower latency, and more predictable response time.
> Typically, there are some issues that impact BigData applications'
> performance and scalability:
> 
> 1) The Complexity of Data Transformation/Organization: In most cases,
> during data processing, applications use their own complicated data
> caching mechanism for SerDes data objects, spilling to different
> storage and eviction large amount of data. Some data objects contains
> complex values and structure that will make it much more difficulty
> for data organization. To load and then parse/decode its datasets from
> storage consumes high system resource and computation power.
> 
> 2) Lack of Caching, Burst Temporary Object Creation/Destruction Causes
> Frequent Long GC Pauses: Big Data computing/syntax generates large
> amount of temporary objects during processing, e.g. lambda, SerDes,
> copying and etc. This will trigger frequent long Java GC pause to scan
> references, to update references lists, and to copy live objects from
> one memory location to another blindly.
> 
> 3) The Unpredictable GC Pause: For latency sensitive applications,
> such as database, search engine, web query, real-time/streaming
> computing, require latency/request-response under control. But current
> Java GC does not provide predictable GC activities with large on-heap
> memory management.
> 
> 4) High JNI Invocation Cost: JNI calls are expensive, but high
> performance applications 

Re: [VOTE] Accept Gearpump into the Apache Incubator

[Hao Chen]

+1 (non-binding)

Regards,
Hao

On Thu, Mar 3, 2016 at 9:18 AM, Felix Cheung  wrote:

> +1 (non-binding)
>
> On Thu, Mar 3, 2016 at 9:03 AM Vasudevan, Ramkrishna S <
> ramkrishna.s.vasude...@intel.com> wrote:
>
> > +1 (non-binding)
> >
> > Regards
> > Ram
> >
> > -Original Message-
> > From: Zheng, Kai [mailto:kai.zh...@intel.com]
> > Sent: Wednesday, March 2, 2016 1:54 PM
> > To: general@incubator.apache.org
> > Subject: RE: [VOTE] Accept Gearpump into the Apache Incubator
> >
> > +1 (non-binding).
> >
> > Regards,
> > Kai
> >
> > -Original Message-
> > From: JiangAlan [mailto:whji...@outlook.com]
> > Sent: Wednesday, March 02, 2016 3:21 PM
> > To: general@incubator.apache.org
> > Subject: RE: [VOTE] Accept Gearpump into the Apache Incubator
> >
> > +1 (non-binding)
> >
> > > From: r...@databricks.com
> > > Date: Tue, 1 Mar 2016 23:14:30 -0800
> > > Subject: Re: [VOTE] Accept Gearpump into the Apache Incubator
> > > To: general@incubator.apache.org
> > >
> > > +1 (binding)
> > >
> > >
> > > On Tue, Mar 1, 2016 at 5:05 PM, James Taylor 
> > wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > On Tue, Mar 1, 2016 at 4:53 PM, Andrew Purtell 
> > > > wrote:
> > > >
> > > > > Greetings,
> > > > >
> > > > > The discussion of the Gearpump proposal has concluded. Please vote
> > > > > to accept Gearpump into the Apache Incubator. I will leave this
> > > > > vote open
> > > > for
> > > > > at least the next 72 hours and will aim to close it Monday the 7th
> > > > > of March, 2016 at midnight PT. Gearpump is a flexible, efficient,
> > > > > and
> > > > scalable
> > > > > micro-service based real-time big data streaming engine. The text
> > > > > of the proposal is included below and is also available at
> > > > > https://wiki.apache.org/incubator/GearpumpProposal
> > > > >
> > > > > [ ] +1 Accept Gearpump as an Apache Incubator podling.
> > > > > [ ] +0 Abstain.
> > > > > [ ] -1 Don’t accept Gearpump as an Apache Incubator podling because
> > ...
> > > > >
> > > > > Note that while votes from Incubator PMC members are binding, all
> > > > > are
> > > > most
> > > > > definitely welcome to vote!
> > > > >
> > > > > I am +1 (binding).
> > > > >
> > > > > Best regards,
> > > > >
> > > > >- Andy
> > > > >
> > > > > ​-
> > > > >
> > > > > = Gearpump Proposal =
> > > > >
> > > > > === Abstract ===
> > > > > Gearpump is a flexible, efficient and scalable micro-service based
> > > > > real-time big data streaming engine developed by Intel Corporation
> > > > > which has been licensed by Intel under the Apache License 2.0.
> > > > >
> > > > > === Proposal ===
> > > > > Gearpump is a reactive real-time streaming engine; completely
> > > > > based on
> > > > the
> > > > > micro-service Actor model. Gearpump provides extremely high
> > > > > performance stream processing while maintaining millisecond latency
> > message delivery.
> > > > > It enables reusable, composable flows or partial graphs that can
> > > > > be remotely deployed and executed in a diverse set of
> > > > > environments,
> > > > including
> > > > > IoT edge devices. These flows may be deployed and modified at
> > > > > runtime --
> > > > a
> > > > > capability few real time streaming frameworks provide today.
> > > > >
> > > > > The goal of this proposal is to incubate Gearpump as an Apache
> > > > > project in order to build a diverse, healthy, and self-governed
> > > > > open source
> > > > community
> > > > > around this project.
> > > > >
> > > > > === Background ===
> > > > > In past decade, there have been many advances within real-time
> > > > > streaming frameworks. Despite many advances, users of streaming
> > > > > frameworks often complain about flexibility, efficiency, and
> > > > > scalability. Gearpump
> > > > endeavors
> > > > > to solve these challenges by adopting the micro-service Actor
> > > > > model. The Actor model was proposed by Carl Hewitt in 1973. In the
> > > > > Actor model, each actor is a message driven micro-service; actors
> > > > > are the basic building blocks of concurrent computation. By
> > > > > leveraging Actor Model’s location transparency feature,Gearpump
> > > > > allows a graph to be composed of several partial graphs, where,
> > > > > for example, some parts may be deployed to remote IoT edge
> > > > > devices, and other parts to a data center. This division and
> > > > > deployment model can be changed at runtime to adapt to a changing
> > > > physical
> > > > > environment, providing extreme flexibility and elasticity in
> > > > > solving various ingestion and analytics problems. We’ve found
> > > > > Actors to be a much smaller computation unit compared with
> > > > > threads, where smaller usually
> > > > means
> > > > > better concurrency, and potentially better CPU utilization.
> > > > >
> > > > > === Rationale ===
> > > > > Gearpump tightly integrates and enhances the big data community of
> > > > > Apache projects. 

Re: [VOTE] Accept Gearpump into the Apache Incubator

[Felix Cheung]

+1 (non-binding)

On Thu, Mar 3, 2016 at 9:03 AM Vasudevan, Ramkrishna S <
ramkrishna.s.vasude...@intel.com> wrote:

> +1 (non-binding)
>
> Regards
> Ram
>
> -Original Message-
> From: Zheng, Kai [mailto:kai.zh...@intel.com]
> Sent: Wednesday, March 2, 2016 1:54 PM
> To: general@incubator.apache.org
> Subject: RE: [VOTE] Accept Gearpump into the Apache Incubator
>
> +1 (non-binding).
>
> Regards,
> Kai
>
> -Original Message-
> From: JiangAlan [mailto:whji...@outlook.com]
> Sent: Wednesday, March 02, 2016 3:21 PM
> To: general@incubator.apache.org
> Subject: RE: [VOTE] Accept Gearpump into the Apache Incubator
>
> +1 (non-binding)
>
> > From: r...@databricks.com
> > Date: Tue, 1 Mar 2016 23:14:30 -0800
> > Subject: Re: [VOTE] Accept Gearpump into the Apache Incubator
> > To: general@incubator.apache.org
> >
> > +1 (binding)
> >
> >
> > On Tue, Mar 1, 2016 at 5:05 PM, James Taylor 
> wrote:
> >
> > > +1 (binding)
> > >
> > > On Tue, Mar 1, 2016 at 4:53 PM, Andrew Purtell 
> > > wrote:
> > >
> > > > Greetings,
> > > >
> > > > The discussion of the Gearpump proposal has concluded. Please vote
> > > > to accept Gearpump into the Apache Incubator. I will leave this
> > > > vote open
> > > for
> > > > at least the next 72 hours and will aim to close it Monday the 7th
> > > > of March, 2016 at midnight PT. Gearpump is a flexible, efficient,
> > > > and
> > > scalable
> > > > micro-service based real-time big data streaming engine. The text
> > > > of the proposal is included below and is also available at
> > > > https://wiki.apache.org/incubator/GearpumpProposal
> > > >
> > > > [ ] +1 Accept Gearpump as an Apache Incubator podling.
> > > > [ ] +0 Abstain.
> > > > [ ] -1 Don’t accept Gearpump as an Apache Incubator podling because
> ...
> > > >
> > > > Note that while votes from Incubator PMC members are binding, all
> > > > are
> > > most
> > > > definitely welcome to vote!
> > > >
> > > > I am +1 (binding).
> > > >
> > > > Best regards,
> > > >
> > > >- Andy
> > > >
> > > > ​-
> > > >
> > > > = Gearpump Proposal =
> > > >
> > > > === Abstract ===
> > > > Gearpump is a flexible, efficient and scalable micro-service based
> > > > real-time big data streaming engine developed by Intel Corporation
> > > > which has been licensed by Intel under the Apache License 2.0.
> > > >
> > > > === Proposal ===
> > > > Gearpump is a reactive real-time streaming engine; completely
> > > > based on
> > > the
> > > > micro-service Actor model. Gearpump provides extremely high
> > > > performance stream processing while maintaining millisecond latency
> message delivery.
> > > > It enables reusable, composable flows or partial graphs that can
> > > > be remotely deployed and executed in a diverse set of
> > > > environments,
> > > including
> > > > IoT edge devices. These flows may be deployed and modified at
> > > > runtime --
> > > a
> > > > capability few real time streaming frameworks provide today.
> > > >
> > > > The goal of this proposal is to incubate Gearpump as an Apache
> > > > project in order to build a diverse, healthy, and self-governed
> > > > open source
> > > community
> > > > around this project.
> > > >
> > > > === Background ===
> > > > In past decade, there have been many advances within real-time
> > > > streaming frameworks. Despite many advances, users of streaming
> > > > frameworks often complain about flexibility, efficiency, and
> > > > scalability. Gearpump
> > > endeavors
> > > > to solve these challenges by adopting the micro-service Actor
> > > > model. The Actor model was proposed by Carl Hewitt in 1973. In the
> > > > Actor model, each actor is a message driven micro-service; actors
> > > > are the basic building blocks of concurrent computation. By
> > > > leveraging Actor Model’s location transparency feature,Gearpump
> > > > allows a graph to be composed of several partial graphs, where,
> > > > for example, some parts may be deployed to remote IoT edge
> > > > devices, and other parts to a data center. This division and
> > > > deployment model can be changed at runtime to adapt to a changing
> > > physical
> > > > environment, providing extreme flexibility and elasticity in
> > > > solving various ingestion and analytics problems. We’ve found
> > > > Actors to be a much smaller computation unit compared with
> > > > threads, where smaller usually
> > > means
> > > > better concurrency, and potentially better CPU utilization.
> > > >
> > > > === Rationale ===
> > > > Gearpump tightly integrates and enhances the big data community of
> > > > Apache projects. Intel believes Gearpump can bring benefits to the
> > > > Apache community in a number of ways:
> > > >
> > > > 1. Gearpump complements many existing Apache projects, in
> > > > particular,
> > > those
> > > > commonly found within the big data space. Users of this project
> > > > are also users of other Apache projects, such as Hadoop ecosystem
> > > > projects. It is 

RE: [VOTE] Accept Gearpump into the Apache Incubator

[Vasudevan, Ramkrishna S]

+1 (non-binding)

Regards
Ram

-Original Message-
From: Zheng, Kai [mailto:kai.zh...@intel.com] 
Sent: Wednesday, March 2, 2016 1:54 PM
To: general@incubator.apache.org
Subject: RE: [VOTE] Accept Gearpump into the Apache Incubator

+1 (non-binding).

Regards,
Kai

-Original Message-
From: JiangAlan [mailto:whji...@outlook.com]
Sent: Wednesday, March 02, 2016 3:21 PM
To: general@incubator.apache.org
Subject: RE: [VOTE] Accept Gearpump into the Apache Incubator

+1 (non-binding)

> From: r...@databricks.com
> Date: Tue, 1 Mar 2016 23:14:30 -0800
> Subject: Re: [VOTE] Accept Gearpump into the Apache Incubator
> To: general@incubator.apache.org
> 
> +1 (binding)
> 
> 
> On Tue, Mar 1, 2016 at 5:05 PM, James Taylor  wrote:
> 
> > +1 (binding)
> >
> > On Tue, Mar 1, 2016 at 4:53 PM, Andrew Purtell 
> > wrote:
> >
> > > Greetings,
> > >
> > > The discussion of the Gearpump proposal has concluded. Please vote 
> > > to accept Gearpump into the Apache Incubator. I will leave this 
> > > vote open
> > for
> > > at least the next 72 hours and will aim to close it Monday the 7th 
> > > of March, 2016 at midnight PT. Gearpump is a flexible, efficient, 
> > > and
> > scalable
> > > micro-service based real-time big data streaming engine. The text 
> > > of the proposal is included below and is also available at 
> > > https://wiki.apache.org/incubator/GearpumpProposal
> > >
> > > [ ] +1 Accept Gearpump as an Apache Incubator podling.
> > > [ ] +0 Abstain.
> > > [ ] -1 Don’t accept Gearpump as an Apache Incubator podling because ...
> > >
> > > Note that while votes from Incubator PMC members are binding, all 
> > > are
> > most
> > > definitely welcome to vote!
> > >
> > > I am +1 (binding).
> > >
> > > Best regards,
> > >
> > >- Andy
> > >
> > > ​-
> > >
> > > = Gearpump Proposal =
> > >
> > > === Abstract ===
> > > Gearpump is a flexible, efficient and scalable micro-service based 
> > > real-time big data streaming engine developed by Intel Corporation 
> > > which has been licensed by Intel under the Apache License 2.0.
> > >
> > > === Proposal ===
> > > Gearpump is a reactive real-time streaming engine; completely 
> > > based on
> > the
> > > micro-service Actor model. Gearpump provides extremely high 
> > > performance stream processing while maintaining millisecond latency 
> > > message delivery.
> > > It enables reusable, composable flows or partial graphs that can 
> > > be remotely deployed and executed in a diverse set of 
> > > environments,
> > including
> > > IoT edge devices. These flows may be deployed and modified at 
> > > runtime --
> > a
> > > capability few real time streaming frameworks provide today.
> > >
> > > The goal of this proposal is to incubate Gearpump as an Apache 
> > > project in order to build a diverse, healthy, and self-governed 
> > > open source
> > community
> > > around this project.
> > >
> > > === Background ===
> > > In past decade, there have been many advances within real-time 
> > > streaming frameworks. Despite many advances, users of streaming 
> > > frameworks often complain about flexibility, efficiency, and 
> > > scalability. Gearpump
> > endeavors
> > > to solve these challenges by adopting the micro-service Actor 
> > > model. The Actor model was proposed by Carl Hewitt in 1973. In the 
> > > Actor model, each actor is a message driven micro-service; actors 
> > > are the basic building blocks of concurrent computation. By 
> > > leveraging Actor Model’s location transparency feature,Gearpump 
> > > allows a graph to be composed of several partial graphs, where, 
> > > for example, some parts may be deployed to remote IoT edge 
> > > devices, and other parts to a data center. This division and 
> > > deployment model can be changed at runtime to adapt to a changing
> > physical
> > > environment, providing extreme flexibility and elasticity in 
> > > solving various ingestion and analytics problems. We’ve found 
> > > Actors to be a much smaller computation unit compared with 
> > > threads, where smaller usually
> > means
> > > better concurrency, and potentially better CPU utilization.
> > >
> > > === Rationale ===
> > > Gearpump tightly integrates and enhances the big data community of 
> > > Apache projects. Intel believes Gearpump can bring benefits to the 
> > > Apache community in a number of ways:
> > >
> > > 1. Gearpump complements many existing Apache projects, in 
> > > particular,
> > those
> > > commonly found within the big data space. Users of this project 
> > > are also users of other Apache projects, such as Hadoop ecosystem 
> > > projects. It is beneficial to align these projects under the ASF 
> > > umbrella. In real-time streaming, Gearpump offers some special 
> > > features that are useful for
> > Apache
> > > users, such as exactly-once processing with millisecond message 
> > > level latency and dynamic DAGs that allow online topology modifications.
> > >
> > > 2. 

Re: [VOTE] Release taverna-language-0.15.1-incubating-RC5 and taverna-osgi-0.2.1-incubating-RC5

[Pierce, Marlon]

Hello Incubator,

Apache Taverna is looking for new active mentors [1] and in the meantime will 
need your help with this vote. 

Thanks,

Marlon

[1] 
https://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3CCAMBJEmW6ezFS7Dtsxo2FwSV7dXj1MPQ_=efuiqmkcvsqcj7...@mail.gmail.com%3E



On 3/2/16, 12:07 PM, "Stian Soiland-Reyes"  wrote:

>I am pleased to be calling this vote for the source release of
>
>  Apache Taverna Maven Parent 2-incubating
>  Apache Taverna Language 0.15.1-incubating
>  Apache Taverna OSGi plugin system 0.2.1-incubating
>
>The Apache Taverna IPMC has voted in favour of this release with 5 IPMC votes:
>
>http://markmail.org/message/346xxkywuexw6z52
>http://mail-archives.apache.org/mod_mbox/taverna-dev/201603.mbox/
>
>We now ask for the Incubator PMC to vote on this release candidate.
>
>
>Apache Taverna Language is a set of APIs for workflow definitions
>(SCUFL2) and workflow inputs/outputs/run (DataBundle), as consumed and
>produced by the Apache Taverna workflow system. The API includes
>support for working with Research Object Bundles, and loading/saving
>Taverna workflows in different formats.
>
>Apache Taverna OSGi is a plugin system for OSGi with support for
>online updates, which can be used by Java desktop and command line
>applications.
>
>
>The release candidates to be voted over are available at:
>
>  
> https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-parent-2-incubating-RC5/
>  
> https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-language-0.15.1-incubating-RC5/
>  
> https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-osgi-0.2.1-incubating-RC5/
>
>
>Checksums:
>
>md5sum:
>8e7ee332896d314877af481b348dbf51
>apache-taverna-parent-2-incubating-source-release.zip
>
>6bd8ae9e2b1bc2e675e5573b87feaa2a
>apache-taverna-language-0.15.1-incubating-source-release.zip
>
>4d595212a813f62a0c16a31d3a872af4
>apache-taverna-osgi-0.2.1-incubating-source-release.zip
>
>
>sha1sum:
>d4b675763eb03bc5a9863db27779d725e1209af6
>apache-taverna-parent-2-incubating-source-release.zip
>
>af3a14ec6d9386e9aa97309275f7b147be6f0a38
>apache-taverna-language-0.15.1-incubating-source-release.zip
>
>2e91b5176322c0e029e1a856f0752159b1564158
>apache-taverna-osgi-0.2.1-incubating-source-release.zip
>
>
>sha512sum:
>d5787ba7066d0d3b7c3b292434eb3de909c8ebaf43f0a3ea5e9dd25f0f19b5c1b7d508ffde97c0e6afd53265835d1aa4f22bb3187011b50b7f5aac99892bd0aa
>apache-taverna-parent-2-incubating-source-release.zip
>
>7cb4860abb4c57b91e81703a0d362d2824f10f1d2abe62c3df028fdca4f3ce33c4fe572c3349e629c8d409a7b25f3c86b79487d840c642a4b39e84432aa86c04
>apache-taverna-language-0.15.1-incubating-source-release.zip
>
>31b50a87243a01f3a5a657643d0f3b7f56d86fcc309df74392df3915ef8a787948ff8c74bc6a7684e6f9049b6430324373c50959ff658803dbc2d67d8a3dc45c
>apache-taverna-osgi-0.2.1-incubating-source-release.zip
>
>
>
>To build the release candidates you need Apache Maven 3 and Java 8.
>
>
>Build the release candidate, in the above order, using:
>
>mvn clean install
>
>
>The release candidates correspond to the following git commits:
>
>  
> https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-maven-parent.git;a=commit;h=d34dd67fcfa11caead08008d37279b1ea546e3ec
>
>  
> https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-language.git;a=commit;h=66866a5454ed23262c055f65155d7a195c68a17d
>
>  
> https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-osgi.git;a=commit;h=0b7da331e81febade5ce2f4cf1f068013002b7aa
>
>
>Release candidates are signed with a GPG key available at:
>
>  https://dist.apache.org/repos/dist/release/incubator/taverna/KEYS
>
>A staged Maven repository is available for review at:
>
>  https://repository.apache.org/content/repositories/orgapachetaverna-1011/
>
>The changelog for this release is available from JIRA:
>
>  
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333249=12318322
>  
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333250=12318322
>  
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12332248=12318322
>
>
>Please vote on releasing these packages as:
>
>  Apache Taverna Maven Parent 2-incubating
>  Apache Taverna Language 0.15.1-incubating
>  Apache Taverna OSGi plugin system 0.2.1-incubating
>
>
>The vote is open for at least 72 hours
>(let's say Monday 2016-03-07 17:00 GMT)
>and passes if a majority of at least
>three +1 Incubator PMC votes are cast.
>
>[ ] +1 Release this package
>[ ]  0 I don't feel strongly about it, but don't object
>[ ] -1 Do not release this package because...
>
>Anyone can participate in testing and voting, not just Incubator PMC
>members, please feel free to try out the release candidate and provide
>your votes.
>
>
>--
>Stian Soiland-Reyes
>Apache Taverna (incubating), Apache Commons RDF (incubating)
>http://orcid.org/-0001-9842-9718
>

Re: Need access to Incubator Wiki

[Nick Burch]

On Thu, 3 Mar 2016, Gino Bustelo wrote:

lbustelo


Karma granted, enjoy editing!

Nick

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Need access to Incubator Wiki

[Gino Bustelo]

lbustelo

On Thu, Mar 3, 2016 at 9:07 AM, Nick Burch  wrote:

> On Thu, 3 Mar 2016, Gino Bustelo wrote:
>
>> I need access to be able to push Apache Toree updates.
>>
>
> You'll need to tell us your Incubator wiki username if we're to be able to
> help!
>
> Nick
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Need access to Incubator Wiki

[Nick Burch]

On Thu, 3 Mar 2016, Gino Bustelo wrote:

I need access to be able to push Apache Toree updates.


You'll need to tell us your Incubator wiki username if we're to be able to 
help!


Nick


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Update on Apache Toree and LGPL dependency

[Gino Bustelo]

Wanted to give folks an update on our progress with dealing with JeroMQ, an
LGPL package that enables us to communicate via 0MQ. The 0MQ community is
very aware of the issues with LGPL (LGPLv3 + static link exception) and it
is their intention to try to move projects to MPL v2. This is not an easy
task depending on the age and size of the projects.

Apache Toree's API access point is through the 0MQ transport layer (using
JeroMQ) and that is how Apache Toree connects out-of-the-box with Jupyter,
a very common way of consuming Apache Toree that is already in production.

At this point, the JeroMQ project is still released under LGPL, but our
team initiated communications in mid-February with members of the JeroMQ
community to begin their transition to MPL v2 (
https://github.com/zeromq/jeromq/issues/326). The JeroMQ community reacted
very positively and quickly began the process of collecting votes from
their committers (https://github.com/zeromq/jeromq/issues/327). After 15
days, the current tally stands at 26 out of 32 committers have agreed to
switch license.

Apache Toree has a JIRA (https://issues.apache.org/jira/browse/TOREE-262)
where we keep all the relevant links and update with the latest
information. As that process is underway, we will move forward with plans
to release a 0.1.0 version of Apache Toree based on the precedence set by
Apache Mynewt (
http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3C5F118AA0-4ADA-403B-A6EB-4A85F0B30651%40me.com%3E
).

Thanks,
Gino

Need access to Incubator Wiki

[Gino Bustelo]

I need access to be able to push Apache Toree updates.