This is mostly a good idea but then one of the templates is 3 times the size of incubator-predictionio:
$ du -d 1 -h 53M ./incubator-predictionio 1.3M ./incubator-predictionio-sdk-java 288K ./incubator-predictionio-sdk-php 536K ./incubator-predictionio-sdk-python 264K ./incubator-predictionio-sdk-ruby 236K ./incubator-predictionio-template-attribute-based-classifier 220K ./incubator-predictionio-template-ecom-recommender 264K ./incubator-predictionio-template-java-ecom-recommender 184K ./incubator-predictionio-template-recommender 196K ./incubator-predictionio-template-similar-product 440K ./incubator-predictionio-template-skeleton 160M ./incubator-predictionio-template-text-classifier This 160M will be downloaded by all users regardless of whether they use it or not, if we choose to consolidate them all into one repo. Tom On Thu, Nov 3, 2016 at 2:16 PM, Simon Chan <si...@salesforce.com> wrote: > Hi guys, > > I'm actually thinking we should consolidate all core templates / SDKs repos > that are donated to Apache (i.e. > https://github.com/search?q=org%3Aapache+PredictionIO) into one main repo > ( > https://github.com/apache/incubator-predictionio) > > The benefit may be that: > 1. We can track Apache PredictionIO project activity in a unified place; > 2. Making these templates part of the main repo encourages contributors to > make sure they are all compatible with the latest version of PredictionIO > core; > 3. I don't see other projects (e.g. Mahout and its libraries) hosting core > and components separately. > > Thought? > > Simon >
