Re: First release

[Donald Szeto]

For 4, I have been manually pushing the livedoc site for the first few
changes. Hoping to get Jenkins running soon.

How about Aug 8 as our first release? Due to all these package name
changes, I'd also like to suggest to start a new minor version. How about
0.10.0?

Regards,
Donald

On Sat, Jul 23, 2016 at 7:45 AM, Pat Ferrel  wrote:

> I’d like to propose a first minimum release from Apache to include:
>
> 1) SSL optional (I think @alex has already merged this PR)
> 2) Heal ActionML fork
> 3) change to Apache class naming and include Apache license notices in all
> code
> 4) live doc site
> 5) Apache classes published to the maven/sbt universe.
>
> I’ve talked to Alex separately and we are up for doing 1 and 2, and I
> think 3 is already a PR. I’ll help with 4 but it sounds like Donald is on
> that. If this sounds good can someone propose a date? I can do 2 and other
> things on my plate by first week of Aug.
>
>
>

Re: [Proposal] The new template gallery

[Donald Szeto]

Sounds like great progress! Feel free to file a JIRA ticket and create a PR.

Regards,
Donald

On Mon, Jul 25, 2016 at 5:05 PM, Marcin Ziemiński <ziem...@gmail.com> wrote:

> I agree that the script should be rewritten in Ruby and I have already done
> that.
> In addition to that I have copied the entire old gallery to the yaml file
> and updated the docs with guidelines on how to submit new templates.
> Introduced changes
> <
> https://github.com/apache/incubator-predictionio/compare/develop...Ziemin:template-gallery
> >
>
> śr., 20.07.2016 o 16:56 użytkownik Pat Ferrel <p...@occamsmachete.com>
> napisał:
>
> > If we used the same mechanisms supported in the site generator it would
> > simplify support. Yaml is fine but isn’t middleman in ruby?Maybe you
> don’t
> > need a separate Python script.
> >
> > On Jul 20, 2016, at 9:50 AM, Donald Szeto <don...@apache.org> wrote:
> >
> > Hey Marcin,
> >
> > I think this looks great for now! I think it is fine to put
> templates.yaml
> > anywhere inside docs. We just have to update the instruction in the
> Engine
> > Template Submission section so that template contributors know where to
> > edit templates.yaml as a way of "submission".
> >
> > Any thoughts from the wider community is welcome.
> >
> > Regards,
> > Donald
> >
> > On Tue, Jul 19, 2016 at 4:48 PM, Marcin Ziemiński <ziem...@gmail.com>
> > wrote:
> >
> > > Hey Donald,
> > >
> > > I added the script to my local version of PredictionIO repository. It
> is
> > > being called from config.rb file during website build process.
> > > After some tweaking it looks like this:
> > > http://imgur.com/a/SDrl3
> > > The stars are visible now.
> > > I also put the templates.yaml file in the repo in the same directory. I
> > am
> > > quite not sure what would be the perfect place for it.
> > >
> > > wt., 19.07.2016 o 11:10 użytkownik Donald Szeto <don...@apache.org>
> > > napisał:
> > >
> > >> Hi Marcin,
> > >>
> > >> This is a great draft! Since this is generating a Markdown file, one
> > >> suggestion I could think of is to make this an integral part of the
> > > current
> > >> documentation build. Would you like to take a look at it and see how
> > >> feasible this could be?
> > >>
> > >> We used to have a Git branch called "livedoc" which branch off from
> > >> "master" on each release. Immediate documentation contributions and
> > > changes
> > >> go to the "livedoc" branch and get rebuilt and deployed immediately by
> > >> Travis. We can do something similar again.
> > >>
> > >> Regards,
> > >> Donald
> > >>
> > >> On Mon, Jul 18, 2016 at 5:59 PM, Marcin Ziemiński <ziem...@gmail.com>
> > >> wrote:
> > >>
> > >>> Hi!
> > >>>
> > >>> As mentioned in the other thread, there is a need for a new
> > >>> community-driven template gallery.
> > >>> I am proposing basic and simple approach based on github repository
> > >>> developed through pull requests. You can find the first draft here:
> > >>> https://github.com/Ziemin/pio-engine-templates
> > >>>
> > >>>   - The central part of this repo is the *templates.yaml *file*,
> > > *where
> > >>>   new engines are introduced in a unified way*. *At this moment I
> > > tried
> > >> to
> > >>>   keep the schema possibly similar to the old template gallery.
> > >>>   - README.md grouping and listing engines is not modifiable, as it
> is
> > >>>   generated by the python script - *generate_md.py*. Every update to
> > > the
> > >>>   yaml config should entail rerun of the script.
> > >>>
> > >>> Keeping a separate yaml file with all the information related to
> > > engines
> > >>> has both positive and negative sides. Obviously the most visible
> > > drawback
> > >>> is the requirement of re-runing the script manually. On the other
> hand,
> > >> it
> > >>> helps keep the entries in a consistent manner. What is more, future
> > >> changes
> > >>> to the esthetics of README.md file will rely exclusively on the
> script.
> > >> We
> > >>> can also imagine a situation, when someone would create a separate
> > >> website
> > >>> having some more user friendly capabilities like searching and
> > > filtering
> > >>> templates, which would link to the yaml file in the central
> repository.
> > >>>
> > >>> I tried to add the buttons with github stars for every template, but
> it
> > >>> appears that github ignores necessary html tags (iframe).
> > >>>
> > >>> I am aware that neither schema nor README.md is perfect. This repo
> is a
> > >>> draft and definitely could use some comments.
> > >>>
> > >>> Regards,
> > >>>
> > >>> Marcin
> > >>>
> > >>
> > >
> >
> >
>

Re: PIO-20 problems

[Donald Szeto]

Hi all,

I went ahead and pulled Pat's branch, performed a clean build, and repeated
the quick start guide of the Scala parallel recommendation template. I
could produce the same problem, and root caused it to a missing
conf/keystore.jks file.

I think with SSL now optional, we should not be distributing a KeyStore
file. We can either quick fix it now by putting this file back, or modify
SSLConfiguration to not look for this file when SSL support is off.

Regards,
Donald

On Thu, Aug 11, 2016 at 8:03 AM, Chan Lee  wrote:

> I want to clarify some points:
>
> 2) Deploying templates do not require SSL. If you execute
> ./make-distribution.sh using the current develop branch (provided you
> change the namespace in the template from io.prediction to
> org.apache.predictionio), you can deploy without SSL on localhost. The
> travis tests also do not use SSL and pass as can be seen in
> https://travis-ci.org/Ziemin/incubator-predictionio.
>
> 3) You can run the tests locally the same way it is run on travis
> ('python3 ${PIO_DIR}/tests/pio_tests/tests.py'). It is documented in the
> README in the same directory, but maybe this was not clear enough. If you
> have any additional questions or run into issues executing the tests,
> please let me know.
>
> Thanks,
> Chan
>
> On Thu, Aug 11, 2016 at 6:07 AM, Pat Ferrel  wrote:
>
>> I’m always disinclined to commit code that has not been tested. However
>> many things in the current state of the develop branch seem broken or at
>> least too big to address in a single commit.
>>
>> 1) Style test fail in Travis that are not runnable or at least have not
>> been documented for local build. I have fixed these.
>> 2) SSL seems to still be required for deploying an engine, PIO-1 may not
>> have addressed this. Has anyone tried to build and test a template yet
>> without SSL? Unless someone can state otherwise I’m inclined to ignore this
>> failure for now since it is out of scope for this commit.
>> 3) the test framework has been integrated into Travis but again no
>> documented way to run it locally and some of the travis errors seem
>> spurious. I am also not inclined to wait for this to be fixed unless
>> someone can point out real problems it is discovering and send instructions
>> for how to run it locally.
>>
>> Before the extra travis tests I was able to build and train a template,
>> which fails on deploy with an SSL config error. Since the PR does not
>> strictly touch any templates I am going to have to ignore this serious
>> issue and address it in Jira.
>>
>> Unless someone vetos this I plan to reluctantly push the PR with these
>> non-trivial issues remaining.
>>
>>
>>
>

Re: [Proposal] The new template gallery

[Donald Szeto]

Hi Marcin,

This is a great draft! Since this is generating a Markdown file, one
suggestion I could think of is to make this an integral part of the current
documentation build. Would you like to take a look at it and see how
feasible this could be?

We used to have a Git branch called "livedoc" which branch off from
"master" on each release. Immediate documentation contributions and changes
go to the "livedoc" branch and get rebuilt and deployed immediately by
Travis. We can do something similar again.

Regards,
Donald

On Mon, Jul 18, 2016 at 5:59 PM, Marcin Ziemiński  wrote:

> Hi!
>
> As mentioned in the other thread, there is a need for a new
> community-driven template gallery.
> I am proposing basic and simple approach based on github repository
> developed through pull requests. You can find the first draft here:
> https://github.com/Ziemin/pio-engine-templates
>
>- The central part of this repo is the *templates.yaml *file*, *where
>new engines are introduced in a unified way*. *At this moment I tried to
>keep the schema possibly similar to the old template gallery.
>- README.md grouping and listing engines is not modifiable, as it is
>generated by the python script - *generate_md.py*. Every update to the
>yaml config should entail rerun of the script.
>
> Keeping a separate yaml file with all the information related to engines
> has both positive and negative sides. Obviously the most visible drawback
> is the requirement of re-runing the script manually. On the other hand, it
> helps keep the entries in a consistent manner. What is more, future changes
> to the esthetics of README.md file will rely exclusively on the script. We
> can also imagine a situation, when someone would create a separate website
> having some more user friendly capabilities like searching and filtering
> templates, which would link to the yaml file in the central repository.
>
> I tried to add the buttons with github stars for every template, but it
> appears that github ignores necessary html tags (iframe).
>
> I am aware that neither schema nor README.md is perfect. This repo is a
> draft and definitely could use some comments.
>
> Regards,
>
> Marcin
>

Re: [Proposal] The new template gallery

[Donald Szeto]

Hey Marcin,

I think this looks great for now! I think it is fine to put templates.yaml
anywhere inside docs. We just have to update the instruction in the Engine
Template Submission section so that template contributors know where to
edit templates.yaml as a way of "submission".

Any thoughts from the wider community is welcome.

Regards,
Donald

On Tue, Jul 19, 2016 at 4:48 PM, Marcin Ziemiński <ziem...@gmail.com> wrote:

> Hey Donald,
>
> I added the script to my local version of PredictionIO repository. It is
> being called from config.rb file during website build process.
> After some tweaking it looks like this:
> http://imgur.com/a/SDrl3
> The stars are visible now.
> I also put the templates.yaml file in the repo in the same directory. I am
> quite not sure what would be the perfect place for it.
>
> wt., 19.07.2016 o 11:10 użytkownik Donald Szeto <don...@apache.org>
> napisał:
>
> > Hi Marcin,
> >
> > This is a great draft! Since this is generating a Markdown file, one
> > suggestion I could think of is to make this an integral part of the
> current
> > documentation build. Would you like to take a look at it and see how
> > feasible this could be?
> >
> > We used to have a Git branch called "livedoc" which branch off from
> > "master" on each release. Immediate documentation contributions and
> changes
> > go to the "livedoc" branch and get rebuilt and deployed immediately by
> > Travis. We can do something similar again.
> >
> > Regards,
> > Donald
> >
> > On Mon, Jul 18, 2016 at 5:59 PM, Marcin Ziemiński <ziem...@gmail.com>
> > wrote:
> >
> > > Hi!
> > >
> > > As mentioned in the other thread, there is a need for a new
> > > community-driven template gallery.
> > > I am proposing basic and simple approach based on github repository
> > > developed through pull requests. You can find the first draft here:
> > > https://github.com/Ziemin/pio-engine-templates
> > >
> > >- The central part of this repo is the *templates.yaml *file*,
> *where
> > >new engines are introduced in a unified way*. *At this moment I
> tried
> > to
> > >keep the schema possibly similar to the old template gallery.
> > >- README.md grouping and listing engines is not modifiable, as it is
> > >generated by the python script - *generate_md.py*. Every update to
> the
> > >yaml config should entail rerun of the script.
> > >
> > > Keeping a separate yaml file with all the information related to
> engines
> > > has both positive and negative sides. Obviously the most visible
> drawback
> > > is the requirement of re-runing the script manually. On the other hand,
> > it
> > > helps keep the entries in a consistent manner. What is more, future
> > changes
> > > to the esthetics of README.md file will rely exclusively on the script.
> > We
> > > can also imagine a situation, when someone would create a separate
> > website
> > > having some more user friendly capabilities like searching and
> filtering
> > > templates, which would link to the yaml file in the central repository.
> > >
> > > I tried to add the buttons with github stars for every template, but it
> > > appears that github ignores necessary html tags (iframe).
> > >
> > > I am aware that neither schema nor README.md is perfect. This repo is a
> > > draft and definitely could use some comments.
> > >
> > > Regards,
> > >
> > > Marcin
> > >
> >
>

Re: All Github PR closed

[Donald Szeto]

>
> > BTW Here are the Mahout instructions:
> http://mahout.apache.org/developers/github.html this would need to be
> modified to use the “develop” branch strategy. It seems less than ideal but
> is actually pretty easy in practice and much better than the purely Jira +
> patch file method.
>

+1.

Re: Time for the first podling report

[Donald Szeto]

Thanks Andrew!

On Wed, Jul 6, 2016 at 9:26 AM, Andrew Purtell <apurt...@apache.org> wrote:

> Posted to the wiki on https://wiki.apache.org/incubator/July2016.
>
> I made one edit while posting. The 'date of last release' section is for
> Apache branded releases. As there has not been an Apache branded release of
> PredictionIO yet, I wrote "No releases yet".
>
>
> On Tue, Jul 5, 2016 at 10:52 AM, Simon Chan <si...@salesforce.com> wrote:
>
> > Looks great. Thanks Donald and Andrew!
> >
> > Simon
> >
> >
> > On Tue, Jul 5, 2016 at 10:26 AM, Andrew Purtell <apurt...@apache.org>
> > wrote:
> >
> > > Looks great, +1
> > >
> > >
> > > On Tue, Jul 5, 2016 at 10:23 AM, Donald Szeto <don...@apache.org>
> wrote:
> > >
> > > > I'm taking a stab at the report. Thanks Andrew for his suggestions!
> > > >
> > > > ---
> > > >
> > > > PredictionIO
> > > >
> > > > 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.
> > > >
> > > > PredictionIO has been incubating since 2016-05-26.
> > > >
> > > > Three most important issues to address in the move towards
> graduation:
> > > >
> > > >   1. Unblock open issues and code merges and create the first Apache
> > > > branded release.
> > > >   2. Migrating the existing community to Apache infrastructure, and
> > > growing
> > > > the contributor base beyond initial committers.
> > > >   3. Implement template gallery in a more scalable, community-driven
> > > > portal, since PredictionIO relies on templates to function.
> > > >
> > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > > > aware of?
> > > >
> > > > Apache JIRA and GitHub integration does not seem to be working 100%.
> > > >
> > > > How has the community developed since the last report?
> > > >
> > > > We have been working to setup infrastructure on ASF, and are looking
> to
> > > > migrate the community from old to new infrastructure to allow further
> > > > growth.
> > > >
> > > > How has the project developed since the last report?
> > > >
> > > > An initial set of JIRA tickets based on outstanding issues before
> > > > incubation have been created. Initial committers / contributors are
> > ready
> > > > to work on them to march toward the first Apache branded release.
> > > >
> > > > Date of last release:
> > > >
> > > >   2016-04-11 (0.9.6, before incubation)
> > > >
> > > > When were the last committers or PMC members elected?
> > > >
> > > > 2016-06-06 (initial committers for incubation)
> > > >
> > > > Signed-off-by:
> > > >
> > > >   [ ](predictionio) Andrew Purtell
> > > >   [ ](predictionio) James Taylor
> > > >   [ ](predictionio) Lars Hofhansl
> > > >   [ ](predictionio) Luciano Resende
> > > >   [ ](predictionio) Xiangrui Meng
> > > >   [ ](predictionio) Suneel Marthi
> > > >
> > > > Shepherd/Mentor notes:
> > > >
> > > > On Fri, Jul 1, 2016 at 3:15 PM, Donald Szeto <don...@apache.org>
> > wrote:
> > > >
> > > > > Sounds good. Will try to fill in as much as possible before Tuesday
> > > > > evening.
> > > > >
> > > > > On Fri, Jul 1, 2016 at 3:13 PM, Andrew Purtell <
> apurt...@apache.org>
> > > > > wrote:
> > > > >
> > > > >> Because of the long weekend we won't have much time to work on
> this.
> > > > >> Hopefully we can have a draft ready by Tuesday evening.
> > > > >>
> > > > >> On Thu, Jun 30, 2016 at 2:56 PM, Andrew Purtell <
> > apurt...@apache.org>
> > > > >> wrote:
> > > > >>
> > > > >>> It's time to produce the first report for the Apache PredictionIO
> > > > >>> (incubating) podling!
> > > > >>>
> > > > >>> The repo

Re: Time for the first podling report

[Donald Szeto]

I'm taking a stab at the report. Thanks Andrew for his suggestions!

---

PredictionIO

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.

PredictionIO has been incubating since 2016-05-26.

Three most important issues to address in the move towards graduation:

  1. Unblock open issues and code merges and create the first Apache
branded release.
  2. Migrating the existing community to Apache infrastructure, and growing
the contributor base beyond initial committers.
  3. Implement template gallery in a more scalable, community-driven
portal, since PredictionIO relies on templates to function.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

Apache JIRA and GitHub integration does not seem to be working 100%.

How has the community developed since the last report?

We have been working to setup infrastructure on ASF, and are looking to
migrate the community from old to new infrastructure to allow further
growth.

How has the project developed since the last report?

An initial set of JIRA tickets based on outstanding issues before
incubation have been created. Initial committers / contributors are ready
to work on them to march toward the first Apache branded release.

Date of last release:

  2016-04-11 (0.9.6, before incubation)

When were the last committers or PMC members elected?

2016-06-06 (initial committers for incubation)

Signed-off-by:

  [ ](predictionio) Andrew Purtell
  [ ](predictionio) James Taylor
  [ ](predictionio) Lars Hofhansl
  [ ](predictionio) Luciano Resende
  [ ](predictionio) Xiangrui Meng
  [ ](predictionio) Suneel Marthi

Shepherd/Mentor notes:

On Fri, Jul 1, 2016 at 3:15 PM, Donald Szeto <don...@apache.org> wrote:

> Sounds good. Will try to fill in as much as possible before Tuesday
> evening.
>
> On Fri, Jul 1, 2016 at 3:13 PM, Andrew Purtell <apurt...@apache.org>
> wrote:
>
>> Because of the long weekend we won't have much time to work on this.
>> Hopefully we can have a draft ready by Tuesday evening.
>>
>> On Thu, Jun 30, 2016 at 2:56 PM, Andrew Purtell <apurt...@apache.org>
>> wrote:
>>
>>> It's time to produce the first report for the Apache PredictionIO
>>> (incubating) podling!
>>>
>>> The report must be posted by the end of day on Wednesday July 6 on the
>>> Incubator wiki as part of https://wiki.apache.org/incubator/July2016. I
>>> can take care of the posting but we will author the report together and
>>> you'll need to sign off on it.
>>>
>>> The report has this format:
>>>
>>> PredictionIOPredictionIO is an open source Machine Learning Server built on 
>>> top of state-of-the-art open source stack, that enables developers to 
>>> manage and deployproduction-ready predictive services for various kinds of 
>>> machine learningtasks.PredictionIO has been incubating since 
>>> 2016-05-26.Three most important issues to address in the move towards 
>>> graduation:  1.  2.  3.Any issues that the Incubator PMC (IPMC) or ASF 
>>> Board wish/need to beaware of?How has the community developed since the 
>>> last report?How has the project developed since the last report?Date of 
>>> last release:  -XX-XXWhen were the last committers or PMC members 
>>> elected?Signed-off-by:  [ ](predictionio) Andrew Purtell  [ ](predictionio) 
>>> James Taylor  [ ](predictionio) Lars Hofhansl  [ ](predictionio) Luciano 
>>> Resende  [ ](predictionio) Xiangrui Meng  [ ](predictionio) Suneel Marthi
>>>
>>> ​When considering
>>> ​what are the three most important issues to address in the move toward
>>> graduation, I recommend they be geared toward your development as a well
>>> functioning Apache project. Technical goals might be important to your
>>> success ultimately, but in this context that's all a means to an end, which
>>> is developing a healthy community at Apache around the code. Feel free to
>>> look at prior reports from other podlings in incubation for examples.
>>> Important goals could include:
>>>
>>> - Making your first Apache branded release
>>> - Growing the community beyond the initial committers
>>> - Completing the integration of prior PIO project features like the
>>> template gallery
>>>
>>>
>>>
>>> --
>>> Best regards,
>>>
>>>- Andy
>>>
>>> Problems worthy of attack prove their worth by hitting back. - Piet Hein
>>> (via Tom White)
>>>
>>
>>
>>
>> --
>> Best regards,
>>
>>- Andy
>>
>> Problems worthy of attack prove their worth by hitting back. - Piet Hein
>> (via Tom White)
>>
>
>

Re: [jira] [Commented] (PIO-1) Make SSL and authKey param authentication optional

[Donald Szeto]

I'm following up at https://issues.apache.org/jira/browse/INFRA-12182

On Mon, Jul 4, 2016 at 6:38 PM, Xusen Yin <yinxu...@gmail.com> wrote:

> It seems that we should link the Github repo with JIRA:
> https://help.github.com/articles/integrating-jira-with-your-projects/ <
> https://help.github.com/articles/integrating-jira-with-your-projects/>.
> This requires Github repo permission and JIRA administration.
>
>
> > On Jul 4, 2016, at 5:24 PM, Xusen Yin (JIRA) <j...@apache.org> wrote:
> >
> >
> >[
> https://issues.apache.org/jira/browse/PIO-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361856#comment-15361856
> ]
> >
> > Xusen Yin commented on PIO-1:
> > -
> >
> > I saw from Github there is a pull request for this JIRA:
> https://github.com/apache/incubator-predictionio/pull/244. However, it is
> not linked with the JIRA. Usually, PRs will be linked automatically with
> corresponding JIRAs in Spark. Any thought on this?
> >
> >> Make SSL and authKey param authentication optional
> >> --
> >>
> >>Key: PIO-1
> >>    URL: https://issues.apache.org/jira/browse/PIO-1
> >>Project: PredictionIO
> >> Issue Type: Improvement
> >>   Reporter: Donald Szeto
> >>   Priority: Critical
> >>
> >> Many PredictionIO SDKs and CLI commands have not been made to handle
> {{pio eventserver}} and {{pio deploy}} to be on HTTPS and protected by
> authentication. These protection measures are great, but should be rolled
> out in a better managed fashion to avoid infrastructural breakage of
> existing deployments.
> >
> >
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v6.3.4#6332)
>
>

Re: All Github PR closed

[Donald Szeto]

But not all PRs are closed, so it left me wondering if there is a set of
conditions that were triggered when GitHub integration was turned on.

On Thursday, June 30, 2016, Pat Ferrel  wrote:

> Maybe I missed the explanation but why are all the gitub PRs against the
> PIO account closed? This is not ideas, especially if some should be merged
> with the ASF git, because the PRs have user/branch info that can be used to
> hand-merge.
>
>

Re: Time for the first podling report

[Donald Szeto]

Sounds good. Will try to fill in as much as possible before Tuesday evening.

On Fri, Jul 1, 2016 at 3:13 PM, Andrew Purtell  wrote:

> Because of the long weekend we won't have much time to work on this.
> Hopefully we can have a draft ready by Tuesday evening.
>
> On Thu, Jun 30, 2016 at 2:56 PM, Andrew Purtell 
> wrote:
>
>> It's time to produce the first report for the Apache PredictionIO
>> (incubating) podling!
>>
>> The report must be posted by the end of day on Wednesday July 6 on the
>> Incubator wiki as part of https://wiki.apache.org/incubator/July2016. I
>> can take care of the posting but we will author the report together and
>> you'll need to sign off on it.
>>
>> The report has this format:
>>
>> PredictionIOPredictionIO is an open source Machine Learning Server built on 
>> top of state-of-the-art open source stack, that enables developers to manage 
>> and deployproduction-ready predictive services for various kinds of machine 
>> learningtasks.PredictionIO has been incubating since 2016-05-26.Three most 
>> important issues to address in the move towards graduation:  1.  2.  3.Any 
>> issues that the Incubator PMC (IPMC) or ASF Board wish/need to beaware 
>> of?How has the community developed since the last report?How has the project 
>> developed since the last report?Date of last release:  -XX-XXWhen were 
>> the last committers or PMC members elected?Signed-off-by:  [ ](predictionio) 
>> Andrew Purtell  [ ](predictionio) James Taylor  [ ](predictionio) Lars 
>> Hofhansl  [ ](predictionio) Luciano Resende  [ ](predictionio) Xiangrui Meng 
>>  [ ](predictionio) Suneel Marthi
>>
>> ​When considering
>> ​what are the three most important issues to address in the move toward
>> graduation, I recommend they be geared toward your development as a well
>> functioning Apache project. Technical goals might be important to your
>> success ultimately, but in this context that's all a means to an end, which
>> is developing a healthy community at Apache around the code. Feel free to
>> look at prior reports from other podlings in incubation for examples.
>> Important goals could include:
>>
>> - Making your first Apache branded release
>> - Growing the community beyond the initial committers
>> - Completing the integration of prior PIO project features like the
>> template gallery
>>
>>
>>
>> --
>> Best regards,
>>
>>- Andy
>>
>> Problems worthy of attack prove their worth by hitting back. - Piet Hein
>> (via Tom White)
>>
>
>
>
> --
> Best regards,
>
>- Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>

Re: Spark update

[Donald Szeto]

Hi Marcin,

This is really great work, and I agree that we should cross build against
different versions of Spark. If we have a cross building infrastructure set
up, we can be more flexible and adapt to different versions of external
dependencies as well, such as different versions of Hadoop and
Elasticsearch.

I cannot see any negative issues impacting the release cycle, besides
requiring more work to generate more versions of binaries. One thing that
we need to be careful of would be making sure that the core artifact, which
all engine templates depend on, be always compatible with different cross
build configurations of PredictionIO. I think with Spark 2 being the
starting point of Scala 2.11 adoption we should be pretty safe to assume
supporting only Spark < 2 for Scala 2.10 artifacts and Spark >= 2 for Scala
2.11 artifacts.

How do others think?

Regards,
Donald

On Mon, Aug 15, 2016 at 2:42 PM, Marcin Ziemiński  wrote:

> Hi,
>
> The recent version of Spark - 2.0.0 comes with many changes and
> improvements. The same is for the related Spark MLlib .
> -> Spark 2.0.0 release notes
> 
> -> Spark 2.0.0 overview
> 
> -> Announcement: DataFrame-based API is primary API
>  announcement-dataframe-based-api-is-primary-api>
>
> The changes are quite serious as they move the usage more towards DataSets
> instead of RDDs and offer many performance improvements.
> The current version of Spark that PredictionIO is built with is quite old
> 1.4.0 and soon some people will want to make use of the latest features in
> new templates.
> What is more, we could come up with a new kind of workflow different from
> DASE fitting better Spark ML pipelines, which would be a part of some next
> future release and would set a different direction of the project.
>
> I am aware that simply upgrading the version of Spark would break a lot of
> existing projects and cause many inconveniences to many people. Besides it
> requires bumping Scala version to 2.11. Having a separate branch for the
> new version is rather not maintainable, therefore I think that we could
> cross-build the project against two versions of Scala - 2.10 and 2.11,
> where the 2.11 version would be specifically for the new version of Spark.
> Any sources not compatible with two versions at the same time, could be
> split up between separate version-specific directories:
> src/main/scala-2.10/,
> src/main/scala-2.11/. Sbt as of 13.8 should not have problems with
> that -> merged
> PR 
> Such setup would make it possible to work on fixes and features available
> in both Scala versions, but more importantly it would let us add new
> functionalities specific to the latest Spark releases without breaking the
> old build.
>
> I have already tried to update Spark in PredictionIO in my own fork and I
> have managed to get a working version without modifying too much code ->
> diff
> here
>  compare/develop...Ziemin:upgrade#diff-fdc3abdfd754eeb24090dbd90aeec2ce>
> .
> Both unit-tests and integration tests were successful.
>
> What do you think? Would it affect the current release cycle in a negative
> way? Maybe someone has a better idea on how to perform this upgrade.
> Sticking to Spark 1.x version forever is probably not an option and the
> sooner we upgrade the better.
>
> Regards,
> Marcin
>

Re: 0.10.0 release

[Donald Szeto]

I agree with removing all reference to pio-build sbt plugin from engine
templates. We will not need the "version tracking" and the pioVersion
settings in engine template's sbt once we start tagging our officially
tested templates.

On Tue, Aug 16, 2016 at 2:17 PM, Pat Ferrel <p...@occamsmachete.com> wrote:

> Awesome, all we need to do is push to the right repo? Can you share the
> links?
>
> Donald mentioned that he though we could do without the pio sbt plugin, no?
>
>
> On Aug 16, 2016, at 2:05 PM, Chan Lee <chanlee...@gmail.com> wrote:
>
> I've changed the namespace for all repos marked "official" except for
> Universal Recommender and is running integration tests on them.
>
> Also, I believe the sbt plugin for pio-build needs to be updated.
>
> On Tue, Aug 16, 2016 at 12:50 PM, Pat Ferrel <p...@occamsmachete.com
> <mailto:p...@occamsmachete.com>> wrote:
> Let me know if anything is missing: https://issues.apache.org/
> jira/browse/PIO-24 <https://issues.apache.org/jira/browse/PIO-24>
>
>
> On Aug 16, 2016, at 12:26 PM, Pat Ferrel <p...@occamsmachete.com  p...@occamsmachete.com>> wrote:
>
> +1
>
>
> > On Aug 16, 2016, at 11:35 AM, Donald Szeto <don...@apache.org  don...@apache.org>> wrote:
> >
> > 1) I’ll volunteer to take a couple templates and put them in their own
> repos if we can get some created.
> > Sure. I believe Chan might have some converted repos as well.
> >
> > 2) do we have a gallery page yet? we had a good proposal, is it
> implemented?
> > It's already been merged in develop. Once we release the old template
> gallery will become a redirection to the new static page.
>
> This is needed only for historical reasons, right? The big blue Template
> button will go there directly after release, I assume.
>
> >
> > 3) What templates are worth inclusion? Seems like some of the ALS
> recommender ones are supersets of others do we need them all?
> > We should start with a core set of templates and one or a couple that
> focuses on a use case (since they are popular): vanilla, recommendation
> (both Scala and Java), similar product, classification, e-commerce, and
> text classification.
>
> sounds good, that is 7. @chan have you scrubbed any of these?
>
> >
> > 4) do we need “release” of these except through Apache git and Github?
> Since they are all built by users I suspect the normal Apache release
> process can be avoided for them, the full push to maven, binary hosting,
> etc.
> > I vote for maintaining the above set of templates to be at least working
> and passing integration tests for the main release. They do not necessarily
> go into the final binary distribution, but they should all be tagged and
> tested against with every release of PredictionIO.
>
> +1
>
> >
> > 5) We need someone to file Infra Jira’s to get repos. If someone can
> coach me on this I will do it.
> > My guess is we can just file an infrastructure ticket to spawn some
> discussion.
> >
>
> Who did the original request for repo? Can someone point me to the Jira,
> I’ll take it from there
>
> >
> > This might only add a week or so to the release date. If we don’t do it
> I bet it will be much more time spent in support and fixing later.
> > Agree. If we all agree let's make this the final major thing to do
> before 0.10.0 release to avoid feature creep.
> >
>
> +1, with the possible exception of fixing install.sh
> https://issues.apache.org/jira/browse/PIO-22 <https://issues.apache.org/
> jira/browse/PIO-22> One option is to remove it from the release, which I
> favor, discussion on the jira.
>
>
>
>
>
>

Re: 0.10.0 release

[Donald Szeto]

I am keeping track of the SGA progress on SFDC side and will keep you guys
updated.

On Tue, Aug 16, 2016 at 4:43 PM, Andrew Purtell <apurt...@apache.org> wrote:

> Thanks for the clarification. I could have phrased that better too. Not
> meant to sound abrasive.
>
> On Tue, Aug 16, 2016 at 3:53 PM, Pat Ferrel <p...@occamsmachete.com> wrote:
>
>> I don’t expect you to know where Simon is, I was just seeing if anyone on
>> the list knew, some are relatives and friends of his and even work at the
>> same location. I’m pretty sure Simon has the answers to take us to the SGA
>> or get one created.
>>
>> Not trying to dump work on you Andy, just trying to track down the
>> answers and not all questions are addressed to you :-)
>>
>>
>> On Aug 16, 2016, at 3:39 PM, Andrew Purtell <apurt...@apache.org> wrote:
>>
>> As I explained on the INFRA JIRA Pat I'm quite clear what was granted and
>> if it's not already in an Apache repo it was not granted by that SGA.
>>
>> Sure, Simon would be a reasonable place to start for a new SGA discussion.
>> I have no idea what he's up to, I'm not his keeper.
>>
>> On Tue, Aug 16, 2016 at 3:36 PM, Pat Ferrel <p...@occamsmachete.com>
>> wrote:
>>
>> > AFAIK Salesforce owns the code and Simon must have filled out the
>> original
>> > PIO grant, which may cover all the templates already. He also started
>> this
>> > discussion so I think we start with Simon unless someone knows better.
>> Is
>> > he on vacation?
>> >
>> >
>> > On Aug 16, 2016, at 3:30 PM, Andrew Purtell <apurt...@apache.org>
>> wrote:
>> >
>> > I see that Pat filed INFRA-12441 (
>> > https://issues.apache.org/jira/browse/INFRA-12441) which I read asks to
>> > import code from GitHub repositories under the old PIO organization not
>> yet
>> > granted to the ASF.
>> >
>> > This presents you with a great opportunity to learn how software grants
>> > work. (smile) Even when you are out of incubation this process will
>> still
>> > be necessary for imports of third party code not covered by an existing
>> > SGA, CCLA, or ICLA. The procedure is pretty simple, assuming a single
>> > rights holder (which is the case I believe for the scope of this
>> request).
>> > I encourage the PPMC to work out who will contact the rights holder to
>> > execute a SGA (https://www.apache.org/licenses/software-grant.txt) that
>> > covers all of the code you would like to import. When the granted code
>> is
>> > coming from a GitHub repository, Exhibit A should list all repository
>> URLs
>> > and exact SHAs desired for import covered by the grant.
>> >
>> > I'm happy to assist but the PPMC should take the lead. Good luck!
>> >
>> >
>> > On Tue, Aug 16, 2016 at 2:27 PM, Andrew Purtell <apurt...@apache.org>
>> > wrote:
>> >
>> >> Go to https://issues.apache.org/jira/ and log in. Find the read
>> 'Create'
>> >> button. There's a drop down menu immediately to the right of it. Open
>> > that
>> >> menu, then click on 'New Git Repository'.
>> >>
>> >> The original request was here: https://issues.apache.
>> >> org/jira/browse/INFRA-12112
>> >> The second request for site was here: https://issues.apache.
>> >> org/jira/browse/INFRA-12180
>> >>
>> >>
>> >> On Tue, Aug 16, 2016 at 12:26 PM, Pat Ferrel <p...@occamsmachete.com>
>> >> wrote:
>> >>
>> >>> +1
>> >>>
>> >>>
>> >>>> On Aug 16, 2016, at 11:35 AM, Donald Szeto <don...@apache.org>
>> wrote:
>> >>>>
>> >>>> 1) I’ll volunteer to take a couple templates and put them in their
>> own
>> >>> repos if we can get some created.
>> >>>> Sure. I believe Chan might have some converted repos as well.
>> >>>>
>> >>>> 2) do we have a gallery page yet? we had a good proposal, is it
>> >>> implemented?
>> >>>> It's already been merged in develop. Once we release the old template
>> >>> gallery will become a redirection to the new static page.
>> >>>
>> >>> This is needed only for historical reasons, right? The big blue
>> Template
>> >>> button will go there directly after release, I assume.
>> >>>
>> >>>>
>> >>>&

Feb 2017 Podling Report

[Donald Szeto]

Hi all,

Please review the following report. If this is good to go, please feel free
to go ahead and put this on the incubator wiki.

Regards,
Donald

---

PredictionIO

PredictionIO is an open source Machine Learning Server built on top of
a 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.

PredictionIO has been incubating since 2016-05-26. The initial code for
PredictionIO was granted on 2016-06-16. The second grant of PredictionIO
templates and SDKs was granted on 2016-09-20.

Three most important issues to address in the move towards graduation:

  1. Establish a formal release schedule and process, allowing for
dependable release cycles in a manner consistent with the Apache way.
  2. Grow the community to establish diversity of background.
  3. Transition remaining former PredictionIO users from google-groups to
ASF mailing lists.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

  None

How has the community developed since the last report?

  1. Both user and development mailing lists are more active than the last
report.
  2. There are major feature contributions from both new committers and the
community.
  3. The ecosystem around engine templates is gaining traction. There are
several new templates added to the engine template gallery.
  4. Local user groups are budding, e.g. Japan PredictionIO User Group.

How has the project developed since the last report?

  1. Several major feature contributions are under review.
  2. The second release is on track for early February release.
  3. There have been active discussions which have driven a solid roadmap
for future releases, especially centering around microservice architecture,
stateless builds, and running from anywhere with a centralized metadata
registry.

Date of the last release:

  Apache PredictionIO 0.10.0-incubating on 2016-10-17

When were the last committers or PMC members elected?

  Chan Lee was elected as committer and PMC member on Nov 14, 2016.
  Marcin Ziemiński was elected as committer and PMC member on Nov 14, 2016.

Re: Modifying the eventserver

[Donald Szeto]

(Please reply only to dev@)

Could you post the full error output after you run your command please?

The make-distribution.sh will make a binary distribution, plus allowing you
to run bin/pio in your code tree directly.

On Tue, Jan 24, 2017 at 2:29 PM Zehao Zhang <zehao0...@gmail.com> wrote:

> Hi Donald,
> Thanks for the response. So this makes another binary distribution of
> predictionio if I'm correct. Is there an easier way to test out the code
> for debugging purposes though? I tried doing "sbt/sbt "data/run-main
> org.apache.predictionio.data.api.Run"" but that gives out a classnotfound
> error for slf4jlogger,
>
> Best,
> -ZZ
> On Tue, Jan 24, 2017 at 2:11 PM Donald Szeto <don...@apache.org> wrote:
>
> Hi,
>
> This question is more suitable for the dev list, so I am moving the thread
> there.
>
> You will need to use make-distribution.sh for the command line to take
> effect. The command line uses the assembly JAR produced by the
> make-distribution.sh script.
>
> It would be great to add some kind of support in the pio command to
> support "sbt run-main". If you are interested please give it a try and make
> a pull request.
>
> Regards,
> Donald
>
> On Tue, Jan 24, 2017 at 1:48 PM Zehao Zhang <zehao0...@gmail.com> wrote:
>
> Hi, I'm trying to add more http endpoints to the eventserver for my
> project. After I have run the command: sbt/sbt "data/run-main
> org.apache.predictionio.data.api.Run", the code successfully compiles but I
> don't know how to run the newly compiled files. It looks like "pio
> eventserver" is still using the old code. Can you help me with this? Thank
> you.
>
> -ZZ
>
>
>
>

Moving Builds to Apache?

[Donald Szeto]

Hi all,

We have been depending on Travis in a while for building our unit and
integration tests, but it looks like the build queue wait time is now
pretty long on average, reducing developer velocity. I have tried to move
everything to container based testing, but it does not seem to reduce that
time.

Do you guys have any experience with using ASF's Jenkins to run tests based
on docker-compose? Also wondering if GitHub integration is in place so that
contributors would know whether their PR has passed test.

Thanks!

Regards,
Donald

Re: Binary distribution with sbt native packager

[Donald Szeto]

This would be a great addition! How are you handling submitting PIO's
artifact to Spark, specifically the CreateWorkflow class in tools?

Regards,
Donald

On Thu, Feb 16, 2017 at 4:10 PM Shinsuke Sugaya 
wrote:

> Hi
>
> Do you have a plan to use sbt native packager?
> In our forked branch, I added it under assembly directory.
> https://github.com/jpioug/incubator-predictionio
> Currently, both make-distribution.sh and
> sbt assembly/universal:packageBin work to build a binary distribution.
> I'd like to create rpm/deb package in the future...
> I'll contribute this task if you don't have any concerns.
>
> Regards,
>  shinsuke
>

Re: Created pull request for change in template Link

[Donald Szeto]

Hi,

Thanks for the PR. I noticed that the PR is against the develop branch,
which will update the template gallery in the next PIO release. If you want
it to be effective immediately, please PR against the livedoc branch
instead.

Regards,
Donald

On Wed, Jan 18, 2017 at 1:19 AM, Bansari Shah 
wrote:

> Hi,
> I have created pull request " *[PIO-50] updated templates.yaml #334* " and
> it'e relavant jiraa issue [PIO-50] to merge updated templates.yaml . It is
> updated with new template repository link for template 'Labelling topics
> with wikipedia [nlp]" .
>
> Please consider it.
>
> Thank you
>
> Regards,
> Bansari Shah
>

Re: 0.10.0 release

[Donald Szeto]

> entire repo and copy the files in templates/, or (2) use
> something like svn to download only the necessary subdirectory. I'd like to
> ask what everyone thinks should be the recommended approach. The
> documentation should be updated accordingly (instead of `pio template get`).
>
> 4) I'd like to ask if there are any ActionML/outside templates that should
> be included or updated. For instance, 
> template-scala-parallel-universal-recommendation
> in PredictionIO repo seems outdate compared to one in actionml repo.
>
>
> Thanks,
> Chan
>
>
>
> On Mon, Aug 8, 2016 at 9:16 AM, Marcin Ziemiński <ziem...@gmail.com
> <mailto:ziem...@gmail.com>> wrote:
> I think that this is a very good idea. Obviously it would require
> configuring more concurrent builds to finish in reasonable time, what
> should not be a problem. Besides, it would make the official templates be
> consistent with every next release of PredictionIO and what is very
> important - it would provide many different tests for the repository.
> Having working templates of different types could give us more material to
> test not only the reliability of PredictionIO, but also its performance
> with every change. It would require adding different types of tests and
> tools to gather runtime statistics, but this is something I would like to
> take a look at in the future.
>
> niedz., 7.08.2016 o 10:21 użytkownik Donald Szeto <don...@apache.org
> <mailto:don...@apache.org>>
> napisał:
>
> > We can also make these templates part of the integration test that Chan
> and
> > Marcin just submitted (
> > https://github.com/apache/incubator-predictionio/pull/267 <
> https://github.com/apache/incubator-predictionio/pull/267>). That way we
> > can
> > make commitment to included templates be part of every committer's
> effort.
> > Just my 2c.
> >
> > On Sun, Aug 7, 2016 at 9:47 AM, Pat Ferrel <p...@occamsmachete.com
> <mailto:p...@occamsmachete.com>> wrote:
> >
> > > If this sound ok, I propose the process be:
> > > 1) inclusion in the gallery is a PR to the yaml gallery file. This is
> > > reviewable by all but takes only one committer to approve and merge.
> > > 2) submission for inclusion in the project can be a PR to the new
> > > templates directory as Simon suggests. But this may require a more
> formal
> > > vote, and come with some commitment for support and possibly
> > consideration
> > > of the author for committer status.
> > >
> > > Someone who knows Apache rules better than me may know the type of vote
> > to
> > > have for #2, maybe this is only informal review and single committer
> > > acceptance too as long as the committer is willing to support the
> > template.
> > >
> > > As far as the Salesforce templates marked official, I’d hope that most
> > > would be donated. According to the proposed rules all we need is a PR
> for
> > > each. And again a big thanks to Salesforce!
> > >
> > >
> > > On Aug 4, 2016, at 2:55 PM, Pat Ferrel <p...@occamsmachete.com  p...@occamsmachete.com>> wrote:
> > >
> > > Actually this is mostly a fine idea but I think the bigger question is
> > how
> > > do we treat templates in general.
> > >
> > > IMO the maintaining author can decide to contribute them or not and the
> > > committers can decide to accept or not. For example in the case of the
> > UR I
> > > may decide to support and maintain it outside of Apache while some from
> > > Salesforce might be submitted as donations.  Donation comes at some
> > > obligation. There are lots of examples in Mahout of algorithms whose
> > > authors no longer support them. These are slowly being deprecated and
> > > removed so I’d like to see a method that avoids this issue.
> > >
> > > If we allow maintainers to submit templates to the Gallery with a link
> to
> > > code as well as support then donating the template code to Apache is
> > > independent of acceptance to the Gallery. Any template donated to
> Apache
> > > should come with some commitment by the author to support it there
> > > indefinitely and perhaps even acceptance as a PIO committer—and if they
> > > disappear or don’t support the template it is easy to deprecate/remove.
> > >
> > > That means if Salesforce wants to donate the templates it
> > maintains—great.
> > > Personally I'd would vote for acceptance of most of them. Then the
> > support
> > > link can be to the Apache user list

Re: Why is the MaxNumberOfEventsPerBatchRequest is 50?

[Donald Szeto]

Hi Mani Teja,

I believe this value is just a measure to avoid sending in huge batches in
a single request. I highly encourage you to make this configurable so that
other users do not need to rebuild from source should they find this value
too small for their use case.

Please feel free to file a JIRA ticket, discuss your approach on dev@ and
work on a patch!

Regards,
Donald

On Tue, Aug 16, 2016 at 12:13 AM, Mani Teja  wrote:

> Can anyone please help me out with this?
> If i change this value to a higher number, will this work? What is the
> reason behind fixing this value.
>
> Thanks,
> Mani Teja
>

Re: Concern for PIO user community

[Donald Szeto]

I just added huge banners to both Google groups web UI. Hope that would
help. Technically I do not think it is possible to set up forwarding. I
will sync up internally whether it's okay to turn on GGroup for the
meanwhile.

Also, last weekend the *.prediction.io domains have been migrated to
redirect to predictionio.incubator.apache.org. This should hopefully remove
all public references to Google Groups. Let's hope that would also clear up
something.

I feel that we should not support GitHub issues going forward just like all
other Apache projects are doing. For now I am manually redirecting traffic
to Apache mailing lists and JIRA.

On Mon, Aug 22, 2016 at 11:33 AM, Pat Ferrel  wrote:

> We shut off all posts to the Goggle Group for PIO. This seems to have
> resulted in loosing virtually all users. We are getting comments on github
> issues asking if the project is defunct. Notice almost no user@ emails
> when there were several a day on the Google Group—why?
>
> At the time of the last post we didn’t have instructions for how to join
> the mailing list. We now do so instructions posted to the group can now be
> updated. Also is it possible to turn on posting again and have the posts
> forwarded to u...@predictionio.incubator.apache.org ? We can turn off in
> time once people have had a reasonable amount of time to switch over.
> People need time to react, like an @Deprecated notice.
>
> Not sure who has the admin keys to the group, Donald? Simon?

Re: Sep 2016 Podling report

[Donald Szeto]

Looks good to me. Thanks Suneel and Pat!

On Thu, Sep 1, 2016 at 9:41 PM, Suneel Marthi  wrote:

> Please find below the proposed Podling PIO report for Sep 2016, let me know
> of any changes/additions you would like to make.
>
> 
>
> Apache PredictionIO (Incubating)
>
> Apache PredictionIO (incubating) is an open source Machine Learning Server
> built on top of state-of-the-art open source stack for developers and data
> scientists create predictive engines for any machine learning task.
>
> PredictionIO has been incubating since 2016-05-26. The initial code for
> PredictionIO was granted on 2016-06-16. A second grant of PredictionIO
> Templates is in process and anticipated to be complete in September 2016.
>
> The important issues to address in the move towards graduation:
>
>
>1.
>
>Establish a formal release schedule and process, allowing for dependable
>release cycles in a manner consistent with the Apache way.
>2.
>
>Grow the community to establish diversity of background.
>
>
> Any issues the Incubator PMC or ASF Board wish/need to be aware of?
>
> None
>
> How has the community developed since the last report?
>
>1.
>
>Users have begun to migrate from the old Google group to the Apache user
>list
>2.
>
>3 new contributors have become active with consistent  acceptable
>contributions and are on path to become committers
>
>
>
> How has the project developed since the last report?
>
>1.
>
>The old Prediction.io docs site has been migrated to
>http://predictionio.incubator.apache.org
>2.
>
>7 templates have been ported to Apache PredictionIO, pending a decision
>on a 2nd grant. The pending 2nd grant will not block a PredictionIO
> release.
>
>
> Date of last release:
>
> No releases have been made yet. Present activities are directed towards
> first Apache Release planned for September 2016.
>
> When were the last committers or PMC members elected?
>
> Paul Li was elected as committer and PMC member on Aug 30, 2016
>

Release Manager

[Donald Szeto]

Hi all,

If there's no objection, I'll volunteer myself to be the release manager
for the first Apache release. I'll make a few more documentation updates,
and start shepherding the Apache release process.

Regards,
Donald

Incubation sponsor

[Donald Szeto]

Hi all,

I am in the process of putting together a release candidate and figured we
need to add a disclaimer (
http://incubator.apache.org/guides/branding.html#disclaimers). It is not
immediately obvious to me who our TLP incubation sponsor is. Any ideas?

Regards,
Donald

Re: [VOTE]: Apache PredictionIO (incubating) 0.10.0 Release

[Donald Szeto]

+1

On Thu, Sep 15, 2016 at 9:04 AM, Pat Ferrel <p...@occamsmachete.com> wrote:

> Donald, you get a vote too. We need 3 (assuming no one is -1) to graduate
> this.
>
> Everyone please vote!
>
> On Sep 14, 2016, at 10:13 AM, Matthew Tovbin <tovb...@apache.org> wrote:
>
> +1
>
> On Wed, Sep 14, 2016 at 10:12 AM, Pat Ferrel <p...@occamsmachete.com>
> wrote:
>
> > +1
> >
> >
> > On Sep 13, 2016, at 11:55 AM, Donald Szeto <donald.sz...@gmail.com>
> wrote:
> >
> > This is the vote for 0.10.0 of Apache PredictionIO (incubating).
> >
> > The vote will run for at least 72 hours and will close on Sept 16th,
> 2016.
> >
> > The artifacts can be downloaded here:
> > https://dist.apache.org/repos/dist/dev/incubator/predictioni
> > o/0.10.0-incubating-rc1/
> > or
> > from the Maven staging repo here:
> > https://repository.apache.org/content/repositories/orgapache
> > predictionio-1001/
> >
> > All JIRAs completed for this release are tagged with 'FixVersion =
> 0.10.0'.
> > You can view them here:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> > ctId=12320420=12337844
> >
> > The artifacts have been signed with Key : 8BF4ABEB
> >
> > Please vote accordingly:
> >
> > [ ] +1, accept RC as the official 0.10.0 release
> > [ ] -1, do not accept RC as the official 0.10.0 release because...
> >
> >
>
>

New PMC member and committer: Paul Li

[Donald Szeto]

Hi all,

The Project Management Committee (PMC) for Apache PredictionIO (incubating)
has asked Paul Li to become a PMC member and committer, and we are pleased
to announce that he has accepted.

Paul Li was a regular committer to the PredictionIO codebase before its
donation to the Apache Software Foundation. Having him join forces with us
would be beneficial for PredictionIO's growth.

Being a committer enables easier contribution to the project since there is
no need to go via the patch submission process. This should enable better
productivity. Being a PMC member enables assistance with the management and
to guide the direction of the project.

Please join us in welcoming Paul.

Regards,
Donald

Re: Regarding New Release

[Donald Szeto]

Hi Bansari,

I'm pleased to tell you that RC5 has just passed IPMC vote. The release
should be out in the next 24 hours.

Templates will need to use the new artifacts with "org.apache.predictionio"
group ID. They should still be compatible with Scala 2.10 and Spark >1.4.0.

Regards,
Donald

On Fri, Oct 7, 2016 at 6:19 AM, Bansari Shah 
wrote:

> Hi,
>
> Can you please suggest when new version of apache predictionIO will get
> released ?
> and will the templates configured with scala-2.10.6, predictionIO
> 0.9.7-SNAPSHOT and spark 1.5.1 be compatible with new release ?
>
> Thank you
>
> Regards,
> Bansari
>

[ANNOUNCE] Apache PredictionIO 0.10.0-incubating Release

[Donald Szeto]

The Apache PredictionIO team would like to announce the release of Apache
PredictionIO 0.10.0-incubating.

Apache PredictionIO (incubating) 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.

More details regarding Apache PredictionIO (incubating) can be found here:
http://predictionio.incubator.apache.org/

The release artifacts can be downloaded here:
https://dist.apache.org/repos/dist/release/incubator/predictionio/0.10.0-incubating/

All JIRAs completed for this release are tagged with 'FixVersion =
0.10.0-incubating'; the release notes can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320420=12337844

Thanks!
The Apache PredictionIO Team

DISCLAIMER
Apache PredictionIO (incubating) is an effort undergoing incubation at the
Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects. While incubation status is not necessarily a reflection of
the completeness or stability of the code, it does indicate that the
project has yet to be fully endorsed by the ASF.

[RESULT][VOTE] Apache PredictionIO (incubating) 0.10.0 Release (RC5)

[Donald Szeto]

The vote passes, with 6 +1 votes (5 binding) and no -1 votes.

+1 Alex Merritt (binding)
+1 Donald Szeto (binding)
+1 Kenneth Chan
+1 Matthew Tovbin (binding)
+1 Pat Ferrel (binding)
+1 Suneel Marthi (binding)

Thanks all for voting.

Apache PredictionIO (incubating) 0.10.0 RC5 has been accepted as the
release. The voting will now proceed to the Incubator PMC.

Regards,
Donald

On Sun, Oct 2, 2016 at 4:04 PM, Alex Merritt <leca...@gmail.com> wrote:

> +1 binding
>
> On Sat, Oct 1, 2016 at 3:17 PM, Donald Szeto <don...@apache.org> wrote:
>
> > Hi all,
> >
> > Thanks for voting. Please indicate binding or non-binding when you cast
> > your vote. Release votes require 3 binding +1's from PMC to pass.
> >
> > Regards,
> > Donald
> >
> > On Saturday, October 1, 2016, Kenneth Chan <kenn...@apache.org> wrote:
> >
> > > +1
> > >
> > > On Saturday, October 1, 2016, Pat Ferrel <p...@occamsmachete.com
> > > <javascript:;>> wrote:
> > >
> > > > +1 binding
> > > >
> > > > On Oct 1, 2016, at 10:20 AM, Suneel Marthi <suneel.mar...@gmail.com
> > > <javascript:;>
> > > > <javascript:;>> wrote:
> > > >
> > > > +1 binding
> > > >
> > > > On Sat, Oct 1, 2016 at 12:05 PM, Matthew Tovbin <matt...@tovbin.com
> > > <javascript:;>
> > > > <javascript:;>> wrote:
> > > >
> > > > > +1
> > > > >
> > > > > - Matthew
> > > > >
> > > > > On Oct 1, 2016 00:18, "Donald Szeto" <don...@apache.org
> > <javascript:;>
> > > <javascript:;>>
> > > > wrote:
> > > > >
> > > > >> This is the vote for 0.10.0 of Apache PredictionIO (incubating).
> > > > >>
> > > > >> The vote will run for at least 72 hours and will close on Oct 3rd,
> > > 2016.
> > > > >>
> > > > >> RC2 adds the "apache-" prefix to artifact filenames.
> > > > >>
> > > > >> RC3 adds on top of RC2 with proper licenses and notices embedded
> in
> > > the
> > > > >> Maven artifacts. It also changes the license of the documentation
> > from
> > > > >> Creative Commons to APLv2.
> > > > >>
> > > > >> RC4 fixes a build error of RC3.
> > > > >>
> > > > >> RC5 fixes issues raised by the IPMC:
> > > > >> - Removed 3rd party dependencies from documentation sources
> > > > >> - Fixed incorrect licensing of semver.sh from ASF to BSD
> > > > >> - Moved MySQL connector to optional scope
> > > > >>
> > > > >> The release candidate artifacts can be downloaded here:
> > > > >> https://dist.apache.org/repos/dist/dev/incubator/
> > predictionio/0.10.0-
> > > > >> incubating-rc5/
> > > > >>
> > > > >> Test results of RC5 can be found here:
> > > > >> https://travis-ci.org/apache/incubator-predictionio/builds/
> > 164221633
> > > > >>
> > > > >> Maven artifacts are built from the release candidate artifacts
> > above,
> > > > and
> > > > >> are provided as convenience for testing with engine templates. The
> > > Maven
> > > > >> artifacts are provided at the Maven staging repo here:
> > > > >> https://repository.apache.org/content/repositories/
> > > > >> orgapachepredictionio-1009/
> > > > >>
> > > > >> All JIRAs completed for this release are tagged with 'FixVersion =
> > > > > 0.10.0'.
> > > > >> You can view them here:
> > > > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > >> projectId=12320420=12337844
> > > > >>
> > > > >> The artifacts have been signed with Key : 8BF4ABEB
> > > > >>
> > > > >> Please vote accordingly:
> > > > >>
> > > > >> [ ] +1, accept RC as the official 0.10.0 release
> > > > >> [ ] -1, do not accept RC as the official 0.10.0 release because...
> > > > >>
> > > > >
> > > >
> > > >
> > >
> >
>

[CANCEL][VOTE]: Apache PredictionIO (incubating) 0.10.0 Release (RC3)

[Donald Szeto]

On Wed, Sep 21, 2016 at 10:41 AM, Donald Szeto <don...@apache.org> wrote:

> Sorry guys. Calling this off until it's fixed.
>
> On Wed, Sep 21, 2016 at 10:39 AM, Suneel Marthi <suneel.mar...@gmail.com>
> wrote:
>
>> -1 binding
>>
>> Got an exception
>>
>> info] SHA-1: b826217743fdd03b6656eb5750b6a775df77cc92
>>
>> [info] Packaging
>> /Users/smarthi/Downloads/apache-predictionio-0.10.0-incubati
>> ng-rc3/assembly/pio-assembly-0.10.0-incubating-rc3.jar
>> ...
>>
>> java.util.zip.ZipException: duplicate entry: META-INF/LICENSE.txt
>>
>> at java.util.zip.ZipOutputStream.putNextEntry(ZipOutputStream.java:233)
>>
>> at java.util.jar.JarOutputStream.putNextEntry(JarOutputStream.java:109)
>>
>> at sbt.IO$.sbt$IO$$addFileEntry$1(IO.scala:445)
>>
>> at sbt.IO$$anonfun$sbt$IO$$writeZip$2.apply(IO.scala:454)
>>
>> at sbt.IO$$anonfun$sbt$IO$$writeZip$2.apply(IO.scala:454)
>>
>> at scala.collection.Iterator$class.foreach(Iterator.scala:727)
>>
>> at scala.collection.AbstractIterator.foreach(Iterator.scala:1157)
>>
>> at scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
>>
>> at scala.collection.AbstractIterable.foreach(Iterable.scala:54)
>>
>> at sbt.IO$.sbt$IO$$writeZip(IO.scala:454)
>>
>> at sbt.IO$$anonfun$archive$1.apply(IO.scala:410)
>>
>> at sbt.IO$$anonfun$archive$1.apply(IO.scala:408)
>>
>> at sbt.IO$$anonfun$withZipOutput$1.apply(IO.scala:498)
>>
>> at sbt.IO$$anonfun$withZipOutput$1.apply(IO.scala:485)
>>
>> at sbt.Using.apply(Using.scala:24)
>>
>> at sbt.IO$.withZipOutput(IO.scala:485)
>>
>> at sbt.IO$.archive(IO.scala:408)
>>
>> at sbt.IO$.jar(IO.scala:392)
>>
>> at sbt.Package$.makeJar(Package.scala:97)
>>
>> at sbtassembly.Assembly$.sbtassembly$Assembly$$makeJar$1(
>> Assembly.scala:40)
>>
>> at sbtassembly.Assembly$$anonfun$5$$anonfun$apply$4.apply(Assem
>> bly.scala:79)
>>
>> at sbtassembly.Assembly$$anonfun$5$$anonfun$apply$4.apply(Assem
>> bly.scala:75)
>>
>> at sbt.Tracked$$anonfun$outputChanged$1.apply(Tracked.scala:57)
>>
>> at sbt.Tracked$$anonfun$outputChanged$1.apply(Tracked.scala:52)
>>
>> at sbtassembly.Assembly$.apply(Assembly.scala:83)
>>
>> at sbtassembly.Assembly$$anonfun$assemblyTask$1.apply(Assembly.scala:241)
>>
>> at sbtassembly.Assembly$$anonfun$assemblyTask$1.apply(Assembly.scala:238)
>>
>> at scala.Function1$$anonfun$compose$1.apply(Function1.scala:47)
>>
>> at sbt.$tilde$greater$$anonfun$$u2219$1.apply(TypeFunctions.scala:40)
>>
>> at sbt.std.Transform$$anon$4.work(System.scala:63)
>>
>> at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute
>> .scala:226)
>>
>> at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute
>> .scala:226)
>>
>> at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:17)
>>
>> at sbt.Execute.work(Execute.scala:235)
>>
>> at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:226)
>>
>> at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:226)
>>
>> at
>> sbt.ConcurrentRestrictions$$anon$4$$anonfun$1.apply(Concurre
>> ntRestrictions.scala:159)
>>
>> at sbt.CompletionService$$anon$2.call(CompletionService.scala:28)
>>
>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>
>> at java.util.concurrent.Executors$RunnableAdapter.call(
>> Executors.java:511)
>>
>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1142)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.java:617)
>>
>> at java.lang.Thread.run(Thread.java:745)
>>
>> [error] (tools/*:assembly) java.util.zip.ZipException: duplicate entry:
>> META-INF/LICENSE.txt
>>
>> [error] Total time: 25 s, completed Sep 21, 2016 1:35:51 PM
>>
>> On Wed, Sep 21, 2016 at 1:27 PM, Donald Szeto <don...@apache.org> wrote:
>>
>> > This is the vote for 0.10.0 of Apache PredictionIO (incubating).
>> >
>> > The vote will run for at least 72 hours and will close on Sept 24th,
>> 2016.
>> >
>> > RC3 adds on top of RC2 with proper licenses and notices embedded in the
>> > Maven artifacts. It also changes the license of the documentation from
>> > Creative Commons to APLv2.
>> >
>> > The release candidate artifacts can be downloa

[VOTE]: Apache PredictionIO (incubating) 0.10.0 Release (RC3)

[Donald Szeto]

This is the vote for 0.10.0 of Apache PredictionIO (incubating).

The vote will run for at least 72 hours and will close on Sept 24th, 2016.

RC3 adds on top of RC2 with proper licenses and notices embedded in the
Maven artifacts. It also changes the license of the documentation from
Creative Commons to APLv2.

The release candidate artifacts can be downloaded here:
https://dist.apache.org/repos/dist/dev/incubator/predictionio/0.10.0-incubating-rc3/

Maven artifacts are built from the release candidate artifacts above, and
are provided as convenience for testing with engine templates. The Maven
artifacts are provided at the Maven staging repo here:
https://repository.apache.org/content/repositories/orgapachepredictionio-1005/

All JIRAs completed for this release are tagged with 'FixVersion = 0.10.0'.
You can view them here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320420=12337844

The artifacts have been signed with Key : 8BF4ABEB

Please vote accordingly:

[ ] +1, accept RC as the official 0.10.0 release
[ ] -1, do not accept RC as the official 0.10.0 release because...

[VOTE]: Apache PredictionIO (incubating) 0.10.0 Release (RC2)

[Donald Szeto]

This is the vote for 0.10.0 of Apache PredictionIO (incubating).

The only difference between RC1 and RC2 is adding the "apache-" prefix to
Maven artifacts.

The vote will run for at least 72 hours and will close on Sept 21st, 2016.

The artifacts can be downloaded here:
https://dist.apache.org/repos/dist/dev/incubator/predictionio/0.10.0-incubating-rc2/
or from the Maven staging repo here:
https://repository.apache.org/content/repositories/orgapachepredictionio-1003/

All JIRAs completed for this release are tagged with 'FixVersion = 0.10.0'.
You can view them here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320420=12337844

The artifacts have been signed with Key : 8BF4ABEB

Please vote accordingly:

[ ] +1, accept RC as the official 0.10.0 release
[ ] -1, do not accept RC as the official 0.10.0 release because...

Re: [VOTE]: Apache PredictionIO (incubating) 0.10.0 Release

[Donald Szeto]

Yes. Many of them are sources, docs, poms and signatures though.

On Sun, Sep 18, 2016 at 6:02 PM, Suneel Marthi <suneel.mar...@gmail.com>
wrote:

> So all of these artifacts need to be verified and validated ?
>
> https://repository.apache.org/content/repositories/
> orgapachepredictionio-1003/org/apache/predictionio/
>
>
>
> On Mon, Sep 19, 2016 at 2:59 AM, Donald Szeto <don...@apache.org> wrote:
>
> > I will start a new voting thread. The staging repo should contain just
> > PredictionIO artifacts.
> >
> > On Sun, Sep 18, 2016 at 5:57 PM, Suneel Marthi <smar...@apache.org>
> wrote:
> >
> > > the MAven staging repo brings up whole load of artifacts, which ones r
> we
> > > voting on again ?
> > >
> > > On Mon, Sep 19, 2016 at 2:49 AM, Donald Szeto <don...@apache.org>
> wrote:
> > >
> > > > I have prepared a RC2. The artifacts can be downloaded here:
> > > > https://dist.apache.org/repos/dist/dev/incubator/
> predictionio/0.10.0-
> > > > incubating-rc2/
> > > > or from the Maven staging repo here:
> > > > https://repository.apache.org/content/repositories/
> > > > orgapachepredictionio-1003/
> > > > .
> > > >
> > > > Do we need to vote on the RC2 again?
> > > >
> > > > On Sat, Sep 17, 2016 at 2:10 PM, Pat Ferrel <p...@occamsmachete.com>
> > > wrote:
> > > >
> > > > > Hate to make more work for you but the new name would also maybe
> > avoid
> > > > > some confusion for older migrating users.
> > > > >
> > > > > On Sep 16, 2016, at 9:02 AM, Donald Szeto <don...@apache.org>
> wrote:
> > > > >
> > > > > If everyone agrees that the artifacts should have an "apache-"
> > prefix,
> > > I
> > > > > will roll an RC2 shortly. Since the namespace change is
> unavoidable,
> > > > might
> > > > > as well get all artifact name changes done in one shot for good.
> > > > >
> > > > > On Friday, September 16, 2016, Andrew Purtell <
> > > andrew.purt...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Let me double check.
> > > > > >
> > > > > >> On Sep 16, 2016, at 7:33 AM, Alex Merritt <
> > emergentor...@apache.org
> > > > > > <javascript:;>> wrote:
> > > > > >>
> > > > > >> I believe it depends on which of the two votes you mean. For the
> > > > podling
> > > > > >> vote, PPMC votes are binding, for the incubator vote,  IPMC
> votes
> > > are,
> > > > > > no?
> > > > > >>
> > > > > >>> On Sep 15, 2016 9:42 PM, "Andrew Purtell" <
> > > andrew.purt...@gmail.com
> > > > > > <javascript:;>> wrote:
> > > > > >>>
> > > > > >>> I believe 'binding' only applies to IPMC.
> > > > > >>>
> > > > > >>>>> On Sep 15, 2016, at 12:49 PM, Suneel Marthi <
> > > > suneel.mar...@gmail.com
> > > > > > <javascript:;>>
> > > > > >>>> wrote:
> > > > > >>>>
> > > > > >>>> Folks, When u vote please specify "+1 Binding" if u r a PMC
> > > member.
> > > > > Its
> > > > > >>>> only the PMC votes that count for a release to pass.
> > > > > >>>>
> > > > > >>>>
> > > > > >>>>
> > > > > >>>>> On Thu, Sep 15, 2016 at 2:11 PM, Robert Lu <
> > > robberp...@outlook.com
> > > > > > <javascript:;>>
> > > > > >>> wrote:
> > > > > >>>>>
> > > > > >>>>> +1
> > > > > >>>>>
> > > > > >>>>>> On Sep 15, 2016, at 01:13, Matthew Tovbin <
> tovb...@apache.org
> > > > > > <javascript:;>> wrote:
> > > > > >>>>>>
> > > > > >>>>>> +1
> > > > > >>>>>>
> > > > > >>>>>>> On Wed, Sep 14, 2016 at 10:12 AM, Pat Ferrel <
> > > > > p...@occamsmachete.com
> > > > > > <javascript:;>>
> > > > > >>>>>> wrote:
> > > > > >>>>>>
> > > > > >>>>>>> +1
> > > > > >>>>>>>
> > > > > >>>>>>>
> > > > > >>>>>>> On Sep 13, 2016, at 11:55 AM, Donald Szeto <
> > > > donald.sz...@gmail.com
> > > > > > <javascript:;>>
> > > > > >>>>> wrote:
> > > > > >>>>>>>
> > > > > >>>>>>> This is the vote for 0.10.0 of Apache PredictionIO
> > > (incubating).
> > > > > >>>>>>>
> > > > > >>>>>>> The vote will run for at least 72 hours and will close on
> > Sept
> > > > > 16th,
> > > > > >>>>> 2016.
> > > > > >>>>>>>
> > > > > >>>>>>> The artifacts can be downloaded here:
> > > > > >>>>>>> https://dist.apache.org/repos/
> dist/dev/incubator/predictioni
> > > > > >>>>>>> o/0.10.0-incubating-rc1/
> > > > > >>>>>>> or
> > > > > >>>>>>> from the Maven staging repo here:
> > > > > >>>>>>> https://repository.apache.org/
> content/repositories/orgapache
> > > > > >>>>>>> predictionio-1001/
> > > > > >>>>>>>
> > > > > >>>>>>> All JIRAs completed for this release are tagged with
> > > 'FixVersion
> > > > =
> > > > > >>>>> 0.10.0'.
> > > > > >>>>>>> You can view them here:
> > > > > >>>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> proje
> > > > > >>>>>>> ctId=12320420=12337844
> > > > > >>>>>>>
> > > > > >>>>>>> The artifacts have been signed with Key : 8BF4ABEB
> > > > > >>>>>>>
> > > > > >>>>>>> Please vote accordingly:
> > > > > >>>>>>>
> > > > > >>>>>>> [ ] +1, accept RC as the official 0.10.0 release
> > > > > >>>>>>> [ ] -1, do not accept RC as the official 0.10.0 release
> > > > because...
> > > > > >>>
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: Model performance history with PredictionIO

[Donald Szeto]

Hi Vijay,

This is definitely an interesting idea and would be very useful for
production and debugging. In fact, if you look at the EngineInstances /
EvaluationInstances classes, some foundation is already in place and it
just desperately need a UI to expose it. Would it be something that you be
interested in contributing?

Regards,
Donald

On Mon, Sep 19, 2016 at 6:17 PM, Vijay Bhat  wrote:

> Hi all,
>
> I've been playing with PredictionIO recently and am impressed with its
> capabilities / ease of use. I like how the model serving engine provides
> clear visibility into the currently deployed ML model and its performance
> (latency, throughput).
>
> What I'm also interested in for some of the work I'm doing is tracking the
> history of models were deployed to an engine. For example, in a
> classification model:
>
>- what algorithms and training parameters were used on each deploy.
>- historical latency and throughput, and how they changed with retrained
>models (computational performance drift).
>- historical AUC (or other performance metric) to track model drift.
>
> Is this something on the Prediction IO roadmap, or something that others
> have expressed interest in?
>
> Thanks,
> Vijay
>

Re: [VOTE]: Apache PredictionIO (incubating) 0.10.0 Release

[Donald Szeto]

Hi Andy,

What if the set of artifacts are built from the source tarball, and they
are an integral part of the ecosystem (e.g. PredictionIO engine developers
use these artifacts to build engines)?

I read from
http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
that we need to have RC artifacts on Nexus for voters to test?

Regards,
Donald

On Tue, Sep 20, 2016 at 2:02 PM, Andrew Purtell <andrew.purt...@gmail.com>
wrote:

> The release artifact should be one signed and summed tarball.
>
> > On Sep 20, 2016, at 10:36 AM, Suneel Marthi <smar...@apache.org> wrote:
> >
> > that was my thinking too, hence I have been holding off from even
> > downloading any of the artifacts.
> >
> >> On Tue, Sep 20, 2016 at 7:32 PM, Pat Ferrel <p...@occamsmachete.com>
> wrote:
> >>
> >> Shouldn’t this be one tarball?
> >>
> >>
> >> On Sep 18, 2016, at 6:53 PM, Donald Szeto <don...@apache.org> wrote:
> >>
> >> Yes. Many of them are sources, docs, poms and signatures though.
> >>
> >> On Sun, Sep 18, 2016 at 6:02 PM, Suneel Marthi <suneel.mar...@gmail.com
> >
> >> wrote:
> >>
> >>> So all of these artifacts need to be verified and validated ?
> >>>
> >>> https://repository.apache.org/content/repositories/
> >>> orgapachepredictionio-1003/org/apache/predictionio/
> >>>
> >>>
> >>>
> >>>> On Mon, Sep 19, 2016 at 2:59 AM, Donald Szeto <don...@apache.org>
> wrote:
> >>>>
> >>>> I will start a new voting thread. The staging repo should contain just
> >>>> PredictionIO artifacts.
> >>>>
> >>>> On Sun, Sep 18, 2016 at 5:57 PM, Suneel Marthi <smar...@apache.org>
> >>> wrote:
> >>>>
> >>>>> the MAven staging repo brings up whole load of artifacts, which ones
> r
> >>> we
> >>>>> voting on again ?
> >>>>>
> >>>>> On Mon, Sep 19, 2016 at 2:49 AM, Donald Szeto <don...@apache.org>
> >>> wrote:
> >>>>>
> >>>>>> I have prepared a RC2. The artifacts can be downloaded here:
> >>>>>> https://dist.apache.org/repos/dist/dev/incubator/
> >>> predictionio/0.10.0-
> >>>>>> incubating-rc2/
> >>>>>> or from the Maven staging repo here:
> >>>>>> https://repository.apache.org/content/repositories/
> >>>>>> orgapachepredictionio-1003/
> >>>>>> .
> >>>>>>
> >>>>>> Do we need to vote on the RC2 again?
> >>>>>>
> >>>>>> On Sat, Sep 17, 2016 at 2:10 PM, Pat Ferrel <p...@occamsmachete.com>
> >>>>> wrote:
> >>>>>>
> >>>>>>> Hate to make more work for you but the new name would also maybe
> >>>> avoid
> >>>>>>> some confusion for older migrating users.
> >>>>>>>
> >>>>>>> On Sep 16, 2016, at 9:02 AM, Donald Szeto <don...@apache.org>
> >>> wrote:
> >>>>>>>
> >>>>>>> If everyone agrees that the artifacts should have an "apache-"
> >>>> prefix,
> >>>>> I
> >>>>>>> will roll an RC2 shortly. Since the namespace change is
> >>> unavoidable,
> >>>>>> might
> >>>>>>> as well get all artifact name changes done in one shot for good.
> >>>>>>>
> >>>>>>> On Friday, September 16, 2016, Andrew Purtell <
> >>>>> andrew.purt...@gmail.com>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> Let me double check.
> >>>>>>>>
> >>>>>>>>> On Sep 16, 2016, at 7:33 AM, Alex Merritt <
> >>>> emergentor...@apache.org
> >>>>>>>> <javascript:;>> wrote:
> >>>>>>>>>
> >>>>>>>>> I believe it depends on which of the two votes you mean. For the
> >>>>>> podling
> >>>>>>>>> vote, PPMC votes are binding, for the incubator vote,  IPMC
> >>> votes
> >>>>> are,
> >>>>>>>> no?
> >>>>>>>>>
> >>>>>>>>>> On Sep 15, 2016 9:42 P

Re: [VOTE]: Apache PredictionIO (incubating) 0.10.0 Release

[Donald Szeto]

If everyone agrees that the artifacts should have an "apache-" prefix, I
will roll an RC2 shortly. Since the namespace change is unavoidable, might
as well get all artifact name changes done in one shot for good.

On Friday, September 16, 2016, Andrew Purtell <andrew.purt...@gmail.com>
wrote:

> Let me double check.
>
> > On Sep 16, 2016, at 7:33 AM, Alex Merritt <emergentor...@apache.org
> <javascript:;>> wrote:
> >
> > I believe it depends on which of the two votes you mean. For the podling
> > vote, PPMC votes are binding, for the incubator vote,  IPMC votes are,
> no?
> >
> >> On Sep 15, 2016 9:42 PM, "Andrew Purtell" <andrew.purt...@gmail.com
> <javascript:;>> wrote:
> >>
> >> I believe 'binding' only applies to IPMC.
> >>
> >>>> On Sep 15, 2016, at 12:49 PM, Suneel Marthi <suneel.mar...@gmail.com
> <javascript:;>>
> >>> wrote:
> >>>
> >>> Folks, When u vote please specify "+1 Binding" if u r a PMC member. Its
> >>> only the PMC votes that count for a release to pass.
> >>>
> >>>
> >>>
> >>>> On Thu, Sep 15, 2016 at 2:11 PM, Robert Lu <robberp...@outlook.com
> <javascript:;>>
> >> wrote:
> >>>>
> >>>> +1
> >>>>
> >>>>> On Sep 15, 2016, at 01:13, Matthew Tovbin <tovb...@apache.org
> <javascript:;>> wrote:
> >>>>>
> >>>>> +1
> >>>>>
> >>>>>> On Wed, Sep 14, 2016 at 10:12 AM, Pat Ferrel <p...@occamsmachete.com
> <javascript:;>>
> >>>>> wrote:
> >>>>>
> >>>>>> +1
> >>>>>>
> >>>>>>
> >>>>>> On Sep 13, 2016, at 11:55 AM, Donald Szeto <donald.sz...@gmail.com
> <javascript:;>>
> >>>> wrote:
> >>>>>>
> >>>>>> This is the vote for 0.10.0 of Apache PredictionIO (incubating).
> >>>>>>
> >>>>>> The vote will run for at least 72 hours and will close on Sept 16th,
> >>>> 2016.
> >>>>>>
> >>>>>> The artifacts can be downloaded here:
> >>>>>> https://dist.apache.org/repos/dist/dev/incubator/predictioni
> >>>>>> o/0.10.0-incubating-rc1/
> >>>>>> or
> >>>>>> from the Maven staging repo here:
> >>>>>> https://repository.apache.org/content/repositories/orgapache
> >>>>>> predictionio-1001/
> >>>>>>
> >>>>>> All JIRAs completed for this release are tagged with 'FixVersion =
> >>>> 0.10.0'.
> >>>>>> You can view them here:
> >>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> >>>>>> ctId=12320420=12337844
> >>>>>>
> >>>>>> The artifacts have been signed with Key : 8BF4ABEB
> >>>>>>
> >>>>>> Please vote accordingly:
> >>>>>>
> >>>>>> [ ] +1, accept RC as the official 0.10.0 release
> >>>>>> [ ] -1, do not accept RC as the official 0.10.0 release because...
> >>
>

Remove engine registration

[Donald Szeto]

Hi all,

I want to start the discussion of removing engine registration. How many
people actually take advantage of being able to run pio commands everywhere
outside of an engine template directory? This will be a nontrivial change
on the operational side so I want to gauge the potential impact to existing
users.

Pros:
- Stateless build. This would work well with many PaaS.
- Eliminate the "pio build" command once and for all.
- Ability to use your own build system, i.e. Maven, Ant, Gradle, etc.
- Potentially better experience with IDE since engine templates no longer
depends on an SBT plugin.

Cons:
- Inability to run pio engine training and deployment commands outside of
engine template directory.
- No automatic version matching of PIO binary distribution and artifacts
version used in the engine template.
- A less unified user experience: from pio-build-train-deploy to build,
then pio-train-deploy.

Regards,
Donald

[RESULT] [VOTE]: Apache PredictionIO (incubating) 0.10.0 Release (RC4)

[Donald Szeto]

The vote passes, with 4 +1 votes (4 binding) and no -1 votes.

+1 Alex Merritt (binding)
+1 Donald Szeto (binding)
+1 Pat Ferrel (binding)
+1 Suneel Marthi (binding)

Thanks all for voting.

Apache PredictionIO (incubating) 0.10.0 RC4 has been accepted as the
release. The voting will now proceed to the Incubator PMC.

Regards,
Donald

Re: Would like to add PredictionIO to Spark Third-Party wiki page...

[Donald Szeto]

Hi Sarasija,

Thanks for helping out on adding links in the Spark wiki. It is managed by
the Apache Spark PMC and we do not have access. I have the best way to go
is to subscribe to d...@spark.apache.org and suggest an edit to the Spark
PMC.

Regards,
Donald

On Mon, Sep 26, 2016 at 1:31 PM, Sarasija Parthasarthy <
sparthasar...@salesforce.com> wrote:

> Hi:
>
> I would like to add PredictionIO as part of Infrastructure projects to this
> wiki:
> https://cwiki.apache.org/confluence/display/SPARK/Third+Party+Projects
>
> I registered, but do not seem to have edit rights to the wiki.  Can you
> give me access?
>
> Thanks,
> Sarasija
>

[VOTE] Apache PredictionIO (incubating) 0.10.0 Release (RC5)

[Donald Szeto]

This is the vote for 0.10.0 of Apache PredictionIO (incubating).

The vote will run for at least 72 hours and will close on Oct 3rd, 2016.

RC2 adds the "apache-" prefix to artifact filenames.

RC3 adds on top of RC2 with proper licenses and notices embedded in the
Maven artifacts. It also changes the license of the documentation from
Creative Commons to APLv2.

RC4 fixes a build error of RC3.

RC5 fixes issues raised by the IPMC:
- Removed 3rd party dependencies from documentation sources
- Fixed incorrect licensing of semver.sh from ASF to BSD
- Moved MySQL connector to optional scope

The release candidate artifacts can be downloaded here:
https://dist.apache.org/repos/dist/dev/incubator/predictionio/0.10.0-incubating-rc5/

Test results of RC5 can be found here:
https://travis-ci.org/apache/incubator-predictionio/builds/164221633

Maven artifacts are built from the release candidate artifacts above, and
are provided as convenience for testing with engine templates. The Maven
artifacts are provided at the Maven staging repo here:
https://repository.apache.org/content/repositories/orgapachepredictionio-1009/

All JIRAs completed for this release are tagged with 'FixVersion = 0.10.0'.
You can view them here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320420=12337844

The artifacts have been signed with Key : 8BF4ABEB

Please vote accordingly:

[ ] +1, accept RC as the official 0.10.0 release
[ ] -1, do not accept RC as the official 0.10.0 release because...

Re: [VOTE] Apache PredictionIO (incubating) 0.10.0 Release (RC5)

[Donald Szeto]

Hi all,

Thanks for voting. Please indicate binding or non-binding when you cast
your vote. Release votes require 3 binding +1's from PMC to pass.

Regards,
Donald

On Saturday, October 1, 2016, Kenneth Chan <kenn...@apache.org> wrote:

> +1
>
> On Saturday, October 1, 2016, Pat Ferrel <p...@occamsmachete.com
> <javascript:;>> wrote:
>
> > +1 binding
> >
> > On Oct 1, 2016, at 10:20 AM, Suneel Marthi <suneel.mar...@gmail.com
> <javascript:;>
> > <javascript:;>> wrote:
> >
> > +1 binding
> >
> > On Sat, Oct 1, 2016 at 12:05 PM, Matthew Tovbin <matt...@tovbin.com
> <javascript:;>
> > <javascript:;>> wrote:
> >
> > > +1
> > >
> > > - Matthew
> > >
> > > On Oct 1, 2016 00:18, "Donald Szeto" <don...@apache.org <javascript:;>
> <javascript:;>>
> > wrote:
> > >
> > >> This is the vote for 0.10.0 of Apache PredictionIO (incubating).
> > >>
> > >> The vote will run for at least 72 hours and will close on Oct 3rd,
> 2016.
> > >>
> > >> RC2 adds the "apache-" prefix to artifact filenames.
> > >>
> > >> RC3 adds on top of RC2 with proper licenses and notices embedded in
> the
> > >> Maven artifacts. It also changes the license of the documentation from
> > >> Creative Commons to APLv2.
> > >>
> > >> RC4 fixes a build error of RC3.
> > >>
> > >> RC5 fixes issues raised by the IPMC:
> > >> - Removed 3rd party dependencies from documentation sources
> > >> - Fixed incorrect licensing of semver.sh from ASF to BSD
> > >> - Moved MySQL connector to optional scope
> > >>
> > >> The release candidate artifacts can be downloaded here:
> > >> https://dist.apache.org/repos/dist/dev/incubator/predictionio/0.10.0-
> > >> incubating-rc5/
> > >>
> > >> Test results of RC5 can be found here:
> > >> https://travis-ci.org/apache/incubator-predictionio/builds/164221633
> > >>
> > >> Maven artifacts are built from the release candidate artifacts above,
> > and
> > >> are provided as convenience for testing with engine templates. The
> Maven
> > >> artifacts are provided at the Maven staging repo here:
> > >> https://repository.apache.org/content/repositories/
> > >> orgapachepredictionio-1009/
> > >>
> > >> All JIRAs completed for this release are tagged with 'FixVersion =
> > > 0.10.0'.
> > >> You can view them here:
> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > >> projectId=12320420=12337844
> > >>
> > >> The artifacts have been signed with Key : 8BF4ABEB
> > >>
> > >> Please vote accordingly:
> > >>
> > >> [ ] +1, accept RC as the official 0.10.0 release
> > >> [ ] -1, do not accept RC as the official 0.10.0 release because...
> > >>
> > >
> >
> >
>

Re: Nov 2016 Podling Report

[Donald Szeto]

Hi Drew,

Is this resolved? I can see the entry on the wiki page [1] now. John
granted me edit permission to the wiki so I can post directly next time.
Thank you for your suggestions!

Regards,
Donald

[1] https://wiki.apache.org/incubator/November2016

On Sat, Nov 5, 2016 at 8:17 AM, Drew Farris  wrote:

> Hi PredictionIO Podling,
>
> I'm your assigned Apache Incubator shepherd this month. Your monthly report
> looks great.
>
> In the process of putting my notes together I noticed that although the
> podling report was mailed out to the list[1], it does not look like it made
> it on to the Incubator Board Report wiki page[2] - possibly as a result of
> an edit conflict.
>
> Would someone post this report as soon as possible? I was due end of day
> 11/2.
>
> It would be a good idea for additional authors from PredictionIO to request
> write permissions for the Incubator wiki so they can post the reports
> directly instead of relying on the mentors to do so. This is as simple as
> creating an account on the wiki and sending an e-mail to
> gene...@incubator.apache.org list requesting write access as a result of
> being associated with the PredictionIO Podling.
>
> Regards,
> Drew Farris
>
> [1] https://s.apache.org/UlqQ
> [2] https://wiki.apache.org/incubator/November2016
>

Re: Failed to load implementation Libraries

[Donald Szeto]

Hi Jim,

You can also reduce the number of iterations in engine.json if you are
testing locally.

Regards,
Donald

On Monday, October 17, 2016, Jim Miller  wrote:

> Thanks Chan.  I stopped the vm and increased memory from 6114 to 8192 and
> that seemed to do the trick:
>
> vbox.customize ["modifyvm", :id, "--memory", 8192]
>
> Thanks,
>
> Jim
>
> --
> Jim Miller
>
> On October 17, 2016 at 12:00:24 AM, Chan Lee (chanlee...@gmail.com) wrote:
>
> Hi Jim,
>
> Could you try increasing the driver memory size by running `pio train --
> --driver-memory 4G`?
>
> Chan
>
> On Sun, Oct 16, 2016 at 6:09 PM, Jim Miller 
> wrote:
>
> > Hi,
> >
> > I just finished the Comics Recommendation Demo and now I am running thru
> > the "Quick Start - Recommendation Engine Template” and I'm running into
> > errors loading some libraries.
> >
> > On the step to train the engine I get this set of errors:
> >
> > vagrant:MyRecommendation/ $ pio train
> >
> >
> > [18:38:26]
> > [INFO] [Console$] Using existing engine manifest JSON at
> > /home/vagrant/apache-predictionio-0.10.0-incubating/MyRecommendation/
> > manifest.json
> > [INFO] [Runner$] Submission command: /home/vagrant/apache-
> > predictionio-0.10.0-incubating/vendors/spark-1.5.
> > 1-bin-hadoop2.6/bin/spark-submit --class org.apache.predictionio.
> workflow.CreateWorkflow
> > --jars file:/home/vagrant/apache-predictionio-0.10.0-
> > incubating/MyRecommendation/target/scala-2.10/template-
> > scala-parallel-recommendation-assembly-0.1-SNAPSHOT-deps.
> > jar,file:/home/vagrant/apache-predictionio-0.10.0-
> > incubating/MyRecommendation/target/scala-2.10/template-
> > scala-parallel-recommendation_2.10-0.1-SNAPSHOT.jar --files
> > file:/home/vagrant/apache-predictionio-0.10.0-incubating/conf/log4j.
> properties
> > --driver-class-path /home/vagrant/apache-predictionio-0.10.0-
> > incubating/conf:/home/vagrant/apache-predictionio-0.10.0-
> > incubating/lib/postgresql-9.4-1204.jdbc41.jar:/home/vagrant/
> > apache-predictionio-0.10.0-incubating/lib/mysql-
> connector-java-5.1.37.jar
> > file:/home/vagrant/apache-predictionio-0.10.0-incubating/assembly/pio-
> assembly-0.10.0-incubating.jar
> > --engine-id 2gh2yQNyqkiMcAjjcgXNWXuVqxb5Phc6 --engine-version
> > deb358192507f9db45d36fa42d479bff6eb23766 --engine-variant
> > file:/home/vagrant/apache-predictionio-0.10.0-
> incubating/MyRecommendation/engine.json
> > --verbosity 0 --json-extractor Both --env PIO_ENV_LOADED=1,PIO_STORAGE_
> > REPOSITORIES_METADATA_NAME=pio_meta,PIO_FS_BASEDIR=/home/
> > vagrant/.pio_store,PIO_STORAGE_SOURCES_ELASTICSEARCH_
> > HOSTS=localhost,PIO_HOME=/home/vagrant/apache-predictionio-0.10.0-
> > incubating,PIO_FS_ENGINESDIR=/home/vagrant/.pio_store/
> > engines,PIO_STORAGE_SOURCES_PGSQL_URL=jdbc:postgresql://
> > localhost/pio,PIO_STORAGE_SOURCES_ELASTICSEARCH_TYPE=
> > elasticsearch,PIO_STORAGE_REPOSITORIES_METADATA_SOURCE=
> PGSQL,PIO_STORAGE_
> > REPOSITORIES_MODELDATA_SOURCE=PGSQL,PIO_STORAGE_
> > REPOSITORIES_EVENTDATA_NAME=pio_event,PIO_STORAGE_SOURCES_
> > PGSQL_PASSWORD=pio,PIO_STORAGE_SOURCES_ELASTICSEARCH_
> > HOME=/home/vagrant/apache-predictionio-0.10.0-incubating/vendors/
> > elasticsearch-1.4.4,PIO_STORAGE_SOURCES_PGSQL_TYPE=
> > jdbc,PIO_FS_TMPDIR=/home/vagrant/.pio_store/tmp,PIO_
> STORAGE_SOURCES_PGSQL_
> > USERNAME=pio,PIO_STORAGE_REPOSITORIES_MODELDATA_NAME=
> > pio_model,PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE=
> > PGSQL,PIO_CONF_DIR=/home/vagrant/apache-predictionio-0.
> > 10.0-incubating/conf,PIO_STORAGE_SOURCES_ELASTICSEARCH_PORTS=9300
> > [INFO] [Engine] Extracting datasource params...
> > [INFO] [WorkflowUtils$] No 'name' is found. Default empty String will be
> > used.
> > [INFO] [Engine] Datasource params: (,DataSourceParams(MyApp1,None))
> > [INFO] [Engine] Extracting preparator params...
> > [INFO] [Engine] Preparator params: (,Empty)
> > [INFO] [Engine] Extracting serving params...
> > [INFO] [Engine] Serving params: (,Empty)
> > [WARN] [Utils] Your hostname, imhotep-dev-host resolves to a loopback
> > address: 127.0.1.1; using 10.0.2.15 instead (on interface eth0)
> > [WARN] [Utils] Set SPARK_LOCAL_IP if you need to bind to another address
> > [INFO] [Remoting] Starting remoting
> > [INFO] [Remoting] Remoting started; listening on addresses :[akka.tcp://
> > sparkDriver@10.0.2.15:49568]
> > [WARN] [MetricsSystem] Using default name DAGScheduler for source because
> > spark.app.id is not set.
> > [INFO] [Engine$] EngineWorkflow.train
> > [INFO] [Engine$] DataSource: JimTest.DataSource@839df62
> > [INFO] [Engine$] Preparator: JimTest.Preparator@67cffead
> > [INFO] [Engine$] AlgorithmList: List(JimTest.ALSAlgorithm@217c23ce)
> > [INFO] [Engine$] Data sanity check is on.
> > [INFO] [Engine$] JimTest.TrainingData does not support data sanity check.
> > Skipping check.
> > [INFO] [Engine$] JimTest.PreparedData does not support data sanity check.
> > Skipping check.
> > [WARN] [BLAS] Failed to load implementation from:
> 

Re: Micro-releases

[Donald Szeto]

We should also talk about how we proceed with versioning these patch
releases. We follow semantic versioning, so naturally we could use major
and minor portions for official releases, and the patch portion for
micro-releases / hotfixes. This way, even though Maven artifacts won't be
published to the central repository, users will not get tripped with
different cached versions of the artifacts.

On Mon, Nov 28, 2016 at 10:14 AM, Donald Szeto <don...@apache.org> wrote:

> Pat's link is the best description of the Git development model that
> PredictionIO has been using since the beginning. I also support the use of
> hotfix branches that will merge into both master and develop branches.
>
> Branching for different sets of external dependencies, in my opinion,
> should be the last resort. We can try to work our build system to
> accommodate.
>
> When we have a conclusion we should update http://predictionio.
> incubator.apache.org/community/contribute-code/
>
> On Sat, Nov 26, 2016 at 10:00 AM, Pat Ferrel <p...@occamsmachete.com>
> wrote:
>
>> This is a better description of how we should be managing code and git
>> branches than I have every seen: http://nvie.com/posts/a-succes
>> sful-git-branching-model/ <http://nvie.com/posts/a-succe
>> ssful-git-branching-model/> It includes the use of develop, a stable
>> master branch, and hotfixes to master. I also like more than one release
>> branch because I imagine once we support two versions of Elasticsearch or
>> Spark that require code changes, a branch is the natural way to assemble
>> the code.
>>
>> The post is worth a read and discussion. My other Apache git based
>> project could use this approach too.
>>
>> In this case I’m only proposing that major bug fixes (hotfixes) be
>> allowed into master and be tagged. The post gives good rationale for this.
>>
>>
>> On Nov 25, 2016, at 11:30 PM, Paul-Armand Verhaegen <
>> paularmand.verhae...@gmail.com> wrote:
>>
>>
>> Great proposal. I certainly agree with the needs in the community and
>> associated benefits for fast bug fixes in master.
>> If I may suggest to hotfix against master with merge towards development.
>> Merges can be cumbersome when dev and master diverge.
>> It can become very difficult if the fixes (from dev) cannot be applied to
>> master, and additional commits need to be made, that has messed up my head
>> before.
>> Although more or less the same work, I believe it to be less of an issue
>> if we end up messing up dev.
>> I'm also in favor of using a well-documented approach such as gitflow,
>> since I often forget the exact workflows of different projects.
>>
>> > On 25 Nov 2016, at 18:57, Pat Ferrel <p...@actionml.com> wrote:
>> >
>> > Our dev process includes edge/snapshot code being kept in the develop
>> branch until release time. I like this process because it allows us to keep
>> master clean and stable. So imagine that we have a major bug fix. To get
>> this to users we could do a release but this can’t happen soon enough if a
>> user has discovered it and already needs the fix. We could point to a
>> commit in develop but that branch is a little wild until release time.
>> >
>> > I’d like to propose we allow some commits to master, to fix critical
>> bugs, and tag these with the Jira # describing the bug. The fix would also
>> go in develop so at merge time there would be nothing to merge.
>> >
>> > At present we have a source only release so this would work fairly
>> well, even with a binary release it would be safer and easier to document
>> than suggesting a build of the develop branch.
>> >
>> > Opinions? If no one objects there was a critical bug fixed recently and
>> I’ll do the above to get the fix in master.
>>
>>
>>
>

Re: Micro-releases

[Donald Szeto]

Pat's link is the best description of the Git development model that
PredictionIO has been using since the beginning. I also support the use of
hotfix branches that will merge into both master and develop branches.

Branching for different sets of external dependencies, in my opinion,
should be the last resort. We can try to work our build system to
accommodate.

When we have a conclusion we should update
http://predictionio.incubator.apache.org/community/contribute-code/

On Sat, Nov 26, 2016 at 10:00 AM, Pat Ferrel  wrote:

> This is a better description of how we should be managing code and git
> branches than I have every seen: http://nvie.com/posts/a-
> successful-git-branching-model/  successful-git-branching-model/> It includes the use of develop, a stable
> master branch, and hotfixes to master. I also like more than one release
> branch because I imagine once we support two versions of Elasticsearch or
> Spark that require code changes, a branch is the natural way to assemble
> the code.
>
> The post is worth a read and discussion. My other Apache git based project
> could use this approach too.
>
> In this case I’m only proposing that major bug fixes (hotfixes) be allowed
> into master and be tagged. The post gives good rationale for this.
>
>
> On Nov 25, 2016, at 11:30 PM, Paul-Armand Verhaegen <
> paularmand.verhae...@gmail.com> wrote:
>
>
> Great proposal. I certainly agree with the needs in the community and
> associated benefits for fast bug fixes in master.
> If I may suggest to hotfix against master with merge towards development.
> Merges can be cumbersome when dev and master diverge.
> It can become very difficult if the fixes (from dev) cannot be applied to
> master, and additional commits need to be made, that has messed up my head
> before.
> Although more or less the same work, I believe it to be less of an issue
> if we end up messing up dev.
> I'm also in favor of using a well-documented approach such as gitflow,
> since I often forget the exact workflows of different projects.
>
> > On 25 Nov 2016, at 18:57, Pat Ferrel  wrote:
> >
> > Our dev process includes edge/snapshot code being kept in the develop
> branch until release time. I like this process because it allows us to keep
> master clean and stable. So imagine that we have a major bug fix. To get
> this to users we could do a release but this can’t happen soon enough if a
> user has discovered it and already needs the fix. We could point to a
> commit in develop but that branch is a little wild until release time.
> >
> > I’d like to propose we allow some commits to master, to fix critical
> bugs, and tag these with the Jira # describing the bug. The fix would also
> go in develop so at merge time there would be nothing to merge.
> >
> > At present we have a source only release so this would work fairly well,
> even with a binary release it would be safer and easier to document than
> suggesting a build of the develop branch.
> >
> > Opinions? If no one objects there was a critical bug fixed recently and
> I’ll do the above to get the fix in master.
>
>
>

Nov 2016 Podling Report

[Donald Szeto]

Hi all,

Please review the following report. If this is good to go, please feel free
to go ahead and put this on the incubator wiki.

Regards,
Donald

---

PredictionIO

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.

PredictionIO has been incubating since 2016-05-26. The initial code for
PredictionIO was granted on 2016-06-16. A second grant of PredictionIO
templates and SDKs was granted on 2016-09-20.

Three most important issues to address in the move towards graduation:

  1. Establish a formal release schedule and process, allowing for
dependable release cycles in a manner consistent with the Apache way.
  2. Grow the community to establish diversity of background.
  3. Transition remaining former PredictionIO users from google-groups to
ASF mailing lists.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

  None

How has the community developed since the last report?

  1. Both user and development mailing list are more active than last
report.
  2. People who requested for features has become interested in
contributing. There has been more discussions of future roadmap and
development driven by the community.
  3. The ecosystem around engine templates is slowly gaining traction again
on Apache infrastructure. There are discussions around engine templates.

How has the project developed since the last report?

  1. The first Apache release has been released on 2016-10-17.
  2. The second grant has been issued and recorded by ASF. Seven templates
and five SDKs are now transferred to Apache.
  3. There are some pull requests against PredictionIO and its engine
templates.

Date of last release:

  Apache PredictionIO 0.10.0-incubating on 2016-10-17

When were the last committers or PMC members elected?

  Paul Li was elected as committer and PMC member on Aug 30, 2016.

Re: template-user-similarity

[Donald Szeto]

Hi Jim,

Without knowing your exact use case, if you only have users and their
attributes in your system, you can treat users as "items" and start with
Alexey's template. Please provide more details about your use case so other
people can chip in with their ideas.

Regards,
Donald

On Sun, Oct 23, 2016 at 8:49 PM, Jim Miller  wrote:

> Hi,
>
> I’m working on comparing users. I found this template listed but with only
> the initial commit.
>
> https://github.com/PredictionIO/template-user-similarity
>
> My thought is that I may be able to edit this template to work in a
> similar fashion:
>
> https://github.com/alexice/template-scala-parallel-svd-item-similarity
>
> In your opinion, would this be a suitable starting point or is there
> another template would work better?
>
> Thanks,
>
> Jim
>
> --
> Jim Miller
>

Re: Thanks for reviewing Dockerfile for PredictionIO-0.10.0

[Donald Szeto]

Hi Steven,

Looks like a good start. If nobody objects, I will create a repo on Apache,
so hopefully we can converge all the great contributions to one place. Let
me know if this sounds good / bad to you.

Regards,
Donald

On Mon, Oct 24, 2016 at 11:03 AM, Steven Yan 
wrote:

> To whom may be interested in,
>
> I could not find Dockerfile for PredictionIO-0.10.0, so I modified
> sphereio's
> Dockerfile for older version to be:
> https://github.com/steveny2k/docker-predictionio
>
> Thanks for reviewing and comments.
>
> My long term plan is to install various examples into this Docker,
> pre-train the algorithms, upload the docker image, so that users can easily
> create docker container and start seeing how machine learning works,
> without need of following the tutorials through copy-pasting commands.
>
>
> Thanks,
> Steven
>

Re: Help for another Apache incubator project

[Donald Szeto]

Hey Chip,

Have you been able to publish staging artifacts? If not I will spend some
time looking into it.

Regards,
Donald

On Wed, Dec 7, 2016 at 11:50 AM, Chip Senkbeil 
wrote:

> Hi everyone,
>
> I'm one of the PMCs for Apache Toree, another Apache incubator project.
> Like predictionio, we're also using sbt to build and deploy our artifacts.
> We're currently trying to publish signed jars to staging for our first
> release (via sbt publishSigned), but we're getting a forbidden error when
> trying to do so. We had no issue publishing signed jars to Apache's
> snapshot repo.
>
> We're using the following as the publishTo for staging:
> https://repository.apache.org/content/repositories/staging/
>
> Did you do anything specific for predictionio to publish signed jars to
> Apache's staging repository via sbt and the sbt-sonatype plugin? We've set
> our credentials via a sonatype.sbt global plugin file (and also tried via
> ~/.ivy2/.credentials). The credentials are definitely picked up and I can
> see all of the artifacts including the signatures.
>
> Did you have to get infrastructure to enable staging for you? Is there
> anything you had to do the first time you published to staging? Our mentors
> are advocating Maven or other build tools, but we're heavily invested in
> sbt at this point.
>
> Thanks for all the help!
>

Re: Micro-releases

[Donald Szeto]

Yes. I was suggesting to use 0.10.1-incubating. The upside of this is that
our end users know which one has included all the latest fix instead of
tracking different JIRA ticket numbered suffices. We can limit real
releases to touch only major and minor version parts.

On Mon, Nov 28, 2016 at 10:26 AM, Pat Ferrel <p...@occamsmachete.com> wrote:

> Good point (reliable building). An extension of strict semantic versioning
> allows an extension like -incubating, this could include a Jira # too so
> the full artifact name might be:
>
> org.apache.predictionio-0.10.0-incubating-jira-255 and this would be
> tagged jira-255 in either hotfix of master branches.
>
> This allows the docs to remain unchanged because the version 0.10.0 does
> not change, which we might reserve for real releases. Donald are you
> suggesting a new 0.10.1-incubating for each hotfix?
>
>
> On Nov 28, 2016, at 10:18 AM, Donald Szeto <don...@apache.org> wrote:
>
> We should also talk about how we proceed with versioning these patch
> releases. We follow semantic versioning, so naturally we could use major
> and minor portions for official releases, and the patch portion for
> micro-releases / hotfixes. This way, even though Maven artifacts won't be
> published to the central repository, users will not get tripped with
> different cached versions of the artifacts.
>
> On Mon, Nov 28, 2016 at 10:14 AM, Donald Szeto <don...@apache.org> wrote:
>
> > Pat's link is the best description of the Git development model that
> > PredictionIO has been using since the beginning. I also support the use
> of
> > hotfix branches that will merge into both master and develop branches.
> >
> > Branching for different sets of external dependencies, in my opinion,
> > should be the last resort. We can try to work our build system to
> > accommodate.
> >
> > When we have a conclusion we should update http://predictionio.
> > incubator.apache.org/community/contribute-code/
> >
> > On Sat, Nov 26, 2016 at 10:00 AM, Pat Ferrel <p...@occamsmachete.com>
> > wrote:
> >
> >> This is a better description of how we should be managing code and git
> >> branches than I have every seen: http://nvie.com/posts/a-succes
> >> sful-git-branching-model/ <http://nvie.com/posts/a-succe
> >> ssful-git-branching-model/> It includes the use of develop, a stable
> >> master branch, and hotfixes to master. I also like more than one release
> >> branch because I imagine once we support two versions of Elasticsearch
> or
> >> Spark that require code changes, a branch is the natural way to assemble
> >> the code.
> >>
> >> The post is worth a read and discussion. My other Apache git based
> >> project could use this approach too.
> >>
> >> In this case I’m only proposing that major bug fixes (hotfixes) be
> >> allowed into master and be tagged. The post gives good rationale for
> this.
> >>
> >>
> >> On Nov 25, 2016, at 11:30 PM, Paul-Armand Verhaegen <
> >> paularmand.verhae...@gmail.com> wrote:
> >>
> >>
> >> Great proposal. I certainly agree with the needs in the community and
> >> associated benefits for fast bug fixes in master.
> >> If I may suggest to hotfix against master with merge towards
> development.
> >> Merges can be cumbersome when dev and master diverge.
> >> It can become very difficult if the fixes (from dev) cannot be applied
> to
> >> master, and additional commits need to be made, that has messed up my
> head
> >> before.
> >> Although more or less the same work, I believe it to be less of an issue
> >> if we end up messing up dev.
> >> I'm also in favor of using a well-documented approach such as gitflow,
> >> since I often forget the exact workflows of different projects.
> >>
> >>> On 25 Nov 2016, at 18:57, Pat Ferrel <p...@actionml.com> wrote:
> >>>
> >>> Our dev process includes edge/snapshot code being kept in the develop
> >> branch until release time. I like this process because it allows us to
> keep
> >> master clean and stable. So imagine that we have a major bug fix. To get
> >> this to users we could do a release but this can’t happen soon enough
> if a
> >> user has discovered it and already needs the fix. We could point to a
> >> commit in develop but that branch is a little wild until release time.
> >>>
> >>> I’d like to propose we allow some commits to master, to fix critical
> >> bugs, and tag these with the Jira # describing the bug. The fix would
> also
> >> go in develop so at merge time there would be nothing to merge.
> >>>
> >>> At present we have a source only release so this would work fairly
> >> well, even with a binary release it would be safer and easier to
> document
> >> than suggesting a build of the develop branch.
> >>>
> >>> Opinions? If no one objects there was a critical bug fixed recently and
> >> I’ll do the above to get the fix in master.
> >>
> >>
> >>
> >
>
>

Stateless Builds

[Donald Szeto]

Hi all,

I am moving the discussion of stateless build (
https://github.com/apache/incubator-predictionio/pull/328) here. Replying
Pat:

> BTW @chanlee514 @dszeto Are we thinking of a new command, something like
pio register that would add metadata to the metastore? This would need to
be run every time the engine.json changed for instance? It would also do
not compile? Is there an alternative? What state does this leave us in?

I imagine we would need pio register after this. Something like what docker
push would do for you today. Changes of engine.json will not require
registration because it is consumed during runtime by pio train and pio
deploy. We are phasing out pio build so that engine templates will be more
friendly with different IDEs.

> After the push, what action create binary (I assume pio build) what
action adds metadata to the metastore (I assume pio train) So does this
require they run on the same machine? They often do not.
pio build will still create the binary at this point (and hopefully phased
out as mentioned). Right now the only metadata that is disappearing are
engine manifests. Engine instances will still be written after pio train,
and used by pio deploy.

> One more question. After push how do we run the PredictionServer or train
on multiple machines? In the past this required copying the manifest.json
and making sure binaries are in the same location on all machines.
"In the same location" is actually a downside IMO of the manifest.json
design. Without manifest.json now, you would need to run pio commands from
a location with a built engine, because instead of looking at engine
manifests, it will now look locally for engine JARs. So deployment would
still involve copying engine JARs to a remote deployment machine, running
pio commands at the engine template location with engine-id and
engine-version arguments.

Regards,
Donald

Re: Micro-releases

[Donald Szeto]

I am okay with reserving patch for official releases, and use suffix that
have something with an increasing numerical in it.

We will probably need a dedicated page or micro site in the doc for these
kind of unofficial tar balls. It is against ASF policy to mark anything as
release and encourage people to use without the formal voting process. They
also cannot be sync to ASF distribution.

On Thu, Dec 1, 2016 at 10:25 AM Pat Ferrel <p...@occamsmachete.com> wrote:

> But the downside is we never touch major, or haven’t in all the years of
> PIO. So in effect all releases will be minor number changes and so far we
> have only touched that 10 times in all the years of PIO. We could skip many
> patch numbers and only fully release on important ones. But Semantic
> Versioning 2.0 allows a lot of other encoding of minor information in the
> hyphen extension like dot numbers, beta, RC, incubating etc.
> http://semver.org/#spec-item-9 <http://semver.org/#spec-item-9> They
> account for things as crazy as 1.0.0-x.7.z.92.
>
> I guess I’m ok with either skipping a lot of patch numbers per actual
> release and only using patch numbers to denote hotfixes or adding something
> to the hyphen extension but limiting release numbers to something as course
> grained as major and minor seems problematic.
>
> And yet if everyone likes this so be it.
>
> On Dec 1, 2016, at 10:05 AM, Donald Szeto <don...@apache.org> wrote:
>
> Yes. I was suggesting to use 0.10.1-incubating. The upside of this is that
> our end users know which one has included all the latest fix instead of
> tracking different JIRA ticket numbered suffices. We can limit real
> releases to touch only major and minor version parts.
>
> On Mon, Nov 28, 2016 at 10:26 AM, Pat Ferrel <p...@occamsmachete.com>
> wrote:
>
> > Good point (reliable building). An extension of strict semantic
> versioning
> > allows an extension like -incubating, this could include a Jira # too so
> > the full artifact name might be:
> >
> > org.apache.predictionio-0.10.0-incubating-jira-255 and this would be
> > tagged jira-255 in either hotfix of master branches.
> >
> > This allows the docs to remain unchanged because the version 0.10.0 does
> > not change, which we might reserve for real releases. Donald are you
> > suggesting a new 0.10.1-incubating for each hotfix?
> >
> >
> > On Nov 28, 2016, at 10:18 AM, Donald Szeto <don...@apache.org> wrote:
> >
> > We should also talk about how we proceed with versioning these patch
> > releases. We follow semantic versioning, so naturally we could use major
> > and minor portions for official releases, and the patch portion for
> > micro-releases / hotfixes. This way, even though Maven artifacts won't be
> > published to the central repository, users will not get tripped with
> > different cached versions of the artifacts.
> >
> > On Mon, Nov 28, 2016 at 10:14 AM, Donald Szeto <don...@apache.org>
> wrote:
> >
> >> Pat's link is the best description of the Git development model that
> >> PredictionIO has been using since the beginning. I also support the use
> > of
> >> hotfix branches that will merge into both master and develop branches.
> >>
> >> Branching for different sets of external dependencies, in my opinion,
> >> should be the last resort. We can try to work our build system to
> >> accommodate.
> >>
> >> When we have a conclusion we should update http://predictionio.
> >> incubator.apache.org/community/contribute-code/
> >>
> >> On Sat, Nov 26, 2016 at 10:00 AM, Pat Ferrel <p...@occamsmachete.com>
> >> wrote:
> >>
> >>> This is a better description of how we should be managing code and git
> >>> branches than I have every seen: http://nvie.com/posts/a-succes
> >>> sful-git-branching-model/ <http://nvie.com/posts/a-succe
> >>> ssful-git-branching-model/> It includes the use of develop, a stable
> >>> master branch, and hotfixes to master. I also like more than one
> release
> >>> branch because I imagine once we support two versions of Elasticsearch
> > or
> >>> Spark that require code changes, a branch is the natural way to
> assemble
> >>> the code.
> >>>
> >>> The post is worth a read and discussion. My other Apache git based
> >>> project could use this approach too.
> >>>
> >>> In this case I’m only proposing that major bug fixes (hotfixes) be
> >>> allowed into master and be tagged. The post gives good rationale for
> > this.
> >>>
> >

[VOTE] Apache PredictionIO (incubating) 0.11.0 Release (RC1)

[Donald Szeto]

This is the vote for 0.11.0 of Apache PredictionIO (incubating).

The vote will run for at least 72 hours and will close on Apr 7th, 2017.

The release candidate artifacts can be downloaded here:
https://dist.apache.org/repos/dist/dev/incubator/predictionio/0.11.0-incubating-rc1/

Test results of RC1 can be found here:
https://travis-ci.org/apache/incubator-predictionio/builds/218542558

Maven artifacts are built from the release candidate artifacts above, and
are provided as convenience for testing with engine templates. The Maven
artifacts are provided at the Maven staging repo here:
https://repository.apache.org/content/repositories/orgapachepredictionio-1015/

All JIRAs completed for this release are tagged with 'FixVersion =
0.11.0-incubating'. You can view them here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320420=12338381

The artifacts have been signed with Key : 8BF4ABEB

Please vote accordingly:

[ ] +1, accept RC as the official 0.11.0 release
[ ] -1, do not accept RC as the official 0.11.0 release because...

Re: [VOTE] Apache PredictionIO (incubating) 0.11.0 Release (RC2)

[Donald Szeto]

Thanks! Just a reminder that PMC members should indicate whether the vote
is binding or not.

On Mon, Apr 10, 2017 at 1:15 PM Mars Hall <m...@heroku.com> wrote:

> My non-binding vote for rc2!
>
> [X] +1, accept RC as the official 0.11.0 release
> [ ] -1, do not accept RC as the official 0.11.0 release because...
>
> *Mars
>
> ( <> .. <> )
>
> > On Apr 9, 2017, at 21:29, Steven Yan <steven@salesforce.com> wrote:
> >
> > [X] +1, accept RC as the official 0.11.0 release
> > [ ] -1, do not accept RC as the official 0.11.0 release because...
> >
> > Thanks,
> > Steven
> >
> > On Sun, Apr 9, 2017 at 5:21 PM, Donald Szeto <don...@apache.org> wrote:
> >
> >> This is the vote for 0.11.0 of Apache PredictionIO (incubating).
> >>
> >> The vote will run for at least 72 hours and will close on Apr 12th,
> 2017.
> >>
> >> RC2 fixes a usage bug where the pio command does not pass through
> >> --driver-java-options to spark-submit.
> >>
> >> The release candidate artifacts can be downloaded here:
> >> https://dist.apache.org/repos/dist/dev/incubator/predictionio/0.11.0-
> >> incubating-rc2/
> >>
> >> Test results of RC2 can be found here:
> >> https://travis-ci.org/apache/incubator-predictionio/builds/220381611
> >>
> >> Maven artifacts are built from the release candidate artifacts above,
> and
> >> are provided as convenience for testing with engine templates. The Maven
> >> artifacts are provided at the Maven staging repo here:
> >> https://repository.apache.org/content/repositories/
> >> orgapachepredictionio-1016/
> >>
> >> All JIRAs completed for this release are tagged with 'FixVersion =
> >> 0.11.0-incubating'. You can view them here:
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >> projectId=12320420=12338381
> >>
> >> The artifacts have been signed with Key : 8BF4ABEB
> >>
> >> Please vote accordingly:
> >>
> >> [ ] +1, accept RC as the official 0.11.0 release
> >> [ ] -1, do not accept RC as the official 0.11.0 release because...
> >>
>
>

[CANCEL][VOTE] Apache PredictionIO (incubating) 0.11.0 Release (RC1)

[Donald Szeto]

We have found a usage bug with spark-submit --driver-java-options being
overridden by code, which made it impossible to pass in custom
--driver-java-options from CLI. Checking in a fix and restarting the vote.

On Wed, Apr 5, 2017 at 12:33 AM, Marcin Ziemiński <ziem...@gmail.com> wrote:

> [+1]
>
> 2017-04-05 5:58 GMT+02:00 Chan Lee <chanlee...@gmail.com>:
>
> > [+1]
> >
> >
> > On Tue, Apr 4, 2017 at 11:55 AM, Donald Szeto <don...@apache.org> wrote:
> >
> > > This is the vote for 0.11.0 of Apache PredictionIO (incubating).
> > >
> > > The vote will run for at least 72 hours and will close on Apr 7th,
> 2017.
> > >
> > > The release candidate artifacts can be downloaded here:
> > > https://dist.apache.org/repos/dist/dev/incubator/predictionio/0.11.0-
> > > incubating-rc1/
> > >
> > > Test results of RC1 can be found here:
> > > https://travis-ci.org/apache/incubator-predictionio/builds/218542558
> > >
> > > Maven artifacts are built from the release candidate artifacts above,
> and
> > > are provided as convenience for testing with engine templates. The
> Maven
> > > artifacts are provided at the Maven staging repo here:
> > > https://repository.apache.org/content/repositories/
> > > orgapachepredictionio-1015/
> > >
> > > All JIRAs completed for this release are tagged with 'FixVersion =
> > > 0.11.0-incubating'. You can view them here:
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > projectId=12320420=12338381
> > >
> > > The artifacts have been signed with Key : 8BF4ABEB
> > >
> > > Please vote accordingly:
> > >
> > > [ ] +1, accept RC as the official 0.11.0 release
> > > [ ] -1, do not accept RC as the official 0.11.0 release because...
> > >
> >
>

[VOTE] Apache PredictionIO (incubating) 0.11.0 Release (RC2)

[Donald Szeto]

This is the vote for 0.11.0 of Apache PredictionIO (incubating).

The vote will run for at least 72 hours and will close on Apr 12th, 2017.

RC2 fixes a usage bug where the pio command does not pass through
--driver-java-options to spark-submit.

The release candidate artifacts can be downloaded here:
https://dist.apache.org/repos/dist/dev/incubator/predictionio/0.11.0-incubating-rc2/

Test results of RC2 can be found here:
https://travis-ci.org/apache/incubator-predictionio/builds/220381611

Maven artifacts are built from the release candidate artifacts above, and
are provided as convenience for testing with engine templates. The Maven
artifacts are provided at the Maven staging repo here:
https://repository.apache.org/content/repositories/orgapachepredictionio-1016/

All JIRAs completed for this release are tagged with 'FixVersion =
0.11.0-incubating'. You can view them here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320420=12338381

The artifacts have been signed with Key : 8BF4ABEB

Please vote accordingly:

[ ] +1, accept RC as the official 0.11.0 release
[ ] -1, do not accept RC as the official 0.11.0 release because...

Re: es5 storageClient class not found

[Donald Szeto]

Hi Paul,

Are you trying the latest commit on the develop branch? You can skip
manually moving JARs by building PredictionIO with

./make-distribution.sh --with-es=5

>From this error message: java.lang.ClassNotFoundException:
ELASTICSEARCH.StorageClient
Did you happen to have this in your conf/pio-env.sh?

PIO_STORAGE_SOURCES_ELASTICSEARCH_TYPE=ELASTICSEARCH

Notice that the value for *_TYPE needs to be lowercase, because that will
be used to locate the Java package for storage drivers.

Regards,
Donald

On Thu, Mar 9, 2017 at 7:58 AM, Paul-Armand Verhaegen <
paularmand.verhae...@gmail.com> wrote:

>
> Hi all,
>
> Trying to setup the 0.11 with es5 storage for meta en events (localfs for
> models).
>
> I had some difficulties:
>
> 1. with make_distribution: had to substitute the origin of the copy
> operation from
> /lib/spark/pio-data-elasticsearch-assembly-*.jar
> to the directory
> storage/elasticsearch/target/scala-2.10/apache-predictionio-data-
> elasticsearch-assembly-*.jar
>
> 2. [probably particular to my case] had to make sure ES5 was open for
> 0.0.0.0 on tcp4, make jvm not change this to tcp6, and change allowed mem
> for jvm (ES5 now has some bootstrapping checks)
>
> 3. had to uncomment some parts from the pio-start-all: hbase and pgsql part
>
> After making a distribution, elastic comes up, but pio throws a bubbled up
> error:
>
> 2017-03-09 12:29:34,948 INFO  
> org.apache.predictionio.tools.commands.Management$
> [main] - Creating Event Server at 0.0.0.0:7070
> 2017-03-09 12:29:35,951 ERROR org.apache.predictionio.data.storage.Storage$
> [main] - Error initializing storage client for source ELASTICSEARCH
> java.lang.ClassNotFoundException: ELASTICSEARCH.StorageClient
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.apache.predictionio.data.storage.Storage$.getClient(
> Storage.scala:225)
> at org.apache.predictionio.data.storage.Storage$.org$apache$
> predictionio$data$storage$Storage$$updateS2CM(Storage.scala:251)
> at org.apache.predictionio.data.storage.Storage$$anonfun$
> sourcesToClientMeta$1.apply(Storage.scala:212)
> at org.apache.predictionio.data.storage.Storage$$anonfun$
> sourcesToClientMeta$1.apply(Storage.scala:212)
> at scala.collection.mutable.MapLike$class.getOrElseUpdate(
> MapLike.scala:189)
> at scala.collection.mutable.AbstractMap.getOrElseUpdate(
> Map.scala:91)
> at org.apache.predictionio.data.storage.Storage$.
> sourcesToClientMeta(Storage.scala:212)
> at org.apache.predictionio.data.storage.Storage$.
> getDataObject(Storage.scala:281)
> at org.apache.predictionio.data.storage.Storage$.
> getDataObjectFromRepo(Storage.scala:266)
> at org.apache.predictionio.data.storage.Storage$.getLEvents(
> Storage.scala:384)
> at org.apache.predictionio.data.api.EventServer$.
> createEventServer(EventServer.scala:617)
> at org.apache.predictionio.tools.commands.Management$.
> eventserver(Management.scala:77)
> at org.apache.predictionio.tools.console.Pio$.eventserver(Pio.
> scala:123)
> at org.apache.predictionio.tools.console.Console$$anonfun$main$
> 1.apply(Console.scala:665)
> at org.apache.predictionio.tools.console.Console$$anonfun$main$
> 1.apply(Console.scala:626)
> at scala.Option.map(Option.scala:145)
> at org.apache.predictionio.tools.console.Console$.main(Console.
> scala:626)
> at org.apache.predictionio.tools.console.Console.main(Console.
> scala)
>
>
> I believe that I did not include the 
> apache-predictionio-data-elasticsearch-assembly-*.jar
> in the right place, or I have to config that place better.
> From what I've read on the mailing list this was in quite some flux, but I
> thought that this file should end up in lib/extra ? Is that still correct?
>
> I can wait for the official 0.11, but I figured I can also try to get my
> feet wet a little ;)
>
> Thanks in advance,
> Paul
>
>

Re: Request for Integration of Issue Management

[Donald Szeto]

Agree with using only one system. We kept GitHub issues because we wanted
to migrate issues to JIRA, but didn't have chance to look at everyone of
them yet.

Any help would be appreciated. Perhaps there's a way to migrate all of them
to JIRA first and examine later?

On Fri, Apr 7, 2017 at 4:53 AM takako shimamoto 
wrote:

> Hi All,
>
> I think it would be better to integrate issues management.
> In particular, it is hard for new users to understand whether issues
> are managed by JIRA or GitHub.
>
> For example in case of Spark or Hadoop, which are other Apache
> Project, users cannot use GitHub Issues.
> I was hoping that you might consider this.
>
> Best regards,
>

Re: Podling Report Reminder - August 2017

[Donald Szeto]

Any PMC member who want to take a shot at this? A sample of the previous
report can be found on this mailing list's archive.

Regards,
Donald

On Sat, Jul 29, 2017 at 6:02 AM,  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 16 August 2017, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, August 02).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://wiki.apache.org/incubator/August2017
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

August 2017 Podling Report

[Donald Szeto]

Hi all,

Please review the following report. Mentors, if this is good to go, please
put this on the incubator wiki.

Regards,
Donald

---

PredictionIO

PredictionIO is an open source Machine Learning Server built on top of a
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.

PredictionIO has been incubating since 2016-05-26. The initial code for
PredictionIO was granted on 2016-06-16. The second grant of PredictionIO
templates and SDKs was granted on 2016-09-20.

Three most important issues to address in the move towards graduation:

  1. Establish a formal release schedule and process, allowing for
dependable release cycles in a manner consistent with the Apache way.
  2. Grow the community to establish diversity of background.
  3. Transition remaining former PredictionIO users from google-groups to
ASF mailing lists.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

  None

How has the community developed since the last report?

  1. Our new committers have been actively contributing new features and
bug fixes to the core codebase.
  2. There are new local meetups about PredictionIO in Japan.
  3. There has been growing integration effort of PredictionIO on the
Heroku platform.
  4. Increased traffic on the user mailing list.

How has the project developed since the last report?

  1. Around 40 pull requests have been accepted and merged since 0.11's
release, from both committers and contributors.
  2. On track to stick with a bi-monthly release schedule. Proposing a new
release for the beginning of August.
  3. Many cleanup effort into TLP graduation.

Date of the last release:

  Apache PredictionIO 0.11.0-incubating on 2017-04-25

When were the last committers or PMC members elected?

  Mars Hall was elected as committer and PMC member on July 8, 2017.

Re: August 2017 Release

[Donald Szeto]

On Thu, Aug 3, 2017 at 10:07 AM, Mars Hall  wrote:

> I just opened a PR to add docs for batch predict.
>
> Moving forward with the 0.12.0 release sounds great. Today, I will pull
> develop and see how it's working with the Heroku buildpack.
>

Awesome. Thanks!


> > On Aug 3, 2017, at 00:37, takako shimamoto  wrote:
> >
> > I think it's almost ready, and now we just have to update the current
> > documentation.
> > The deadline of several unresolved issues for Target Version/s:
> > 0.12.0-incubating is extended, right?
>

Yes. Let's extend those that have not started working if there's no
objection.

Re: License for templates and sdk

[Donald Szeto]

Hi Shinsuke,

It's a good question. Templates and SDKs are not part of an actual release
defined by ASF, and they don't go into ASF distribution network. That's why
they don't get voted on like the core release.

Would a mentor kindly weigh in on this? Templates are like hello-worlds
tailored for different ML use cases. SDKs are lightweight client code for
REST APIs exposed by core (event and engine server).

Regards,
Donald

On Tue, Jul 11, 2017 at 11:18 AM Shinsuke Sugaya  wrote:

> Hi,
>
> For license updates, my understanding is that we need to
> also update the following repositories for graduation.
> Is it correct? If yes, I'll file JIRA issues.
>
> https://github.com//apache/incubator-predictionio-sdk-python
> https://github.com//apache/incubator-predictionio-sdk-php
> https://github.com//apache/incubator-predictionio-sdk-ruby
> https://github.com//apache/incubator-predictionio-sdk-java
> https://github.com//apache/incubator-predictionio-template-recommender
> https://github.com//apache/incubator-predictionio-template-skeleton
> https://github.com//apache/incubator-predictionio-template-similar-product
> https://github.com//apache/incubator-predictionio-template-ecom-recommender
> https://github.com//apache/incubator-predictionio-template-text-classifier
>
> https://github.com//apache/incubator-predictionio-template-attribute-based-classifier
>
> https://github.com//apache/incubator-predictionio-template-java-ecom-recommender
>
> It seems not to update Swift SDK repository for a long time.
> If nobody update it, it's better to remove it at graduation.
>
> https://github.com//apache/incubator-predictionio-sdk-swift
>
> Regards,
>  shinsuke
>

[ANNOUNCE] Apache PredictionIO 0.11.0-incubating Release

[Donald Szeto]

The Apache PredictionIO team would like to announce the release of Apache
PredictionIO 0.11.0-incubating.

Release notes are here:
https://github.com/apache/incubator-predictionio/blob/v0.11.0-incubating/RELEASE.md

Apache PredictionIO (incubating) 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.

More details regarding Apache PredictionIO (incubating) can be found here:
http://predictionio.incubator.apache.org/

The release artifacts can be downloaded here:
https://dist.apache.org/repos/dist/release/incubator/predictionio/0.11.0-incubating/

All JIRAs completed for this release are tagged with 'FixVersion =
0.11.0-incubating'; the JIRA release notes can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320420=12338381

Thanks!
The Apache PredictionIO Team

DISCLAIMER
Apache PredictionIO (incubating) is an effort undergoing incubation at the
Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects. While incubation status is not necessarily a reflection of
the completeness or stability of the code, it does indicate that the
project has yet to be fully endorsed by the ASF.

Re: August 2017 Release

[Donald Szeto]

Hey Mars,

Is this the PR in question?
https://github.com/apache/incubator-predictionio/pull/372

Regards,
Donald

On Thu, Aug 3, 2017 at 11:49 AM, Mars Hall <m...@heroku.com> wrote:

> Hit an Authenticated Elasticsearch 5.x problem on the current develop
> branch.
>
> I just tested the HEAD of develop by performing:
>
>   ./make-distribution.sh \
> -Dscala.version=2.11.8 \
> -Dspark.version=2.1.0 \
> -Dhadoop.version=2.7.3 \
> -Delasticsearch.version=5.1.1
>
> Then, tried build/train/deploy of our Universal Recommender template.
>
> Locally, it makes it through train to the point when it saves to
> Elasticsearch, failing with:
>
> > Exception in thread "main" java.lang.NoSuchMethodError:
> org.elasticsearch.client.RestClient.performRequest(
> Ljava/lang/String;Ljava/lang/String;Ljava/util/Map;[Lorg/
> apache/http/Header;)Lorg/elasticsearch/client/Response;
> >   at org.template.EsClient$.createIndex(EsClient.scala:132)
> >   at org.template.EsClient$.hotSwap(EsClient.scala:218)
> >   at org.template.URModel.save(URModel.scala:86)
>
> I tried deploying it to Heroku as well, and it fails much earlier when
> simply connecting to Elasticsearch:
>
> > remote: Exception in thread "main" 
> > org.elasticsearch.client.ResponseException:
> HEAD https://xx.us-east-1.bonsaisearch.net:443/pio_meta: HTTP/1.1 401
> Unauthorized
> > remote:   at org.elasticsearch.client.RestClient$1.completed(
> RestClient.java:311)
> > remote:   at org.elasticsearch.client.RestClient$1.completed(
> RestClient.java:300)
> > remote:   at shadeio.data.http.concurrent.BasicFuture.completed(
> BasicFuture.java:119)
> > remote:   at shadeio.data.http.impl.nio.client.
> DefaultClientExchangeHandlerImpl.responseCompleted(
> DefaultClientExchangeHandlerImpl.java:177)
> > remote:   at shadeio.data.http.nio.protocol.
> HttpAsyncRequestExecutor.processResponse(HttpAsyncRequestExecutor.java:
> 436)
> > remote:   at shadeio.data.http.nio.protocol.
> HttpAsyncRequestExecutor.responseReceived(HttpAsyncRequestExecutor.java:
> 309)
> > remote:   at shadeio.data.http.impl.nio.
> DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.
> java:255)
>
>
> These issues were previously found to be caused by this shade rule:
>   https://github.com/apache/incubator-predictionio/blob/
> develop/storage/elasticsearch/build.sbt#L42
>
> It looks like the shaded package does not actually use the new
> authentication code.
>
> Chan Lee mentioned to me that he was only able to make the TravisCI build
> pass by adding this shade rule, but it is clearly breaking the authenicated
> Elasticsearch functionality.
>
> Any ideas how to solve this?
>
> *Mars
>
> ( <> .. <> )
>
> > On Aug 3, 2017, at 11:02, Donald Szeto <don...@apache.org> wrote:
> >
> > On Thu, Aug 3, 2017 at 10:07 AM, Mars Hall <m...@heroku.com> wrote:
> >
> >> I just opened a PR to add docs for batch predict.
> >>
> >> Moving forward with the 0.12.0 release sounds great. Today, I will pull
> >> develop and see how it's working with the Heroku buildpack.
> >>
> >
> > Awesome. Thanks!
> >
> >
> >>> On Aug 3, 2017, at 00:37, takako shimamoto <chiboch...@gmail.com>
> wrote:
> >>>
> >>> I think it's almost ready, and now we just have to update the current
> >>> documentation.
> >>> The deadline of several unresolved issues for Target Version/s:
> >>> 0.12.0-incubating is extended, right?
> >>
> >
> > Yes. Let's extend those that have not started working if there's no
> > objection.
>
>

New PMC member and committer: Mars Hall

[Donald Szeto]

Hi all,

The Project Management Committee (PMC) for Apache PredictionIO (incubating)
has asked Mars Hall to become a PMC member and committer, and we are
pleased to announce that he has accepted.

Mars has been working on PredictionIO since 0.10 and has suggested and made
changes to the core so that it has become more configurable and easier to
deploy on Heroku. He added authentication support to the REST-based
Elasticsearch client. He has also found and fixed core bugs.

Mars is the primary driver in delivering a good developer experience
through Heroku buildpacks for PredictionIO (
https://github.com/heroku/predictionio-buildpack), which allows engine
templates to be submitted to Heroku and deployed automatically. He also
made a couple engine templates that are preset to do so (
https://github.com/heroku/predictionio-engine-classification,
https://github.com/heroku/predictionio-engine-ur).

Being a committer enables easier contribution to the project since there is
no need to go via the patch submission process. This should enable better
productivity. Being a PMC member enables assistance with the management and
to guide the direction of the project.

Please join us in welcoming Mars.

Regards,
Donald

August 2017 Release

[Donald Szeto]

Hey all,

To adhere to the proposed release cadence by Sara, let's shoot to cut a
release in early August that addresses all the top level graduation issues.

How does the developer community feel about this? Any major issues that we
should also resolve with this release? It looks like many TLP cleanup, new
features and bug fixes have already gone into the current development
branch.

Regards,
Donald

May 2017 Podling Report

[Donald Szeto]

Hi all,

Please review the following report. Mentors, if this is good to go, please
put this on the incubator wiki.

Regards,
Donald

---

PredictionIO

PredictionIO is an open source Machine Learning Server built on top of a
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.

PredictionIO has been incubating since 2016-05-26. The initial code for
PredictionIO was granted on 2016-06-16. The second grant of PredictionIO
templates and SDKs was granted on 2016-09-20.

Three most important issues to address in the move towards graduation:

  1. Establish a formal release schedule and process, allowing for
dependable release cycles in a manner consistent with the Apache way.
  2. Grow the community to establish diversity of background.
  3. Transition remaining former PredictionIO users from google-groups to
ASF mailing lists.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

  None

How has the community developed since the last report?

  1. We have published the first release (0.11.0) that incorporates major
changes by non-committer contributors.
  2. There are new tutorials and online classes for PredictionIO by third
parties.
  3. The user mailing list has more activities than last report.
  4. GitHub stars keep growing.

How has the project developed since the last report?

  1. Released version 0.11.0 with major contributions from the
non-committer community.
  2. Established PMC documentation regarding release processes.
  3. In the process of preparing for top level graduation discussion.

Date of the last release:

  Apache PredictionIO 0.11.0-incubating on 2017-04-25

When were the last committers or PMC members elected?

  Naoki Takezoe was elected as committer and PMC member on Apr 28, 2017.
  Shinsuke Sugaya was elected as committer and PMC member on Apr 28, 2017.
  Takahiro Hagino was elected as committer and PMC member on Apr 28, 2017.
  Takako Shimamoto was elected as committer and PMC member on Apr 28, 2017.
  Sara Asher was elected as product manager and JIRA administrator on Apr
30, 2017.

New PMC member and committer: Shinsuke Sugaya

[Donald Szeto]

Hi all,

The Project Management Committee (PMC) for Apache PredictionIO (incubating)
has asked Shinsuke Sugaya to become a PMC member and committer, and we are
pleased to announce that he has accepted. He is also a committer of the
Apache Portals project.

He has made major contributions to the PredictionIO 0.11.0 release by
adding Elasticsearch 5 support. This shows solid understanding of the core
PredictionIO codebase. In addition, he also helped cleaning up and
refactoring code in the core. Having him join forces with us would be
beneficial for PredictionIO's growth.

Being a committer enables easier contribution to the project since there is
no need to go via the patch submission process. This should enable better
productivity. Being a PMC member enables assistance with the management and
to guide the direction of the project.

Please join us in welcoming Shinsuke.

Regards,
Donald

Re: Maintain template projects

[Donald Szeto]

So far we have been following a similar procedure outlined here:
http://mahout.apache.org/developers/github.html

We should definitely create our own committer documentation as well.

On Tue, May 9, 2017 at 8:43 PM Naoki Takezoe  wrote:

> Hi all,
>
> I found some pull requests which should be merged in template projects
> such as:
>
> -
> https://github.com/apache/incubator-predictionio-template-recommender/pull/16
> -
> https://github.com/apache/incubator-predictionio-template-java-ecom-recommender/pull/5
>
> I would like to take them, but I don't know a correct way to merge from
> GitHub.
> Just merge from GitHub and push it to ASF repo?
>
> Regards,
>
> --
> Naoki Takezoe
>

Re: Pipeline support for predictionIO

[Donald Szeto]

Hey Ravi,

For pipeline support do you mean Spark ML pipelines? If so, let's continue
the discussion on other thread named "Support for Spark ML pipelines". The
JIRA ticket is https://issues.apache.org/jira/browse/PIO-71.

Regards,
Donald

On Tue, May 16, 2017 at 3:55 AM, Ravi Kiran  wrote:

> Hi,
> How can I follow/contribute to development of 'pipeline support for
> predicitonio'?
>

Re: Support for spark ML pipelines

[Donald Szeto]

Hi Pankil,

Thank you for your interest. There is a ticket at
https://issues.apache.org/jira/browse/PIO-71. There isn't a design yet, so
we are open to collaborate on starting one.

Regards,
Donald

On Fri, May 12, 2017 at 11:04 AM, Pankil Doshi  wrote:

> Hi,
>
> I am interested to know about the road map of having Spark pipelines work
> natively with prediction.io. Is there a rough draft or plan ? May be JIRA
> ticket?
>
> Thanks,
> Pankil
>

Re: New PMC member and committer: Takahiro Hagino

[Donald Szeto]

Correction: Takahiro is not a committer of Apache Portals. Sorry for the
misinformation.

On Wed, May 17, 2017 at 8:50 AM, Donald Szeto <don...@apache.org> wrote:

> Hi all,
>
> The Project Management Committee (PMC) for Apache PredictionIO
> (incubating) has asked Takahiro Hagino to become a PMC member and
> committer, and we are pleased to announce that he has accepted. He is also
> a committer of the Apache Portals project.
>
> He has made major contributions to the PredictionIO 0.11.0 release by
> adding Elasticsearch 5 support. This shows solid understanding of the core
> PredictionIO codebase. In addition, he also helped cleaning up and
> refactoring code in the core. Having him join forces with us would be
> beneficial for PredictionIO's growth.
>
> Being a committer enables easier contribution to the project since there
> is no need to go via the patch submission process. This should enable
> better productivity. Being a PMC member enables assistance with the
> management and to guide the direction of the project.
>
> Please join us in welcoming Takahiro.
>
> Regards,
> Donald
>

New product manager: Sara Asher

[Donald Szeto]

Hi all,

The Project Management Committee (PMC) for Apache PredictionIO (incubating)
has asked Sara Asher to become a product manager, and we are pleased to
announce that she has accepted.

Sara is a Director of Product Management for Salesforce Einstein, where she
creates products that let people build smarter applications with Salesforce
and advanced AI. Prior to Salesforce, Sara worked at Alpine Data where she
was chief product manager and founding director of Alpine Labs. Sara holds
an AB in mathematics from Princeton University and a PhD in mathematics
from Northwestern University.

Being a product manager enables management of JIRA tickets. This should
make prioritizing product features more efficient.

Please join us in welcoming Sara.

Regards,
Donald

Re: GitHub settings for templates

[Donald Szeto]

Hey Shinsuke,

For GitHub integration issues, we need to file Apache JIRA tickets in the
INFRA project. They will be able to help. Please give it a shot.

Regards,
Donald

On Thu, May 11, 2017 at 9:18 PM Shinsuke Sugaya 
wrote:

> Hi,
>
> I have 2 questions for template repositories in GitHub:
>
> 1) incubator-predictionio-template-text-classifier
>
> This repository uses master branch as default, but others use develop.
> Can we change the default branch to develop?
>
> 2) incubator-predictionio-template-similar-product
>
> I updated this repository, but it seems not to send a notification mail
> to dev@predictionio.i.a.o. Could you check notification settings
> in this repository of GitHub?
>
> Regards,
>  shinsuke
>

Re: PIO 0.12.0 and Graduation Time?

[Donald Szeto]

Thanks Pat for starting this. Added some edits to it. Everyone please feel
free to comment. PMCs please feel free to request edit access.

Very happy that we started the discussion!

On Thu, May 18, 2017 at 1:50 PM Pat Ferrel  wrote:

> Should we apply for graduation to Apache TLP soon, like maybe the next
> release? I started a Google doc for features we want and any Mentors can
> add things we need to demonstrate for graduation since some may not be
> Jira-able.
>
> All user’s should feel free to input.
>
>
> https://docs.google.com/document/d/1LTlzxH_CcWi67p8kCQPfPyu-1SwIJBkEonH3Yw4T6pY/edit?usp=sharing

Re: [Proposal] Update the default build targets

[Donald Szeto]

By the way, one of the graduation criteria is to establish a stable release
process. Sara has proposed one, so let's review that as well.

On Thu, May 18, 2017 at 1:28 PM Donald Szeto <don...@apache.org> wrote:

> +1 on this. We should do a survey in user@ to measure the impact as well.
>
> We should start a separate thread for graduation discussion. There are a
> couple cleanups that we need to address and are already filed in JIRA.
>
> On Thu, May 18, 2017 at 10:07 AM Naoki Takezoe <take...@gmail.com> wrote:
>
>> Hi all,
>>
>> Currently, the default build targets look like following:
>>
>> - PIO_SCALA_VERSION=2.10.6
>> - PIO_SPARK_VERSION=1.6.3
>> - PIO_ELASTICSEARCH_VERSION=1.7.6
>> - PIO_HADOOP_VERSION=2.6.5
>>
>> However they look too old now despite PredictionIO has supported newer
>> versions.
>> How is change the default build targets as following?
>>
>> - PIO_SCALA_VERSION=2.11.8
>> - PIO_SPARK_VERSION=2.1.0
>> - PIO_ELASTICSEARCH_VERSION=5.2.2
>> - PIO_HADOOP_VERSION=2.7.3
>>
>> Also, are there roadmap for graduating incubator?
>> It might have to contain the plan of default and supported versions if
>> we will change them.
>>
>> Regards,
>>
>> --
>> Naoki Takezoe
>>
>

Re: JIRA and release process for PredictionIO

[Donald Szeto]

+1. Thanks Sara!

On Thu, May 18, 2017 at 8:48 AM Sara Asher  wrote:

> Hi everyone,
>
> Thank you for allowing me to join the PredictionIO team!
>
> To start with, I would like to document a process for using JIRA and to
> suggest a standard release cadence for PredictionIO.
>
> I've worked with Donald to come up with the following:
>
> https://docs.google.com/document/d/1nQpENncXZq72KeI3WMe_
> X8Xz8HKkYO2QC12GD3ZKP9g/edit?usp=sharing
>
> Please comment and give suggestions!  When you are all content, I will add
> this to our public documentation.
>
> Thanks,
> Sara
>

Re: [Proposal] Update the default build targets

[Donald Szeto]

+1 on this. We should do a survey in user@ to measure the impact as well.

We should start a separate thread for graduation discussion. There are a
couple cleanups that we need to address and are already filed in JIRA.

On Thu, May 18, 2017 at 10:07 AM Naoki Takezoe  wrote:

> Hi all,
>
> Currently, the default build targets look like following:
>
> - PIO_SCALA_VERSION=2.10.6
> - PIO_SPARK_VERSION=1.6.3
> - PIO_ELASTICSEARCH_VERSION=1.7.6
> - PIO_HADOOP_VERSION=2.6.5
>
> However they look too old now despite PredictionIO has supported newer
> versions.
> How is change the default build targets as following?
>
> - PIO_SCALA_VERSION=2.11.8
> - PIO_SPARK_VERSION=2.1.0
> - PIO_ELASTICSEARCH_VERSION=5.2.2
> - PIO_HADOOP_VERSION=2.7.3
>
> Also, are there roadmap for graduating incubator?
> It might have to contain the plan of default and supported versions if
> we will change them.
>
> Regards,
>
> --
> Naoki Takezoe
>

Re: PIO 0.12.0 and Graduation Time?

[Donald Szeto]

Hey Andrew, is it possible for us to create non-release binary
distributions and ask Incubator PMC to help take a look without starting a
voting thread? This would allow us iron out issues in parallel to working
on 0.12.

On Wed, May 31, 2017 at 9:08 AM, Andrew Purtell  wrote:

> Really glad to see this discussion started, because I think your podling
> is nearing graduation. The most important determination of that is taking
> the initiative to propose it.
>
> I looked over the spreadsheet and have only this comment: You'll gain from
> having the incubator picking over your binary artifact release attempt, the
> first time you try to put one together. You won't have that after
> graduation. I recommend working through binary artifacts as part of 0.12,
> then proposing yourselves for graduation.
>
>
> On Thu, May 18, 2017 at 1:49 PM, Pat Ferrel  wrote:
>
>> Should we apply for graduation to Apache TLP soon, like maybe the next
>> release? I started a Google doc for features we want and any Mentors can
>> add things we need to demonstrate for graduation since some may not be
>> Jira-able.
>>
>> All user’s should feel free to input.
>>
>> https://docs.google.com/document/d/1LTlzxH_CcWi67p8kCQPfPyu-
>> 1SwIJBkEonH3Yw4T6pY/edit?usp=sharing
>
>
>
>
> --
> Best regards,
>
>- Andy
>
> If you are given a choice, you believe you have acted freely. - Raymond
> Teller (via Peter Watts)
>

Re: May 2017 Podling Report

[Donald Szeto]

Adding a note that the new PMC members were voted on but status change has
not yet completed. Please review.

---

PredictionIO

PredictionIO is an open source Machine Learning Server built on top of a
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.

PredictionIO has been incubating since 2016-05-26. The initial code for
PredictionIO was granted on 2016-06-16. The second grant of PredictionIO
templates and SDKs was granted on 2016-09-20.

Three most important issues to address in the move towards graduation:

  1. Establish a formal release schedule and process, allowing for
dependable release cycles in a manner consistent with the Apache way.
  2. Grow the community to establish diversity of background.
  3. Transition remaining former PredictionIO users from google-groups to
ASF mailing lists.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

  None

How has the community developed since the last report?

  1. We have published the first release (0.11.0) that incorporates major
changes by non-committer contributors.
  2. There are new tutorials and online classes for PredictionIO by third
parties.
  3. The user mailing list has more activities than last report.
  4. GitHub stars keep growing.

How has the project developed since the last report?

  1. Released version 0.11.0 with major contributions from the
non-committer community.
  2. Established PMC documentation regarding release processes.
  3. In the process of preparing for top level graduation discussion.

Date of the last release:

  Apache PredictionIO 0.11.0-incubating on 2017-04-25

When were the last committers or PMC members elected?

  Naoki Takezoe was elected as committer and PMC member on Apr 28, 2017,
pending acceptance of invitation and status change.
  Shinsuke Sugaya was elected as committer and PMC member on Apr 28, 2017,
pending acceptance of invitation and status change.
  Takahiro Hagino was elected as committer and PMC member on Apr 28, 2017,
pending acceptance of invitation and status change.
  Takako Shimamoto was elected as committer and PMC member on Apr 28, 2017,
pending acceptance of invitation and status change.
  Sara Asher was elected as product manager and JIRA administrator on Apr
30, 2017.

On Tue, May 2, 2017 at 10:29 AM, Donald Szeto <don...@apache.org> wrote:

> Hi all,
>
> Please review the following report. Mentors, if this is good to go, please
> put this on the incubator wiki.
>
> Regards,
> Donald
>
> ---
>
> PredictionIO
>
> PredictionIO is an open source Machine Learning Server built on top of a
> 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.
>
> PredictionIO has been incubating since 2016-05-26. The initial code for
> PredictionIO was granted on 2016-06-16. The second grant of PredictionIO
> templates and SDKs was granted on 2016-09-20.
>
> Three most important issues to address in the move towards graduation:
>
>   1. Establish a formal release schedule and process, allowing for
> dependable release cycles in a manner consistent with the Apache way.
>   2. Grow the community to establish diversity of background.
>   3. Transition remaining former PredictionIO users from google-groups to
> ASF mailing lists.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   None
>
> How has the community developed since the last report?
>
>   1. We have published the first release (0.11.0) that incorporates major
> changes by non-committer contributors.
>   2. There are new tutorials and online classes for PredictionIO by third
> parties.
>   3. The user mailing list has more activities than last report.
>   4. GitHub stars keep growing.
>
> How has the project developed since the last report?
>
>   1. Released version 0.11.0 with major contributions from the
> non-committer community.
>   2. Established PMC documentation regarding release processes.
>   3. In the process of preparing for top level graduation discussion.
>
> Date of the last release:
>
>   Apache PredictionIO 0.11.0-incubating on 2017-04-25
>
> When were the last committers or PMC members elected?
>
>   Naoki Takezoe was elected as committer and PMC member on Apr 28, 2017.
>   Shinsuke Sugaya was elected as committer and PMC member on Apr 28, 2017.
>   Takahiro Hagino was elected as committer and PMC member on Apr 28, 2017.
>   Takako Shimamoto was elected as committer and PMC member on Apr 28, 2017.
>   Sara Asher was elected as product manager and JIRA administrator on Apr
> 30, 2017.
>

Re: [VOTE] Apache PredictionIO (incubating) 0.12.0 Release (RC2)

[Donald Szeto]

Votes are tied to tag/commit by ASF convention, so a new RC and vote will
be required.

On Fri, Sep 15, 2017 at 10:57 AM Mars Hall <mars.h...@salesforce.com> wrote:

> I just opened a release notes PR against apache:release/0.12.0, because
> that seems to be the right place.
>
> Chan, will that work okay with the release process?
>
> On Fri, Sep 15, 2017 at 10:20 AM, Mars Hall <mars.h...@salesforce.com>
> wrote:
>
> > Also, I'd love to directly link the PIO-* issue numbers to JIRA.
> >
> > On Fri, Sep 15, 2017 at 10:19 AM, Mars Hall <mars.h...@salesforce.com>
> > wrote:
> >
> >> RC2 is working perfectly.
> >>
> >> I see a few issues with the releases notes:
> >>
> >>
> >>- PIO-95 should be "Raised request timeout for REST API to
> 35-seconds"
> >>- PIO-102, PIO-106, PIO-117, PIO-118, PIO-120 actually includes a
> >>breaking change to Elasticsearch 5.x StorageClient interface. I
> think these
> >>should be enumerated more explicitly with one of them called out in a
> >>"Breaking changes" section.
> >>
> >> May I revise RELEASE.md on develop to fix these issues? Does that
> require
> >> restarting vote for an RC3?
> >>
> >>
> >> On Thu, Sep 14, 2017 at 11:49 PM, Donald Szeto <don...@apache.org>
> wrote:
> >>
> >>> I believe those are fixed by PIO-60, PIO-62 and PIO-63 in the release
> >>> notes.
> >>>
> >>> +1 binding from me
> >>>
> >>> On Thu, Sep 14, 2017 at 2:13 PM Pat Ferrel <p...@occamsmachete.com>
> >>> wrote:
> >>>
> >>> > The last release was hung up by the IPMC regarding content licensing
> >>> > issues and libraries used by the doc site, which we promised to
> >>> address in
> >>> > this release. Have these been resolved, don’t recall the specifics?
> It
> >>> > would be great to fly through the IPMC vote without issue.
> >>> >
> >>> >
> >>> > On Sep 14, 2017, at 2:06 PM, Chan Lee <chanlee...@gmail.com> wrote:
> >>> >
> >>> > This is the vote for 0.12.0 of Apache PredictionIO (incubating).
> >>> >
> >>> > The vote will run for at least 72 hours and will close on Sep 17th,
> >>> 2017.
> >>> >
> >>> > The release candidate artifacts can be downloaded here:
> >>> > https://dist.apache.org/repos/dist/dev/incubator/predi
> >>> > ctionio/0.12.0-incubating-rc2
> >>> >
> >>> > Test results of RC1 can be found here: https://travis-ci.org/ap
> >>> > ache/incubator-predictionio/builds/275634960
> >>> >
> >>> > Maven artifacts are built from the release candidate artifacts above,
> >>> and
> >>> > are provided as convenience for testing with engine templates. The
> >>> Maven
> >>> > artifacts are provided at the Maven staging repo here:
> >>> >
> >>> > https://repository.apache.org/content/repositories/orgapache
> >>> predictionio-1020
> >>> >
> >>> > All JIRAs completed for this release are tagged with 'FixVersion =
> >>> > 0.12.0-incubating'. You can view them here: https://issues.apache.or
> >>> > g/jira/secure/ReleaseNote.jspa?version=12340591=12320420
> >>> >
> >>> > The artifacts have been signed with Key: ytX8GpWv
> >>> >
> >>> > Please vote accordingly:
> >>> >
> >>> > [ ] +1, accept RC as the official 0.12.0 release
> >>> > [ ] -1, do not accept RC as the official 0.12.0 release because...
> >>> >
> >>> >
> >>>
> >>
> >>
> >>
> >> --
> >> *Mars Hall
> >> 415-818-7039 <(415)%20818-7039>
> >> Customer Facing Architect
> >> Salesforce Platform / Heroku
> >> San Francisco, California
> >>
> >
> >
> >
> > --
> > *Mars Hall
> > 415-818-7039 <(415)%20818-7039>
> > Customer Facing Architect
> > Salesforce Platform / Heroku
> > San Francisco, California
> >
>
>
>
> --
> *Mars Hall
> 415-818-7039
> Customer Facing Architect
> Salesforce Platform / Heroku
> San Francisco, California
>

Re: [VOTE] Apache PredictionIO (incubating) 0.12.0 Release (RC2)

[Donald Szeto]

I believe those are fixed by PIO-60, PIO-62 and PIO-63 in the release notes.

+1 binding from me

On Thu, Sep 14, 2017 at 2:13 PM Pat Ferrel  wrote:

> The last release was hung up by the IPMC regarding content licensing
> issues and libraries used by the doc site, which we promised to address in
> this release. Have these been resolved, don’t recall the specifics? It
> would be great to fly through the IPMC vote without issue.
>
>
> On Sep 14, 2017, at 2:06 PM, Chan Lee  wrote:
>
> This is the vote for 0.12.0 of Apache PredictionIO (incubating).
>
> The vote will run for at least 72 hours and will close on Sep 17th, 2017.
>
> The release candidate artifacts can be downloaded here:
> https://dist.apache.org/repos/dist/dev/incubator/predi
> ctionio/0.12.0-incubating-rc2
>
> Test results of RC1 can be found here: https://travis-ci.org/ap
> ache/incubator-predictionio/builds/275634960
>
> Maven artifacts are built from the release candidate artifacts above, and
> are provided as convenience for testing with engine templates. The Maven
> artifacts are provided at the Maven staging repo here:
>
> https://repository.apache.org/content/repositories/orgapachepredictionio-1020
>
> All JIRAs completed for this release are tagged with 'FixVersion =
> 0.12.0-incubating'. You can view them here: https://issues.apache.or
> g/jira/secure/ReleaseNote.jspa?version=12340591=12320420
>
> The artifacts have been signed with Key: ytX8GpWv
>
> Please vote accordingly:
>
> [ ] +1, accept RC as the official 0.12.0 release
> [ ] -1, do not accept RC as the official 0.12.0 release because...
>
>

Re: [VOTE] Apache PredictionIO (incubating) 0.12.0 Release (RC2)

[Donald Szeto]

That should be fine. Chan, the binary distribution package should be
treated the same as what we are doing with publishing Maven artifacts
(classified as convenience binaries by ASF). Instead of going to Nexus,
they need to go alongside the source (i.e. SVN). We will similarly need to
produce PGP signature, MD5 and SHA512 for the binary distribution.

On Sat, Sep 16, 2017 at 5:13 AM Naoki Takezoe  wrote:

> Can we publish the binary distribution which is built by
> make-distribution.sh together?
> It would makes possible newbies to try PredictionIO in default
> combination without build from source code.
>
> I fixed make-distribution.sh to include a license file in PIO-69, so
> it's ready to be released.
>
> https://github.com/apache/incubator-predictionio/commit/2a4ecf3bc873a5fc5532c1b95166b9232e82d525#diff-a482fdd2c39acfb78529c30718c3c9ab
>
> 2017-09-15 6:06 GMT+09:00 Chan Lee :
> > This is the vote for 0.12.0 of Apache PredictionIO (incubating).
> >
> > The vote will run for at least 72 hours and will close on Sep 17th, 2017.
> >
> > The release candidate artifacts can be downloaded here:
> > https://dist.apache.org/repos/dist/dev/incubator/predi
> > ctionio/0.12.0-incubating-rc2
> >
> > Test results of RC1 can be found here: https://travis-ci.org/ap
> > ache/incubator-predictionio/builds/275634960
> >
> > Maven artifacts are built from the release candidate artifacts above, and
> > are provided as convenience for testing with engine templates. The Maven
> > artifacts are provided at the Maven staging repo here:
> >
> https://repository.apache.org/content/repositories/orgapachepredictionio-1020
> >
> > All JIRAs completed for this release are tagged with 'FixVersion =
> > 0.12.0-incubating'. You can view them here: https://issues.apache.or
> > g/jira/secure/ReleaseNote.jspa?version=12340591=12320420
> >
> > The artifacts have been signed with Key: ytX8GpWv
> >
> > Please vote accordingly:
> >
> > [ ] +1, accept RC as the official 0.12.0 release
> > [ ] -1, do not accept RC as the official 0.12.0 release because...
>
>
>
> --
> Naoki Takezoe
>

Re: Graduation to TLP

[Donald Szeto]

Goal is the follow Apache's convention, so I think we will proceed with the
same list, excluding those who have requested to be excluded.

On Mon, Sep 18, 2017 at 11:00 AM Luciano Resende <luckbr1...@gmail.com>
wrote:

> On Mon, Aug 28, 2017 at 10:20 PM, Donald Szeto <don...@apache.org> wrote:
>
> > Hi all,
> >
> > Since the ASF Board meeting in May (
> > http://apache.org/foundation/records/minutes/2017/board_
> > minutes_2017_05_17.txt),
> > PredictionIO has been considered nearing graduation and I think we are
> > almost there. I am kickstarting this thread so that we can discuss on
> these
> > 3 things:
> >
> > 1. Does the development community feel ready to graduate?
> >
>
> +1
>
>
> > 2. If we are to graduate, who should we include in the list of the
> initial
> > PMC?
> >
>
> Not sure about the goal of the question, but usually the PPMC will become
> the PMC unless you had done explicit committer versus ppmc votes or folks
> explicitly request to leave.
>
>
> > 3. If we are to graduate, who should be the VP of the initial PMC?
> >
> > These points are relevant for graduation. Please take a look at the
> > official graduation guide:
> > http://incubator.apache.org/guides/graduation.html.
> >
> > In addition, Sara and I have been working to transfer the PredictionIO
> > trademark to the ASF. We will keep you updated with our progress.
> >
> > I would also like to propose to cut a 0.12.0 release by merging JIRAs
> that
> > have a target version set to 0.12.0-incubating for graduation. 0.12.0
> will
> > contain cleanups for minor license and copyright issues that were pointed
> > out in previous releases by IPMC.
> >
> > Let me know what you think.
> >
> > Regards,
> > Donald
> >
>
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>

Re: [VOTE] Apache PredictionIO (incubating) 0.12.0 Release (RC3)

[Donald Szeto]

+1 binding

I checked:
- Downloads matched PGP signatures, MD5, and SHA512
- Binaries working out of the box
- Test results on Travis
- Maven artifacts structure in good shape

Thanks, Chan!

On Sun, Sep 17, 2017 at 11:31 AM, Chan Lee  wrote:

> This is the vote for 0.12.0 of Apache PredictionIO (incubating).
>
> The vote will run for at least 72 hours and will close on Sep 20th, 2017.
>
> The release candidate artifacts can be downloaded here:
> https://dist.apache.org/repos/dist/dev/incubator/predictionio/0.12.0-
> incubating-rc3
>
> Test results of RC3 can be found here:
> https://travis-ci.org/apache/incubator-predictionio/builds/276558626
>
> Maven artifacts are built from the release candidate artifacts above, and
> are provided as convenience for testing with engine templates. The Maven
> artifacts are provided at the Maven staging repo here:
> https://repository.apache.org/content/repositories/
> orgapachepredictionio-1021/
>
> All JIRAs completed for this release are tagged with 'FixVersion =
> 0.12.0-incubating'. You can view them here: https://issues.apache.or
> g/jira/secure/ReleaseNote.jspa?version=12340591=12320420
>
> The artifacts have been signed with Key: ytX8GpWv
>
> Please vote accordingly:
>
> [ ] +1, accept RC as the official 0.12.0 release
> [ ] -1, do not accept RC as the official 0.12.0 release because...
>

[DISCUSS] Resolution to create a TLP from graduating Incubator podling

[Donald Szeto]

Hi all,

Based on the previous discussion (
https://lists.apache.org/thread.html/2b4ef7c394584988cf0c99920824afaa60ee4c648d5c0069b1bf55c0@%3Cdev.predictionio.apache.org%3E),
I would like to start discussing a graduation resolution and reach a
consent before starting a community vote on the following. Please read
carefully the resolution, and voice any concerns you may have. If you are a
current PMC member, please make sure your name is listed unless you have
already asked to be excluded. We will start an official community vote when
a consent is reached.

Regarding the PredictionIO trademark assignment, Salesforce has signed and
executed an assignment agreement, and is only pending ASF to countersign.

The graduation process we are following is described here:
http://incubator.apache.org/guides/graduation.html

Thank you all! Let's graduate.

Regards,
Donald

-

X. Establish the Apache PredictionIO Project

   WHEREAS, the Board of Directors deems it to be in the best
   interests of the Foundation and consistent with the
   Foundation's purpose to establish a Project Management
   Committee charged with the creation and maintenance of
   open-source software, for distribution at no charge to
   the public, related to a 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.

   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the "Apache PredictionIO Project",
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further

   RESOLVED, that the Apache PredictionIO Project be and hereby is
   responsible for the creation and maintenance of software
   related to a 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;
   and be it further

   RESOLVED, that the office of "Vice President, Apache PredictionIO" be
   and hereby is created, the person holding such office to
   serve at the direction of the Board of Directors as the chair
   of the Apache PredictionIO Project, and to have primary
responsibility
   for management of the projects within the scope of
   responsibility of the Apache PredictionIO Project; and be it further

   RESOLVED, that the persons listed immediately below be and
   hereby are appointed to serve as the initial members of the
   Apache PredictionIO Project:

 * Alex Merritt <emergentor...@apache.org>
 * Andrew Kyle Purtell <apurt...@apache.org>
 * Chan Lee <chan...@apache.org>
 * Donald Szeto <don...@apache.org>
 * Felipe Oliveira <fel...@apache.org>
 * James Taylor <jtay...@apache.org>
 * Justin Yip <yipjus...@apache.org>
 * Kenneth Chan <kenn...@apache.org>
 * Lars Hofhansl <la...@apache.org>
 * Lee Moon Soo <m...@apache.org>
 * Luciano Resende <lrese...@apache.org>
 * Marcin Ziemiński <zie...@apache.org>
 * Marco Vivero <mviv...@apache.org>
 * Mars Hall <m...@apache.org>
 * Matthew Tovbin <tovb...@apache.org>
 * Naoki Takezoe <take...@apache.org>
 * Pat Ferrel <p...@apache.org>
 * Paul Li <pau...@apache.org>
 * Shinsuke Sugaya <shins...@apache.org>
 * Simon Chan <sim...@apache.org>
 * Takahiro Hagino <hag...@apache.org>
 * Takako Shimamoto <shimam...@apache.org>
 * Tamas Jambor <tjam...@apache.org>
 * Tom Chan <tc...@apache.org>
 * Vitaly Gordon <vit...@apache.org>
 * Xiangrui Meng <m...@apache.org>
 * Xusen Yin <y...@apache.org>
 * Yevgeny Khodorkovsky <y...@apache.org>

   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Donald Szeto
   be appointed to the office of Vice President, Apache PredictionIO, to
   serve in accordance with and subject to the direction of the
   Board of Directors and the Bylaws of the Foundation until
   death, resignation, retirement, removal or disqualification,
   or until a successor is appointed; and be it further

   RESOLVED, that the initial Apache PredictionIO PMC be and hereby is
   tasked with the creation of a set of bylaws intended to
   encourage open development and increased participation in the
   Apache PredictionIO Project; and be it further

   RESOLVED, that the Apache PredictionIO Project be and hereby
   is tasked with the migration and rationalization of the Apache
  

Re: [ANNOUNCE] Apache PredictionIO 0.12.0-incubating Release

[Donald Szeto]

The doc build failed at Scaladoc:
https://builds.apache.org/job/PredictionIO-build-site/78/console

And this has blocked the subsequent publish build. I'll just go ahead and
disable Scaladoc generation for now to get the main site updated first.

On Mon, Oct 2, 2017 at 12:59 PM, Mars Hall  wrote:

> Actually, I still don't see the updates for version 0.12.0.
>
> Why don't we see this "Batch Predictions" entry on the docs site?
>
> https://github.com/apache/incubator-predictionio/blob/
> develop/docs/manual/data/nav/main.yml#L65
>
> When I made that change locally, that entry did appear under "Deploying an
> Engine" navigation section, but it's still not on the docs site:
>   https://predictionio.incubator.apache.org/deploy/
>
>
> On Mon, Oct 2, 2017 at 12:52 PM, Mars Hall 
> wrote:
>
> > Thank you Chan!
> >
> > On Thu, Sep 28, 2017 at 9:02 AM, Chan Lee  wrote:
> >
> >> My apologies. The doc site has been updated now.
> >>
> >
> >
> >
> > --
> > *Mars Hall
> > 415-818-7039 <(415)%20818-7039>
> > Customer Facing Architect
> > Salesforce Platform / Heroku
> > San Francisco, California
> >
> >
> > 
> >
>
>
>
> --
> *Mars Hall
> 415-818-7039
> Customer Facing Architect
> Salesforce Platform / Heroku
> San Francisco, California
>
>
> 
>

Re: [ANNOUNCE] Apache PredictionIO 0.12.0-incubating Release

[Donald Szeto]

Mars, it's fixed now.

Re: https://issues.apache.org/jira/browse/INFRA-15208

On Mon, Oct 2, 2017 at 3:37 PM, Donald Szeto <don...@apache.org> wrote:

> The build went through but the site is not reflecting the new version. I
> will open a ticket against ASF Infra to take a look.
>
> On Mon, Oct 2, 2017 at 2:47 PM, Donald Szeto <don...@apache.org> wrote:
>
>> The doc build failed at Scaladoc: https://builds.apach
>> e.org/job/PredictionIO-build-site/78/console
>>
>> And this has blocked the subsequent publish build. I'll just go ahead and
>> disable Scaladoc generation for now to get the main site updated first.
>>
>> On Mon, Oct 2, 2017 at 12:59 PM, Mars Hall <mars.h...@salesforce.com>
>> wrote:
>>
>>> Actually, I still don't see the updates for version 0.12.0.
>>>
>>> Why don't we see this "Batch Predictions" entry on the docs site?
>>>
>>> https://github.com/apache/incubator-predictionio/blob/develo
>>> p/docs/manual/data/nav/main.yml#L65
>>>
>>> When I made that change locally, that entry did appear under "Deploying
>>> an
>>> Engine" navigation section, but it's still not on the docs site:
>>>   https://predictionio.incubator.apache.org/deploy/
>>>
>>>
>>> On Mon, Oct 2, 2017 at 12:52 PM, Mars Hall <mars.h...@salesforce.com>
>>> wrote:
>>>
>>> > Thank you Chan!
>>> >
>>> > On Thu, Sep 28, 2017 at 9:02 AM, Chan Lee <chanlee...@gmail.com>
>>> wrote:
>>> >
>>> >> My apologies. The doc site has been updated now.
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > *Mars Hall
>>> > 415-818-7039 <(415)%20818-7039>
>>> > Customer Facing Architect
>>> > Salesforce Platform / Heroku
>>> > San Francisco, California
>>> >
>>> >
>>> > <http://smart.salesforce.com/sig/mars.hall//us_mb/default/link.html>
>>> >
>>>
>>>
>>>
>>> --
>>> *Mars Hall
>>> 415-818-7039
>>> Customer Facing Architect
>>> Salesforce Platform / Heroku
>>> San Francisco, California
>>>
>>>
>>> <http://smart.salesforce.com/sig/mars.hall//us_mb/default/link.html>
>>>
>>
>>
>

Re: [ANNOUNCE] Apache PredictionIO 0.12.0-incubating Release

[Donald Szeto]

The build went through but the site is not reflecting the new version. I
will open a ticket against ASF Infra to take a look.

On Mon, Oct 2, 2017 at 2:47 PM, Donald Szeto <don...@apache.org> wrote:

> The doc build failed at Scaladoc: https://builds.
> apache.org/job/PredictionIO-build-site/78/console
>
> And this has blocked the subsequent publish build. I'll just go ahead and
> disable Scaladoc generation for now to get the main site updated first.
>
> On Mon, Oct 2, 2017 at 12:59 PM, Mars Hall <mars.h...@salesforce.com>
> wrote:
>
>> Actually, I still don't see the updates for version 0.12.0.
>>
>> Why don't we see this "Batch Predictions" entry on the docs site?
>>
>> https://github.com/apache/incubator-predictionio/blob/develo
>> p/docs/manual/data/nav/main.yml#L65
>>
>> When I made that change locally, that entry did appear under "Deploying an
>> Engine" navigation section, but it's still not on the docs site:
>>   https://predictionio.incubator.apache.org/deploy/
>>
>>
>> On Mon, Oct 2, 2017 at 12:52 PM, Mars Hall <mars.h...@salesforce.com>
>> wrote:
>>
>> > Thank you Chan!
>> >
>> > On Thu, Sep 28, 2017 at 9:02 AM, Chan Lee <chanlee...@gmail.com> wrote:
>> >
>> >> My apologies. The doc site has been updated now.
>> >>
>> >
>> >
>> >
>> > --
>> > *Mars Hall
>> > 415-818-7039 <(415)%20818-7039>
>> > Customer Facing Architect
>> > Salesforce Platform / Heroku
>> > San Francisco, California
>> >
>> >
>> > <http://smart.salesforce.com/sig/mars.hall//us_mb/default/link.html>
>> >
>>
>>
>>
>> --
>> *Mars Hall
>> 415-818-7039
>> Customer Facing Architect
>> Salesforce Platform / Heroku
>> San Francisco, California
>>
>>
>> <http://smart.salesforce.com/sig/mars.hall//us_mb/default/link.html>
>>
>
>

Call for quote for the upcoming PredictionIO graduation announcement

[Donald Szeto]

Dear PredictionIO community,

With your support and contribution over the past year, the PredictionIO
project is now very close to graduating to become a top-level project. The
Apache Incubator PMC has voted positively on our proposed graduation, and
it will be included in the ASF Board Meeting on 10/18.

Once the graduation proposal passed, ASF will help make a press release
formally announcing PredictionIO's graduation. There is an opportunity to
include a few quotes from the community. If you find PredictionIO helpful
and would like to be part of the press release, please drop us a message
with your name, affiliation, and the text your quote.

Upon ASF accepting our graduation resolution on 10/18, the press release
will go out the following week. Please note that only a few quotes can be
included, so apologies in advance if yours is not included.

Regards,
Donald

Re: Graduation to TLP

[Donald Szeto]

It would be my pleasure to pick up TLP Chair responsibilities if nobody
objects.

Andrew, it would be really great and beneficial to the community if you
could stay on mentoring as PMC of the new TLP. Could you also help update
the project status page on the incubator site please?

I will reference other podling's graduation proposal and draft a board
resolution.

On Thu, Sep 7, 2017 at 1:26 PM, Andrew Purtell <andrew.purt...@gmail.com>
wrote:

> Donald would be great.
> Donald - please think about it.
>
> It was suggested privately to me that I stay on from mentoring as PMC. If
> you'll have me, I would be glad to help the new TLP as/if needed.
>
>
> > On Sep 7, 2017, at 6:07 PM, Pat Ferrel <p...@occamsmachete.com> wrote:
> >
> > This has been an informal poll and it looks like people are ready. I
> suggest we push for graduation after the next release, which will be done
> by someone not Donald, I think we have 2 volunteers? I think this will be a
> requirement since it’s been mentioned by several IPMC members.
> >
> > I’d like to think several people could be our candidate VP but since
> most of them are too busy and since we have another great candidate in
> Donald, I’d like to nominate him for TLP Chair/VP.
> >
> > I’d suggest we poll the committers and PMC members to see if any want
> out of the TLP, and otherwise go with the current list. We should try to
> add any committers that are ready before the graduation push, the more the
> better to the IPMC.
> >
> > We should put this in a proposal and get mentors feedback before
> applying since mentors are also IPMC members.
> >
> > Andy has mentioned several choices for convention that we should
> discuss, like our choice of git flow for commit process. He mentioned
> rotating Chair, which seems better suited to a larger project IMO but
> please chime in if you like the idea.
> >
> > If that is all clear we have to release, have a podling vote, then have
> the IPMC vote. If there is anything else regarding how we are run speak up
> now.
> >
> >
> > On Sep 7, 2017, at 5:01 AM, takako shimamoto <chiboch...@gmail.com>
> wrote:
> >
> > I'd like to remain as committer and contribute my humble efforts to
> > the prosperity of the project.
> >
> >> I propose we stay with the current PMC and committer list unless
> someone wants to remove themselves.
> >
> > It may be good. In fact, most of committers carry out a task with
> > limited time. Anyway I hope the project will progress in a good
> > direction.
> >
> >
> >
> > 2017-09-06 3:43 GMT+09:00 Pat Ferrel <p...@occamsmachete.com>:
> >> I personally don’t see much benefit in removing people unless they
> prove the exception. AFAIK this generally does not happen in ASF. I’m
> certainly not aware of the process except that it is easier in moving from
> podling to TLP.  You prove some worthiness and once that’s done, it’s done.
> A poll might just ask project members if they want to be removed. I have
> seen people ask to be removed from PMC and also “go emeritus” and those are
> cases of the individuals making the choice.
> >>
> >> So to settle the role call issue I propose we stay with the current PMC
> and committer list unless someone wants to remove themselves.
> >>
> >> As to maturity I agree with Donald that the checklist is heavy in our
> favor.
> >>
> >>
> >> On Sep 5, 2017, at 11:16 AM, Simon Chan <si...@salesforce.com> wrote:
> >>
> >> +1 for graduation
> >>
> >>> On Tue, Sep 5, 2017 at 10:32 AM, Donald Szeto <don...@apache.org>
> wrote:
> >>>
> >>> Thanks for the clarification Pat! It always help to have Apache
> veterans to
> >>> provide historical context to these processes.
> >>>
> >>> As for me, I'd like to remain as PMC and committer.
> >>>
> >>> I like the idea of polling the current committers and PMC, but like you
> >>> said, most of them got pretty busy and may not be reading mailing list
> in a
> >>> while. Maybe let me try a shout out here and see if anyone would
> >>> acknowledge it, so that we know whether a poll will be effective.
> >>>
> >>> *>> If you're a PMC or committer who see this line but hasn't been
> replying
> >>> this thread, please acknowledge. <<*
> >>>
> >>> Regarding the maturity model, this is my perception right now:
> >>> - CD10, CD20, CD30, CD40 (and we start to have CD50 as well)
> >>> - LC10, LC20, LC30, LC40, LC50
> >>

Re: Graduation to TLP

[Donald Szeto]

Thanks for the clarification Pat! It always help to have Apache veterans to
provide historical context to these processes.

As for me, I'd like to remain as PMC and committer.

I like the idea of polling the current committers and PMC, but like you
said, most of them got pretty busy and may not be reading mailing list in a
while. Maybe let me try a shout out here and see if anyone would
acknowledge it, so that we know whether a poll will be effective.

*>> If you're a PMC or committer who see this line but hasn't been replying
this thread, please acknowledge. <<*

Regarding the maturity model, this is my perception right now:
- CD10, CD20, CD30, CD40 (and we start to have CD50 as well)
- LC10, LC20, LC30, LC40, LC50
- RE10, RE20, RE30, RE50 (I think we hope to also do RE40 with 0.12)
- QU10, QU30, QU40, QU50 (we should put a bit of focus to QU20)
- CO10, CO20, CO30, CO40, CO60, CO70 (for CO50, I think we've been
operating under the assumption that PMC and contributors are pretty
standard definitions by ASF. We can call those out explicitly.)
- CS10, CS50 (We are also assuming implicitly CS20, CS30, and CS40 from
main ASF doc)
- IN10, IN20

Let me know what you think.

On Fri, Sep 1, 2017 at 10:32 AM, Pat Ferrel <p...@occamsmachete.com> wrote:

> The Chair, PMC, and Committers may be different after graduation.
> PMC/committers are sometimes not active committers but can have a valuable
> role as mentors, in non-technical roles, as support people on the mailing
> list, or as sometimes committers who don’t seem very active but come in
> every so often to make a key contribution. So I hope this doesn’t become a
> time to prune too deeply. I’d suggest we only do that if one of the
> committers has done something to lessen our project maturity or wants to be
> left out for their own reasons. An example of bad behavior is someone
> trying to exert corporate dominance (which is severely frowned on by the
> ASF). Another would be someone who is disruptive to the point of destroying
> team effectiveness. I personally haven’t seen any of this but purposely
> don’t read everything so chime in here.
>
> It would be good to have people declare their interest-level. As for me,
> I’d like to remain on the PMC as a committer but have no interest in Chair.
> Since people can become busy periodically and not read @dev (me?) we could,
> maybe should, poll the current committers and PMC to get the lists ready
> for the graduation proposal.
>
>
> Don’t forget that we are not just asking for dev community opinion about
> graduation. We are also asking that people check things like the Maturity
> Checklist to see it we are ready. http://community.apache.org/
> apache-way/apache-project-maturity-model.html <
> http://community.apache.org/apache-way/apache-project-maturity-model.html>
> People seem fairly enthusiastic about applying for graduation, but are
> there things we need to do before hand? The goal is to show that we do not
> require the second level check for decisions that the IPMC provides. The
> last release required no changes but had a proviso about content licenses.
> This next release should fly through without provisos IMHO. Are there other
> things we should do?
>
>
> On Sep 1, 2017, at 6:16 AM, takako shimamoto <chiboch...@gmail.com> wrote:
>
> I entirely agree with everyone else.
> I hope the PIO community will become more active after graduation.
>
> > 2. If we are to graduate, who should we include in the list of the
> initial
> > PMC?
>
> Don't all present IPMC members are included in the list of the initial PMC?
>
> Personally, I think we may as well check and see if present IPMC
> members intend to become an initial PMC for graduation.
> Members who make a declaration of intent to become it will surely
> contribute to the project.
> It is a great contribution not only to develop a program but also to
> respond to email aggressively or fix document.
>
>
> 2017-08-29 14:20 GMT+09:00 Donald Szeto <don...@apache.org>:
> > Hi all,
> >
> > Since the ASF Board meeting in May (
> > http://apache.org/foundation/records/minutes/2017/board_
> minutes_2017_05_17.txt),
> > PredictionIO has been considered nearing graduation and I think we are
> > almost there. I am kickstarting this thread so that we can discuss on
> these
> > 3 things:
> >
> > 1. Does the development community feel ready to graduate?
> > 2. If we are to graduate, who should we include in the list of the
> initial
> > PMC?
> > 3. If we are to graduate, who should be the VP of the initial PMC?
> >
> > These points are relevant for graduation. Please take a look at the
> > official graduation guide:
> > http://incubator.apache.org/guides/graduation

Re: [DISCUSS] Resolution to create a TLP from graduating Incubator podling

[Donald Szeto]

Thank you. I will move this forward to a formal vote.

On Fri, Sep 22, 2017 at 2:30 PM, Mars Hall <mars.h...@salesforce.com> wrote:

> Thank you for creating this resolution Donald.
>
> I move that we start the vote, pending any additional feedback from the
> group.
>
> Best regards,
>
> On Thu, Sep 21, 2017 at 12:19 PM, Andrew Purtell <apurt...@apache.org>
> wrote:
>
> > This looks great Donald, and I'm so glad you accepted the role of Chair.
> >
> > This part of the Special Order will establish the project description
> text
> > which must appear at the top of every report to the Board:
> >
> > [...] software related to *a 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*
> >
> >
> > It is in effect the Apache in-house elevator pitch to other projects and
> > PMC or anyone reading the reports. This is the opportunity to improve
> this
> > description, if desired. It could also be fine as-is.
> >
> >
> > On Thu, Sep 21, 2017 at 10:29 AM, Donald Szeto <don...@apache.org>
> wrote:
> >
> > > Hi all,
> > >
> > > Based on the previous discussion (
> > > https://lists.apache.org/thread.html/2b4ef7c394584988cf0c99920824af
> > > aa60ee4c648d5c0069b1bf55c0@%3Cdev.predictionio.apache.org%3E),
> > > I would like to start discussing a graduation resolution and reach a
> > > consent before starting a community vote on the following. Please read
> > > carefully the resolution, and voice any concerns you may have. If you
> > are a
> > > current PMC member, please make sure your name is listed unless you
> have
> > > already asked to be excluded. We will start an official community vote
> > when
> > > a consent is reached.
> > >
> > > Regarding the PredictionIO trademark assignment, Salesforce has signed
> > and
> > > executed an assignment agreement, and is only pending ASF to
> countersign.
> > >
> > > The graduation process we are following is described here:
> > > http://incubator.apache.org/guides/graduation.html
> > >
> > > Thank you all! Let's graduate.
> > >
> > > Regards,
> > > Donald
> > >
> > > -
> > >
> > > X. Establish the Apache PredictionIO Project
> > >
> > >WHEREAS, the Board of Directors deems it to be in the best
> > >interests of the Foundation and consistent with the
> > >Foundation's purpose to establish a Project Management
> > >Committee charged with the creation and maintenance of
> > >open-source software, for distribution at no charge to
> > >the public, related to a 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.
> > >
> > >NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > >Committee (PMC), to be known as the "Apache PredictionIO
> Project",
> > >be and hereby is established pursuant to Bylaws of the
> > >Foundation; and be it further
> > >
> > >RESOLVED, that the Apache PredictionIO Project be and hereby is
> > >responsible for the creation and maintenance of software
> > >related to a 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;
> > >and be it further
> > >
> > >RESOLVED, that the office of "Vice President, Apache
> PredictionIO"
> > > be
> > >and hereby is created, the person holding such office to
> > >serve at the direction of the Board of Directors as the chair
> > >of the Apache PredictionIO Project, and to have primary
> > > responsibility
> > >for management of the projects within the scope of
> > >responsibility of the Apache PredictionIO Project; and be it
> > further
> > >
> > >RESOLVED, that the persons listed immediately below be and

[VOTE] Resolution to create a TLP from graduating Incubator podling

[Donald Szeto]

Hi all,

Based on previous discussions (
https://lists.apache.org/thread.html/2b4ef7c394584988cf0c99920824afaa60ee4c648d5c0069b1bf55c0@%3Cdev.predictionio.apache.org%3E
and
https://lists.apache.org/thread.html/1b06e510773ee1d315728e0ce25f220c9cf7d9e8ad601ec9dba4fe1d@%3Cdev.predictionio.apache.org%3E),
I would like to start a formal vote on graduating PredictionIO from an
Incubator podling to a top level project with the following resolution.
This thread will be forwarded to the Incubator general mailing list.

Once again, Salesforce has already signed and executed an assignment
agreement to assign the PredictionIO mark to ASF.

The graduation process we are following is described here:
http://incubator.apache.org/guides/graduation.html

Once this vote passes, a discussion will be started on Incubator general,
followed by a vote when a consensus there would be arrived. The vote will
run for at least 72 hours before closing at 9PM PST on 9/28/2017.

Thank you all! Let's graduate.

+1 (binding) from me.

Regards,
Donald

-

X. Establish the Apache PredictionIO Project

   WHEREAS, the Board of Directors deems it to be in the best
   interests of the Foundation and consistent with the
   Foundation's purpose to establish a Project Management
   Committee charged with the creation and maintenance of
   open-source software, for distribution at no charge to
   the public, related to a 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.

   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the "Apache PredictionIO Project",
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further

   RESOLVED, that the Apache PredictionIO Project be and hereby is
   responsible for the creation and maintenance of software
   related to a 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;
   and be it further

   RESOLVED, that the office of "Vice President, Apache PredictionIO" be
   and hereby is created, the person holding such office to
   serve at the direction of the Board of Directors as the chair
   of the Apache PredictionIO Project, and to have primary
responsibility
   for management of the projects within the scope of
   responsibility of the Apache PredictionIO Project; and be it further

   RESOLVED, that the persons listed immediately below be and
   hereby are appointed to serve as the initial members of the
   Apache PredictionIO Project:

 * Alex Merritt <emergentor...@apache.org>
 * Andrew Kyle Purtell <apurt...@apache.org>
 * Chan Lee <chan...@apache.org>
 * Donald Szeto <don...@apache.org>
 * Felipe Oliveira <fel...@apache.org>
 * James Taylor <jtay...@apache.org>
 * Justin Yip <yipjus...@apache.org>
 * Kenneth Chan <kenn...@apache.org>
 * Lars Hofhansl <la...@apache.org>
 * Lee Moon Soo <m...@apache.org>
 * Luciano Resende <lrese...@apache.org>
 * Marcin Ziemiński <zie...@apache.org>
 * Marco Vivero <mviv...@apache.org>
 * Mars Hall <m...@apache.org>
 * Matthew Tovbin <tovb...@apache.org>
 * Naoki Takezoe <take...@apache.org>
 * Pat Ferrel <p...@apache.org>
 * Paul Li <pau...@apache.org>
 * Shinsuke Sugaya <shins...@apache.org>
 * Simon Chan <sim...@apache.org>
 * Takahiro Hagino <hag...@apache.org>
 * Takako Shimamoto <shimam...@apache.org>
 * Tamas Jambor <tjam...@apache.org>
 * Tom Chan <tc...@apache.org>
 * Vitaly Gordon <vit...@apache.org>
 * Xiangrui Meng <m...@apache.org>
 * Xusen Yin <y...@apache.org>
 * Yevgeny Khodorkovsky <y...@apache.org>

   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Donald Szeto
   be appointed to the office of Vice President, Apache PredictionIO, to
   serve in accordance with and subject to the direction of the
   Board of Directors and the Bylaws of the Foundation until
   death, resignation, retirement, removal or disqualification,
   or until a successor is appointed; and be it further

   RESOLVED, that the initial Apache PredictionIO PMC be and hereby is
   tasked with the creation of a set of bylaws intended to
   encourage open development and increased participation in the
   Apache PredictionIO Project; and be

[RESULT][VOTE] Resolution to create a TLP from graduating Incubator podling

[Donald Szeto]

The vote passes, with 9 +1 votes (8 binding) and no -1 votes.

+1 Andrew Purtell (binding)
+1 Chan Lee (binding)
+1 Donald Szeto (binding)
+1 Jianhe Liao (non-PPMC, non-binding)
+1 Mars Hall (binding)
+1 Naoki Takezoe (binding)
+1 Shinsuke Sugaya (binding)
+1 Suneel Marthi (binding)
+1 Takako Shimamoto (binding)

Thanks all for voting. We will proceed to post our resolution to the
general incubator list for discussion.

On Wed, Sep 27, 2017 at 9:54 PM, takako shimamoto <chiboch...@gmail.com>
wrote:

> +1 binding
>
> Thanks, Donald! I really appreciate that.
>
>
> 2017-09-26 12:50 GMT+09:00 Donald Szeto <don...@apache.org>:
> > Hi all,
> >
> > Based on previous discussions (
> > https://lists.apache.org/thread.html/2b4ef7c394584988cf0c99920824af
> aa60ee4c648d5c0069b1bf55c0@%3Cdev.predictionio.apache.org%3E
> > and
> > https://lists.apache.org/thread.html/1b06e510773ee1d315728e0ce25f22
> 0c9cf7d9e8ad601ec9dba4fe1d@%3Cdev.predictionio.apache.org%3E),
> > I would like to start a formal vote on graduating PredictionIO from an
> > Incubator podling to a top level project with the following resolution.
> > This thread will be forwarded to the Incubator general mailing list.
> >
> > Once again, Salesforce has already signed and executed an assignment
> > agreement to assign the PredictionIO mark to ASF.
> >
> > The graduation process we are following is described here:
> > http://incubator.apache.org/guides/graduation.html
> >
> > Once this vote passes, a discussion will be started on Incubator general,
> > followed by a vote when a consensus there would be arrived. The vote will
> > run for at least 72 hours before closing at 9PM PST on 9/28/2017.
> >
> > Thank you all! Let's graduate.
> >
> > +1 (binding) from me.
> >
> > Regards,
> > Donald
> >
> > -
> >
> > X. Establish the Apache PredictionIO Project
> >
> >WHEREAS, the Board of Directors deems it to be in the best
> >interests of the Foundation and consistent with the
> >Foundation's purpose to establish a Project Management
> >Committee charged with the creation and maintenance of
> >open-source software, for distribution at no charge to
> >the public, related to a 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.
> >
> >NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >Committee (PMC), to be known as the "Apache PredictionIO Project",
> >be and hereby is established pursuant to Bylaws of the
> >Foundation; and be it further
> >
> >RESOLVED, that the Apache PredictionIO Project be and hereby is
> >responsible for the creation and maintenance of software
> >related to a 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;
> >and be it further
> >
> >RESOLVED, that the office of "Vice President, Apache
> PredictionIO" be
> >and hereby is created, the person holding such office to
> >serve at the direction of the Board of Directors as the chair
> >of the Apache PredictionIO Project, and to have primary
> > responsibility
> >for management of the projects within the scope of
> >    responsibility of the Apache PredictionIO Project; and be it
> further
> >
> >RESOLVED, that the persons listed immediately below be and
> >hereby are appointed to serve as the initial members of the
> >Apache PredictionIO Project:
> >
> >  * Alex Merritt <emergentor...@apache.org>
> >  * Andrew Kyle Purtell <apurt...@apache.org>
> >  * Chan Lee <chan...@apache.org>
> >  * Donald Szeto <don...@apache.org>
> >  * Felipe Oliveira <fel...@apache.org>
> >  * James Taylor <jtay...@apache.org>
> >  * Justin Yip <yipjus...@apache.org>
> >  * Kenneth Chan <kenn...@apache.org>
> >  * Lars Hofhansl <la...@apache.org>
> >  * Lee Moon Soo <m...@apache.org>
> >  * Luciano Resende <lrese...@apache.org>
> >  * Marcin Ziemiński <zie...

Re: [ANNOUNCE] Apache PredictionIO 0.12.0-incubating Release

[Donald Szeto]

Congrats to everyone who is part of this, and Chan for his first Apache
release!

On Wed, Sep 27, 2017 at 2:40 PM Chan Lee  wrote:

> The Apache PredictionIO team would like to announce the release of Apache
> PredictionIO 0.12.0-incubating.
>
> Release notes are here:
>
> https://github.com/apache/incubator-predictionio/blob/release/0.12.0/RELEASE.md
>
> Apache PredictionIO (incubating) 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.
>
> More details regarding Apache PredictionIO (incubating) can be found here:
> http://predictionio.incubator.apache.org/
>
> The release artifacts can be downloaded here:
>
> https://dist.apache.org/repos/dist/release/incubator/predictionio/0.12.0-incubating/
>
> All JIRAs completed for this release are tagged with 'FixVersion =
> 0.12.0-incubating'; the JIRA release notes can be found here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12340591=12320420
>
> Thanks!
> The Apache PredictionIO Team
>
> DISCLAIMER
> Apache PredictionIO (incubating) is an effort undergoing incubation at the
> Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC.
> Incubation is required of all newly accepted projects until a further
> review indicates that the infrastructure, communications, and decision
> making process have stabilized in a manner consistent with other successful
> ASF projects. While incubation status is not necessarily a reflection of
> the completeness or stability of the code, it does indicate that the
> project has yet to be fully endorsed by the ASF.
>

Graduation to TLP

[Donald Szeto]

Hi all,

Since the ASF Board meeting in May (
http://apache.org/foundation/records/minutes/2017/board_minutes_2017_05_17.txt),
PredictionIO has been considered nearing graduation and I think we are
almost there. I am kickstarting this thread so that we can discuss on these
3 things:

1. Does the development community feel ready to graduate?
2. If we are to graduate, who should we include in the list of the initial
PMC?
3. If we are to graduate, who should be the VP of the initial PMC?

These points are relevant for graduation. Please take a look at the
official graduation guide:
http://incubator.apache.org/guides/graduation.html.

In addition, Sara and I have been working to transfer the PredictionIO
trademark to the ASF. We will keep you updated with our progress.

I would also like to propose to cut a 0.12.0 release by merging JIRAs that
have a target version set to 0.12.0-incubating for graduation. 0.12.0 will
contain cleanups for minor license and copyright issues that were pointed
out in previous releases by IPMC.

Let me know what you think.

Regards,
Donald

Re: 2d-animated video for Artificial Intelligence

[Donald Szeto]

Hi Max,

Apache projects are non-profit. Specifically this mailing list is for
development of the project by community effort. Do not use this to
advertise your service.

Regards,
Donald

On Thu, Oct 12, 2017 at 11:51 AM Max Harrison  wrote:

> Hey !
>
> My name is Max, I'm a team leader at “Inovit” animation studio.
>
> Our company creates professional 2d animation explainer videos to deliver a
> message about your company or product to your prospects in the best form,
> which helps you attract new customers and potential clients.
>
> We’ve checked your website and we think that our services could be useful
> for you.
>
> You can find some examples of our videos in the links below:
>
> https://www.youtube.com/watch?v=0U1w0qFUD5c
>
> https://youtu.be/OdB-AbkEyvE
>
> Our portfolio: https://vimeo.com/inovitagency
>
> Let me know if you're interested in any kind of cooperation.
>
> Looking forward to hearing from you.
>
> --
> Best Regards
> Max Harrison, Team leader
> 187 E. Warm Springs Rd. Suite B398
> Las Vegas, Nevada 89119, USA
> skype: inovit_order
> Tel: +18882748845; code: 01
> http://inovitagency.com/
>

[jira] [Updated] (PIO-6) Create doc site

[Donald Szeto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIO-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Szeto updated PIO-6:
---
Fix Version/s: 0.9.7

> Create doc site
> ---
>
> Key: PIO-6
> URL: https://issues.apache.org/jira/browse/PIO-6
> Project: PredictionIO
>  Issue Type: Task
> Environment: Apache git pubsub docs site
>Reporter: Pat Ferrel
>Assignee: Donald Szeto
> Fix For: 0.9.7
>
>
> create the pio site and start adding docs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)