No misunderstanding—so far at least :-) What we want to do it host the templates on Github as non-Apache projects until the donation paper-work is done. This will remove a blocking issue—templates that work with the new org namespace and have some (even if incomplete) integration tests. We are thinking about the 7 mentioned in this Jira: https://issues.apache.org/jira/browse/PIO-24
If you want to push them to Github we can work from that. This is completely non-Apache but with Apache licenses we should be on sound legal ground. PIO was designed with template forking as part of the usage model. If you have any problem with this, that’s fine. I’ll start making the same changes you’ve done. I have no problem assuming responsibility since I already maintain a couple external templates. I just want to get a release of PIO done. On Aug 18, 2016, at 3:31 PM, Chan Lee <[email protected]> wrote: Hi Pat, I think there may have been a misunderstanding. The work I've done is only local: 1) I've cloned the 10 official PredictionIO templates and changed the org namespace locally. 2) I've added some tests in the main repo to make sure the templates are compatible with the latest release. As of now, I don't have write access to PredictionIO org repos, and the gallery certainly shouldn't list my fork as the "official" template. So if the release must happen before template donation, I would make a PR to each of the template repos to change org namespace and update minimum PIO version as 0.10. I will leave out the tests for now. But personally, I think it would be better if we wait for the legal grant issue to be resolved, so that it is clearer how template code should be managed. On Thu, Aug 18, 2016 at 1:13 PM, Pat Ferrel <[email protected] <mailto:[email protected]>> wrote: I think we are not waiting for the official template donation to release PIO, can you point me to the templates you have working? I’ll make sure they get added to the new gallery. We can push them to Apache once the grant is done. Thanks for the help.
