It took Gearpump six release candidates before their first release from
incubation passed the IPMC's checks on correct LICENSE and NOTICE files (note:
different requirements for source and binary artifacts) and that all the
licenses of all transitive dependencies were accounted for and did not r
[
https://issues.apache.org/jira/browse/PIO-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pat Ferrel updated PIO-27:
--
Issue Type: Task (was: Bug)
> Check release artifacts for licenses and the LICENSE.txt file
> -
[
https://issues.apache.org/jira/browse/PIO-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429484#comment-15429484
]
Pat Ferrel commented on PIO-27:
---
It looks like some work has gone into these but they haven't be
Github user moeamla commented on the issue:
https://github.com/apache/incubator-predictionio/issues/278
Same here .. I have been searching online on how to download predictionIO
and most of the links are outdated. I just want to download it and work with it
locally.
Is the su
Pat Ferrel created PIO-27:
-
Summary: Check release artifacts for licenses and the LICENSE.txt
file
Key: PIO-27
URL: https://issues.apache.org/jira/browse/PIO-27
Project: PredictionIO
Issue Type: Bug
This is a laborious manual thing. Most incubator projects get dinged on
those very issues.
We have been trying to get a first Pirk release for a week now, but holding
off to fix the license and notices.
Maybe in PIO, its already been taken care of. Donald?
Regardless it would be good if someone
Sound good. Is this a hand thing or can we automate it like PIO-26 RAT. Could
you add a Jira with comments?
On Aug 20, 2016, at 11:16 AM, Suneel Marthi wrote:
While waiting on #1 below, I would ask that you do the due diligence on the
License and Notice files and ensure that all third party jar
While waiting on #1 below, I would ask that you do the due diligence on the
License and Notice files and ensure that all third party jars have been
accounted for and the License and Notice files are included in the
appropriate project release artifacts.
On Sat, Aug 20, 2016 at 2:00 PM, Pat Ferrel
What do people think remains for release?
1) template donation and mods. Chan Lee has done work on this but we can’t
review until the donation and repos are set up.
2) install.sh. There are some suggestions on how to deal with the one-line
install here: https://issues.apache.org/jira/browse/PIO-
[
https://issues.apache.org/jira/browse/PIO-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pat Ferrel updated PIO-18:
--
Priority: Minor (was: Major)
> Documentation for setting up the project for developers
> --
[
https://issues.apache.org/jira/browse/PIO-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429466#comment-15429466
]
Pat Ferrel commented on PIO-18:
---
I think this works, but you need to create the correct class fo
[
https://issues.apache.org/jira/browse/PIO-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pat Ferrel resolved PIO-13.
---
Resolution: Fixed
seems fixed on the develop branch
> Update Gemnasium dependency status
> --
[
https://issues.apache.org/jira/browse/PIO-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429462#comment-15429462
]
Pat Ferrel commented on PIO-13:
---
This seems to have been fixed.
[~xusen] I'll close but can you
[
https://issues.apache.org/jira/browse/PIO-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429460#comment-15429460
]
Pat Ferrel commented on PIO-11:
---
Can you describe this. Did you mean python3? I use it with pyth
[
https://issues.apache.org/jira/browse/PIO-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pat Ferrel updated PIO-9:
-
Priority: Minor (was: Major)
> Clean up examples under examples/
> -
>
>
It's no problem at all. I would like you all to be successful.
> On Aug 20, 2016, at 10:16 AM, Pat Ferrel wrote:
>
> Thanks Andy. Very good to hear. I think Donald is taking lead in SF last I
> heard. As I said not trying to dump work on you :-)
>
>
> On Aug 20, 2016, at 10:11 AM, Andrew Pur
Github user alex9311 commented on the issue:
https://github.com/apache/incubator-predictionio/issues/141
If any of the predictionIO people think it would be helpful, I'd be happy
to add a CORS guide to the documentation
---
If your project is set up for it, you can reply to this emai
Thanks Andy. Very good to hear. I think Donald is taking lead in SF last I
heard. As I said not trying to dump work on you :-)
On Aug 20, 2016, at 10:11 AM, Andrew Purtell wrote:
With respect to my estimation of getting that SGA in about a week, I am
optimistic we can turn that around. I will
With respect to my estimation of getting that SGA in about a week, I am
optimistic we can turn that around. I will do what I can to drive it.
There will be no problem with third party (or templates of any provenance)
calling PIO code in an org.apache namespace going forward, of course.
I also
Ok, I don't see a problem with that.
> On Aug 20, 2016, at 9:32 AM, Pat Ferrel wrote:
>
> Ah, ok I see the misunderstanding. I'm not talking about claiming org.apache
> on template code I’m talking about *calling* the new org.apache code in PIO
> from the templates. The copyright notice and
"a week or so” is the first I’ve heard of an order of magnitude and would agree
if that’s true. I’ll remove the suggestion but I think there is a bigger issue
here.
Understood about what would be granted and it would not be these modified
templates but that’s that way the PIO ecosystem is meant
Another (minor) consideration is the donation will be by way of SGA that
specifies exact git shas. Those will be what are imported into the Apache
repos. Presumably the shas specified are not from this fork-in-progress. I see
no problem doing package munging and various other things at this time
Ah, ok I see the misunderstanding. I'm not talking about claiming org.apache on
template code I’m talking about *calling* the new org.apache code in PIO from
the templates. The copyright notice and license of the templates will not be
modified, only the pio lib namespace *used* by the templates.
I concur with Andy.
On Sat, Aug 20, 2016 at 12:18 PM, Andrew Purtell
wrote:
> I don't think you should author code in the org.apache namespace that has
> not gone through proper IP clearance channels. This came up with Gearpump
> before it went into incubation. They dropped code on GitHub in the
I don't think you should author code in the org.apache namespace that has not
gone through proper IP clearance channels. This came up with Gearpump before it
went into incubation. They dropped code on GitHub in the org.apache package
namespace. I asked if that was proper. The advice received was
The old Google Group for PIO was fairly active but it seems all of those users
have vanished. I suggest that this is bad for the project as well as the user
base. One possible solution is to retract the no-posting rule and forward all
posts to the user@ list address. Then questions will get answ
[
https://issues.apache.org/jira/browse/PIO-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429432#comment-15429432
]
Pat Ferrel commented on PIO-24:
---
[~chanlee514] are you willing to put your modified templates in
27 matches
Mail list logo
