[jira] [Assigned] (PIO-1) Make SSL and authKey param authentication optional

2016-07-05 Thread Donald Szeto (JIRA)

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

Donald Szeto reassigned PIO-1:
--

Assignee: Donald Szeto

> 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
>Assignee: 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)


[jira] [Updated] (PIO-1) Make SSL and authKey param authentication optional

2016-07-05 Thread Donald Szeto (JIRA)

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

Donald Szeto updated PIO-1:
---
External issue URL: 
https://github.com/apache/incubator-predictionio/pull/244

> 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
>Assignee: 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

2016-07-05 Thread 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

2016-07-05 Thread Simon Chan
Looks great. Thanks Donald and Andrew!

Simon


On Tue, Jul 5, 2016 at 10:26 AM, Andrew Purtell  wrote:

> Looks great, +1
>
>
> On Tue, Jul 5, 2016 at 10:23 AM, Donald Szeto  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  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 
> > > 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 

[jira] [Assigned] (PIO-1) Make SSL and authKey param authentication optional

2016-07-05 Thread Donald Szeto (JIRA)

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

Donald Szeto reassigned PIO-1:
--

Assignee: Donald Szeto

> 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
>Assignee: 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)


[jira] [Updated] (PIO-1) Make SSL and authKey param authentication optional

2016-07-05 Thread Donald Szeto (JIRA)

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

Donald Szeto updated PIO-1:
---
Assignee: (was: Donald Szeto)

> 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: Time for the first podling report

2016-07-05 Thread Andrew Purtell
Looks great, +1


On Tue, Jul 5, 2016 at 10:23 AM, Donald Szeto  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  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 
> > 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)
> >>
> >
> >
>



-- 
Best regards,

   - Andy

Problems worthy of attack prove 

Re: Time for the first podling report

2016-07-05 Thread 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  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 
> 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: [jira] [Commented] (PIO-1) Make SSL and authKey param authentication optional

2016-07-05 Thread 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  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)  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)
>
>