Re: [DISCUSS] PredictionIO incubation proposal

[Nick Pentreath]

Hi everyone

I just want to make it clear that my suggestion was in no way some sort of
attempt to hijack the project or push a corporate agenda.

For me personally, I have not been directly involved in PredictionIO, that
is true. I have however spent the past 3 years prior to joining IBM
building from scratch, single-handedly, a commercial SaaS product that is
at its core fundamentally very similar in terms of architecture and design
(though admittedly less general as it was focused on the recommendation
space). Also, I've had some chats with Simon over the past couple of years
and also recently specifically about this proposal, hence my interest.

I can't speak for Mike directly, but certainly I see a potential SystemML
integration in the future as something interesting for both projects (I'm
not suggesting it should be worked on immediately as a primary focus).

In any case, I see the proposal is in voting stage and it appears the vote
will easily pass, so all the best with Apache PredictionIO (incubating)!
We'll look at getting involved where it makes sense and we could add value.

Nick

On Fri, 20 May 2016 at 18:14 Pat Ferrel  wrote:

> +1 for the current committer list, but please, anyone interested get
> familiar, we will need more help soon!
>
> Also I’d like to bring up the template gallery again. Plugins may be
> problematic in other projects but pio does nothing of interest *without* a
> template. There are some examples in the core repo but...
>
> Questions:
> 1) can the gallery be transferred? This is just a listing of templates
> that may be maintained by external people and is the source from which they
> are downloaded by default.
> 2) which templates are proposed for the transfer? Didn’t see that spelled
> out beyond the included examples.
>
> On May 20, 2016, at 8:53 AM, Suneel Marthi  wrote:
>
> The current list is good to go and includes all (both present and former)
> PIO folks.
> I am fine with going for Voting with the present list.
>
> +1
>
> On Fri, May 20, 2016 at 11:47 AM, Andrew Purtell 
> wrote:
>
> > The current list of initial committers was that provided me by the
> > PredictionIO folks so I have every reason to believe they all have a
> stake
> > at entering incubation.
> >
> > It's totally fine with me if we stick to that list. I am just trying to
> > facilitate the fairest process possible.
> >
> >
> > On Friday, May 20, 2016, Roman Shaposhnik  wrote:
> >
> >> On Thu, May 19, 2016 at 9:16 PM, Suneel Marthi  >> > wrote:
> >>> I definitely have concerns about too many folks becoming initial
> >> committers
> >>> and bringing their own corporate agendas to this project.
> >>>
> >>> I suggest that first we vote PIO into incubator then bring in those
> > less
> >>> experienced with the project. We have a good start with people who have
> >>> worked on the project from several orgs. Let us get organized first and
> >>> then bring in new people.
> >>
> >> I think this is a reasonable concern. Andrew, any chance you can look
> > over
> >> the names of initial committers and let us know who has had a stake in
> > the
> >> project before entering the incubation vs. those who are trying to join
> > in
> >> as
> >> part of the ASF Incubation.
> >>
> >> I'm not saying we need to pass judgement one way or the other yet, but
> it
> >> will be a very useful data point to know before voting.
> >>
> >> Thanks,
> >> Roman.
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> 
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >> 
> >>
> >>
> >
> > --
> > Best regards,
> >
> >   - Andy
> >
> > Problems worthy of attack prove their worth by hitting back. - Piet Hein
> > (via Tom White)
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Myrle Krantz]

+1 (non-binding)

(Thank you guys for doing this.)


*Myrle Krantz*
Solutions Architect
RɅĐɅЯ, The Mifos Initiative
mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org
  


On Tue, May 24, 2016 at 8:36 AM, Sergio Fernández  wrote:

> +++1 (binding)
>
> On Tue, May 24, 2016 at 7:56 AM, Daniel Gruno 
> wrote:
>
> > Since it seems the discussion has died down, I am now calling a vote on
> > accepting Pony Mail into the Incubator. Sorry in advance for potato.
> >
> > This vote will run for the usual 72 hours.
> >
> > ### PROPOSAL BELOW ###
> >
> > Abstract
> >
> > Pony Mail is a mail-archiving, archive viewing, and interaction service,
> > that can be integrated with many email platforms.
> >
> > Proposal
> >
> > Background
> >
> > Pony Mail began as a response to two things; the lack of diversity in
> > mailing list archives that are less bureaucratic all-or-nothing and more
> > fluid way to interact with mailing lists than what is typically offered,
> > and the lack of a performant system that solves this issue. Modern users
> > of software want to jump right into a discussion they see, but cannot
> > normally do so in a mailing list driven environment because of the rules
> > generally surrounding said environment. Pony Mail, along with a select
> > handful of newer archive systems, provides an interface that allows
> > people to just hop into a thread, and take part. Without the need to
> > subscribe, download the mbox archive, load it into your MTA, and respond.
> >
> > As Rich writes in a very short essay:
> >
> > You see a thread in which someone is WRONG ON THE INTERNET! You need to
> > correct them. How do you do this today? You kinda don't. If you really
> > wanted, you could download mbox files (and who the hell knows where they
> > are?) and then try to get them into your mail client (which never works)
> > and then reply to it. Which will break threading, because you did
> > something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> > (sound of hoof beats)
> >
> > Rationale
> >
> > One of the oft-heard complaints about Apache's development model is that
> > mailing lists are an old person's tool, and web-based communication -
> > forums - are the way to go in the 21st Century. Providing a
> > full-featured forum-like interface to mailing lists is one goal,while
> > keeping all of the enormous benefits that mailing lists already provide.
> > Asecond goal is to provide the ability to "jump in" to a mailing list
> > conversation - even one that was a while back, without the convolutions
> > that a mailing list requires. That is, to join this conversation the old
> > way, one would have had to subscribe to the mailing list, download an
> > mbox, and import it into ones mail client, in order that I be able to
> > reply to this message with correct threading. With Pony Mail, one has to
> > do none of those things, but can simply reply using the Web UI. To us,
> > this is a HUGE benefit for building community. The requirement to jump
> > through hoops to join a mailing list conversation drives away a lot of
> > people (at least, anecdotally, it does) and if we can remove that
> > barrier I think we'll have an easier time of drawing a new generation
> > into our projects.
> >
> > Initial Goals
> >
> > The initial goals of transitioning to the ASF is to expand and grow both
> > the Pony codebase and community, and ensure the project's continued
> > growth and stability through forming a diverse and reliable community,
> > in which the various facets of developers and contributors help keep the
> > project up to date with latest developments and technical as well as
> > social needs.
> >
> > Current Status
> >
> > Meritocracy:
> >
> > The bulk of the code has been written by Daniel Gruno to date, but has
> > had oversight from other committers, and mentors.
> >
> > All members of the Pony project and wider community have a deep
> > understanding and appreciation for the ASF meritocracy ideals, and are
> > almost solely current ASF Members.
> >
> > Community:
> > The community is currently heavily focused within the ASF, and
> > more specifically the Infrastructure group. This is to be expected given
> > the nature of how the code came into existence in the first place. It
> > should be noted that we have started reaching out to other groups who we
> > know are using mailing list systems and therefore also rely on mailing
> > list archive interfaces.
> >
> > Core Developers:
> >
> > Almost all core developers are ASF members, and are already intimately
> > familiar with the Apache Way.
> >
> > Alignment:
> >
> > Pony will be very in line with ASF practices and processes as many of
> > the founding members are long term ASF members and committers.
> >
> > Known Risks
> >
> > Orphaned products:
> >
> > We are not aware of any issues with orphaned products related 

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Jacques Le Roux]

+1 (not binding)

Jacques


Le 24/05/2016 à 07:56, Daniel Gruno a écrit :

Since it seems the discussion has died down, I am now calling a vote on
accepting Pony Mail into the Incubator. Sorry in advance for potato.

This vote will run for the usual 72 hours.

### PROPOSAL BELOW ###

Abstract

Pony Mail is a mail-archiving, archive viewing, and interaction service,
that can be integrated with many email platforms.

Proposal

Background

Pony Mail began as a response to two things; the lack of diversity in
mailing list archives that are less bureaucratic all-or-nothing and more
fluid way to interact with mailing lists than what is typically offered,
and the lack of a performant system that solves this issue. Modern users
of software want to jump right into a discussion they see, but cannot
normally do so in a mailing list driven environment because of the rules
generally surrounding said environment. Pony Mail, along with a select
handful of newer archive systems, provides an interface that allows
people to just hop into a thread, and take part. Without the need to
subscribe, download the mbox archive, load it into your MTA, and respond.

As Rich writes in a very short essay:

You see a thread in which someone is WRONG ON THE INTERNET! You need to
correct them. How do you do this today? You kinda don't. If you really
wanted, you could download mbox files (and who the hell knows where they
are?) and then try to get them into your mail client (which never works)
and then reply to it. Which will break threading, because you did
something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
(sound of hoof beats)

Rationale

One of the oft-heard complaints about Apache's development model is that
mailing lists are an old person's tool, and web-based communication -
forums - are the way to go in the 21st Century. Providing a
full-featured forum-like interface to mailing lists is one goal,while
keeping all of the enormous benefits that mailing lists already provide.
Asecond goal is to provide the ability to "jump in" to a mailing list
conversation - even one that was a while back, without the convolutions
that a mailing list requires. That is, to join this conversation the old
way, one would have had to subscribe to the mailing list, download an
mbox, and import it into ones mail client, in order that I be able to
reply to this message with correct threading. With Pony Mail, one has to
do none of those things, but can simply reply using the Web UI. To us,
this is a HUGE benefit for building community. The requirement to jump
through hoops to join a mailing list conversation drives away a lot of
people (at least, anecdotally, it does) and if we can remove that
barrier I think we'll have an easier time of drawing a new generation
into our projects.

Initial Goals

The initial goals of transitioning to the ASF is to expand and grow both
the Pony codebase and community, and ensure the project's continued
growth and stability through forming a diverse and reliable community,
in which the various facets of developers and contributors help keep the
project up to date with latest developments and technical as well as
social needs.

Current Status

 Meritocracy:

The bulk of the code has been written by Daniel Gruno to date, but has
had oversight from other committers, and mentors.

 All members of the Pony project and wider community have a deep
understanding and appreciation for the ASF meritocracy ideals, and are
almost solely current ASF Members.

 Community:
 The community is currently heavily focused within the ASF, and
more specifically the Infrastructure group. This is to be expected given
the nature of how the code came into existence in the first place. It
should be noted that we have started reaching out to other groups who we
know are using mailing list systems and therefore also rely on mailing
list archive interfaces.

 Core Developers:

Almost all core developers are ASF members, and are already intimately
familiar with the Apache Way.

 Alignment:

Pony will be very in line with ASF practices and processes as many of
the founding members are long term ASF members and committers.

Known Risks

 Orphaned products:

We are not aware of any issues with orphaned products related to this
project.

 Pony Mail relies on a set of CSS3 templates as well as some very stable
 programming languages. We have no reason to believe these would
be orphaned or, should they become orphaned, that it would impact the
development of the project.

 Inexperience with Open Source:
 Most of the current committers are already ASF members and
committers, we do not believe there to be any concerns around OSS
inexperience.

 Homogenous Developers:
 While the current mix of people involved in the project spans
several continents with a wide variety of skills and experience, a long
standing relation with the ASF applies to all com

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Justin Mclean]

+1 (binding)

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

Re: [VOTE] Accept PredictionIO into the Apache Incubator

[Sergio Fernández]

+1 (binding)

On Tue, May 24, 2016 at 12:22 AM, Andrew Purtell 
wrote:

> Since discussion on the matter of PredictionIO has died down, I would like
> to call a VOTE
> on accepting PredictionIO into the Apache Incubator.
>
> Proposal: https://wiki.apache.org/incubator/PredictionIO
>
> ​[ ] +1 Accept PredictionIO into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept PredictionIO into the Apache Incubator, because ...
>
> This vote will be open for at least 72 hours.
>
> My vote is +1 (binding)
>
> --
>
> PredictionIO Proposal
>
> Abstract
>
> PredictionIO is an open source Machine Learning Server built on top of
> state-of-the-art open source stack, that enables developers to manage and
> deploy production-ready predictive services for various kinds of machine
> learning tasks.
>
> Proposal
>
> The PredictionIO platform consists of the following components:
>
>* PredictionIO framework - provides the machine learning stack for
>  building, evaluating and deploying engines with machine learning
>  algorithms. It uses Apache Spark for processing.
>
>* Event Server - the machine learning analytics layer for unifying
> events
>  from multiple platforms. It can use Apache HBase or any JDBC backends
>  as its data store.
>
> The PredictionIO community also maintains a Template Gallery, a place to
> publish and download (free or proprietary) engine templates for different
> types of machine learning applications, and is a complemental part of the
> project. At this point we exclude the Template Gallery from the proposal,
> as it has a separate set of contributors and we’re not familiar with an
> Apache approved mechanism to maintain such a gallery.
>
> Background
>
> PredictionIO was started with a mission to democratize and bring machine
> learning to the masses.
>
> Machine learning has traditionally been a luxury for big companies like
> Google, Facebook, and Netflix. There are ML libraries and tools lying
> around the internet but the effort of putting them all together as a
> production-ready infrastructure is a very resource-intensive task that is
> remotely reachable by individuals or small businesses.
>
> PredictionIO is a production-ready, full stack machine learning system that
> allows organizations of any scale to quickly deploy machine learning
> capabilities. It comes with official and community-contributed machine
> learning engine templates that are easy to customize.
>
> Rationale
>
> As usage and number of contributors to PredictionIO has grown bigger and
> more diverse, we have sought for an independent framework for the project
> to keep thriving. We believe the Apache foundation is a great fit. Joining
> Apache would ensure that tried and true processes and procedures are in
> place for the growing number of organizations interested in contributing
> to PredictionIO. PredictionIO is also a good fit for the Apache foundation.
> PredictionIO was built on top of several Apache projects (HBase, Spark,
> Hadoop). We are familiar with the Apache process and believe that the
> democratic and meritocratic nature of the foundation aligns with the
> project goals.
>
> Initial Goals
>
> The initial milestones will be to move the existing codebase to Apache and
> integrate with the Apache development process. Once this is accomplished,
> we plan for incremental development and releases that follow the Apache
> guidelines, as well as growing our developer and user communities.
>
> Current Status
>
> PredictionIO has undergone nine minor releases and many patches.
> PredictionIO is being used in production by Salesforce.com as well as many
> other organizations and apps. The PredictionIO codebase is currently
> hosted at GitHub, which will form the basis of the Apache git repository.
>
> Meritocracy
>
> We plan to invest in supporting a meritocracy. We will discuss the
> requirements in an open forum. We intend to invite additional developers
> to participate. We will encourage and monitor community participation so
> that privileges can be extended to those that contribute.
>
> Community
>
> Acceptance into the Apache foundation would bolster the already strong
> user and developer community around PredictionIO. That community includes
> many contributors from various other companies, and an active mailing list
> composed of hundreds of users.
>
> Core Developers
>
> The core developers of our project are listed in our contributors and
> initial PPMC below. Though many are employed at Salesforce.com, there are
> also engineers from ActionML, and independent developers.
>
> Alignment
>
> The ASF is the natural choice to host the PredictionIO project as its goal
> is democratizing Machine Learning by making it more easily accessible to
> every user/developer. PredictionIO is built on top of several top level
> Apache projects as outlined above.
>
> Known Risks
>
> Orphaned Products
>
> PredictionIO has a solid and growing community. It is deployed on
> production environmen

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Pierre Smits]

+1 (non-binding)

This is a good approach. In the past we have seen a few TopLevel projects
spawned on the basis of its core product being in use as an ASF internal
solution without having gone through the incubation proces. Some of these
projects lead a marginal existence, don't do releases and don't work on
community building and expansion.

Best regards,


Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Tue, May 24, 2016 at 9:26 AM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> +1 (not binding)
>
> Jacques
>
>
>
> Le 24/05/2016 à 07:56, Daniel Gruno a écrit :
>
>> Since it seems the discussion has died down, I am now calling a vote on
>> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>>
>> This vote will run for the usual 72 hours.
>>
>> ### PROPOSAL BELOW ###
>>
>> Abstract
>>
>> Pony Mail is a mail-archiving, archive viewing, and interaction service,
>> that can be integrated with many email platforms.
>>
>> Proposal
>>
>> Background
>>
>> Pony Mail began as a response to two things; the lack of diversity in
>> mailing list archives that are less bureaucratic all-or-nothing and more
>> fluid way to interact with mailing lists than what is typically offered,
>> and the lack of a performant system that solves this issue. Modern users
>> of software want to jump right into a discussion they see, but cannot
>> normally do so in a mailing list driven environment because of the rules
>> generally surrounding said environment. Pony Mail, along with a select
>> handful of newer archive systems, provides an interface that allows
>> people to just hop into a thread, and take part. Without the need to
>> subscribe, download the mbox archive, load it into your MTA, and respond.
>>
>> As Rich writes in a very short essay:
>>
>> You see a thread in which someone is WRONG ON THE INTERNET! You need to
>> correct them. How do you do this today? You kinda don't. If you really
>> wanted, you could download mbox files (and who the hell knows where they
>> are?) and then try to get them into your mail client (which never works)
>> and then reply to it. Which will break threading, because you did
>> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
>> (sound of hoof beats)
>>
>> Rationale
>>
>> One of the oft-heard complaints about Apache's development model is that
>> mailing lists are an old person's tool, and web-based communication -
>> forums - are the way to go in the 21st Century. Providing a
>> full-featured forum-like interface to mailing lists is one goal,while
>> keeping all of the enormous benefits that mailing lists already provide.
>> Asecond goal is to provide the ability to "jump in" to a mailing list
>> conversation - even one that was a while back, without the convolutions
>> that a mailing list requires. That is, to join this conversation the old
>> way, one would have had to subscribe to the mailing list, download an
>> mbox, and import it into ones mail client, in order that I be able to
>> reply to this message with correct threading. With Pony Mail, one has to
>> do none of those things, but can simply reply using the Web UI. To us,
>> this is a HUGE benefit for building community. The requirement to jump
>> through hoops to join a mailing list conversation drives away a lot of
>> people (at least, anecdotally, it does) and if we can remove that
>> barrier I think we'll have an easier time of drawing a new generation
>> into our projects.
>>
>> Initial Goals
>>
>> The initial goals of transitioning to the ASF is to expand and grow both
>> the Pony codebase and community, and ensure the project's continued
>> growth and stability through forming a diverse and reliable community,
>> in which the various facets of developers and contributors help keep the
>> project up to date with latest developments and technical as well as
>> social needs.
>>
>> Current Status
>>
>>  Meritocracy:
>>
>> The bulk of the code has been written by Daniel Gruno to date, but has
>> had oversight from other committers, and mentors.
>>
>>  All members of the Pony project and wider community have a deep
>> understanding and appreciation for the ASF meritocracy ideals, and are
>> almost solely current ASF Members.
>>
>>  Community:
>>  The community is currently heavily focused within the ASF, and
>> more specifically the Infrastructure group. This is to be expected given
>> the nature of how the code came into existence in the first place. It
>> should be noted that we have started reaching out to other groups who we
>> know are using mailing list systems and therefore also rely on mailing
>> list archive interfaces.
>>
>>  Core Developers:
>>
>> Almost all core developers are ASF members, and are already intimately
>> familiar with the Apache Way.
>>
>>  Alignment:
>>
>> Pony will be very in line with ASF practices

Re: [DISCUSS] CarbonData incubation proposal

[JihongMa]

Thank you Julian!!

we are going to prepare a BD scan result to ensure source code clearance is
done properly, and as an ongoing effort to do a diligent job as we move
forward on this regards. 

Regards.

Jihong



--
View this message in context: 
http://apache-incubator-general.996316.n3.nabble.com/DISCUSS-CarbonData-incubation-proposal-tp49643p49756.html
Sent from the Apache Incubator - General mailing list archive at Nabble.com.

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

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Sam Ruby]

On Tue, May 24, 2016 at 1:56 AM, Daniel Gruno  wrote:
> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>
> This vote will run for the usual 72 hours.

+1 (binding)

- Sam Ruby

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

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[John D. Ament]

+1

On Tue, May 24, 2016 at 1:56 AM Daniel Gruno  wrote:

> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>
> This vote will run for the usual 72 hours.
>
> ### PROPOSAL BELOW ###
>
> Abstract
>
> Pony Mail is a mail-archiving, archive viewing, and interaction service,
> that can be integrated with many email platforms.
>
> Proposal
>
> Background
>
> Pony Mail began as a response to two things; the lack of diversity in
> mailing list archives that are less bureaucratic all-or-nothing and more
> fluid way to interact with mailing lists than what is typically offered,
> and the lack of a performant system that solves this issue. Modern users
> of software want to jump right into a discussion they see, but cannot
> normally do so in a mailing list driven environment because of the rules
> generally surrounding said environment. Pony Mail, along with a select
> handful of newer archive systems, provides an interface that allows
> people to just hop into a thread, and take part. Without the need to
> subscribe, download the mbox archive, load it into your MTA, and respond.
>
> As Rich writes in a very short essay:
>
> You see a thread in which someone is WRONG ON THE INTERNET! You need to
> correct them. How do you do this today? You kinda don't. If you really
> wanted, you could download mbox files (and who the hell knows where they
> are?) and then try to get them into your mail client (which never works)
> and then reply to it. Which will break threading, because you did
> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> (sound of hoof beats)
>
> Rationale
>
> One of the oft-heard complaints about Apache's development model is that
> mailing lists are an old person's tool, and web-based communication -
> forums - are the way to go in the 21st Century. Providing a
> full-featured forum-like interface to mailing lists is one goal,while
> keeping all of the enormous benefits that mailing lists already provide.
> Asecond goal is to provide the ability to "jump in" to a mailing list
> conversation - even one that was a while back, without the convolutions
> that a mailing list requires. That is, to join this conversation the old
> way, one would have had to subscribe to the mailing list, download an
> mbox, and import it into ones mail client, in order that I be able to
> reply to this message with correct threading. With Pony Mail, one has to
> do none of those things, but can simply reply using the Web UI. To us,
> this is a HUGE benefit for building community. The requirement to jump
> through hoops to join a mailing list conversation drives away a lot of
> people (at least, anecdotally, it does) and if we can remove that
> barrier I think we'll have an easier time of drawing a new generation
> into our projects.
>
> Initial Goals
>
> The initial goals of transitioning to the ASF is to expand and grow both
> the Pony codebase and community, and ensure the project's continued
> growth and stability through forming a diverse and reliable community,
> in which the various facets of developers and contributors help keep the
> project up to date with latest developments and technical as well as
> social needs.
>
> Current Status
>
> Meritocracy:
>
> The bulk of the code has been written by Daniel Gruno to date, but has
> had oversight from other committers, and mentors.
>
> All members of the Pony project and wider community have a deep
> understanding and appreciation for the ASF meritocracy ideals, and are
> almost solely current ASF Members.
>
> Community:
> The community is currently heavily focused within the ASF, and
> more specifically the Infrastructure group. This is to be expected given
> the nature of how the code came into existence in the first place. It
> should be noted that we have started reaching out to other groups who we
> know are using mailing list systems and therefore also rely on mailing
> list archive interfaces.
>
> Core Developers:
>
> Almost all core developers are ASF members, and are already intimately
> familiar with the Apache Way.
>
> Alignment:
>
> Pony will be very in line with ASF practices and processes as many of
> the founding members are long term ASF members and committers.
>
> Known Risks
>
> Orphaned products:
>
> We are not aware of any issues with orphaned products related to this
> project.
>
> Pony Mail relies on a set of CSS3 templates as well as some very stable
> programming languages. We have no reason to believe these would
> be orphaned or, should they become orphaned, that it would impact the
> development of the project.
>
> Inexperience with Open Source:
> Most of the current committers are already ASF members and
> committers, we do not believe there to be any concerns around OSS
> inexperience.
>
> Homogenous Developers:
> While the curr

Re: [VOTE] Accept PredictionIO into the Apache Incubator

[John D. Ament]

+1

On Mon, May 23, 2016 at 6:23 PM Andrew Purtell  wrote:

> Since discussion on the matter of PredictionIO has died down, I would like
> to call a VOTE
> on accepting PredictionIO into the Apache Incubator.
>
> Proposal: https://wiki.apache.org/incubator/PredictionIO
>
> ​[ ] +1 Accept PredictionIO into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept PredictionIO into the Apache Incubator, because ...
>
> This vote will be open for at least 72 hours.
>
> My vote is +1 (binding)
>
> --
>
> PredictionIO Proposal
>
> Abstract
>
> PredictionIO is an open source Machine Learning Server built on top of
> state-of-the-art open source stack, that enables developers to manage and
> deploy production-ready predictive services for various kinds of machine
> learning tasks.
>
> Proposal
>
> The PredictionIO platform consists of the following components:
>
>* PredictionIO framework - provides the machine learning stack for
>  building, evaluating and deploying engines with machine learning
>  algorithms. It uses Apache Spark for processing.
>
>* Event Server - the machine learning analytics layer for unifying
> events
>  from multiple platforms. It can use Apache HBase or any JDBC backends
>  as its data store.
>
> The PredictionIO community also maintains a Template Gallery, a place to
> publish and download (free or proprietary) engine templates for different
> types of machine learning applications, and is a complemental part of the
> project. At this point we exclude the Template Gallery from the proposal,
> as it has a separate set of contributors and we’re not familiar with an
> Apache approved mechanism to maintain such a gallery.
>
> Background
>
> PredictionIO was started with a mission to democratize and bring machine
> learning to the masses.
>
> Machine learning has traditionally been a luxury for big companies like
> Google, Facebook, and Netflix. There are ML libraries and tools lying
> around the internet but the effort of putting them all together as a
> production-ready infrastructure is a very resource-intensive task that is
> remotely reachable by individuals or small businesses.
>
> PredictionIO is a production-ready, full stack machine learning system that
> allows organizations of any scale to quickly deploy machine learning
> capabilities. It comes with official and community-contributed machine
> learning engine templates that are easy to customize.
>
> Rationale
>
> As usage and number of contributors to PredictionIO has grown bigger and
> more diverse, we have sought for an independent framework for the project
> to keep thriving. We believe the Apache foundation is a great fit. Joining
> Apache would ensure that tried and true processes and procedures are in
> place for the growing number of organizations interested in contributing
> to PredictionIO. PredictionIO is also a good fit for the Apache foundation.
> PredictionIO was built on top of several Apache projects (HBase, Spark,
> Hadoop). We are familiar with the Apache process and believe that the
> democratic and meritocratic nature of the foundation aligns with the
> project goals.
>
> Initial Goals
>
> The initial milestones will be to move the existing codebase to Apache and
> integrate with the Apache development process. Once this is accomplished,
> we plan for incremental development and releases that follow the Apache
> guidelines, as well as growing our developer and user communities.
>
> Current Status
>
> PredictionIO has undergone nine minor releases and many patches.
> PredictionIO is being used in production by Salesforce.com as well as many
> other organizations and apps. The PredictionIO codebase is currently
> hosted at GitHub, which will form the basis of the Apache git repository.
>
> Meritocracy
>
> We plan to invest in supporting a meritocracy. We will discuss the
> requirements in an open forum. We intend to invite additional developers
> to participate. We will encourage and monitor community participation so
> that privileges can be extended to those that contribute.
>
> Community
>
> Acceptance into the Apache foundation would bolster the already strong
> user and developer community around PredictionIO. That community includes
> many contributors from various other companies, and an active mailing list
> composed of hundreds of users.
>
> Core Developers
>
> The core developers of our project are listed in our contributors and
> initial PPMC below. Though many are employed at Salesforce.com, there are
> also engineers from ActionML, and independent developers.
>
> Alignment
>
> The ASF is the natural choice to host the PredictionIO project as its goal
> is democratizing Machine Learning by making it more easily accessible to
> every user/developer. PredictionIO is built on top of several top level
> Apache projects as outlined above.
>
> Known Risks
>
> Orphaned Products
>
> PredictionIO has a solid and growing community. It is deployed on
> production environments by compan

Help with new ARIA TOSCA proposal

[Sebastien Goasguen]

Hi folks,

I am an ASF member but I have not been involved with the incubator much.

The last few weeks I have been chatting with folks at Gigaspaces [1]. Some of 
you may know them as the ones behind Cloudify [2] a cloud orchestration 
platform.

The folks at Gigaspaces are interested to donate the orchestration engine 
behind Cloudify to ASF. With the motivation to open the governance of the core 
of Cloudify.

They have already started laying a foundation for an incubator project, putting 
most of the software under a separate organization called ARIA [3] with 
software currently in gitHub [4].

I would like to introduce Arthur Berezin from Gigaspaces who is working on 
putting together a proposal to the incubator. He got an account on the Wiki but 
no karma to add a page yet it seems.

The proposal would need a champion, I don’t feel I have the experience with the 
incubator to do this well, so while I will help, it would be great to get a 
Champion to help shepherd this properly. Any takers ?

Cheers,

[1] http://www.gigaspaces.com
[2] http://getcloudify.org
[3] http://ariatosca.org
[4] https://github.com/aria-tosca

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

Re: [DISCUSS] Accept SensSoft into the Incubator

[Ted Dunning]

This looks like an excellent project.

How likely is it that it will be able to survive a hypothetical loss of
DARPA funding?



On Mon, May 23, 2016 at 3:00 PM, lewis john mcgibbney 
wrote:

> Hi general@,
> I would like to open a DISCUSS thread on the topic of accepting The
> Software as a Sensor™ (SensSoft <
> https://wiki.apache.org/incubator/SensSoft>)
> Project into the Incubator. I am CC'ing Joshua Poore from the Charles Stark
> Draper Laboratory, Inc. who we have been working with to build community
> around a kick-ass set of software projects under the SensSoft umbrella.
> At this stage we would very much appreciate critical feedback from general@
> community.
> We are also open to mentors who may have an interest in the project
> proposal.
> The proposal is pasted below.
> Thanks in advance,
> Lewis
>
> = SensSoft Proposal =
>
> == Abstract ==
> The Software as a Sensor™ (SensSoft) Project offers an open-source (ALv2.0)
> software tool usability testing platform. It includes a number of
> components that work together to provide a platform for collecting data
> about user interactions with software tools, as well as archiving,
> analyzing and visualizing that data. Additional components allow for
> conducting web-based experiments in order to capture this data within a
> larger experimental framework for formal user testing. These components
> currently support Java Script-based web applications, although the schema
> for “logging” user interactions can support mobile and desktop
> applications, as well. Collectively, the Software as a Sensor Project
> provides an open source platform for assessing how users interacted with
> technology, not just collecting what they interacted with.
>
> == Proposal ==
> The Software as a Sensor™ Project is a next-generation platform for
> analyzing how individuals and groups of people make use of software tools
> to perform tasks or interact with other systems. It is composed of a number
> of integrated components:
>  * User Analytic Logging Engine (User ALE) refers to a simple Application
> Program Interface (API) and backend infrastructure. User ALE provides
> “instrumentation” for software tools, such that each user interaction
> within the application can be logged, and sent as a JSON message to an
> Elasticsearch/Logstash/Kibana (Elastic Stack) backend.
>* The API provides a robust schema that makes user activities human
> readable, and provides an interpretive context for understanding that
> activity’s functional relevance within the application. The schema provides
> highly granular information best suited for advanced analytics. This
> hierarchical schema is as follows:
>  * Element Group: App features that share function (e.g., map group)
>  * Element Sub: Specific App feature (e.g., map tiles)
>  * Element Type: Category of feature (e.g., map)
>  * Element ID: [attribute] id
>  * Activity: Human imposed label (e.g., “search”)
>  * Action: Event class (e.g., zoom, hover, click)
>* The API can either be manually embedded in the app source code, or
> implemented automatically by inserting a script tag in the source code.
>* Users can either setup up their own Elastic stack instance, or use
> Vagrant, a virtualization environment, to deploy a fully configured Elastic
> stack instance to ship and ingest user activity logs and visualize their
> log data with Kibana.
>* RESTful APIs allow other services to access logs directly from
> Elasticsearch.
>* User ALE allows adopters to own the data they collect from users
> outright, and utilize it as they see fit.
>  * Distill is an analytics stack for processing user activity logs
> collected through User ALE. Distill is fully implemented in Python,
> dependent on graph-tool to support graph analytics and other external
> python libraries to query Elasticsearch. The two principle functions of
> Distill are segmentation and graph analytics:
>* Segmentation allows for partitioning of the available data along
> multiple axes. Subsets of log data can be selected via their attributes in
> User ALE (e.g. Element Group or Activity), and by users/sessions.  Distill
> also has the capability to ingest and segment data by additional attributes
> collected through other channels (e.g. survey data, demographics).This
> allows adopters to focus their analysis of log data on precisely the
> attributes of their app (or users) they care most about.
>* Distill’s usage metrics are derived from a probabilistic
> representation of the time series of users’ interactions with the elements
> of the application. A directed network is constructed from the
> representation, and metrics from graph theory (e.g. betweenness centrality,
> in/out-degree of nodes) are derived from the structure. These metrics
> provide adopters ways of understanding how different facets of the app are
> used together, and they capture canonical usage patterns of their
> application. This broad analytic framewo

Re: [DISCUSS] CarbonData incubation proposal

[Nick Burch]

On Thu, 19 May 2016, Jean-Baptiste Onofré wrote:

The proposal is included below and also available on the wiki:

https://wiki.apache.org/incubator/CarbonDataProposal


Comparing the Initial Committers list with the Github contributors list, 
there look to be a few people currently quite involved in the project not 
on the initial list. Is there a reason for that? Is there a plan to try to 
bring them over?



Thinking about the challenges that might be faced, I've a few non-standard 
questions too

 * How experienced are the team at communicating in written English?
   (User support is allowed in other languages, but generally development
needs to be in English)
 * How experienced is the team at working with in a distributed / remote
   way?
   (Before graduation, the project will need a distributed and diverse
set of contributors working in non-realtime, if things are only ever
done in Shenzhen today, then they'll need help and support to make the
change)
 * Have any of the current committers contributed to other Apache
   projects already?
   (If a few people can / do contribute to other Apache projects, they can
learn some of the Apache Way from those communities, reducing the
amount of help they'll need from Mentors on learning it)

Thanks
Nick

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

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Ralph Goers]

+1 (binding)

Ralph

> On May 23, 2016, at 10:56 PM, Daniel Gruno  wrote:
> 
> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
> 
> This vote will run for the usual 72 hours.
> 
> ### PROPOSAL BELOW ###
> 
> Abstract
> 
> Pony Mail is a mail-archiving, archive viewing, and interaction service,
> that can be integrated with many email platforms.
> 
> Proposal
> 
> Background
> 
> Pony Mail began as a response to two things; the lack of diversity in
> mailing list archives that are less bureaucratic all-or-nothing and more
> fluid way to interact with mailing lists than what is typically offered,
> and the lack of a performant system that solves this issue. Modern users
> of software want to jump right into a discussion they see, but cannot
> normally do so in a mailing list driven environment because of the rules
> generally surrounding said environment. Pony Mail, along with a select
> handful of newer archive systems, provides an interface that allows
> people to just hop into a thread, and take part. Without the need to
> subscribe, download the mbox archive, load it into your MTA, and respond.
> 
> As Rich writes in a very short essay:
> 
> You see a thread in which someone is WRONG ON THE INTERNET! You need to
> correct them. How do you do this today? You kinda don't. If you really
> wanted, you could download mbox files (and who the hell knows where they
> are?) and then try to get them into your mail client (which never works)
> and then reply to it. Which will break threading, because you did
> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> (sound of hoof beats)
> 
> Rationale
> 
> One of the oft-heard complaints about Apache's development model is that
> mailing lists are an old person's tool, and web-based communication -
> forums - are the way to go in the 21st Century. Providing a
> full-featured forum-like interface to mailing lists is one goal,while
> keeping all of the enormous benefits that mailing lists already provide.
> Asecond goal is to provide the ability to "jump in" to a mailing list
> conversation - even one that was a while back, without the convolutions
> that a mailing list requires. That is, to join this conversation the old
> way, one would have had to subscribe to the mailing list, download an
> mbox, and import it into ones mail client, in order that I be able to
> reply to this message with correct threading. With Pony Mail, one has to
> do none of those things, but can simply reply using the Web UI. To us,
> this is a HUGE benefit for building community. The requirement to jump
> through hoops to join a mailing list conversation drives away a lot of
> people (at least, anecdotally, it does) and if we can remove that
> barrier I think we'll have an easier time of drawing a new generation
> into our projects.
> 
> Initial Goals
> 
> The initial goals of transitioning to the ASF is to expand and grow both
> the Pony codebase and community, and ensure the project's continued
> growth and stability through forming a diverse and reliable community,
> in which the various facets of developers and contributors help keep the
> project up to date with latest developments and technical as well as
> social needs.
> 
> Current Status
> 
>Meritocracy:
> 
> The bulk of the code has been written by Daniel Gruno to date, but has
> had oversight from other committers, and mentors.
> 
>All members of the Pony project and wider community have a deep
> understanding and appreciation for the ASF meritocracy ideals, and are
> almost solely current ASF Members.
> 
>Community:
>The community is currently heavily focused within the ASF, and
> more specifically the Infrastructure group. This is to be expected given
> the nature of how the code came into existence in the first place. It
> should be noted that we have started reaching out to other groups who we
> know are using mailing list systems and therefore also rely on mailing
> list archive interfaces.
> 
>Core Developers:
> 
> Almost all core developers are ASF members, and are already intimately
> familiar with the Apache Way.
> 
>Alignment:
> 
> Pony will be very in line with ASF practices and processes as many of
> the founding members are long term ASF members and committers.
> 
> Known Risks
> 
>Orphaned products:
> 
> We are not aware of any issues with orphaned products related to this
> project.
> 
>Pony Mail relies on a set of CSS3 templates as well as some very stable
>programming languages. We have no reason to believe these would
> be orphaned or, should they become orphaned, that it would impact the
> development of the project.
> 
>Inexperience with Open Source:
>Most of the current committers are already ASF members and
> committers, we do not believe there to be any concerns around OSS
> inexperience.
> 
>Homogenous D

Re: [VOTE] Accept PredictionIO into the Apache Incubator

[Ralph Goers]

+1 (binding)

Ralph

> On May 24, 2016, at 3:44 AM, John D. Ament  wrote:
> 
> +1
> 
> On Mon, May 23, 2016 at 6:23 PM Andrew Purtell  wrote:
> 
>> Since discussion on the matter of PredictionIO has died down, I would like
>> to call a VOTE
>> on accepting PredictionIO into the Apache Incubator.
>> 
>> Proposal: https://wiki.apache.org/incubator/PredictionIO
>> 
>> ​[ ] +1 Accept PredictionIO into the Apache Incubator
>> [ ] +0 Abstain
>> [ ] -1 Do not accept PredictionIO into the Apache Incubator, because ...
>> 
>> This vote will be open for at least 72 hours.
>> 
>> My vote is +1 (binding)
>> 
>> --
>> 
>> PredictionIO Proposal
>> 
>> Abstract
>> 
>> PredictionIO is an open source Machine Learning Server built on top of
>> state-of-the-art open source stack, that enables developers to manage and
>> deploy production-ready predictive services for various kinds of machine
>> learning tasks.
>> 
>> Proposal
>> 
>> The PredictionIO platform consists of the following components:
>> 
>>   * PredictionIO framework - provides the machine learning stack for
>> building, evaluating and deploying engines with machine learning
>> algorithms. It uses Apache Spark for processing.
>> 
>>   * Event Server - the machine learning analytics layer for unifying
>> events
>> from multiple platforms. It can use Apache HBase or any JDBC backends
>> as its data store.
>> 
>> The PredictionIO community also maintains a Template Gallery, a place to
>> publish and download (free or proprietary) engine templates for different
>> types of machine learning applications, and is a complemental part of the
>> project. At this point we exclude the Template Gallery from the proposal,
>> as it has a separate set of contributors and we’re not familiar with an
>> Apache approved mechanism to maintain such a gallery.
>> 
>> Background
>> 
>> PredictionIO was started with a mission to democratize and bring machine
>> learning to the masses.
>> 
>> Machine learning has traditionally been a luxury for big companies like
>> Google, Facebook, and Netflix. There are ML libraries and tools lying
>> around the internet but the effort of putting them all together as a
>> production-ready infrastructure is a very resource-intensive task that is
>> remotely reachable by individuals or small businesses.
>> 
>> PredictionIO is a production-ready, full stack machine learning system that
>> allows organizations of any scale to quickly deploy machine learning
>> capabilities. It comes with official and community-contributed machine
>> learning engine templates that are easy to customize.
>> 
>> Rationale
>> 
>> As usage and number of contributors to PredictionIO has grown bigger and
>> more diverse, we have sought for an independent framework for the project
>> to keep thriving. We believe the Apache foundation is a great fit. Joining
>> Apache would ensure that tried and true processes and procedures are in
>> place for the growing number of organizations interested in contributing
>> to PredictionIO. PredictionIO is also a good fit for the Apache foundation.
>> PredictionIO was built on top of several Apache projects (HBase, Spark,
>> Hadoop). We are familiar with the Apache process and believe that the
>> democratic and meritocratic nature of the foundation aligns with the
>> project goals.
>> 
>> Initial Goals
>> 
>> The initial milestones will be to move the existing codebase to Apache and
>> integrate with the Apache development process. Once this is accomplished,
>> we plan for incremental development and releases that follow the Apache
>> guidelines, as well as growing our developer and user communities.
>> 
>> Current Status
>> 
>> PredictionIO has undergone nine minor releases and many patches.
>> PredictionIO is being used in production by Salesforce.com as well as many
>> other organizations and apps. The PredictionIO codebase is currently
>> hosted at GitHub, which will form the basis of the Apache git repository.
>> 
>> Meritocracy
>> 
>> We plan to invest in supporting a meritocracy. We will discuss the
>> requirements in an open forum. We intend to invite additional developers
>> to participate. We will encourage and monitor community participation so
>> that privileges can be extended to those that contribute.
>> 
>> Community
>> 
>> Acceptance into the Apache foundation would bolster the already strong
>> user and developer community around PredictionIO. That community includes
>> many contributors from various other companies, and an active mailing list
>> composed of hundreds of users.
>> 
>> Core Developers
>> 
>> The core developers of our project are listed in our contributors and
>> initial PPMC below. Though many are employed at Salesforce.com, there are
>> also engineers from ActionML, and independent developers.
>> 
>> Alignment
>> 
>> The ASF is the natural choice to host the PredictionIO project as its goal
>> is democratizing Machine Learning by making it more easily accessible to
>> every user/developer. Predict

Re: [DISCUSS] Accept SensSoft into the Incubator

[Lewis John Mcgibbney]

Hi Ted,
Thank you for your input. Replies inline

On Tue, May 24, 2016 at 6:44 AM, 
wrote:

>
> From: Ted Dunning 
> To: "general@incubator.apache.org" 
> Cc: jpo...@draper.com
> Date: Tue, 24 May 2016 09:44:15 -0400
> Subject: Re: [DISCUSS] Accept SensSoft into the Incubator
> This looks like an excellent project.
>

I agree. We have been working with Draper Labs and have engaged in a number
of their user testing. The software is particularly interesting... also
more or less everything is named after some kind of alcohol so I've been a
devoted fan from the outset :)


>
> How likely is it that it will be able to survive a hypothetical loss of
> DARPA funding?
>
>
I think that the project codebase itself is in a mature enough position now
that it can be considered beyond what DARPA will inevitably continue to
fund development of and is in a position to stand on it's own feet,
building out community as it goes. The software is not DARPA R&TD/early
technology readiness level anymore. It is beyond that as it presents a
suite of productized software. The Draper Labs team have been working hard
to drive the software towards product-level OSS. As with all DARPA
projects, funding is not guaranteed (or expected) forever, SensSoft falls
in to that category. Draper have been aware of this and it was expected all
along.
Having spoke with the Draper Labs team, I have been convinced that the
software components have wider applicable uses and that there is a large
opportunity to grow diverse community around the codebase. Hopefully the
proposal reflects that.
Thanks
Lewis

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Billie Rinaldi]

+1 (binding)

On Tue, May 24, 2016 at 7:56 AM, Daniel Gruno  wrote:
> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>
> This vote will run for the usual 72 hours.
>
> ### PROPOSAL BELOW ###
>
> Abstract
>
> Pony Mail is a mail-archiving, archive viewing, and interaction service,
> that can be integrated with many email platforms.
>
> Proposal
>
> Background
>
> Pony Mail began as a response to two things; the lack of diversity in
> mailing list archives that are less bureaucratic all-or-nothing and more
> fluid way to interact with mailing lists than what is typically offered,
> and the lack of a performant system that solves this issue. Modern users
> of software want to jump right into a discussion they see, but cannot
> normally do so in a mailing list driven environment because of the rules
> generally surrounding said environment. Pony Mail, along with a select
> handful of newer archive systems, provides an interface that allows
> people to just hop into a thread, and take part. Without the need to
> subscribe, download the mbox archive, load it into your MTA, and respond.
>
> As Rich writes in a very short essay:
>
> You see a thread in which someone is WRONG ON THE INTERNET! You need to
> correct them. How do you do this today? You kinda don't. If you really
> wanted, you could download mbox files (and who the hell knows where they
> are?) and then try to get them into your mail client (which never works)
> and then reply to it. Which will break threading, because you did
> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> (sound of hoof beats)
>
> Rationale
>
> One of the oft-heard complaints about Apache's development model is that
> mailing lists are an old person's tool, and web-based communication -
> forums - are the way to go in the 21st Century. Providing a
> full-featured forum-like interface to mailing lists is one goal,while
> keeping all of the enormous benefits that mailing lists already provide.
> Asecond goal is to provide the ability to "jump in" to a mailing list
> conversation - even one that was a while back, without the convolutions
> that a mailing list requires. That is, to join this conversation the old
> way, one would have had to subscribe to the mailing list, download an
> mbox, and import it into ones mail client, in order that I be able to
> reply to this message with correct threading. With Pony Mail, one has to
> do none of those things, but can simply reply using the Web UI. To us,
> this is a HUGE benefit for building community. The requirement to jump
> through hoops to join a mailing list conversation drives away a lot of
> people (at least, anecdotally, it does) and if we can remove that
> barrier I think we'll have an easier time of drawing a new generation
> into our projects.
>
> Initial Goals
>
> The initial goals of transitioning to the ASF is to expand and grow both
> the Pony codebase and community, and ensure the project's continued
> growth and stability through forming a diverse and reliable community,
> in which the various facets of developers and contributors help keep the
> project up to date with latest developments and technical as well as
> social needs.
>
> Current Status
>
> Meritocracy:
>
> The bulk of the code has been written by Daniel Gruno to date, but has
> had oversight from other committers, and mentors.
>
> All members of the Pony project and wider community have a deep
> understanding and appreciation for the ASF meritocracy ideals, and are
> almost solely current ASF Members.
>
> Community:
> The community is currently heavily focused within the ASF, and
> more specifically the Infrastructure group. This is to be expected given
> the nature of how the code came into existence in the first place. It
> should be noted that we have started reaching out to other groups who we
> know are using mailing list systems and therefore also rely on mailing
> list archive interfaces.
>
> Core Developers:
>
> Almost all core developers are ASF members, and are already intimately
> familiar with the Apache Way.
>
> Alignment:
>
> Pony will be very in line with ASF practices and processes as many of
> the founding members are long term ASF members and committers.
>
> Known Risks
>
> Orphaned products:
>
> We are not aware of any issues with orphaned products related to this
> project.
>
> Pony Mail relies on a set of CSS3 templates as well as some very
stable
> programming languages. We have no reason to believe these would
> be orphaned or, should they become orphaned, that it would impact the
> development of the project.
>
> Inexperience with Open Source:
> Most of the current committers are already ASF members and
> committers, we do not believe there to be any concerns around OSS
> inexperience.
>
> Homogenous Developers:
> Whil

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[James Taylor]

+1 (binding)

On Tue, May 24, 2016 at 7:48 AM, Billie Rinaldi  wrote:

> +1 (binding)
>
> On Tue, May 24, 2016 at 7:56 AM, Daniel Gruno 
> wrote:
> > Since it seems the discussion has died down, I am now calling a vote on
> > accepting Pony Mail into the Incubator. Sorry in advance for potato.
> >
> > This vote will run for the usual 72 hours.
> >
> > ### PROPOSAL BELOW ###
> >
> > Abstract
> >
> > Pony Mail is a mail-archiving, archive viewing, and interaction service,
> > that can be integrated with many email platforms.
> >
> > Proposal
> >
> > Background
> >
> > Pony Mail began as a response to two things; the lack of diversity in
> > mailing list archives that are less bureaucratic all-or-nothing and more
> > fluid way to interact with mailing lists than what is typically offered,
> > and the lack of a performant system that solves this issue. Modern users
> > of software want to jump right into a discussion they see, but cannot
> > normally do so in a mailing list driven environment because of the rules
> > generally surrounding said environment. Pony Mail, along with a select
> > handful of newer archive systems, provides an interface that allows
> > people to just hop into a thread, and take part. Without the need to
> > subscribe, download the mbox archive, load it into your MTA, and respond.
> >
> > As Rich writes in a very short essay:
> >
> > You see a thread in which someone is WRONG ON THE INTERNET! You need to
> > correct them. How do you do this today? You kinda don't. If you really
> > wanted, you could download mbox files (and who the hell knows where they
> > are?) and then try to get them into your mail client (which never works)
> > and then reply to it. Which will break threading, because you did
> > something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> > (sound of hoof beats)
> >
> > Rationale
> >
> > One of the oft-heard complaints about Apache's development model is that
> > mailing lists are an old person's tool, and web-based communication -
> > forums - are the way to go in the 21st Century. Providing a
> > full-featured forum-like interface to mailing lists is one goal,while
> > keeping all of the enormous benefits that mailing lists already provide.
> > Asecond goal is to provide the ability to "jump in" to a mailing list
> > conversation - even one that was a while back, without the convolutions
> > that a mailing list requires. That is, to join this conversation the old
> > way, one would have had to subscribe to the mailing list, download an
> > mbox, and import it into ones mail client, in order that I be able to
> > reply to this message with correct threading. With Pony Mail, one has to
> > do none of those things, but can simply reply using the Web UI. To us,
> > this is a HUGE benefit for building community. The requirement to jump
> > through hoops to join a mailing list conversation drives away a lot of
> > people (at least, anecdotally, it does) and if we can remove that
> > barrier I think we'll have an easier time of drawing a new generation
> > into our projects.
> >
> > Initial Goals
> >
> > The initial goals of transitioning to the ASF is to expand and grow both
> > the Pony codebase and community, and ensure the project's continued
> > growth and stability through forming a diverse and reliable community,
> > in which the various facets of developers and contributors help keep the
> > project up to date with latest developments and technical as well as
> > social needs.
> >
> > Current Status
> >
> > Meritocracy:
> >
> > The bulk of the code has been written by Daniel Gruno to date, but has
> > had oversight from other committers, and mentors.
> >
> > All members of the Pony project and wider community have a deep
> > understanding and appreciation for the ASF meritocracy ideals, and are
> > almost solely current ASF Members.
> >
> > Community:
> > The community is currently heavily focused within the ASF, and
> > more specifically the Infrastructure group. This is to be expected given
> > the nature of how the code came into existence in the first place. It
> > should be noted that we have started reaching out to other groups who we
> > know are using mailing list systems and therefore also rely on mailing
> > list archive interfaces.
> >
> > Core Developers:
> >
> > Almost all core developers are ASF members, and are already intimately
> > familiar with the Apache Way.
> >
> > Alignment:
> >
> > Pony will be very in line with ASF practices and processes as many of
> > the founding members are long term ASF members and committers.
> >
> > Known Risks
> >
> > Orphaned products:
> >
> > We are not aware of any issues with orphaned products related to this
> > project.
> >
> > Pony Mail relies on a set of CSS3 templates as well as some very
> stable
> > programming languages. We have no reason to believe these would
> > be orphaned or, should they become orphaned, th

[RESULT][VOTE] Release of Apache Mnemonic-0.1.2-incubating [rc2] (Revised)

[Gary]

Hi all,


After being open for over 72 hours, the vote for releasing Apache Mnemonic 
0.1.2-incubating passed with 3 binding +1s and no +0 and no -1.

 

Binding +1s:

Henry Saputra

Justin Mclean
Gangumalla, Uma


A issue we need to work on -

1. Justin had issues building from source on OSX . We will look into the issue.


Thanks to everyone who voted!


Thanks,

Gary on behalf of the Apache Mnemonic (incubating) team




signature.asc
Description: OpenPGP digital signature

Re: [RESULT][VOTE] Release of Apache Mnemonic-0.1.2-incubating [rc2] (Revised)

[Patrick Hunt]

Hi Gary. You want to summarize all the votes, including the ones on the
project's dev list, here - I (and others) had voted on the dev list thread
already.

Patrick

On Tue, May 24, 2016 at 8:55 AM, Gary  wrote:

> Hi all,
>
>
> After being open for over 72 hours, the vote for releasing Apache Mnemonic
> 0.1.2-incubating passed with 3 binding +1s and no +0 and no -1.
>
>
>
> Binding +1s:
>
> Henry Saputra
>
> Justin Mclean
> Gangumalla, Uma
>
>
> A issue we need to work on -
>
> 1. Justin had issues building from source on OSX . We will look into the
> issue.
>
>
> Thanks to everyone who voted!
>
>
> Thanks,
>
> Gary on behalf of the Apache Mnemonic (incubating) team
>
>
>

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Leif Hedstrom]

> On May 23, 2016, at 11:56 PM, Daniel Gruno  wrote:
> 
> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
> 
> This vote will run for the usual 72 hours.


+1 (binding).

— leif


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

[VOTE] Release Apache Ranger 0.5.3 (incubating) - rc3

[Velmurugan Periasamy]

Incubator PMC:

Apache Ranger community has voted on and approved a proposal to release Apache 
Ranger 0.5.3 (incubating). 

[VOTE RESULT] thread:
https://lists.apache.org/thread.html/Ztlreja8-xl1xr8

Apache ranger-0.5.3-rc3 release candidate (addressing few issues raised in 
previous IPMC reviews) is now available with the following artifacts up for 
IPMC vote. I kindly request that the Incubator PMC members review and vote on 
this incubator release.

Git tag for the release:
https://github.com/apache/incubator-ranger/tree/ranger-0.5.3-rc3

Source release:

https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.3-incubating-rc3/apache-ranger-incubating-0.5.3.tar.gz

Source release verification:
PGP Signature:  

https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.3-incubating-rc3/apache-ranger-incubating-0.5.3.tar.gz.asc
MD5/SHA  Hash:  

https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.3-incubating-rc3/apache-ranger-incubating-0.5.3.tar.gz.mds
Keys to verify the signature of the release artifact are available at:
https://dist.apache.org/repos/dist/release/incubator/ranger/KEYS

Release Notes:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=62694969  

Build verification steps can be found at:
http://ranger.incubator.apache.org/quick_start_guide.html

The vote will be open for at least 72 hours or until necessary number of votes 
are reached.
[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Here is my +1 (non binding)

Thanks,
Vel

Re: [VOTE] Release Apache Mynewt 0.9.0-incubating-rc1

[Christopher Collins]

Hello all,

I would like to make an open request to the PMC community: if you have
the time, could you please take a look at this release candidate and
cast a vote?  This release contains some critical bug fixes, so we would
like to release it if possible.

I can tell from all the traffic that there is a lot going on right now.
All votes, positive and negative, are greatly appreciated.

Chris

On Sun, May 22, 2016 at 11:52:15AM -0700, Christopher Collins wrote:
> Hello,
> 
> The Apache Mynewt Incubator PPMC has approved a proposal to release
> Apache Mynewt 0.9.0-incubating. We now kindly request that the Incubator
> PMC members review and vote on this incubator release.
> 
> Apache Mynewt is a community-driven, permissively licensed open source
> initiative for constrained, embedded applications. Mynewt provides a
> real-time operating system, flash file system, network stacks, and
> support utilities for real-world embedded systems.
> 
> The highlights of this release are:
> * Bug fixes for the bleprph example app.  The bugs are described
>   under "known issues" here:
>   https://cwiki.apache.org/confluence/display/MYNEWT/RN-0.8.0-incubating)
> 
> * NimBLE stack: BLE pairing and bonding support
> * These features are now enabled by default, and are available
>   in the example BLE apps: bleprph and bletiny.
> 
> * NimBLE stack: Eddystone beacon support
> 
> * Boot loader: The file system no longer fills up after repeated
>   image upgrades.
> 
> [VOTE] thread:
> https://lists.apache.org/thread.html/Za581nzdkku97cr
> 
> [VOTE RESULT] thread:
> https://lists.apache.org/thread.html/Z9ezdety3cst2d5
> 
> [DISCUSS] thread:
> https://lists.apache.org/thread.html/Zse8zizsjwcnfz4
> 
> This release candidate was tested as follows:
> 1. Manual execution of the Mynewt test plan
>
> (https://cwiki.apache.org/confluence/display/MYNEWT/Apache+Mynewt+Test+Plan).
> 2. The full unit test suite for this release was executed via "newt
>test all" with no failures. This testing was performed on the
>following platforms:
>  * OS X 10.10.5
>  * Linux 3.19.0 (Ubuntu 14.04)
> 
> The release candidate to be voted on is available at:
> https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-0.9.0-incubating/rc1/
> 
> The commits under consideration are as follows:
> 
> blinky:
> repos: https://git-wip-us.apache.org/repos/asf/incubator-mynewt-blinky
> commit: 82f09fa2cc4c67fb30165ef6be0291aa76e6213e
> 
> core:
> repos: https://git-wip-us.apache.org/repos/asf/incubator-mynewt-core
> commit: 48df9b088c50cfc97d2518a823294ace761633d6
> 
> newt:
> repos: https://git-wip-us.apache.org/repos/asf/incubator-mynewt-newt
> commit: 0afe655414bbefc922d2adfddf238479bedac5c0
> 
> In addition, the following newt convenience binaries are available:
> linux: 
> https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-0.9.0-incubating/rc1/apache-newt-bin-linux-0.9.0-incubating.tgz
> osx: 
> https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-0.9.0-incubating/rc1/apache-newt-bin-osx-0.9.0-incubating.tgz
> 
> The release candidate is signed with a GPG key available at:
> https://dist.apache.org/repos/dist/dev/incubator/mynewt/KEYS
> 
> The vote is open for at least 72 hours.
> 
> [ ] +1 Release this package
> [ ]  0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because…
> 
> Thanks,
> Chris

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

Re: [VOTE] Accept PredictionIO into the Apache Incubator

[Seetharam Venkatesh]

+1 (binding)

All the best,
Venkatesh

On Tue, May 24, 2016 at 7:15 AM Ralph Goers 
wrote:

> +1 (binding)
>
> Ralph
>
> > On May 24, 2016, at 3:44 AM, John D. Ament 
> wrote:
> >
> > +1
> >
> > On Mon, May 23, 2016 at 6:23 PM Andrew Purtell 
> wrote:
> >
> >> Since discussion on the matter of PredictionIO has died down, I would
> like
> >> to call a VOTE
> >> on accepting PredictionIO into the Apache Incubator.
> >>
> >> Proposal: https://wiki.apache.org/incubator/PredictionIO
> >>
> >> ​[ ] +1 Accept PredictionIO into the Apache Incubator
> >> [ ] +0 Abstain
> >> [ ] -1 Do not accept PredictionIO into the Apache Incubator, because ...
> >>
> >> This vote will be open for at least 72 hours.
> >>
> >> My vote is +1 (binding)
> >>
> >> --
> >>
> >> PredictionIO Proposal
> >>
> >> Abstract
> >>
> >> PredictionIO is an open source Machine Learning Server built on top of
> >> state-of-the-art open source stack, that enables developers to manage
> and
> >> deploy production-ready predictive services for various kinds of machine
> >> learning tasks.
> >>
> >> Proposal
> >>
> >> The PredictionIO platform consists of the following components:
> >>
> >>   * PredictionIO framework - provides the machine learning stack for
> >> building, evaluating and deploying engines with machine learning
> >> algorithms. It uses Apache Spark for processing.
> >>
> >>   * Event Server - the machine learning analytics layer for unifying
> >> events
> >> from multiple platforms. It can use Apache HBase or any JDBC
> backends
> >> as its data store.
> >>
> >> The PredictionIO community also maintains a Template Gallery, a place to
> >> publish and download (free or proprietary) engine templates for
> different
> >> types of machine learning applications, and is a complemental part of
> the
> >> project. At this point we exclude the Template Gallery from the
> proposal,
> >> as it has a separate set of contributors and we’re not familiar with an
> >> Apache approved mechanism to maintain such a gallery.
> >>
> >> Background
> >>
> >> PredictionIO was started with a mission to democratize and bring machine
> >> learning to the masses.
> >>
> >> Machine learning has traditionally been a luxury for big companies like
> >> Google, Facebook, and Netflix. There are ML libraries and tools lying
> >> around the internet but the effort of putting them all together as a
> >> production-ready infrastructure is a very resource-intensive task that
> is
> >> remotely reachable by individuals or small businesses.
> >>
> >> PredictionIO is a production-ready, full stack machine learning system
> that
> >> allows organizations of any scale to quickly deploy machine learning
> >> capabilities. It comes with official and community-contributed machine
> >> learning engine templates that are easy to customize.
> >>
> >> Rationale
> >>
> >> As usage and number of contributors to PredictionIO has grown bigger and
> >> more diverse, we have sought for an independent framework for the
> project
> >> to keep thriving. We believe the Apache foundation is a great fit.
> Joining
> >> Apache would ensure that tried and true processes and procedures are in
> >> place for the growing number of organizations interested in contributing
> >> to PredictionIO. PredictionIO is also a good fit for the Apache
> foundation.
> >> PredictionIO was built on top of several Apache projects (HBase, Spark,
> >> Hadoop). We are familiar with the Apache process and believe that the
> >> democratic and meritocratic nature of the foundation aligns with the
> >> project goals.
> >>
> >> Initial Goals
> >>
> >> The initial milestones will be to move the existing codebase to Apache
> and
> >> integrate with the Apache development process. Once this is
> accomplished,
> >> we plan for incremental development and releases that follow the Apache
> >> guidelines, as well as growing our developer and user communities.
> >>
> >> Current Status
> >>
> >> PredictionIO has undergone nine minor releases and many patches.
> >> PredictionIO is being used in production by Salesforce.com as well as
> many
> >> other organizations and apps. The PredictionIO codebase is currently
> >> hosted at GitHub, which will form the basis of the Apache git
> repository.
> >>
> >> Meritocracy
> >>
> >> We plan to invest in supporting a meritocracy. We will discuss the
> >> requirements in an open forum. We intend to invite additional developers
> >> to participate. We will encourage and monitor community participation so
> >> that privileges can be extended to those that contribute.
> >>
> >> Community
> >>
> >> Acceptance into the Apache foundation would bolster the already strong
> >> user and developer community around PredictionIO. That community
> includes
> >> many contributors from various other companies, and an active mailing
> list
> >> composed of hundreds of users.
> >>
> >> Core Developers
> >>
> >> The core developers of our project are listed in our contributors and
> >> initial PPMC b

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Seetharam Venkatesh]

+1 (binding)

All the best,
Venkatesh

On Tue, May 24, 2016 at 10:05 AM Leif Hedstrom  wrote:

>
> > On May 23, 2016, at 11:56 PM, Daniel Gruno  wrote:
> >
> > Since it seems the discussion has died down, I am now calling a vote on
> > accepting Pony Mail into the Incubator. Sorry in advance for potato.
> >
> > This vote will run for the usual 72 hours.
>
>
> +1 (binding).
>
> — leif
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Luke Han]

+1 (binding)

Very great experience, people love the lists.apache.org when I introduced
it to them!

Thanks.
Luke


Best Regards!
-

Luke Han

On Tue, May 24, 2016 at 10:51 AM, Seetharam Venkatesh <
venkat...@innerzeal.com> wrote:

> +1 (binding)
>
> All the best,
> Venkatesh
>
> On Tue, May 24, 2016 at 10:05 AM Leif Hedstrom  wrote:
>
> >
> > > On May 23, 2016, at 11:56 PM, Daniel Gruno 
> wrote:
> > >
> > > Since it seems the discussion has died down, I am now calling a vote on
> > > accepting Pony Mail into the Incubator. Sorry in advance for potato.
> > >
> > > This vote will run for the usual 72 hours.
> >
> >
> > +1 (binding).
> >
> > — leif
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Luciano Resende]

+1 (binding)

On Mon, May 23, 2016 at 10:56 PM, Daniel Gruno  wrote:

> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>
> This vote will run for the usual 72 hours.
>
> ### PROPOSAL BELOW ###
>
> Abstract
>
> Pony Mail is a mail-archiving, archive viewing, and interaction service,
> that can be integrated with many email platforms.
>
> Proposal
>
> Background
>
> Pony Mail began as a response to two things; the lack of diversity in
> mailing list archives that are less bureaucratic all-or-nothing and more
> fluid way to interact with mailing lists than what is typically offered,
> and the lack of a performant system that solves this issue. Modern users
> of software want to jump right into a discussion they see, but cannot
> normally do so in a mailing list driven environment because of the rules
> generally surrounding said environment. Pony Mail, along with a select
> handful of newer archive systems, provides an interface that allows
> people to just hop into a thread, and take part. Without the need to
> subscribe, download the mbox archive, load it into your MTA, and respond.
>
> As Rich writes in a very short essay:
>
> You see a thread in which someone is WRONG ON THE INTERNET! You need to
> correct them. How do you do this today? You kinda don't. If you really
> wanted, you could download mbox files (and who the hell knows where they
> are?) and then try to get them into your mail client (which never works)
> and then reply to it. Which will break threading, because you did
> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> (sound of hoof beats)
>
> Rationale
>
> One of the oft-heard complaints about Apache's development model is that
> mailing lists are an old person's tool, and web-based communication -
> forums - are the way to go in the 21st Century. Providing a
> full-featured forum-like interface to mailing lists is one goal,while
> keeping all of the enormous benefits that mailing lists already provide.
> Asecond goal is to provide the ability to "jump in" to a mailing list
> conversation - even one that was a while back, without the convolutions
> that a mailing list requires. That is, to join this conversation the old
> way, one would have had to subscribe to the mailing list, download an
> mbox, and import it into ones mail client, in order that I be able to
> reply to this message with correct threading. With Pony Mail, one has to
> do none of those things, but can simply reply using the Web UI. To us,
> this is a HUGE benefit for building community. The requirement to jump
> through hoops to join a mailing list conversation drives away a lot of
> people (at least, anecdotally, it does) and if we can remove that
> barrier I think we'll have an easier time of drawing a new generation
> into our projects.
>
> Initial Goals
>
> The initial goals of transitioning to the ASF is to expand and grow both
> the Pony codebase and community, and ensure the project's continued
> growth and stability through forming a diverse and reliable community,
> in which the various facets of developers and contributors help keep the
> project up to date with latest developments and technical as well as
> social needs.
>
> Current Status
>
> Meritocracy:
>
> The bulk of the code has been written by Daniel Gruno to date, but has
> had oversight from other committers, and mentors.
>
> All members of the Pony project and wider community have a deep
> understanding and appreciation for the ASF meritocracy ideals, and are
> almost solely current ASF Members.
>
> Community:
> The community is currently heavily focused within the ASF, and
> more specifically the Infrastructure group. This is to be expected given
> the nature of how the code came into existence in the first place. It
> should be noted that we have started reaching out to other groups who we
> know are using mailing list systems and therefore also rely on mailing
> list archive interfaces.
>
> Core Developers:
>
> Almost all core developers are ASF members, and are already intimately
> familiar with the Apache Way.
>
> Alignment:
>
> Pony will be very in line with ASF practices and processes as many of
> the founding members are long term ASF members and committers.
>
> Known Risks
>
> Orphaned products:
>
> We are not aware of any issues with orphaned products related to this
> project.
>
> Pony Mail relies on a set of CSS3 templates as well as some very stable
> programming languages. We have no reason to believe these would
> be orphaned or, should they become orphaned, that it would impact the
> development of the project.
>
> Inexperience with Open Source:
> Most of the current committers are already ASF members and
> committers, we do not believe there to be any concerns around OSS
> inexperience.
>
> Homogenous Developers:
> Wh

Re: [DISCUSS] CarbonData incubation proposal

[Liang Chen]

Hi Nick

Thanks for your questions.

The initial committers are contributors who are fully involved for
CarbonData project, after some time based on contribution and Meritocracy ,
we will include more contributors into the committer list.

1.Some of the committers are actually located in the US (in labs), and our
internal communication is in english for remote work.
2.Current committers are spread in different locations (from the US to
China, and India) , and work in different time zone.
3.Yes, we participated in other Apache project contribution works, Apache
Spark, Apache Flink, Apache Hadoop etc, some contribution list as below:
https://github.com/apache/spark/commits?author=jihongMA
https://github.com/apache/spark/commits?author=jackylk
https://github.com/apache/flink/commits?author=chenliang613

Regards
Liang



--
View this message in context: 
http://apache-incubator-general.996316.n3.nabble.com/DISCUSS-CarbonData-incubation-proposal-tp49643p49794.html
Sent from the Apache Incubator - General mailing list archive at Nabble.com.

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

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Andrew Purtell]

+1 (binding)


On Mon, May 23, 2016 at 10:56 PM, Daniel Gruno  wrote:

> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>
> This vote will run for the usual 72 hours.
>
> ### PROPOSAL BELOW ###
>
> Abstract
>
> Pony Mail is a mail-archiving, archive viewing, and interaction service,
> that can be integrated with many email platforms.
>
> Proposal
>
> Background
>
> Pony Mail began as a response to two things; the lack of diversity in
> mailing list archives that are less bureaucratic all-or-nothing and more
> fluid way to interact with mailing lists than what is typically offered,
> and the lack of a performant system that solves this issue. Modern users
> of software want to jump right into a discussion they see, but cannot
> normally do so in a mailing list driven environment because of the rules
> generally surrounding said environment. Pony Mail, along with a select
> handful of newer archive systems, provides an interface that allows
> people to just hop into a thread, and take part. Without the need to
> subscribe, download the mbox archive, load it into your MTA, and respond.
>
> As Rich writes in a very short essay:
>
> You see a thread in which someone is WRONG ON THE INTERNET! You need to
> correct them. How do you do this today? You kinda don't. If you really
> wanted, you could download mbox files (and who the hell knows where they
> are?) and then try to get them into your mail client (which never works)
> and then reply to it. Which will break threading, because you did
> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> (sound of hoof beats)
>
> Rationale
>
> One of the oft-heard complaints about Apache's development model is that
> mailing lists are an old person's tool, and web-based communication -
> forums - are the way to go in the 21st Century. Providing a
> full-featured forum-like interface to mailing lists is one goal,while
> keeping all of the enormous benefits that mailing lists already provide.
> Asecond goal is to provide the ability to "jump in" to a mailing list
> conversation - even one that was a while back, without the convolutions
> that a mailing list requires. That is, to join this conversation the old
> way, one would have had to subscribe to the mailing list, download an
> mbox, and import it into ones mail client, in order that I be able to
> reply to this message with correct threading. With Pony Mail, one has to
> do none of those things, but can simply reply using the Web UI. To us,
> this is a HUGE benefit for building community. The requirement to jump
> through hoops to join a mailing list conversation drives away a lot of
> people (at least, anecdotally, it does) and if we can remove that
> barrier I think we'll have an easier time of drawing a new generation
> into our projects.
>
> Initial Goals
>
> The initial goals of transitioning to the ASF is to expand and grow both
> the Pony codebase and community, and ensure the project's continued
> growth and stability through forming a diverse and reliable community,
> in which the various facets of developers and contributors help keep the
> project up to date with latest developments and technical as well as
> social needs.
>
> Current Status
>
> Meritocracy:
>
> The bulk of the code has been written by Daniel Gruno to date, but has
> had oversight from other committers, and mentors.
>
> All members of the Pony project and wider community have a deep
> understanding and appreciation for the ASF meritocracy ideals, and are
> almost solely current ASF Members.
>
> Community:
> The community is currently heavily focused within the ASF, and
> more specifically the Infrastructure group. This is to be expected given
> the nature of how the code came into existence in the first place. It
> should be noted that we have started reaching out to other groups who we
> know are using mailing list systems and therefore also rely on mailing
> list archive interfaces.
>
> Core Developers:
>
> Almost all core developers are ASF members, and are already intimately
> familiar with the Apache Way.
>
> Alignment:
>
> Pony will be very in line with ASF practices and processes as many of
> the founding members are long term ASF members and committers.
>
> Known Risks
>
> Orphaned products:
>
> We are not aware of any issues with orphaned products related to this
> project.
>
> Pony Mail relies on a set of CSS3 templates as well as some very stable
> programming languages. We have no reason to believe these would
> be orphaned or, should they become orphaned, that it would impact the
> development of the project.
>
> Inexperience with Open Source:
> Most of the current committers are already ASF members and
> committers, we do not believe there to be any concerns around OSS
> inexperience.
>
> Homogenous Developers:
> W

Re: [VOTE] Accept PredictionIO into the Apache Incubator

[Hitesh Shah]

+1 (binding)

— Hitesh

> On May 23, 2016, at 3:22 PM, Andrew Purtell  wrote:
> 
> Since discussion on the matter of PredictionIO has died down, I would like
> to call a VOTE
> on accepting PredictionIO into the Apache Incubator.
> 
> Proposal: https://wiki.apache.org/incubator/PredictionIO
> 
> ​[ ] +1 Accept PredictionIO into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept PredictionIO into the Apache Incubator, because ...
> 
> This vote will be open for at least 72 hours.
> 
> My vote is +1 (binding)
> 
> --
> 
> PredictionIO Proposal
> 
> Abstract
> 
> PredictionIO is an open source Machine Learning Server built on top of
> state-of-the-art open source stack, that enables developers to manage and
> deploy production-ready predictive services for various kinds of machine
> learning tasks.
> 
> Proposal
> 
> The PredictionIO platform consists of the following components:
> 
>   * PredictionIO framework - provides the machine learning stack for
> building, evaluating and deploying engines with machine learning
> algorithms. It uses Apache Spark for processing.
> 
>   * Event Server - the machine learning analytics layer for unifying events
> from multiple platforms. It can use Apache HBase or any JDBC backends
> as its data store.
> 
> The PredictionIO community also maintains a Template Gallery, a place to
> publish and download (free or proprietary) engine templates for different
> types of machine learning applications, and is a complemental part of the
> project. At this point we exclude the Template Gallery from the proposal,
> as it has a separate set of contributors and we’re not familiar with an
> Apache approved mechanism to maintain such a gallery.
> 
> Background
> 
> PredictionIO was started with a mission to democratize and bring machine
> learning to the masses.
> 
> Machine learning has traditionally been a luxury for big companies like
> Google, Facebook, and Netflix. There are ML libraries and tools lying
> around the internet but the effort of putting them all together as a
> production-ready infrastructure is a very resource-intensive task that is
> remotely reachable by individuals or small businesses.
> 
> PredictionIO is a production-ready, full stack machine learning system that
> allows organizations of any scale to quickly deploy machine learning
> capabilities. It comes with official and community-contributed machine
> learning engine templates that are easy to customize.
> 
> Rationale
> 
> As usage and number of contributors to PredictionIO has grown bigger and
> more diverse, we have sought for an independent framework for the project
> to keep thriving. We believe the Apache foundation is a great fit. Joining
> Apache would ensure that tried and true processes and procedures are in
> place for the growing number of organizations interested in contributing
> to PredictionIO. PredictionIO is also a good fit for the Apache foundation.
> PredictionIO was built on top of several Apache projects (HBase, Spark,
> Hadoop). We are familiar with the Apache process and believe that the
> democratic and meritocratic nature of the foundation aligns with the
> project goals.
> 
> Initial Goals
> 
> The initial milestones will be to move the existing codebase to Apache and
> integrate with the Apache development process. Once this is accomplished,
> we plan for incremental development and releases that follow the Apache
> guidelines, as well as growing our developer and user communities.
> 
> Current Status
> 
> PredictionIO has undergone nine minor releases and many patches.
> PredictionIO is being used in production by Salesforce.com as well as many
> other organizations and apps. The PredictionIO codebase is currently
> hosted at GitHub, which will form the basis of the Apache git repository.
> 
> Meritocracy
> 
> We plan to invest in supporting a meritocracy. We will discuss the
> requirements in an open forum. We intend to invite additional developers
> to participate. We will encourage and monitor community participation so
> that privileges can be extended to those that contribute.
> 
> Community
> 
> Acceptance into the Apache foundation would bolster the already strong
> user and developer community around PredictionIO. That community includes
> many contributors from various other companies, and an active mailing list
> composed of hundreds of users.
> 
> Core Developers
> 
> The core developers of our project are listed in our contributors and
> initial PPMC below. Though many are employed at Salesforce.com, there are
> also engineers from ActionML, and independent developers.
> 
> Alignment
> 
> The ASF is the natural choice to host the PredictionIO project as its goal
> is democratizing Machine Learning by making it more easily accessible to
> every user/developer. PredictionIO is built on top of several top level
> Apache projects as outlined above.
> 
> Known Risks
> 
> Orphaned Products
> 
> PredictionIO has a solid and growing community. It is 

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Drew Farris]

+1 (binding)

On Tue, May 24, 2016, 5:27 PM Andrew Purtell  wrote:

> +1 (binding)
>
>
> On Mon, May 23, 2016 at 10:56 PM, Daniel Gruno 
> wrote:
>
> > Since it seems the discussion has died down, I am now calling a vote on
> > accepting Pony Mail into the Incubator. Sorry in advance for potato.
> >
> > This vote will run for the usual 72 hours.
> >
> > ### PROPOSAL BELOW ###
> >
> > Abstract
> >
> > Pony Mail is a mail-archiving, archive viewing, and interaction service,
> > that can be integrated with many email platforms.
> >
> > Proposal
> >
> > Background
> >
> > Pony Mail began as a response to two things; the lack of diversity in
> > mailing list archives that are less bureaucratic all-or-nothing and more
> > fluid way to interact with mailing lists than what is typically offered,
> > and the lack of a performant system that solves this issue. Modern users
> > of software want to jump right into a discussion they see, but cannot
> > normally do so in a mailing list driven environment because of the rules
> > generally surrounding said environment. Pony Mail, along with a select
> > handful of newer archive systems, provides an interface that allows
> > people to just hop into a thread, and take part. Without the need to
> > subscribe, download the mbox archive, load it into your MTA, and respond.
> >
> > As Rich writes in a very short essay:
> >
> > You see a thread in which someone is WRONG ON THE INTERNET! You need to
> > correct them. How do you do this today? You kinda don't. If you really
> > wanted, you could download mbox files (and who the hell knows where they
> > are?) and then try to get them into your mail client (which never works)
> > and then reply to it. Which will break threading, because you did
> > something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> > (sound of hoof beats)
> >
> > Rationale
> >
> > One of the oft-heard complaints about Apache's development model is that
> > mailing lists are an old person's tool, and web-based communication -
> > forums - are the way to go in the 21st Century. Providing a
> > full-featured forum-like interface to mailing lists is one goal,while
> > keeping all of the enormous benefits that mailing lists already provide.
> > Asecond goal is to provide the ability to "jump in" to a mailing list
> > conversation - even one that was a while back, without the convolutions
> > that a mailing list requires. That is, to join this conversation the old
> > way, one would have had to subscribe to the mailing list, download an
> > mbox, and import it into ones mail client, in order that I be able to
> > reply to this message with correct threading. With Pony Mail, one has to
> > do none of those things, but can simply reply using the Web UI. To us,
> > this is a HUGE benefit for building community. The requirement to jump
> > through hoops to join a mailing list conversation drives away a lot of
> > people (at least, anecdotally, it does) and if we can remove that
> > barrier I think we'll have an easier time of drawing a new generation
> > into our projects.
> >
> > Initial Goals
> >
> > The initial goals of transitioning to the ASF is to expand and grow both
> > the Pony codebase and community, and ensure the project's continued
> > growth and stability through forming a diverse and reliable community,
> > in which the various facets of developers and contributors help keep the
> > project up to date with latest developments and technical as well as
> > social needs.
> >
> > Current Status
> >
> > Meritocracy:
> >
> > The bulk of the code has been written by Daniel Gruno to date, but has
> > had oversight from other committers, and mentors.
> >
> > All members of the Pony project and wider community have a deep
> > understanding and appreciation for the ASF meritocracy ideals, and are
> > almost solely current ASF Members.
> >
> > Community:
> > The community is currently heavily focused within the ASF, and
> > more specifically the Infrastructure group. This is to be expected given
> > the nature of how the code came into existence in the first place. It
> > should be noted that we have started reaching out to other groups who we
> > know are using mailing list systems and therefore also rely on mailing
> > list archive interfaces.
> >
> > Core Developers:
> >
> > Almost all core developers are ASF members, and are already intimately
> > familiar with the Apache Way.
> >
> > Alignment:
> >
> > Pony will be very in line with ASF practices and processes as many of
> > the founding members are long term ASF members and committers.
> >
> > Known Risks
> >
> > Orphaned products:
> >
> > We are not aware of any issues with orphaned products related to this
> > project.
> >
> > Pony Mail relies on a set of CSS3 templates as well as some very
> stable
> > programming languages. We have no reason to believe these would
> > be orphaned or, should they become orphaned, 

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Christopher]

+1 (non-binding)

On Tue, May 24, 2016 at 7:41 PM Drew Farris  wrote:

> +1 (binding)
>
> On Tue, May 24, 2016, 5:27 PM Andrew Purtell  wrote:
>
> > +1 (binding)
> >
> >
> > On Mon, May 23, 2016 at 10:56 PM, Daniel Gruno 
> > wrote:
> >
> > > Since it seems the discussion has died down, I am now calling a vote on
> > > accepting Pony Mail into the Incubator. Sorry in advance for potato.
> > >
> > > This vote will run for the usual 72 hours.
> > >
> > > ### PROPOSAL BELOW ###
> > >
> > > Abstract
> > >
> > > Pony Mail is a mail-archiving, archive viewing, and interaction
> service,
> > > that can be integrated with many email platforms.
> > >
> > > Proposal
> > >
> > > Background
> > >
> > > Pony Mail began as a response to two things; the lack of diversity in
> > > mailing list archives that are less bureaucratic all-or-nothing and
> more
> > > fluid way to interact with mailing lists than what is typically
> offered,
> > > and the lack of a performant system that solves this issue. Modern
> users
> > > of software want to jump right into a discussion they see, but cannot
> > > normally do so in a mailing list driven environment because of the
> rules
> > > generally surrounding said environment. Pony Mail, along with a select
> > > handful of newer archive systems, provides an interface that allows
> > > people to just hop into a thread, and take part. Without the need to
> > > subscribe, download the mbox archive, load it into your MTA, and
> respond.
> > >
> > > As Rich writes in a very short essay:
> > >
> > > You see a thread in which someone is WRONG ON THE INTERNET! You need to
> > > correct them. How do you do this today? You kinda don't. If you really
> > > wanted, you could download mbox files (and who the hell knows where
> they
> > > are?) and then try to get them into your mail client (which never
> works)
> > > and then reply to it. Which will break threading, because you did
> > > something wrong. Then you tear out your hair. PONY MAIL TO THE
> RESCUE!!!
> > > (sound of hoof beats)
> > >
> > > Rationale
> > >
> > > One of the oft-heard complaints about Apache's development model is
> that
> > > mailing lists are an old person's tool, and web-based communication -
> > > forums - are the way to go in the 21st Century. Providing a
> > > full-featured forum-like interface to mailing lists is one goal,while
> > > keeping all of the enormous benefits that mailing lists already
> provide.
> > > Asecond goal is to provide the ability to "jump in" to a mailing list
> > > conversation - even one that was a while back, without the convolutions
> > > that a mailing list requires. That is, to join this conversation the
> old
> > > way, one would have had to subscribe to the mailing list, download an
> > > mbox, and import it into ones mail client, in order that I be able to
> > > reply to this message with correct threading. With Pony Mail, one has
> to
> > > do none of those things, but can simply reply using the Web UI. To us,
> > > this is a HUGE benefit for building community. The requirement to jump
> > > through hoops to join a mailing list conversation drives away a lot of
> > > people (at least, anecdotally, it does) and if we can remove that
> > > barrier I think we'll have an easier time of drawing a new generation
> > > into our projects.
> > >
> > > Initial Goals
> > >
> > > The initial goals of transitioning to the ASF is to expand and grow
> both
> > > the Pony codebase and community, and ensure the project's continued
> > > growth and stability through forming a diverse and reliable community,
> > > in which the various facets of developers and contributors help keep
> the
> > > project up to date with latest developments and technical as well as
> > > social needs.
> > >
> > > Current Status
> > >
> > > Meritocracy:
> > >
> > > The bulk of the code has been written by Daniel Gruno to date, but has
> > > had oversight from other committers, and mentors.
> > >
> > > All members of the Pony project and wider community have a deep
> > > understanding and appreciation for the ASF meritocracy ideals, and are
> > > almost solely current ASF Members.
> > >
> > > Community:
> > > The community is currently heavily focused within the ASF, and
> > > more specifically the Infrastructure group. This is to be expected
> given
> > > the nature of how the code came into existence in the first place. It
> > > should be noted that we have started reaching out to other groups who
> we
> > > know are using mailing list systems and therefore also rely on mailing
> > > list archive interfaces.
> > >
> > > Core Developers:
> > >
> > > Almost all core developers are ASF members, and are already intimately
> > > familiar with the Apache Way.
> > >
> > > Alignment:
> > >
> > > Pony will be very in line with ASF practices and processes as many of
> > > the founding members are long term ASF members and committers.
> > >
> > > Known Risks
> > >
> > > Or

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On May 24, 2016, at 1:56 AM, Daniel Gruno  wrote:
> 
> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
> 
> This vote will run for the usual 72 hours.
> 
> ### PROPOSAL BELOW ###
> 
> Abstract
> 
> Pony Mail is a mail-archiving, archive viewing, and interaction service,
> that can be integrated with many email platforms.
> 
> Proposal
> 
> Background
> 
> Pony Mail began as a response to two things; the lack of diversity in
> mailing list archives that are less bureaucratic all-or-nothing and more
> fluid way to interact with mailing lists than what is typically offered,
> and the lack of a performant system that solves this issue. Modern users
> of software want to jump right into a discussion they see, but cannot
> normally do so in a mailing list driven environment because of the rules
> generally surrounding said environment. Pony Mail, along with a select
> handful of newer archive systems, provides an interface that allows
> people to just hop into a thread, and take part. Without the need to
> subscribe, download the mbox archive, load it into your MTA, and respond.
> 
> As Rich writes in a very short essay:
> 
> You see a thread in which someone is WRONG ON THE INTERNET! You need to
> correct them. How do you do this today? You kinda don't. If you really
> wanted, you could download mbox files (and who the hell knows where they
> are?) and then try to get them into your mail client (which never works)
> and then reply to it. Which will break threading, because you did
> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> (sound of hoof beats)
> 
> Rationale
> 
> One of the oft-heard complaints about Apache's development model is that
> mailing lists are an old person's tool, and web-based communication -
> forums - are the way to go in the 21st Century. Providing a
> full-featured forum-like interface to mailing lists is one goal,while
> keeping all of the enormous benefits that mailing lists already provide.
> Asecond goal is to provide the ability to "jump in" to a mailing list
> conversation - even one that was a while back, without the convolutions
> that a mailing list requires. That is, to join this conversation the old
> way, one would have had to subscribe to the mailing list, download an
> mbox, and import it into ones mail client, in order that I be able to
> reply to this message with correct threading. With Pony Mail, one has to
> do none of those things, but can simply reply using the Web UI. To us,
> this is a HUGE benefit for building community. The requirement to jump
> through hoops to join a mailing list conversation drives away a lot of
> people (at least, anecdotally, it does) and if we can remove that
> barrier I think we'll have an easier time of drawing a new generation
> into our projects.
> 
> Initial Goals
> 
> The initial goals of transitioning to the ASF is to expand and grow both
> the Pony codebase and community, and ensure the project's continued
> growth and stability through forming a diverse and reliable community,
> in which the various facets of developers and contributors help keep the
> project up to date with latest developments and technical as well as
> social needs.
> 
> Current Status
> 
>Meritocracy:
> 
> The bulk of the code has been written by Daniel Gruno to date, but has
> had oversight from other committers, and mentors.
> 
>All members of the Pony project and wider community have a deep
> understanding and appreciation for the ASF meritocracy ideals, and are
> almost solely current ASF Members.
> 
>Community:
>The community is currently heavily focused within the ASF, and
> more specifically the Infrastructure group. This is to be expected given
> the nature of how the code came into existence in the first place. It
> should be noted that we have started reaching out to other groups who we
> know are using mailing list systems and therefore also rely on mailing
> list archive interfaces.
> 
>Core Developers:
> 
> Almost all core developers are ASF members, and are already intimately
> familiar with the Apache Way.
> 
>Alignment:
> 
> Pony will be very in line with ASF practices and processes as many of
> the founding members are long term ASF members and committers.
> 
> Known Risks
> 
>Orphaned products:
> 
> We are not aware of any issues with orphaned products related to this
> project.
> 
>Pony Mail relies on a set of CSS3 templates as well as some very stable
>programming languages. We have no reason to believe these would
> be orphaned or, should they become orphaned, that it would impact the
> development of the project.
> 
>Inexperience with Open Source:
>Most of the current committers are already ASF members and
> committers, we do not believe there to be any concerns around OSS
> inexperience.
> 
>Homogenous 

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Henry Saputra]

+1 (binding)

Have fun guys!

On Mon, May 23, 2016 at 10:56 PM, Daniel Gruno  wrote:

> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>
> This vote will run for the usual 72 hours.
>
> ### PROPOSAL BELOW ###
>
> Abstract
>
> Pony Mail is a mail-archiving, archive viewing, and interaction service,
> that can be integrated with many email platforms.
>
> Proposal
>
> Background
>
> Pony Mail began as a response to two things; the lack of diversity in
> mailing list archives that are less bureaucratic all-or-nothing and more
> fluid way to interact with mailing lists than what is typically offered,
> and the lack of a performant system that solves this issue. Modern users
> of software want to jump right into a discussion they see, but cannot
> normally do so in a mailing list driven environment because of the rules
> generally surrounding said environment. Pony Mail, along with a select
> handful of newer archive systems, provides an interface that allows
> people to just hop into a thread, and take part. Without the need to
> subscribe, download the mbox archive, load it into your MTA, and respond.
>
> As Rich writes in a very short essay:
>
> You see a thread in which someone is WRONG ON THE INTERNET! You need to
> correct them. How do you do this today? You kinda don't. If you really
> wanted, you could download mbox files (and who the hell knows where they
> are?) and then try to get them into your mail client (which never works)
> and then reply to it. Which will break threading, because you did
> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> (sound of hoof beats)
>
> Rationale
>
> One of the oft-heard complaints about Apache's development model is that
> mailing lists are an old person's tool, and web-based communication -
> forums - are the way to go in the 21st Century. Providing a
> full-featured forum-like interface to mailing lists is one goal,while
> keeping all of the enormous benefits that mailing lists already provide.
> Asecond goal is to provide the ability to "jump in" to a mailing list
> conversation - even one that was a while back, without the convolutions
> that a mailing list requires. That is, to join this conversation the old
> way, one would have had to subscribe to the mailing list, download an
> mbox, and import it into ones mail client, in order that I be able to
> reply to this message with correct threading. With Pony Mail, one has to
> do none of those things, but can simply reply using the Web UI. To us,
> this is a HUGE benefit for building community. The requirement to jump
> through hoops to join a mailing list conversation drives away a lot of
> people (at least, anecdotally, it does) and if we can remove that
> barrier I think we'll have an easier time of drawing a new generation
> into our projects.
>
> Initial Goals
>
> The initial goals of transitioning to the ASF is to expand and grow both
> the Pony codebase and community, and ensure the project's continued
> growth and stability through forming a diverse and reliable community,
> in which the various facets of developers and contributors help keep the
> project up to date with latest developments and technical as well as
> social needs.
>
> Current Status
>
> Meritocracy:
>
> The bulk of the code has been written by Daniel Gruno to date, but has
> had oversight from other committers, and mentors.
>
> All members of the Pony project and wider community have a deep
> understanding and appreciation for the ASF meritocracy ideals, and are
> almost solely current ASF Members.
>
> Community:
> The community is currently heavily focused within the ASF, and
> more specifically the Infrastructure group. This is to be expected given
> the nature of how the code came into existence in the first place. It
> should be noted that we have started reaching out to other groups who we
> know are using mailing list systems and therefore also rely on mailing
> list archive interfaces.
>
> Core Developers:
>
> Almost all core developers are ASF members, and are already intimately
> familiar with the Apache Way.
>
> Alignment:
>
> Pony will be very in line with ASF practices and processes as many of
> the founding members are long term ASF members and committers.
>
> Known Risks
>
> Orphaned products:
>
> We are not aware of any issues with orphaned products related to this
> project.
>
> Pony Mail relies on a set of CSS3 templates as well as some very stable
> programming languages. We have no reason to believe these would
> be orphaned or, should they become orphaned, that it would impact the
> development of the project.
>
> Inexperience with Open Source:
> Most of the current committers are already ASF members and
> committers, we do not believe there to be any concerns around OSS
> inexperience.
>
> Homogenous Develope

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Mattmann, Chris A (3980)]

+1 binding

++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: chris.a.mattm...@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++
Director, Information Retrieval and Data Science Group (IRDS)
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
WWW: http://irds.usc.edu/
++










On 5/24/16, 5:03 PM, "Henry Saputra"  wrote:

>+1 (binding)
>
>Have fun guys!
>
>On Mon, May 23, 2016 at 10:56 PM, Daniel Gruno  wrote:
>
>> Since it seems the discussion has died down, I am now calling a vote on
>> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>>
>> This vote will run for the usual 72 hours.
>>
>> ### PROPOSAL BELOW ###
>>
>> Abstract
>>
>> Pony Mail is a mail-archiving, archive viewing, and interaction service,
>> that can be integrated with many email platforms.
>>
>> Proposal
>>
>> Background
>>
>> Pony Mail began as a response to two things; the lack of diversity in
>> mailing list archives that are less bureaucratic all-or-nothing and more
>> fluid way to interact with mailing lists than what is typically offered,
>> and the lack of a performant system that solves this issue. Modern users
>> of software want to jump right into a discussion they see, but cannot
>> normally do so in a mailing list driven environment because of the rules
>> generally surrounding said environment. Pony Mail, along with a select
>> handful of newer archive systems, provides an interface that allows
>> people to just hop into a thread, and take part. Without the need to
>> subscribe, download the mbox archive, load it into your MTA, and respond.
>>
>> As Rich writes in a very short essay:
>>
>> You see a thread in which someone is WRONG ON THE INTERNET! You need to
>> correct them. How do you do this today? You kinda don't. If you really
>> wanted, you could download mbox files (and who the hell knows where they
>> are?) and then try to get them into your mail client (which never works)
>> and then reply to it. Which will break threading, because you did
>> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
>> (sound of hoof beats)
>>
>> Rationale
>>
>> One of the oft-heard complaints about Apache's development model is that
>> mailing lists are an old person's tool, and web-based communication -
>> forums - are the way to go in the 21st Century. Providing a
>> full-featured forum-like interface to mailing lists is one goal,while
>> keeping all of the enormous benefits that mailing lists already provide.
>> Asecond goal is to provide the ability to "jump in" to a mailing list
>> conversation - even one that was a while back, without the convolutions
>> that a mailing list requires. That is, to join this conversation the old
>> way, one would have had to subscribe to the mailing list, download an
>> mbox, and import it into ones mail client, in order that I be able to
>> reply to this message with correct threading. With Pony Mail, one has to
>> do none of those things, but can simply reply using the Web UI. To us,
>> this is a HUGE benefit for building community. The requirement to jump
>> through hoops to join a mailing list conversation drives away a lot of
>> people (at least, anecdotally, it does) and if we can remove that
>> barrier I think we'll have an easier time of drawing a new generation
>> into our projects.
>>
>> Initial Goals
>>
>> The initial goals of transitioning to the ASF is to expand and grow both
>> the Pony codebase and community, and ensure the project's continued
>> growth and stability through forming a diverse and reliable community,
>> in which the various facets of developers and contributors help keep the
>> project up to date with latest developments and technical as well as
>> social needs.
>>
>> Current Status
>>
>> Meritocracy:
>>
>> The bulk of the code has been written by Daniel Gruno to date, but has
>> had oversight from other committers, and mentors.
>>
>> All members of the Pony project and wider community have a deep
>> understanding and appreciation for the ASF meritocracy ideals, and are
>> almost solely current ASF Members.
>>
>> Community:
>> The community is currently heavily focused within the ASF, and
>> more specifically the Infrastructure group. This is to be expected given
>> the nature of how the code came into existence in the first place. It
>> should be noted that we have started reaching out to other groups who we
>> know are using mailing list systems and therefore also rely on mailing
>> list archive interfaces.
>>
>> Core Developers:
>>
>> Almost all core developers are ASF me

Re: Help with new ARIA TOSCA proposal

[John D. Ament]

Hi,

If you're still looking for help, I'd be happy to step up.

John

On Tue, May 24, 2016 at 8:34 AM Sebastien Goasguen  wrote:

> Hi folks,
>
> I am an ASF member but I have not been involved with the incubator much.
>
> The last few weeks I have been chatting with folks at Gigaspaces [1]. Some
> of you may know them as the ones behind Cloudify [2] a cloud orchestration
> platform.
>
> The folks at Gigaspaces are interested to donate the orchestration engine
> behind Cloudify to ASF. With the motivation to open the governance of the
> core of Cloudify.
>
> They have already started laying a foundation for an incubator project,
> putting most of the software under a separate organization called ARIA [3]
> with software currently in gitHub [4].
>
> I would like to introduce Arthur Berezin from Gigaspaces who is working on
> putting together a proposal to the incubator. He got an account on the Wiki
> but no karma to add a page yet it seems.
>
> The proposal would need a champion, I don’t feel I have the experience
> with the incubator to do this well, so while I will help, it would be great
> to get a Champion to help shepherd this properly. Any takers ?
>
> Cheers,
>
> [1] http://www.gigaspaces.com
> [2] http://getcloudify.org
> [3] http://ariatosca.org
> [4] https://github.com/aria-tosca
>
> -Sebastien
> cloudstack, libcloud PMC
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Roman Shaposhnik]

On Mon, May 23, 2016 at 10:56 PM, Daniel Gruno  wrote:
> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>
> This vote will run for the usual 72 hours.

An enthusiastic +1

Roman.

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

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Jake Farrell]

+1 (binding)

-Jake

On Tue, May 24, 2016 at 1:56 AM, Daniel Gruno  wrote:

> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>
> This vote will run for the usual 72 hours.
>
> ### PROPOSAL BELOW ###
>
> Abstract
>
> Pony Mail is a mail-archiving, archive viewing, and interaction service,
> that can be integrated with many email platforms.
>
> Proposal
>
> Background
>
> Pony Mail began as a response to two things; the lack of diversity in
> mailing list archives that are less bureaucratic all-or-nothing and more
> fluid way to interact with mailing lists than what is typically offered,
> and the lack of a performant system that solves this issue. Modern users
> of software want to jump right into a discussion they see, but cannot
> normally do so in a mailing list driven environment because of the rules
> generally surrounding said environment. Pony Mail, along with a select
> handful of newer archive systems, provides an interface that allows
> people to just hop into a thread, and take part. Without the need to
> subscribe, download the mbox archive, load it into your MTA, and respond.
>
> As Rich writes in a very short essay:
>
> You see a thread in which someone is WRONG ON THE INTERNET! You need to
> correct them. How do you do this today? You kinda don't. If you really
> wanted, you could download mbox files (and who the hell knows where they
> are?) and then try to get them into your mail client (which never works)
> and then reply to it. Which will break threading, because you did
> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> (sound of hoof beats)
>
> Rationale
>
> One of the oft-heard complaints about Apache's development model is that
> mailing lists are an old person's tool, and web-based communication -
> forums - are the way to go in the 21st Century. Providing a
> full-featured forum-like interface to mailing lists is one goal,while
> keeping all of the enormous benefits that mailing lists already provide.
> Asecond goal is to provide the ability to "jump in" to a mailing list
> conversation - even one that was a while back, without the convolutions
> that a mailing list requires. That is, to join this conversation the old
> way, one would have had to subscribe to the mailing list, download an
> mbox, and import it into ones mail client, in order that I be able to
> reply to this message with correct threading. With Pony Mail, one has to
> do none of those things, but can simply reply using the Web UI. To us,
> this is a HUGE benefit for building community. The requirement to jump
> through hoops to join a mailing list conversation drives away a lot of
> people (at least, anecdotally, it does) and if we can remove that
> barrier I think we'll have an easier time of drawing a new generation
> into our projects.
>
> Initial Goals
>
> The initial goals of transitioning to the ASF is to expand and grow both
> the Pony codebase and community, and ensure the project's continued
> growth and stability through forming a diverse and reliable community,
> in which the various facets of developers and contributors help keep the
> project up to date with latest developments and technical as well as
> social needs.
>
> Current Status
>
> Meritocracy:
>
> The bulk of the code has been written by Daniel Gruno to date, but has
> had oversight from other committers, and mentors.
>
> All members of the Pony project and wider community have a deep
> understanding and appreciation for the ASF meritocracy ideals, and are
> almost solely current ASF Members.
>
> Community:
> The community is currently heavily focused within the ASF, and
> more specifically the Infrastructure group. This is to be expected given
> the nature of how the code came into existence in the first place. It
> should be noted that we have started reaching out to other groups who we
> know are using mailing list systems and therefore also rely on mailing
> list archive interfaces.
>
> Core Developers:
>
> Almost all core developers are ASF members, and are already intimately
> familiar with the Apache Way.
>
> Alignment:
>
> Pony will be very in line with ASF practices and processes as many of
> the founding members are long term ASF members and committers.
>
> Known Risks
>
> Orphaned products:
>
> We are not aware of any issues with orphaned products related to this
> project.
>
> Pony Mail relies on a set of CSS3 templates as well as some very stable
> programming languages. We have no reason to believe these would
> be orphaned or, should they become orphaned, that it would impact the
> development of the project.
>
> Inexperience with Open Source:
> Most of the current committers are already ASF members and
> committers, we do not believe there to be any concerns around OSS
> inexperience.
>
> Homogenous Developers:
> 

Re: [VOTE] Accept PredictionIO into the Apache Incubator

[Jake Farrell]

+1

-Jake

On Mon, May 23, 2016 at 6:22 PM, Andrew Purtell  wrote:

> Since discussion on the matter of PredictionIO has died down, I would like
> to call a VOTE
> on accepting PredictionIO into the Apache Incubator.
>
> Proposal: https://wiki.apache.org/incubator/PredictionIO
>
> ​[ ] +1 Accept PredictionIO into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept PredictionIO into the Apache Incubator, because ...
>
> This vote will be open for at least 72 hours.
>
> My vote is +1 (binding)
>
> --
>
> PredictionIO Proposal
>
> Abstract
>
> PredictionIO is an open source Machine Learning Server built on top of
> state-of-the-art open source stack, that enables developers to manage and
> deploy production-ready predictive services for various kinds of machine
> learning tasks.
>
> Proposal
>
> The PredictionIO platform consists of the following components:
>
>* PredictionIO framework - provides the machine learning stack for
>  building, evaluating and deploying engines with machine learning
>  algorithms. It uses Apache Spark for processing.
>
>* Event Server - the machine learning analytics layer for unifying
> events
>  from multiple platforms. It can use Apache HBase or any JDBC backends
>  as its data store.
>
> The PredictionIO community also maintains a Template Gallery, a place to
> publish and download (free or proprietary) engine templates for different
> types of machine learning applications, and is a complemental part of the
> project. At this point we exclude the Template Gallery from the proposal,
> as it has a separate set of contributors and we’re not familiar with an
> Apache approved mechanism to maintain such a gallery.
>
> Background
>
> PredictionIO was started with a mission to democratize and bring machine
> learning to the masses.
>
> Machine learning has traditionally been a luxury for big companies like
> Google, Facebook, and Netflix. There are ML libraries and tools lying
> around the internet but the effort of putting them all together as a
> production-ready infrastructure is a very resource-intensive task that is
> remotely reachable by individuals or small businesses.
>
> PredictionIO is a production-ready, full stack machine learning system that
> allows organizations of any scale to quickly deploy machine learning
> capabilities. It comes with official and community-contributed machine
> learning engine templates that are easy to customize.
>
> Rationale
>
> As usage and number of contributors to PredictionIO has grown bigger and
> more diverse, we have sought for an independent framework for the project
> to keep thriving. We believe the Apache foundation is a great fit. Joining
> Apache would ensure that tried and true processes and procedures are in
> place for the growing number of organizations interested in contributing
> to PredictionIO. PredictionIO is also a good fit for the Apache foundation.
> PredictionIO was built on top of several Apache projects (HBase, Spark,
> Hadoop). We are familiar with the Apache process and believe that the
> democratic and meritocratic nature of the foundation aligns with the
> project goals.
>
> Initial Goals
>
> The initial milestones will be to move the existing codebase to Apache and
> integrate with the Apache development process. Once this is accomplished,
> we plan for incremental development and releases that follow the Apache
> guidelines, as well as growing our developer and user communities.
>
> Current Status
>
> PredictionIO has undergone nine minor releases and many patches.
> PredictionIO is being used in production by Salesforce.com as well as many
> other organizations and apps. The PredictionIO codebase is currently
> hosted at GitHub, which will form the basis of the Apache git repository.
>
> Meritocracy
>
> We plan to invest in supporting a meritocracy. We will discuss the
> requirements in an open forum. We intend to invite additional developers
> to participate. We will encourage and monitor community participation so
> that privileges can be extended to those that contribute.
>
> Community
>
> Acceptance into the Apache foundation would bolster the already strong
> user and developer community around PredictionIO. That community includes
> many contributors from various other companies, and an active mailing list
> composed of hundreds of users.
>
> Core Developers
>
> The core developers of our project are listed in our contributors and
> initial PPMC below. Though many are employed at Salesforce.com, there are
> also engineers from ActionML, and independent developers.
>
> Alignment
>
> The ASF is the natural choice to host the PredictionIO project as its goal
> is democratizing Machine Learning by making it more easily accessible to
> every user/developer. PredictionIO is built on top of several top level
> Apache projects as outlined above.
>
> Known Risks
>
> Orphaned Products
>
> PredictionIO has a solid and growing community. It is deployed on
> production environments b

Re: [VOTE] Accept PredictionIO into the Apache Incubator

[Reynold Xin]

+1 (binding)


On Mon, May 23, 2016 at 3:22 PM, Andrew Purtell  wrote:

> Since discussion on the matter of PredictionIO has died down, I would like
> to call a VOTE
> on accepting PredictionIO into the Apache Incubator.
>
> Proposal: https://wiki.apache.org/incubator/PredictionIO
>
> ​[ ] +1 Accept PredictionIO into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept PredictionIO into the Apache Incubator, because ...
>
> This vote will be open for at least 72 hours.
>
> My vote is +1 (binding)
>
> --
>
> PredictionIO Proposal
>
> Abstract
>
> PredictionIO is an open source Machine Learning Server built on top of
> state-of-the-art open source stack, that enables developers to manage and
> deploy production-ready predictive services for various kinds of machine
> learning tasks.
>
> Proposal
>
> The PredictionIO platform consists of the following components:
>
>* PredictionIO framework - provides the machine learning stack for
>  building, evaluating and deploying engines with machine learning
>  algorithms. It uses Apache Spark for processing.
>
>* Event Server - the machine learning analytics layer for unifying
> events
>  from multiple platforms. It can use Apache HBase or any JDBC backends
>  as its data store.
>
> The PredictionIO community also maintains a Template Gallery, a place to
> publish and download (free or proprietary) engine templates for different
> types of machine learning applications, and is a complemental part of the
> project. At this point we exclude the Template Gallery from the proposal,
> as it has a separate set of contributors and we’re not familiar with an
> Apache approved mechanism to maintain such a gallery.
>
> Background
>
> PredictionIO was started with a mission to democratize and bring machine
> learning to the masses.
>
> Machine learning has traditionally been a luxury for big companies like
> Google, Facebook, and Netflix. There are ML libraries and tools lying
> around the internet but the effort of putting them all together as a
> production-ready infrastructure is a very resource-intensive task that is
> remotely reachable by individuals or small businesses.
>
> PredictionIO is a production-ready, full stack machine learning system that
> allows organizations of any scale to quickly deploy machine learning
> capabilities. It comes with official and community-contributed machine
> learning engine templates that are easy to customize.
>
> Rationale
>
> As usage and number of contributors to PredictionIO has grown bigger and
> more diverse, we have sought for an independent framework for the project
> to keep thriving. We believe the Apache foundation is a great fit. Joining
> Apache would ensure that tried and true processes and procedures are in
> place for the growing number of organizations interested in contributing
> to PredictionIO. PredictionIO is also a good fit for the Apache foundation.
> PredictionIO was built on top of several Apache projects (HBase, Spark,
> Hadoop). We are familiar with the Apache process and believe that the
> democratic and meritocratic nature of the foundation aligns with the
> project goals.
>
> Initial Goals
>
> The initial milestones will be to move the existing codebase to Apache and
> integrate with the Apache development process. Once this is accomplished,
> we plan for incremental development and releases that follow the Apache
> guidelines, as well as growing our developer and user communities.
>
> Current Status
>
> PredictionIO has undergone nine minor releases and many patches.
> PredictionIO is being used in production by Salesforce.com as well as many
> other organizations and apps. The PredictionIO codebase is currently
> hosted at GitHub, which will form the basis of the Apache git repository.
>
> Meritocracy
>
> We plan to invest in supporting a meritocracy. We will discuss the
> requirements in an open forum. We intend to invite additional developers
> to participate. We will encourage and monitor community participation so
> that privileges can be extended to those that contribute.
>
> Community
>
> Acceptance into the Apache foundation would bolster the already strong
> user and developer community around PredictionIO. That community includes
> many contributors from various other companies, and an active mailing list
> composed of hundreds of users.
>
> Core Developers
>
> The core developers of our project are listed in our contributors and
> initial PPMC below. Though many are employed at Salesforce.com, there are
> also engineers from ActionML, and independent developers.
>
> Alignment
>
> The ASF is the natural choice to host the PredictionIO project as its goal
> is democratizing Machine Learning by making it more easily accessible to
> every user/developer. PredictionIO is built on top of several top level
> Apache projects as outlined above.
>
> Known Risks
>
> Orphaned Products
>
> PredictionIO has a solid and growing community. It is deployed on
> production environmen

Re: [VOTE] Accept PredictionIO into the Apache Incubator

[Tsuyoshi Ozawa]

+1 (non-binding)
- Tsuyoshi

On Wed, May 25, 2016 at 1:00 PM, Reynold Xin  wrote:
> +1 (binding)
>
>
> On Mon, May 23, 2016 at 3:22 PM, Andrew Purtell  wrote:
>
>> Since discussion on the matter of PredictionIO has died down, I would like
>> to call a VOTE
>> on accepting PredictionIO into the Apache Incubator.
>>
>> Proposal: https://wiki.apache.org/incubator/PredictionIO
>>
>> [ ] +1 Accept PredictionIO into the Apache Incubator
>> [ ] +0 Abstain
>> [ ] -1 Do not accept PredictionIO into the Apache Incubator, because ...
>>
>> This vote will be open for at least 72 hours.
>>
>> My vote is +1 (binding)
>>
>> --
>>
>> PredictionIO Proposal
>>
>> Abstract
>>
>> PredictionIO is an open source Machine Learning Server built on top of
>> state-of-the-art open source stack, that enables developers to manage and
>> deploy production-ready predictive services for various kinds of machine
>> learning tasks.
>>
>> Proposal
>>
>> The PredictionIO platform consists of the following components:
>>
>>* PredictionIO framework - provides the machine learning stack for
>>  building, evaluating and deploying engines with machine learning
>>  algorithms. It uses Apache Spark for processing.
>>
>>* Event Server - the machine learning analytics layer for unifying
>> events
>>  from multiple platforms. It can use Apache HBase or any JDBC backends
>>  as its data store.
>>
>> The PredictionIO community also maintains a Template Gallery, a place to
>> publish and download (free or proprietary) engine templates for different
>> types of machine learning applications, and is a complemental part of the
>> project. At this point we exclude the Template Gallery from the proposal,
>> as it has a separate set of contributors and we’re not familiar with an
>> Apache approved mechanism to maintain such a gallery.
>>
>> Background
>>
>> PredictionIO was started with a mission to democratize and bring machine
>> learning to the masses.
>>
>> Machine learning has traditionally been a luxury for big companies like
>> Google, Facebook, and Netflix. There are ML libraries and tools lying
>> around the internet but the effort of putting them all together as a
>> production-ready infrastructure is a very resource-intensive task that is
>> remotely reachable by individuals or small businesses.
>>
>> PredictionIO is a production-ready, full stack machine learning system that
>> allows organizations of any scale to quickly deploy machine learning
>> capabilities. It comes with official and community-contributed machine
>> learning engine templates that are easy to customize.
>>
>> Rationale
>>
>> As usage and number of contributors to PredictionIO has grown bigger and
>> more diverse, we have sought for an independent framework for the project
>> to keep thriving. We believe the Apache foundation is a great fit. Joining
>> Apache would ensure that tried and true processes and procedures are in
>> place for the growing number of organizations interested in contributing
>> to PredictionIO. PredictionIO is also a good fit for the Apache foundation.
>> PredictionIO was built on top of several Apache projects (HBase, Spark,
>> Hadoop). We are familiar with the Apache process and believe that the
>> democratic and meritocratic nature of the foundation aligns with the
>> project goals.
>>
>> Initial Goals
>>
>> The initial milestones will be to move the existing codebase to Apache and
>> integrate with the Apache development process. Once this is accomplished,
>> we plan for incremental development and releases that follow the Apache
>> guidelines, as well as growing our developer and user communities.
>>
>> Current Status
>>
>> PredictionIO has undergone nine minor releases and many patches.
>> PredictionIO is being used in production by Salesforce.com as well as many
>> other organizations and apps. The PredictionIO codebase is currently
>> hosted at GitHub, which will form the basis of the Apache git repository.
>>
>> Meritocracy
>>
>> We plan to invest in supporting a meritocracy. We will discuss the
>> requirements in an open forum. We intend to invite additional developers
>> to participate. We will encourage and monitor community participation so
>> that privileges can be extended to those that contribute.
>>
>> Community
>>
>> Acceptance into the Apache foundation would bolster the already strong
>> user and developer community around PredictionIO. That community includes
>> many contributors from various other companies, and an active mailing list
>> composed of hundreds of users.
>>
>> Core Developers
>>
>> The core developers of our project are listed in our contributors and
>> initial PPMC below. Though many are employed at Salesforce.com, there are
>> also engineers from ActionML, and independent developers.
>>
>> Alignment
>>
>> The ASF is the natural choice to host the PredictionIO project as its goal
>> is democratizing Machine Learning by making it more easily accessible to
>> every user/developer. PredictionIO is b

Re: [VOTE] Accept PredictionIO into the Apache Incubator

[Paul Fremantle]

+1 (binding)
Paul

On Wed, May 25, 2016 at 5:12 AM, Tsuyoshi Ozawa  wrote:

> +1 (non-binding)
> - Tsuyoshi
>
> On Wed, May 25, 2016 at 1:00 PM, Reynold Xin  wrote:
> > +1 (binding)
> >
> >
> > On Mon, May 23, 2016 at 3:22 PM, Andrew Purtell 
> wrote:
> >
> >> Since discussion on the matter of PredictionIO has died down, I would
> like
> >> to call a VOTE
> >> on accepting PredictionIO into the Apache Incubator.
> >>
> >> Proposal: https://wiki.apache.org/incubator/PredictionIO
> >>
> >> [ ] +1 Accept PredictionIO into the Apache Incubator
> >> [ ] +0 Abstain
> >> [ ] -1 Do not accept PredictionIO into the Apache Incubator, because ...
> >>
> >> This vote will be open for at least 72 hours.
> >>
> >> My vote is +1 (binding)
> >>
> >> --
> >>
> >> PredictionIO Proposal
> >>
> >> Abstract
> >>
> >> PredictionIO is an open source Machine Learning Server built on top of
> >> state-of-the-art open source stack, that enables developers to manage
> and
> >> deploy production-ready predictive services for various kinds of machine
> >> learning tasks.
> >>
> >> Proposal
> >>
> >> The PredictionIO platform consists of the following components:
> >>
> >>* PredictionIO framework - provides the machine learning stack for
> >>  building, evaluating and deploying engines with machine learning
> >>  algorithms. It uses Apache Spark for processing.
> >>
> >>* Event Server - the machine learning analytics layer for unifying
> >> events
> >>  from multiple platforms. It can use Apache HBase or any JDBC
> backends
> >>  as its data store.
> >>
> >> The PredictionIO community also maintains a Template Gallery, a place to
> >> publish and download (free or proprietary) engine templates for
> different
> >> types of machine learning applications, and is a complemental part of
> the
> >> project. At this point we exclude the Template Gallery from the
> proposal,
> >> as it has a separate set of contributors and we’re not familiar with an
> >> Apache approved mechanism to maintain such a gallery.
> >>
> >> Background
> >>
> >> PredictionIO was started with a mission to democratize and bring machine
> >> learning to the masses.
> >>
> >> Machine learning has traditionally been a luxury for big companies like
> >> Google, Facebook, and Netflix. There are ML libraries and tools lying
> >> around the internet but the effort of putting them all together as a
> >> production-ready infrastructure is a very resource-intensive task that
> is
> >> remotely reachable by individuals or small businesses.
> >>
> >> PredictionIO is a production-ready, full stack machine learning system
> that
> >> allows organizations of any scale to quickly deploy machine learning
> >> capabilities. It comes with official and community-contributed machine
> >> learning engine templates that are easy to customize.
> >>
> >> Rationale
> >>
> >> As usage and number of contributors to PredictionIO has grown bigger and
> >> more diverse, we have sought for an independent framework for the
> project
> >> to keep thriving. We believe the Apache foundation is a great fit.
> Joining
> >> Apache would ensure that tried and true processes and procedures are in
> >> place for the growing number of organizations interested in contributing
> >> to PredictionIO. PredictionIO is also a good fit for the Apache
> foundation.
> >> PredictionIO was built on top of several Apache projects (HBase, Spark,
> >> Hadoop). We are familiar with the Apache process and believe that the
> >> democratic and meritocratic nature of the foundation aligns with the
> >> project goals.
> >>
> >> Initial Goals
> >>
> >> The initial milestones will be to move the existing codebase to Apache
> and
> >> integrate with the Apache development process. Once this is
> accomplished,
> >> we plan for incremental development and releases that follow the Apache
> >> guidelines, as well as growing our developer and user communities.
> >>
> >> Current Status
> >>
> >> PredictionIO has undergone nine minor releases and many patches.
> >> PredictionIO is being used in production by Salesforce.com as well as
> many
> >> other organizations and apps. The PredictionIO codebase is currently
> >> hosted at GitHub, which will form the basis of the Apache git
> repository.
> >>
> >> Meritocracy
> >>
> >> We plan to invest in supporting a meritocracy. We will discuss the
> >> requirements in an open forum. We intend to invite additional developers
> >> to participate. We will encourage and monitor community participation so
> >> that privileges can be extended to those that contribute.
> >>
> >> Community
> >>
> >> Acceptance into the Apache foundation would bolster the already strong
> >> user and developer community around PredictionIO. That community
> includes
> >> many contributors from various other companies, and an active mailing
> list
> >> composed of hundreds of users.
> >>
> >> Core Developers
> >>
> >> The core developers of our project are listed in our contributors and
> >> initial P

Re: Help with new ARIA TOSCA proposal

[Jakob Homan]

This is an area I'm focusing on right now.  I can sign up to mentor,
if that would be useful.

-Jakob


On 24 May 2016 at 17:57, John D. Ament  wrote:
> Hi,
>
> If you're still looking for help, I'd be happy to step up.
>
> John
>
> On Tue, May 24, 2016 at 8:34 AM Sebastien Goasguen  wrote:
>
>> Hi folks,
>>
>> I am an ASF member but I have not been involved with the incubator much.
>>
>> The last few weeks I have been chatting with folks at Gigaspaces [1]. Some
>> of you may know them as the ones behind Cloudify [2] a cloud orchestration
>> platform.
>>
>> The folks at Gigaspaces are interested to donate the orchestration engine
>> behind Cloudify to ASF. With the motivation to open the governance of the
>> core of Cloudify.
>>
>> They have already started laying a foundation for an incubator project,
>> putting most of the software under a separate organization called ARIA [3]
>> with software currently in gitHub [4].
>>
>> I would like to introduce Arthur Berezin from Gigaspaces who is working on
>> putting together a proposal to the incubator. He got an account on the Wiki
>> but no karma to add a page yet it seems.
>>
>> The proposal would need a champion, I don’t feel I have the experience
>> with the incubator to do this well, so while I will help, it would be great
>> to get a Champion to help shepherd this properly. Any takers ?
>>
>> Cheers,
>>
>> [1] http://www.gigaspaces.com
>> [2] http://getcloudify.org
>> [3] http://ariatosca.org
>> [4] https://github.com/aria-tosca
>>
>> -Sebastien
>> cloudstack, libcloud PMC
>> -
>> 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