Re: Graduation to TLP

2017-08-30 Thread Pat Ferrel 
IMO the VP/Chair responsibilities are mostly administrative and tedious. In the 
best case there is leadership but that will naturally come from thought leaders 
with no regard to title.


On Aug 30, 2017, at 4:41 PM, Chan Lee  wrote:

Agree with everyone else. +1 for graduation.

I was away for a while due to family issues, but I'd be happy to volunteer
for release management.


On Wed, Aug 30, 2017 at 4:30 PM, Pat Ferrel  wrote:

> Along with the link Donald gave, check this out:
> http://community.apache.org/apache-way/apache-project-maturity-model.html
> > 
> 
> We will need at least 2 release managers before graduation, any volunteers?
> 
> 
> On Aug 30, 2017, at 3:51 PM, Mars Hall  wrote:
> 
> Thank you Donald for leading the charge here,
> 
> From my perspective PredictionIO is already Apache in process & title.
> Graduation seems quite natural to reach top-level recognition.
> 
> I'm interested in helping with PMC duties. Would be great to understand
> what the VP vs Member responsibilities look like.
> 
> Let's graduate. +1
> 
> *Mars
> 
> 
> On Wed, Aug 30, 2017 at 15:21 Pat Ferrel  wrote:
> 
>> I have had several people tell me they want to wait until PIO is not
>> incubating before using it. This even after explaining that “incubating”
>> has more to do with getting into the Apache Way of doing things and has
> no
>> direct link to quality or community. I can only conclude from this that
>> “incubating” is holding back adoption.
>> 
>> And yet we have absorbed the Apache Way and will have at least 3 releases
>> (including 12) a incubating. We have brought in a fair number of new
>> committers and seem to have a healthy community of users.
>> 
>> +1 for a push to graduate.
>> 
>> 
>> On Aug 28, 2017, at 10:20 PM, Donald Szeto  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?
>> 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
>> 
>> --
> *Mars Hall
> 415-818-7039
> Customer Facing Architect
> Salesforce Platform / Heroku
> San Francisco, California
> 
>

Re: Graduation to TLP

2017-08-30 Thread Chan Lee 
Agree with everyone else. +1 for graduation.

I was away for a while due to family issues, but I'd be happy to volunteer
for release management.


On Wed, Aug 30, 2017 at 4:30 PM, Pat Ferrel  wrote:

> Along with the link Donald gave, check this out:
> http://community.apache.org/apache-way/apache-project-maturity-model.html
>  >
>
> We will need at least 2 release managers before graduation, any volunteers?
>
>
> On Aug 30, 2017, at 3:51 PM, Mars Hall  wrote:
>
> Thank you Donald for leading the charge here,
>
> From my perspective PredictionIO is already Apache in process & title.
> Graduation seems quite natural to reach top-level recognition.
>
> I'm interested in helping with PMC duties. Would be great to understand
> what the VP vs Member responsibilities look like.
>
> Let's graduate. +1
>
> *Mars
>
>
> On Wed, Aug 30, 2017 at 15:21 Pat Ferrel  wrote:
>
> > I have had several people tell me they want to wait until PIO is not
> > incubating before using it. This even after explaining that “incubating”
> > has more to do with getting into the Apache Way of doing things and has
> no
> > direct link to quality or community. I can only conclude from this that
> > “incubating” is holding back adoption.
> >
> > And yet we have absorbed the Apache Way and will have at least 3 releases
> > (including 12) a incubating. We have brought in a fair number of new
> > committers and seem to have a healthy community of users.
> >
> > +1 for a push to graduate.
> >
> >
> > On Aug 28, 2017, at 10:20 PM, Donald Szeto  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?
> > 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
> >
> > --
> *Mars Hall
> 415-818-7039
> Customer Facing Architect
> Salesforce Platform / Heroku
> San Francisco, California
>
>

Re: Graduation to TLP

2017-08-30 Thread Pat Ferrel 
Along with the link Donald gave, check this out: 
http://community.apache.org/apache-way/apache-project-maturity-model.html 


We will need at least 2 release managers before graduation, any volunteers?


On Aug 30, 2017, at 3:51 PM, Mars Hall  wrote:

Thank you Donald for leading the charge here,

From my perspective PredictionIO is already Apache in process & title.
Graduation seems quite natural to reach top-level recognition.

I'm interested in helping with PMC duties. Would be great to understand
what the VP vs Member responsibilities look like.

Let's graduate. +1

*Mars


On Wed, Aug 30, 2017 at 15:21 Pat Ferrel  wrote:

> I have had several people tell me they want to wait until PIO is not
> incubating before using it. This even after explaining that “incubating”
> has more to do with getting into the Apache Way of doing things and has no
> direct link to quality or community. I can only conclude from this that
> “incubating” is holding back adoption.
> 
> And yet we have absorbed the Apache Way and will have at least 3 releases
> (including 12) a incubating. We have brought in a fair number of new
> committers and seem to have a healthy community of users.
> 
> +1 for a push to graduate.
> 
> 
> On Aug 28, 2017, at 10:20 PM, Donald Szeto  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?
> 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
> 
> --
*Mars Hall
415-818-7039
Customer Facing Architect
Salesforce Platform / Heroku
San Francisco, California

[jira] [Comment Edited] (PIO-99) `pio build` exits successfully even when compilation fails

2017-08-30 Thread Donald Szeto (JIRA) 

[ 
https://issues.apache.org/jira/browse/PIO-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16148202#comment-16148202
 ] 

Donald Szeto edited comment on PIO-99 at 8/30/17 11:20 PM:
---

To reproduce:

# Build an engine that will return a successful run.
# Purposely introduce a syntax error in engine code.
# Build again.

This is a bug because log lines above mentioned it ran into an error and was 
going to abort, but it did not and proceeded to check for build JARs, which 
succeeded because there was a good previous build.


was (Author: dszeto):
To reproduce:

1. Build an engine that will return a successful run.
2. Purposely introduce a syntax error in engine code.
3. Build again.

This is a bug because log lines above mentioned it ran into an error and was 
going to abort, but it did not and proceeded to check for build JARs, which 
succeeded because there was a good previous build.

> `pio build` exits successfully even when compilation fails
> --
>
> Key: PIO-99
> URL: https://issues.apache.org/jira/browse/PIO-99
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Build
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
>  Labels: newbie
>
> The build command does not fail as expected. While not a big deal when 
> working locally, it seems like this could be problematic for automated, 
> continuous build/integration workflows.
> {code}
> $ pio build
> …
> [ERROR] [Engine$] [error] one error found
> [ERROR] [Engine$] [error] (compile:compileIncremental) Compilation failed
> [ERROR] [Engine$] [error] Total time: 5 s, completed Jun 21, 2017 9:59:55 AM
> [ERROR] [Engine$] Return code of build command: 
> /Users/mars.hall/Projects/predictionio-engine-ur/PredictionIO-dist/sbt/sbt  
> package assemblyPackageDependency is 1. Aborting.
> [INFO] [Engine$] Looking for an engine...
> [INFO] [Engine$] Found universal-recommender-assembly-0.5.0-deps.jar
> [INFO] [Engine$] Found universal-recommender_2.11-0.5.0.jar
> [INFO] [Engine$] Build finished successfully.
> [INFO] [Pio$] Your engine is ready for training.
> {code}
> It certainly appears successful at the end, and exit code was {{0}}.
> Looking back for the error is not hard, but this behavior is problematic when 
> composing {{pio build}} command into a shell script.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (PIO-99) `pio build` exits successfully even when compilation fails

2017-08-30 Thread Donald Szeto (JIRA) 

[ 
https://issues.apache.org/jira/browse/PIO-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16148202#comment-16148202
 ] 

Donald Szeto commented on PIO-99:
-

To reproduce:

1. Build an engine that will return a successful run.
2. Purposely introduce a syntax error in engine code.
3. Build again.

This is a bug because log lines above mentioned it ran into an error and was 
going to abort, but it did not and proceeded to check for build JARs, which 
succeeded because there was a good previous build.

> `pio build` exits successfully even when compilation fails
> --
>
> Key: PIO-99
> URL: https://issues.apache.org/jira/browse/PIO-99
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Build
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
>  Labels: newbie
>
> The build command does not fail as expected. While not a big deal when 
> working locally, it seems like this could be problematic for automated, 
> continuous build/integration workflows.
> {code}
> $ pio build
> …
> [ERROR] [Engine$] [error] one error found
> [ERROR] [Engine$] [error] (compile:compileIncremental) Compilation failed
> [ERROR] [Engine$] [error] Total time: 5 s, completed Jun 21, 2017 9:59:55 AM
> [ERROR] [Engine$] Return code of build command: 
> /Users/mars.hall/Projects/predictionio-engine-ur/PredictionIO-dist/sbt/sbt  
> package assemblyPackageDependency is 1. Aborting.
> [INFO] [Engine$] Looking for an engine...
> [INFO] [Engine$] Found universal-recommender-assembly-0.5.0-deps.jar
> [INFO] [Engine$] Found universal-recommender_2.11-0.5.0.jar
> [INFO] [Engine$] Build finished successfully.
> [INFO] [Pio$] Your engine is ready for training.
> {code}
> It certainly appears successful at the end, and exit code was {{0}}.
> Looking back for the error is not hard, but this behavior is problematic when 
> composing {{pio build}} command into a shell script.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Graduation to TLP

2017-08-30 Thread Mars Hall 
Thank you Donald for leading the charge here,

>From my perspective PredictionIO is already Apache in process & title.
Graduation seems quite natural to reach top-level recognition.

I'm interested in helping with PMC duties. Would be great to understand
what the VP vs Member responsibilities look like.

Let's graduate. +1

*Mars


On Wed, Aug 30, 2017 at 15:21 Pat Ferrel  wrote:

> I have had several people tell me they want to wait until PIO is not
> incubating before using it. This even after explaining that “incubating”
> has more to do with getting into the Apache Way of doing things and has no
> direct link to quality or community. I can only conclude from this that
> “incubating” is holding back adoption.
>
> And yet we have absorbed the Apache Way and will have at least 3 releases
> (including 12) a incubating. We have brought in a fair number of new
> committers and seem to have a healthy community of users.
>
> +1 for a push to graduate.
>
>
> On Aug 28, 2017, at 10:20 PM, Donald Szeto  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?
> 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
>
> --
*Mars Hall
415-818-7039
Customer Facing Architect
Salesforce Platform / Heroku
San Francisco, California

Re: Graduation to TLP

2017-08-30 Thread Pat Ferrel 
I have had several people tell me they want to wait until PIO is not incubating 
before using it. This even after explaining that “incubating” has more to do 
with getting into the Apache Way of doing things and has no direct link to 
quality or community. I can only conclude from this that “incubating” is 
holding back adoption.

And yet we have absorbed the Apache Way and will have at least 3 releases 
(including 12) a incubating. We have brought in a fair number of new committers 
and seem to have a healthy community of users.

+1 for a push to graduate.  


On Aug 28, 2017, at 10:20 PM, Donald Szeto  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?
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

[jira] [Commented] (PIO-99) `pio build` exits successfully even when compilation fails

2017-08-30 Thread Sai Teja Lakkimsetty (JIRA) 

[ 
https://issues.apache.org/jira/browse/PIO-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16148042#comment-16148042
 ] 

Sai Teja Lakkimsetty commented on PIO-99:
-

How can I reproduce this problem?

> `pio build` exits successfully even when compilation fails
> --
>
> Key: PIO-99
> URL: https://issues.apache.org/jira/browse/PIO-99
> Project: PredictionIO
>  Issue Type: Bug
>  Components: Build
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
>  Labels: newbie
>
> The build command does not fail as expected. While not a big deal when 
> working locally, it seems like this could be problematic for automated, 
> continuous build/integration workflows.
> {code}
> $ pio build
> …
> [ERROR] [Engine$] [error] one error found
> [ERROR] [Engine$] [error] (compile:compileIncremental) Compilation failed
> [ERROR] [Engine$] [error] Total time: 5 s, completed Jun 21, 2017 9:59:55 AM
> [ERROR] [Engine$] Return code of build command: 
> /Users/mars.hall/Projects/predictionio-engine-ur/PredictionIO-dist/sbt/sbt  
> package assemblyPackageDependency is 1. Aborting.
> [INFO] [Engine$] Looking for an engine...
> [INFO] [Engine$] Found universal-recommender-assembly-0.5.0-deps.jar
> [INFO] [Engine$] Found universal-recommender_2.11-0.5.0.jar
> [INFO] [Engine$] Build finished successfully.
> [INFO] [Pio$] Your engine is ready for training.
> {code}
> It certainly appears successful at the end, and exit code was {{0}}.
> Looking back for the error is not hard, but this behavior is problematic when 
> composing {{pio build}} command into a shell script.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-predictionio pull request #421: Elasticsearch 5.x singleton client...

2017-08-30 Thread asfgit 
Github user asfgit closed the pull request at:

https://github.com/apache/incubator-predictionio/pull/421


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-predictionio pull request #424: [PIO-115] Implement Storage app & ...

2017-08-30 Thread asfgit 
Github user asfgit closed the pull request at:

https://github.com/apache/incubator-predictionio/pull/424


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---