Re: The new project site is up!

[Shane Curcuru]

(Please note mix of public/private lists)

Daniel Ruggeri wrote on 5/17/16 7:48 AM:
> On 5/16/2016 8:57 PM, Mike Jumper wrote:
 Also, I've been beaten into submission... erm, I mean... TRAINED to look
 for trademarks. I haven't dug through the archives yet to know if this
 was discussed, but registration (tradema...@apache.org) and including
 the TM in prominent places on the site (particularly the home page and
 downloads pages) are things to keep in mind as goals once graduation
 from Incubator occurs.

>> If we don't need to wait for TLP status to request registration of
>> "Guacamole" as an ASF trademark, I'd be glad to get that process
>> going. Is this the case?

In general, we do not expend funds for registrations for podlings until
they graduate to TLP.  As a public charity that relies on
sponsors/donors, we need to be careful with legal expenses.

The fact that the PPMC is already thinking about this and has some nice
consistent logos is great, so don't let that discourage you!

I recommend reviewing the PMC branding requirements, and putting TM on
first/most prominent uses of the name and logos, etc., so you can get a
head start on the details:

  http://www.apache.org/foundation/marks/pmcs

The PPMC should make sure to submit a PODLINGNAMESEARCH as per this:

  http://www.apache.org/foundation/marks/naming.html

If you're still excited about branding while you're building community
(which I love to hear!) then you can start making a request to register
your future project name by following this:

  http://www.apache.org/foundation/marks/register#register

Do let me know if 1) any of these procedures aren't clear, and 2) if
there's a better way to ensure that other incubator podlings know about
them.  I never have the time to delve into incubator documentation, but
I know there are still some improvements to make there in terms of
clearly referencing the right docs.

Thanks,
- Shane
>>
>> Logos as well? We currently have three:
>>
>> 1) The detailed full-color guac bowl (currently used as the page favicon)
>> 2) The low-detail tri-color guac bowl (the logo used on the homepage,
>> within the web application, and just about everywhere else)
>> 3) A monochrome version of the same low-detail logo
> 
> This is a good question (that I can't answer without making stuff up) so
> I've added the trademarks@ address to see if that's a thing that can be
> kicked off right now. I've also added general@ for awareness/sage wisdom.
> 


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

Re: [DISCUSS] PredictionIO incubation proposal

[Pat Ferrel]

I’d like to see Apache find a way to sponsor the template gallery. The current 
site collects data and inclusion is controlled by Salesforce I believe. I guess 
there is nothing wrong with that but it would be great to have a free open 
collection of templates as the Apache blessed method of contribution even if 
it’s only a page of github links that committers edit.
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] PredictionIO incubation proposal

[Debo Dutta (dedutta)]

Thx a lot Henry. Would love to. 

Sent from my iPhone

> On May 17, 2016, at 2:19 PM, Henry Saputra  wrote:
> 
> You are welcome, and great to have you as one of mentors for PredictionIO
> polling.
> 
> Should be a fun project to be part of =)
> 
> - Henry
> 
>> On Tue, May 17, 2016 at 2:14 PM, Suneel Marthi  wrote:
>> 
>> Thanks Henry
>> 
>> On Tue, May 17, 2016 at 5:11 PM, Henry Saputra 
>> wrote:
>> 
>>> As mentor, you will have karma to commit to the source repository.
>>> 
>>> As you probably know, the initial committers and mentors will form the
>>> initial PPMCs for the podling.
>>> Hopefully for day to day operations you should not need to have
>> distinction
>>> of committer vs mentors anymore.
>>> 
>>> You do not have to be listed as committer for the proposal.
>>> 
>>> - Henry
>>> 
 On Tue, May 17, 2016 at 1:57 PM, Suneel Marthi 
>>> wrote:
>>> 
 Thanks for having me as a mentor for PIO.  I would like to be added to
>>> the
 initial list of committers and am looking to actively participate in
>> the
 development too. I am not sure if my being a mentor automatically
>> grants
>>> me
 the 'commit' karma.
 
 Its already been suggested earlier in this thread by Roman and
 Jean-Baptiste that the project needs to be decoupled from Spark and
 integrated with Beam.  It would be good to reduce the reliance on
 Spark-Submit from what I have seen of the project so far. But let's not
 talk architecture and design here when the project's not in incubator
>>> yet.
 :)
 
 
 
 
 On Tue, May 17, 2016 at 4:09 PM, Henry Saputra <
>> henry.sapu...@gmail.com>
 wrote:
 
> Cool, this will make code grant process to be easier =)
> 
> The initial committers and mentors look great.
> I am sure more will come as contributions start pouring in to the
 project.
> 
> Looking forward for the VOTE thread soon.
> 
> - Henry
> 
>> On Mon, May 16, 2016 at 12:07 PM, Simon Chan 
> wrote:
> 
>> Yes, it includes everyone who previously contributed code from
> PredictionIO
>> before the acquisition and still want to be involved in the
>> project.
>> 
>> We may have missed "Alex Merritt", going to add him to the list
>> soon.
>> 
>> Simon
>> 
>> 
>> On Mon, May 16, 2016 at 11:58 AM, Suneel Marthi <
>> smar...@apache.org>
>> wrote:
>> 
>>> I do have a question about the proposed list of committers.
>>> 
>>> Does the list also include all of those folks who were with
> PredictionIO
>>> (and had contributed to the project) and then chose to leave when
>>> PIO
> was
>>> acquired by Salesforce?
>>> 
>>> 
>>> 
>>> 
>>> On Mon, May 16, 2016 at 1:13 PM, Jean-Baptiste Onofré <
 j...@nanthrax.net
>> 
>>> wrote:
>>> 
 By the way, we have some discussion about integrating Zeppelin
>>> with
>> Beam
>>> ;)
 
 Regards
 JB
 
> On 05/15/2016 02:32 AM, Roman Shaposhnik wrote:
> 
> Super excited to see this proposal! This will finally allow us
>>> to
> have
> an ASF managed
> backend for next generation data-driven apps that I see
>> emerging
> quite
> rapidly.
> 
> The proposal looks great to me (although I'd recommend calling
 Scala
> as an implementation
> language more prominently since it may attract additional
 developers
> with affinity to it).
> 
> I do have two questions about technology:
>1. do you think it would be possible to leverage Apache
>> Beam
> (incubating)
>for abstracting away dependency on execution
>> frameworks?
 My
> understanding
>is that PredictionIO currently only run on Spark.
>2. is there a potential integration with Apache Zeppelin
> possible?
> 
> Thanks,
> Roman.
> 
> On Fri, May 13, 2016 at 1:41 PM, Andrew Purtell <
> apurt...@apache.org>
> wrote:
> 
>> Greetings,
>> 
>> It is my pleasure to
>> 
>> propose the PredictionIO project for incubation at the Apache
>> Software
>> Foundation.
>> 
>> PredictionIO is a
>> popular
>> open
>> 
>> source Machine Learning Server built on top of a
>>> state-of-the-art
>> open
>> source stack, including several Apache technologies, that
>> 
>> enables developers to manage and deploy production-ready
 predictive
>> services for various kinds of machine learning tasks
>> , with more than 400 production deployments around the world
>>> and
 a
>> growing
>> contributor 

Re: [DISCUSS] PredictionIO incubation proposal

[Simon Chan]

Looks great, Debo!

Simon


On Tue, May 17, 2016 at 2:01 PM, Debo Dutta (dedutta) 
wrote:

> Also some of us have built something similar and would be happy to help
> https://github.com/CiscoSystems/cognitive
>
> debo
>
>
>
>
> On 5/17/16, 12:58 PM, "Nick Pentreath"  wrote:
>
> >Hi there
> >
> >I'm glad to see the proposal to incubate PredictionIO. In my previous life
> >as a startup co-founder, I kept a close eye on the project, and it would
> be
> >fantastic to see it become an Apache incubating project!
> >
> >The folks working on Apache Spark and Apache SystemML (incubating) here at
> >IBM are excited about the possibilities for integrating PredictionIO and
> >SystemML (Mike Dusenberry is a committer on that project), as well
> >as further improving Spark integration (I'm a PMC member on that project).
> >
> >Mike and I, together with Luciano (who is a mentor on this proposal) would
> >like to volunteer our services as initial committers, if that is
> agreeable.
> >
> >Kind regards
> >Nick
> >mln...@apache.org
> >
> >
> >
> >>
> >> -- Forwarded message --
> >> From: Andrew Purtell 
> >> To: "general@incubator.apache.org" 
> >> Cc:
> >> Date: Fri, 13 May 2016 13:41:38 -0700
> >> Subject: [DISCUSS] PredictionIO incubation proposal
> >> Greetings,
> >>
> >> It is my pleasure to
> >> ​ ​
> >> propose the PredictionIO project for incubation at the Apache Software
> >> Foundation.
> >> ​ ​
> >> PredictionIO is a
> >> ​ popular​
> >> open
> >> ​ ​
> >> source Machine Learning Server built on top of a state-of-the-art open
> >> source stack, including several Apache technologies, that
> >> ​ ​
> >> enables developers to manage and deploy production-ready predictive
> >> services for various kinds of machine learning tasks
> >> ​, with more than 400 production deployments around the world and a
> growing
> >> contributor community. ​
> >>
> >>
> >> The text of the proposal is included below and is also available at
> >> https://wiki.apache.org/incubator/PredictionIO
> >>
> >> Best regards,
> >> Andrew Purtell
> >>
> >>
> >> = 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.
> >>
> >> You can find the Template Gallery at https://templates.prediction.io/
> >>
> >> === 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
> >> 

Re: [DISCUSS] PredictionIO incubation proposal

[Henry Saputra]

You are welcome, and great to have you as one of mentors for PredictionIO
polling.

Should be a fun project to be part of =)

- Henry

On Tue, May 17, 2016 at 2:14 PM, Suneel Marthi  wrote:

> Thanks Henry
>
> On Tue, May 17, 2016 at 5:11 PM, Henry Saputra 
> wrote:
>
> > As mentor, you will have karma to commit to the source repository.
> >
> > As you probably know, the initial committers and mentors will form the
> > initial PPMCs for the podling.
> > Hopefully for day to day operations you should not need to have
> distinction
> > of committer vs mentors anymore.
> >
> > You do not have to be listed as committer for the proposal.
> >
> > - Henry
> >
> > On Tue, May 17, 2016 at 1:57 PM, Suneel Marthi 
> wrote:
> >
> > > Thanks for having me as a mentor for PIO.  I would like to be added to
> > the
> > > initial list of committers and am looking to actively participate in
> the
> > > development too. I am not sure if my being a mentor automatically
> grants
> > me
> > > the 'commit' karma.
> > >
> > > Its already been suggested earlier in this thread by Roman and
> > > Jean-Baptiste that the project needs to be decoupled from Spark and
> > > integrated with Beam.  It would be good to reduce the reliance on
> > > Spark-Submit from what I have seen of the project so far. But let's not
> > > talk architecture and design here when the project's not in incubator
> > yet.
> > > :)
> > >
> > >
> > >
> > >
> > > On Tue, May 17, 2016 at 4:09 PM, Henry Saputra <
> henry.sapu...@gmail.com>
> > > wrote:
> > >
> > > > Cool, this will make code grant process to be easier =)
> > > >
> > > > The initial committers and mentors look great.
> > > > I am sure more will come as contributions start pouring in to the
> > > project.
> > > >
> > > > Looking forward for the VOTE thread soon.
> > > >
> > > > - Henry
> > > >
> > > > On Mon, May 16, 2016 at 12:07 PM, Simon Chan 
> > > wrote:
> > > >
> > > > > Yes, it includes everyone who previously contributed code from
> > > > PredictionIO
> > > > > before the acquisition and still want to be involved in the
> project.
> > > > >
> > > > > We may have missed "Alex Merritt", going to add him to the list
> soon.
> > > > >
> > > > > Simon
> > > > >
> > > > >
> > > > > On Mon, May 16, 2016 at 11:58 AM, Suneel Marthi <
> smar...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > I do have a question about the proposed list of committers.
> > > > > >
> > > > > > Does the list also include all of those folks who were with
> > > > PredictionIO
> > > > > > (and had contributed to the project) and then chose to leave when
> > PIO
> > > > was
> > > > > > acquired by Salesforce?
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Mon, May 16, 2016 at 1:13 PM, Jean-Baptiste Onofré <
> > > j...@nanthrax.net
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > By the way, we have some discussion about integrating Zeppelin
> > with
> > > > > Beam
> > > > > > ;)
> > > > > > >
> > > > > > > Regards
> > > > > > > JB
> > > > > > >
> > > > > > > On 05/15/2016 02:32 AM, Roman Shaposhnik wrote:
> > > > > > >
> > > > > > >> Super excited to see this proposal! This will finally allow us
> > to
> > > > have
> > > > > > >> an ASF managed
> > > > > > >> backend for next generation data-driven apps that I see
> emerging
> > > > quite
> > > > > > >> rapidly.
> > > > > > >>
> > > > > > >> The proposal looks great to me (although I'd recommend calling
> > > Scala
> > > > > > >> as an implementation
> > > > > > >> language more prominently since it may attract additional
> > > developers
> > > > > > >> with affinity to it).
> > > > > > >>
> > > > > > >> I do have two questions about technology:
> > > > > > >> 1. do you think it would be possible to leverage Apache
> Beam
> > > > > > >> (incubating)
> > > > > > >> for abstracting away dependency on execution
> frameworks?
> > > My
> > > > > > >> understanding
> > > > > > >> is that PredictionIO currently only run on Spark.
> > > > > > >> 2. is there a potential integration with Apache Zeppelin
> > > > possible?
> > > > > > >>
> > > > > > >> Thanks,
> > > > > > >> Roman.
> > > > > > >>
> > > > > > >> On Fri, May 13, 2016 at 1:41 PM, Andrew Purtell <
> > > > apurt...@apache.org>
> > > > > > >> wrote:
> > > > > > >>
> > > > > > >>> Greetings,
> > > > > > >>>
> > > > > > >>> It is my pleasure to
> > > > > > >>>
> > > > > > >>> propose the PredictionIO project for incubation at the Apache
> > > > > Software
> > > > > > >>> Foundation.
> > > > > > >>>
> > > > > > >>> PredictionIO is a
> > > > > > >>> popular
> > > > > > >>> open
> > > > > > >>>
> > > > > > >>> source Machine Learning Server built on top of a
> > state-of-the-art
> > > > > open
> > > > > > >>> source stack, including several Apache technologies, that
> > > > > > >>>
> > > > > > >>> enables developers to manage and deploy production-ready
> > > predictive
> > > > > > >>> services for 

Re: [DISCUSS] PredictionIO incubation proposal

[Suneel Marthi]

Thanks Henry

On Tue, May 17, 2016 at 5:11 PM, Henry Saputra 
wrote:

> As mentor, you will have karma to commit to the source repository.
>
> As you probably know, the initial committers and mentors will form the
> initial PPMCs for the podling.
> Hopefully for day to day operations you should not need to have distinction
> of committer vs mentors anymore.
>
> You do not have to be listed as committer for the proposal.
>
> - Henry
>
> On Tue, May 17, 2016 at 1:57 PM, Suneel Marthi  wrote:
>
> > Thanks for having me as a mentor for PIO.  I would like to be added to
> the
> > initial list of committers and am looking to actively participate in the
> > development too. I am not sure if my being a mentor automatically grants
> me
> > the 'commit' karma.
> >
> > Its already been suggested earlier in this thread by Roman and
> > Jean-Baptiste that the project needs to be decoupled from Spark and
> > integrated with Beam.  It would be good to reduce the reliance on
> > Spark-Submit from what I have seen of the project so far. But let's not
> > talk architecture and design here when the project's not in incubator
> yet.
> > :)
> >
> >
> >
> >
> > On Tue, May 17, 2016 at 4:09 PM, Henry Saputra 
> > wrote:
> >
> > > Cool, this will make code grant process to be easier =)
> > >
> > > The initial committers and mentors look great.
> > > I am sure more will come as contributions start pouring in to the
> > project.
> > >
> > > Looking forward for the VOTE thread soon.
> > >
> > > - Henry
> > >
> > > On Mon, May 16, 2016 at 12:07 PM, Simon Chan 
> > wrote:
> > >
> > > > Yes, it includes everyone who previously contributed code from
> > > PredictionIO
> > > > before the acquisition and still want to be involved in the project.
> > > >
> > > > We may have missed "Alex Merritt", going to add him to the list soon.
> > > >
> > > > Simon
> > > >
> > > >
> > > > On Mon, May 16, 2016 at 11:58 AM, Suneel Marthi 
> > > > wrote:
> > > >
> > > > > I do have a question about the proposed list of committers.
> > > > >
> > > > > Does the list also include all of those folks who were with
> > > PredictionIO
> > > > > (and had contributed to the project) and then chose to leave when
> PIO
> > > was
> > > > > acquired by Salesforce?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Mon, May 16, 2016 at 1:13 PM, Jean-Baptiste Onofré <
> > j...@nanthrax.net
> > > >
> > > > > wrote:
> > > > >
> > > > > > By the way, we have some discussion about integrating Zeppelin
> with
> > > > Beam
> > > > > ;)
> > > > > >
> > > > > > Regards
> > > > > > JB
> > > > > >
> > > > > > On 05/15/2016 02:32 AM, Roman Shaposhnik wrote:
> > > > > >
> > > > > >> Super excited to see this proposal! This will finally allow us
> to
> > > have
> > > > > >> an ASF managed
> > > > > >> backend for next generation data-driven apps that I see emerging
> > > quite
> > > > > >> rapidly.
> > > > > >>
> > > > > >> The proposal looks great to me (although I'd recommend calling
> > Scala
> > > > > >> as an implementation
> > > > > >> language more prominently since it may attract additional
> > developers
> > > > > >> with affinity to it).
> > > > > >>
> > > > > >> I do have two questions about technology:
> > > > > >> 1. do you think it would be possible to leverage Apache Beam
> > > > > >> (incubating)
> > > > > >> for abstracting away dependency on execution frameworks?
> > My
> > > > > >> understanding
> > > > > >> is that PredictionIO currently only run on Spark.
> > > > > >> 2. is there a potential integration with Apache Zeppelin
> > > possible?
> > > > > >>
> > > > > >> Thanks,
> > > > > >> Roman.
> > > > > >>
> > > > > >> On Fri, May 13, 2016 at 1:41 PM, Andrew Purtell <
> > > apurt...@apache.org>
> > > > > >> wrote:
> > > > > >>
> > > > > >>> Greetings,
> > > > > >>>
> > > > > >>> It is my pleasure to
> > > > > >>>
> > > > > >>> propose the PredictionIO project for incubation at the Apache
> > > > Software
> > > > > >>> Foundation.
> > > > > >>>
> > > > > >>> PredictionIO is a
> > > > > >>> popular
> > > > > >>> open
> > > > > >>>
> > > > > >>> source Machine Learning Server built on top of a
> state-of-the-art
> > > > open
> > > > > >>> source stack, including several Apache technologies, that
> > > > > >>>
> > > > > >>> enables developers to manage and deploy production-ready
> > predictive
> > > > > >>> services for various kinds of machine learning tasks
> > > > > >>> , with more than 400 production deployments around the world
> and
> > a
> > > > > >>> growing
> > > > > >>> contributor community.
> > > > > >>>
> > > > > >>>
> > > > > >>> The text of the proposal is included below and is also
> available
> > at
> > > > > >>> https://wiki.apache.org/incubator/PredictionIO
> > > > > >>>
> > > > > >>> Best regards,
> > > > > >>> Andrew Purtell
> > > > > >>>
> > > > > >>>
> > > > > >>> = PredictionIO Proposal =
> > > > > >>>
> > 

Re: [DISCUSS] PredictionIO incubation proposal

[Henry Saputra]

As mentor, you will have karma to commit to the source repository.

As you probably know, the initial committers and mentors will form the
initial PPMCs for the podling.
Hopefully for day to day operations you should not need to have distinction
of committer vs mentors anymore.

You do not have to be listed as committer for the proposal.

- Henry

On Tue, May 17, 2016 at 1:57 PM, Suneel Marthi  wrote:

> Thanks for having me as a mentor for PIO.  I would like to be added to the
> initial list of committers and am looking to actively participate in the
> development too. I am not sure if my being a mentor automatically grants me
> the 'commit' karma.
>
> Its already been suggested earlier in this thread by Roman and
> Jean-Baptiste that the project needs to be decoupled from Spark and
> integrated with Beam.  It would be good to reduce the reliance on
> Spark-Submit from what I have seen of the project so far. But let's not
> talk architecture and design here when the project's not in incubator yet.
> :)
>
>
>
>
> On Tue, May 17, 2016 at 4:09 PM, Henry Saputra 
> wrote:
>
> > Cool, this will make code grant process to be easier =)
> >
> > The initial committers and mentors look great.
> > I am sure more will come as contributions start pouring in to the
> project.
> >
> > Looking forward for the VOTE thread soon.
> >
> > - Henry
> >
> > On Mon, May 16, 2016 at 12:07 PM, Simon Chan 
> wrote:
> >
> > > Yes, it includes everyone who previously contributed code from
> > PredictionIO
> > > before the acquisition and still want to be involved in the project.
> > >
> > > We may have missed "Alex Merritt", going to add him to the list soon.
> > >
> > > Simon
> > >
> > >
> > > On Mon, May 16, 2016 at 11:58 AM, Suneel Marthi 
> > > wrote:
> > >
> > > > I do have a question about the proposed list of committers.
> > > >
> > > > Does the list also include all of those folks who were with
> > PredictionIO
> > > > (and had contributed to the project) and then chose to leave when PIO
> > was
> > > > acquired by Salesforce?
> > > >
> > > >
> > > >
> > > >
> > > > On Mon, May 16, 2016 at 1:13 PM, Jean-Baptiste Onofré <
> j...@nanthrax.net
> > >
> > > > wrote:
> > > >
> > > > > By the way, we have some discussion about integrating Zeppelin with
> > > Beam
> > > > ;)
> > > > >
> > > > > Regards
> > > > > JB
> > > > >
> > > > > On 05/15/2016 02:32 AM, Roman Shaposhnik wrote:
> > > > >
> > > > >> Super excited to see this proposal! This will finally allow us to
> > have
> > > > >> an ASF managed
> > > > >> backend for next generation data-driven apps that I see emerging
> > quite
> > > > >> rapidly.
> > > > >>
> > > > >> The proposal looks great to me (although I'd recommend calling
> Scala
> > > > >> as an implementation
> > > > >> language more prominently since it may attract additional
> developers
> > > > >> with affinity to it).
> > > > >>
> > > > >> I do have two questions about technology:
> > > > >> 1. do you think it would be possible to leverage Apache Beam
> > > > >> (incubating)
> > > > >> for abstracting away dependency on execution frameworks?
> My
> > > > >> understanding
> > > > >> is that PredictionIO currently only run on Spark.
> > > > >> 2. is there a potential integration with Apache Zeppelin
> > possible?
> > > > >>
> > > > >> Thanks,
> > > > >> Roman.
> > > > >>
> > > > >> On Fri, May 13, 2016 at 1:41 PM, Andrew Purtell <
> > apurt...@apache.org>
> > > > >> wrote:
> > > > >>
> > > > >>> Greetings,
> > > > >>>
> > > > >>> It is my pleasure to
> > > > >>>
> > > > >>> propose the PredictionIO project for incubation at the Apache
> > > Software
> > > > >>> Foundation.
> > > > >>>
> > > > >>> PredictionIO is a
> > > > >>> popular
> > > > >>> open
> > > > >>>
> > > > >>> source Machine Learning Server built on top of a state-of-the-art
> > > open
> > > > >>> source stack, including several Apache technologies, that
> > > > >>>
> > > > >>> enables developers to manage and deploy production-ready
> predictive
> > > > >>> services for various kinds of machine learning tasks
> > > > >>> , with more than 400 production deployments around the world and
> a
> > > > >>> growing
> > > > >>> contributor community.
> > > > >>>
> > > > >>>
> > > > >>> The text of the proposal is included below and is also available
> at
> > > > >>> https://wiki.apache.org/incubator/PredictionIO
> > > > >>>
> > > > >>> Best regards,
> > > > >>> Andrew Purtell
> > > > >>>
> > > > >>>
> > > > >>> = 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 

Re: [DISCUSS] PredictionIO incubation proposal

[Debo Dutta (dedutta)]

Also some of us have built something similar and would be happy to help
https://github.com/CiscoSystems/cognitive 

debo




On 5/17/16, 12:58 PM, "Nick Pentreath"  wrote:

>Hi there
>
>I'm glad to see the proposal to incubate PredictionIO. In my previous life
>as a startup co-founder, I kept a close eye on the project, and it would be
>fantastic to see it become an Apache incubating project!
>
>The folks working on Apache Spark and Apache SystemML (incubating) here at
>IBM are excited about the possibilities for integrating PredictionIO and
>SystemML (Mike Dusenberry is a committer on that project), as well
>as further improving Spark integration (I'm a PMC member on that project).
>
>Mike and I, together with Luciano (who is a mentor on this proposal) would
>like to volunteer our services as initial committers, if that is agreeable.
>
>Kind regards
>Nick
>mln...@apache.org
>
>
>
>>
>> -- Forwarded message --
>> From: Andrew Purtell 
>> To: "general@incubator.apache.org" 
>> Cc:
>> Date: Fri, 13 May 2016 13:41:38 -0700
>> Subject: [DISCUSS] PredictionIO incubation proposal
>> Greetings,
>>
>> It is my pleasure to
>> ​ ​
>> propose the PredictionIO project for incubation at the Apache Software
>> Foundation.
>> ​ ​
>> PredictionIO is a
>> ​ popular​
>> open
>> ​ ​
>> source Machine Learning Server built on top of a state-of-the-art open
>> source stack, including several Apache technologies, that
>> ​ ​
>> enables developers to manage and deploy production-ready predictive
>> services for various kinds of machine learning tasks
>> ​, with more than 400 production deployments around the world and a growing
>> contributor community. ​
>>
>>
>> The text of the proposal is included below and is also available at
>> https://wiki.apache.org/incubator/PredictionIO
>>
>> Best regards,
>> Andrew Purtell
>>
>>
>> = 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.
>>
>> You can find the Template Gallery at https://templates.prediction.io/
>>
>> === 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 

Re: [DISCUSS] PredictionIO incubation proposal

[Suneel Marthi]

Thanks for having me as a mentor for PIO.  I would like to be added to the
initial list of committers and am looking to actively participate in the
development too. I am not sure if my being a mentor automatically grants me
the 'commit' karma.

Its already been suggested earlier in this thread by Roman and
Jean-Baptiste that the project needs to be decoupled from Spark and
integrated with Beam.  It would be good to reduce the reliance on
Spark-Submit from what I have seen of the project so far. But let's not
talk architecture and design here when the project's not in incubator yet.
:)




On Tue, May 17, 2016 at 4:09 PM, Henry Saputra 
wrote:

> Cool, this will make code grant process to be easier =)
>
> The initial committers and mentors look great.
> I am sure more will come as contributions start pouring in to the project.
>
> Looking forward for the VOTE thread soon.
>
> - Henry
>
> On Mon, May 16, 2016 at 12:07 PM, Simon Chan  wrote:
>
> > Yes, it includes everyone who previously contributed code from
> PredictionIO
> > before the acquisition and still want to be involved in the project.
> >
> > We may have missed "Alex Merritt", going to add him to the list soon.
> >
> > Simon
> >
> >
> > On Mon, May 16, 2016 at 11:58 AM, Suneel Marthi 
> > wrote:
> >
> > > I do have a question about the proposed list of committers.
> > >
> > > Does the list also include all of those folks who were with
> PredictionIO
> > > (and had contributed to the project) and then chose to leave when PIO
> was
> > > acquired by Salesforce?
> > >
> > >
> > >
> > >
> > > On Mon, May 16, 2016 at 1:13 PM, Jean-Baptiste Onofré  >
> > > wrote:
> > >
> > > > By the way, we have some discussion about integrating Zeppelin with
> > Beam
> > > ;)
> > > >
> > > > Regards
> > > > JB
> > > >
> > > > On 05/15/2016 02:32 AM, Roman Shaposhnik wrote:
> > > >
> > > >> Super excited to see this proposal! This will finally allow us to
> have
> > > >> an ASF managed
> > > >> backend for next generation data-driven apps that I see emerging
> quite
> > > >> rapidly.
> > > >>
> > > >> The proposal looks great to me (although I'd recommend calling Scala
> > > >> as an implementation
> > > >> language more prominently since it may attract additional developers
> > > >> with affinity to it).
> > > >>
> > > >> I do have two questions about technology:
> > > >> 1. do you think it would be possible to leverage Apache Beam
> > > >> (incubating)
> > > >> for abstracting away dependency on execution frameworks? My
> > > >> understanding
> > > >> is that PredictionIO currently only run on Spark.
> > > >> 2. is there a potential integration with Apache Zeppelin
> possible?
> > > >>
> > > >> Thanks,
> > > >> Roman.
> > > >>
> > > >> On Fri, May 13, 2016 at 1:41 PM, Andrew Purtell <
> apurt...@apache.org>
> > > >> wrote:
> > > >>
> > > >>> Greetings,
> > > >>>
> > > >>> It is my pleasure to
> > > >>>
> > > >>> propose the PredictionIO project for incubation at the Apache
> > Software
> > > >>> Foundation.
> > > >>>
> > > >>> PredictionIO is a
> > > >>> popular
> > > >>> open
> > > >>>
> > > >>> source Machine Learning Server built on top of a state-of-the-art
> > open
> > > >>> source stack, including several Apache technologies, that
> > > >>>
> > > >>> enables developers to manage and deploy production-ready predictive
> > > >>> services for various kinds of machine learning tasks
> > > >>> , with more than 400 production deployments around the world and a
> > > >>> growing
> > > >>> contributor community.
> > > >>>
> > > >>>
> > > >>> The text of the proposal is included below and is also available at
> > > >>> https://wiki.apache.org/incubator/PredictionIO
> > > >>>
> > > >>> Best regards,
> > > >>> Andrew Purtell
> > > >>>
> > > >>>
> > > >>> = 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
> > > 

Re: [DISCUSS] PredictionIO incubation proposal

[Henry Saputra]

Cool, this will make code grant process to be easier =)

The initial committers and mentors look great.
I am sure more will come as contributions start pouring in to the project.

Looking forward for the VOTE thread soon.

- Henry

On Mon, May 16, 2016 at 12:07 PM, Simon Chan  wrote:

> Yes, it includes everyone who previously contributed code from PredictionIO
> before the acquisition and still want to be involved in the project.
>
> We may have missed "Alex Merritt", going to add him to the list soon.
>
> Simon
>
>
> On Mon, May 16, 2016 at 11:58 AM, Suneel Marthi 
> wrote:
>
> > I do have a question about the proposed list of committers.
> >
> > Does the list also include all of those folks who were with PredictionIO
> > (and had contributed to the project) and then chose to leave when PIO was
> > acquired by Salesforce?
> >
> >
> >
> >
> > On Mon, May 16, 2016 at 1:13 PM, Jean-Baptiste Onofré 
> > wrote:
> >
> > > By the way, we have some discussion about integrating Zeppelin with
> Beam
> > ;)
> > >
> > > Regards
> > > JB
> > >
> > > On 05/15/2016 02:32 AM, Roman Shaposhnik wrote:
> > >
> > >> Super excited to see this proposal! This will finally allow us to have
> > >> an ASF managed
> > >> backend for next generation data-driven apps that I see emerging quite
> > >> rapidly.
> > >>
> > >> The proposal looks great to me (although I'd recommend calling Scala
> > >> as an implementation
> > >> language more prominently since it may attract additional developers
> > >> with affinity to it).
> > >>
> > >> I do have two questions about technology:
> > >> 1. do you think it would be possible to leverage Apache Beam
> > >> (incubating)
> > >> for abstracting away dependency on execution frameworks? My
> > >> understanding
> > >> is that PredictionIO currently only run on Spark.
> > >> 2. is there a potential integration with Apache Zeppelin possible?
> > >>
> > >> Thanks,
> > >> Roman.
> > >>
> > >> On Fri, May 13, 2016 at 1:41 PM, Andrew Purtell 
> > >> wrote:
> > >>
> > >>> Greetings,
> > >>>
> > >>> It is my pleasure to
> > >>>
> > >>> propose the PredictionIO project for incubation at the Apache
> Software
> > >>> Foundation.
> > >>>
> > >>> PredictionIO is a
> > >>> popular
> > >>> open
> > >>>
> > >>> source Machine Learning Server built on top of a state-of-the-art
> open
> > >>> source stack, including several Apache technologies, that
> > >>>
> > >>> enables developers to manage and deploy production-ready predictive
> > >>> services for various kinds of machine learning tasks
> > >>> , with more than 400 production deployments around the world and a
> > >>> growing
> > >>> contributor community.
> > >>>
> > >>>
> > >>> The text of the proposal is included below and is also available at
> > >>> https://wiki.apache.org/incubator/PredictionIO
> > >>>
> > >>> Best regards,
> > >>> Andrew Purtell
> > >>>
> > >>>
> > >>> = 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.
> > >>>
> > >>> You can find the Template Gallery at
> https://templates.prediction.io/
> > >>>
> > >>> === 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.
> > 

Re: [DISCUSS] PredictionIO incubation proposal

[Nick Pentreath]

Hi there

I'm glad to see the proposal to incubate PredictionIO. In my previous life
as a startup co-founder, I kept a close eye on the project, and it would be
fantastic to see it become an Apache incubating project!

The folks working on Apache Spark and Apache SystemML (incubating) here at
IBM are excited about the possibilities for integrating PredictionIO and
SystemML (Mike Dusenberry is a committer on that project), as well
as further improving Spark integration (I'm a PMC member on that project).

Mike and I, together with Luciano (who is a mentor on this proposal) would
like to volunteer our services as initial committers, if that is agreeable.

Kind regards
Nick
mln...@apache.org



>
> -- Forwarded message --
> From: Andrew Purtell 
> To: "general@incubator.apache.org" 
> Cc:
> Date: Fri, 13 May 2016 13:41:38 -0700
> Subject: [DISCUSS] PredictionIO incubation proposal
> Greetings,
>
> It is my pleasure to
> ​ ​
> propose the PredictionIO project for incubation at the Apache Software
> Foundation.
> ​ ​
> PredictionIO is a
> ​ popular​
> open
> ​ ​
> source Machine Learning Server built on top of a state-of-the-art open
> source stack, including several Apache technologies, that
> ​ ​
> enables developers to manage and deploy production-ready predictive
> services for various kinds of machine learning tasks
> ​, with more than 400 production deployments around the world and a growing
> contributor community. ​
>
>
> The text of the proposal is included below and is also available at
> https://wiki.apache.org/incubator/PredictionIO
>
> Best regards,
> Andrew Purtell
>
>
> = 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.
>
> You can find the Template Gallery at https://templates.prediction.io/
>
> === 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 

[RESULT][VOTE] Accept Fluo into the Apache Incubator

[Billie Rinaldi]

This vote is now closed and passes with 11 binding +1 votes, 1 non-binding
+1 vote, and no other votes.

+1 binding:
Billie Rinaldi
Julian Hyde
Drew Farris
Henry Saputra
Hitesh Shah
Roman Shaposhnik
James Taylor
Ted Dunning
Suneel Marthi
Josh Elser
Jean-Baptiste Onofré

+1 non-binding:
David Lyle

Thanks to all who voted!

Billie

On Fri, May 13, 2016 at 11:22 AM, Billie Rinaldi  wrote:

> Since discussion has died down, I would like to call a VOTE on accepting
> Fluo into the Apache Incubator.
>
> Proposal: http://wiki.apache.org/incubator/FluoProposal
>
> [ ] +1 Accept Fluo into the Apache Incubator
> [ ] +0 Abstain.
> [ ] -1 Do not accept Fluo into the Apache Incubator because…
>
> This vote will be open for at least 72 hours.
>
> Here is my +1 (binding).
>
> Billie
> --
>
> Fluo Proposal
>
> Abstract
>
> Fluo is a distributed system for incrementally processing large data sets
> stored in Accumulo.
>
> Proposal
>
> Fluo is a distributed transaction and notification system that enables the
> incremental processing of large data sets. Its transaction system allows
> for concurrent, cross-node updates to data stored in Accumulo. Its
> notification system enables developers to write code to be executed when
> observed data changes. Fluo provides a core API to perform transactional
> updates using minimalistic get/set methods. Fluo also provides a higher
> order recipes API that builds on the core API to support more complex
> methods for transactional updates.
>
> Background
>
> Several frameworks exist for batch (i.e Spark, MapReduce) and stream (i.e
> Storm, Spark Streaming) processing of data. While batch and stream
> processing have strong use cases, they are not suited for joining incoming
> data in real-time to a large existing data set. To fill this need, Google
> developed an incremental processing system called Percolator and described
> it in the paper, Large-scale Incremental Processing Using Distributed
> Transactions and Notifications1.
>
> Rationale
>
> Fluo fills the need for cross-row (and cross-node) transactions in
> Accumulo by providing it with an open source implementation of Percolator.
> Fluo also satisfies a gap in Accumulo’s ability to incrementally process
> data. Fluo also provides a novel recipes API which offers higher level
> abstractions for transactional updates.
>
> Current Status
>
> Fluo currently exists as an open source project on GitHub and has been in
> active development since 2013. The project has made an alpha release and
> two beta releases. The major features of Fluo outlined in this proposal
> have been implemented. Several example Fluo applications have been created
> and run successfully on clusters (up to 24 nodes).
>
> Meritocracy
>
> The Fluo project operates as a meritocracy and will continue to do so
> because we feel that a project comprised of a diverse set of committers
> will thrive. Therefore, we welcome new contributors and encourage them on
> their path to committership.
>
> Community
>
> Fluo is currently being used by a subset of the Accumulo community. The
> initial developers have been responsive to external contributions through
> pull requests and issues on GitHub. As Fluo releases a stable 1.0 version
> that is production-ready, we expect this community to grow. To encourage
> growth, we have created a project website with documentation, given talks
> at Meetups and the Accumulo Summit, and engaged with new users on GitHub
> and the Fluo mailing list.
>
> Core Developers
>
> The project was started by Keith Turner (an Apache Member and
> committer/PMC on Gora and Accumulo) in 2013, and the development has
> primarily consisted of his and Mike Walch’s continued efforts. Additional
> developers have contributed over time, which has led to new committers.
>
> Alignment
>
> Fluo is closely linked to the Accumulo community, and fits well within the
> larger Hadoop ecosystem at Apache. Fluo utilizes several Apache projects,
> such as Accumulo, YARN, Twill, and ZooKeeper. Enabling closer collaboration
> between these communities through its coexistence within the ASF would help
> further drive the success of them all.
>
> In addition to our technical ties to other ASF projects, our development
> philosophy aligns with Apache philosophies. Based on our experience with
> existing Apache projects, we are interested in establishing formal
> governance with a PMC and community bylaws, which we feel would best be
> done within Apache.
>
> Known Risks
>
> Orphaned Products
>
> Fluo could be orphaned if the project fails to gain adoption and the core
> developers abandon their interest (this is not anticipated). This risk can
> be mitigated by attracting more committers and developing further
> documentation to ease adoption.
>
> Inexperience with Open Source
>
> Fluo has been an open source project on GitHub from the start of its
> development. Several Fluo developers are committers on other ASF projects
> as well as open source 

Re: [VOTE] Release Apache Ranger 0.5.3 (incubating)

[Velmurugan Periasamy]

Thanks Justin. Pushed few changes addressing your suggestions. Could you please 
verify if the current LICENSE.txt and NOTICE.txt are acceptable? 

LICENSE.txt - https://github.com/apache/incubator-ranger/blob/master/LICENSE.txt
NOTICE.txt - https://github.com/apache/incubator-ranger/blob/master/NOTICE.txt

On May 17, 2016, at 12:50 AM, Justin Mclean  wrote:

> Hi,
> 
>> Just so that we get it right the next time, can you verify that the current
>> NOTICE is acceptable or does it require further changes?
> 
> Doesn’t look correct to me as you are including items that should be in 
> LICENSE not NOTICE. In general permissive licensed items don’t need to be 
> mentioned in NOTICE [1]
> 
> Do any of the Apache licensed bundled items have a NOTICE file? If so then 
> their required notices are needed to be placed in your NOTICE [2]
> 
> I am however more concerned with the missing licenses.
> 
> Thanks,
> Justin
> 
> 1.  http://www.apache.org/dev/licensing-howto.html#permissive-deps
> 2. http://www.apache.org/dev/licensing-howto.html#mod-notice
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

[VOTE] Release Apache Fineract 0.1.2 (incubating)

[Nazeer Shaik]

Hello Incubator PMC,

The Apache Fineract community has voted and approved the proposal to
release Apache Fineract 0.1.2 (incubating).
We now kindly request the Incubator PMC members review and vote on this
incubator release.

Apache Fineract is an open source system for core banking as a platform.
Fineract provides a reliable, robust, and affordable solution for
entrepreneurs, financial institutions, and service providers to offer
financial services to the world’s 2 billion under banked and unbanked. More
information can be found at http://fineract.incubator.apache.org/

The Apache Fineract-0.1.2-incubating release candidate is now available
with the following artifacts for a project vote:

[VOTE] Thread:
http://mail-archives.apache.org/mod_mbox/incubator-fineract-dev/201605.mbox/%3CCAOSe2yvmLHfHtQnPTH1j777AEakKrVw7pzTe%2BWu%3DVw_fw9RnJA%40mail.gmail.com%3E

[VOTE RESULT] Thread:
http://mail-archives.apache.org/mod_mbox/incubator-fineract-dev/201605.mbox/%3CCAOSe2yuyYv4bp7PL52JvzchdANGS-waXxteFKboY%2BaUZSw_YPQ%40mail.gmail.com%3E

The release candidate to be voted on is available at:
https://dist.apache.org/repos/dist/dev/incubator/fineract/0.1.2-incubating/apache-fineract-0.1.2-incubating-src.tar.gz

Git tag for the release:
https://github.com/apache/incubator-fineract/tree/0.1.2-incubating
or
https://git-wip-us.apache.org/repos/asf?p=incubator-fineract.git;a=tree;h=refs/heads/0.1.2-incubating;hb=refs/heads/0.1.2-incubating

Source release verification:
PGP signature:
https://dist.apache.org/repos/dist/dev/incubator/fineract/0.1.2-incubating/apache-fineract-0.1.2-incubating-src.tar.gz.asc
MD5/SHA Hash:
https://dist.apache.org/repos/dist/dev/incubator/fineract/0.1.2-incubating/apache-fineract-0.1.2-incubating-src.tar.gz.md5
Keys to verify the signature of the release artifact are available at:
https://dist.apache.org/repos/dist/dev/incubator/fineract/KEYS

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

Build verification steps can be found at:
https://github.com/apache/incubator-fineract/blob/0.1.2-incubating/README.md
or refer 'README.md' in apache-fineract-0.1.2-incubating-src.tar.gz


*Note: *1) This is a source only release with no binaries, with
instructions on how to
build/test the application.
2) We couldn't migrate to Open JPA to avoid dependency on Hibernate(LGPLv2.1
).
We are referring Hibernate Entity Manager, MySQLDialect,
annotations(LazyCollection, LazyCollectionOption)
at run time only and doesn't include any source or binary from Hibernate. A
separate mail will be initiated to get legal VP approval.

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,
Nazeer

Re: The new project site is up!

[Daniel Ruggeri]

On 5/16/2016 8:57 PM, Mike Jumper wrote:
>> > Also, I've been beaten into submission... erm, I mean... TRAINED to look
>> > for trademarks. I haven't dug through the archives yet to know if this
>> > was discussed, but registration (tradema...@apache.org) and including
>> > the TM in prominent places on the site (particularly the home page and
>> > downloads pages) are things to keep in mind as goals once graduation
>> > from Incubator occurs.
>> >
> If we don't need to wait for TLP status to request registration of
> "Guacamole" as an ASF trademark, I'd be glad to get that process
> going. Is this the case?
>
> Logos as well? We currently have three:
>
> 1) The detailed full-color guac bowl (currently used as the page favicon)
> 2) The low-detail tri-color guac bowl (the logo used on the homepage,
> within the web application, and just about everywhere else)
> 3) A monochrome version of the same low-detail logo

This is a good question (that I can't answer without making stuff up) so
I've added the trademarks@ address to see if that's a thing that can be
kicked off right now. I've also added general@ for awareness/sage wisdom.

-- 
Daniel Ruggeri


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