Podling Report Reminder - November 2016
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 November 2016, 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, November 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. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/November2016 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
[GitHub] incubator-predictionio-template-text-classifier pull request #7: Update temp...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-predictionio-template-text-classifier/pull/7 --- 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. ---
Re: Thanks for reviewing Dockerfile for PredictionIO-0.10.0
Hi Donald Thanks for nice comments. And it is good idea to converge contributions to one place. You can go ahead to create the repo, and I and others can later continue improvements on the new repo. Thanks Steven Thanks, Steven On Mon, Oct 31, 2016 at 10:14 AM, Donald Szeto wrote: > 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: Thanks for reviewing Dockerfile for PredictionIO-0.10.0
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: template-user-similarity
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 >
Consider highlighting your podling at ApacheCON in Seville
Hi! with ApacheCON in Seville right around the corner chances are you've made your travel arrangements already. If you happen to be around the conference on Fri, November 18th, 16:30 - 17:20 why not use that time to highlight your favorite podling? https://s.apache.org/aceu2016_shark_tank Podling Shark Tank is back and it is a perfect opportunity to give a short, 5 min pitch in a fun environment. You don't have to be a committer on the project, or even a developer! All you have to have is a bit of free time and a lot of passion to let the world know how awesome this project is! If you feel interested -- please either sign up on the wiki page (it also provides more details on the event) https://wiki.apache.org/apachecon/Seville16PodlingSharkTank or just reply to this thread. Either way -- hope to see you at Podling Shark Tank in Seville! Thanks, Roman.
[GitHub] incubator-predictionio pull request #322: [PIO-42] : Negative Test Cases for...
GitHub user rajdeepd opened a pull request: https://github.com/apache/incubator-predictionio/pull/322 [PIO-42] : Negative Test Cases for Engine.train - Empty Algo Sequence - Null Spark Context - Null Data Source - Null defaultWorkflowParams You can merge this pull request into a Git repository by running: $ git pull https://github.com/rajdeepd/incubator-predictionio develop Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-predictionio/pull/322.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #322 commit ee97cfb2f32fc6f1297a72d563076e808b804336 Author: Rajdeep Dua Date: 2016-10-31T10:27:12Z PIO-42 : Negative Test Cases for Engine.train --- 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-template-recommender pull request #12: Python 3 suppo...
GitHub user marevol opened a pull request: https://github.com/apache/incubator-predictionio-template-recommender/pull/12 Python 3 support for data/*.py Adding () to print statement, it works on Python 3.5.2. You can merge this pull request into a Git repository by running: $ git pull https://github.com/marevol/incubator-predictionio-template-recommender python3_support Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-predictionio-template-recommender/pull/12.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #12 commit 6dde75b0f0ad6703c3260324d2c10823520dc864 Author: Shinsuke Sugaya Date: 2016-10-31T06:52:23Z modify print statement --- 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. ---
[jira] [Commented] (PIO-42) Negative Test Cases for Engine.train
[ https://issues.apache.org/jira/browse/PIO-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15621838#comment-15621838 ] ASF GitHub Bot commented on PIO-42: --- GitHub user rajdeepd opened a pull request: https://github.com/apache/incubator-predictionio/pull/322 [PIO-42] : Negative Test Cases for Engine.train - Empty Algo Sequence - Null Spark Context - Null Data Source - Null defaultWorkflowParams You can merge this pull request into a Git repository by running: $ git pull https://github.com/rajdeepd/incubator-predictionio develop Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-predictionio/pull/322.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #322 commit ee97cfb2f32fc6f1297a72d563076e808b804336 Author: Rajdeep Dua Date: 2016-10-31T10:27:12Z PIO-42 : Negative Test Cases for Engine.train > Negative Test Cases for Engine.train > > > Key: PIO-42 > URL: https://issues.apache.org/jira/browse/PIO-42 > Project: PredictionIO > Issue Type: Test >Affects Versions: 0.10.0-incubating, future release > Environment: All Envinronments >Reporter: Rajdeep Dua >Priority: Minor > Fix For: future release > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (PIO-42) Negative Test Cases for Engine.train
Rajdeep Dua created PIO-42: -- Summary: Negative Test Cases for Engine.train Key: PIO-42 URL: https://issues.apache.org/jira/browse/PIO-42 Project: PredictionIO Issue Type: Test Affects Versions: 0.10.0-incubating, future release Environment: All Envinronments Reporter: Rajdeep Dua Priority: Minor Fix For: future release -- This message was sent by Atlassian JIRA (v6.3.4#6332)
