Hi all,
Since there was no reaction to creating new repository to aggregate
the official templates I'm considering about incorporating the
official templates with main repository as suggested by Donald. My
work in progress pull request is here:
https://github.com/apache/predictionio/pull/500
My i
On Fri, Oct 12, 2018 at 9:06 AM Donald Szeto wrote:
>
> That’s a pretty radical idea. It may send a wrong message of abandoning
> templates though.
Yes. In fact, I don't want to do it.
> How about incorporating them into the main codebase as part of examples? We
> can write tests around them to
That’s a pretty radical idea. It may send a wrong message of abandoning
templates though.
I am not a big fan of the template command. We got rid of it because it
caused more problems than being user-friendly.
How about incorporating them into the main codebase as part of examples? We
can write te
An another idea is making templates unofficial. It means moving
template repositories to the outside of ASF and we don't guarantee
maintenance for them.
2018年10月9日(火) 19:10 takako shimamoto :
>
> We might as well fold them into one single repo. When running git
> clone, every template/example woul
We might as well fold them into one single repo. When running git
clone, every template/example would be pulled down by default. At this
rate, it's too expensive to use our poor resource to maintain.
On Mon, Oct 1, 2018 at 7:32 AM Naoki Takezoe wrote:
>
> I think that resurrection of "pio templat
I think that resurrection of "pio template" might be one idea.
It would allow us flexible repository layout and also it can rewrite
PredictionIO and Spark versions in build.sbt in templates at setup
time. Though this isn't a standard way (e.g. "git clone" or "sbt
new"), I think it both users and d
Yes. Folding templates into a single repository is ideal except that
users won't able to be use "git clone" to clone a individual template.
"svn" command supports it but using "svn" is not good idea. If we can
revive "pio template", we can implement partial download of git
repository in it. Anyway,
How about folding them into one single repo with each template/examples as
subprojects? Since we have retired the use of `pio template` command for a
while, there is not really a hard requirement that each template has to be
a git repo by itself.
On Fri, Sep 21, 2018 at 10:59 PM takako shimamoto
I don’t think giter8 is the best solution. There's room for
improvement. To improve workability in maintaining 7 official
templates and 12 examples, it's a good idea to put them together into
a repository. Isn't that just one of the options as a solution to
PIO-128?
On Sat, Sep 22, 2018 at 9:10 AM
Hi Donald,
Thanks for your reply!
> I think Giter8 is a nice idea, but my concern with it is its tight coupling
> with sbt.
Yes, giter8 templates changes user experience largely. This is my
concern about it.
> How about creating scripts that would make managing these templates easier,
> despi
Thanks for bringing this up, Naoki!
I think Giter8 is a nice idea, but my concern with it is its tight coupling
with sbt. It requires users to have access to sbt in their terminal instead
of a simple git clone. How about creating scripts that would make managing
these templates easier, despite the
Hi all,
I'd like to discuss about maintenance of the official templates.
I updated all official templates for PredictionIO 0.13.0. There are 7
templates for now and I think it's too expensive to use our poor
resource to maintain. So I'd like to propose something to reduce
maintenance cost of thes
12 matches
Mail list logo
