Thanks for the clarification. I could have phrased that better too. Not meant to sound abrasive.
On Tue, Aug 16, 2016 at 3:53 PM, Pat Ferrel <p...@occamsmachete.com> wrote: > I don’t expect you to know where Simon is, I was just seeing if anyone on > the list knew, some are relatives and friends of his and even work at the > same location. I’m pretty sure Simon has the answers to take us to the SGA > or get one created. > > Not trying to dump work on you Andy, just trying to track down the answers > and not all questions are addressed to you :-) > > > On Aug 16, 2016, at 3:39 PM, Andrew Purtell <apurt...@apache.org> wrote: > > As I explained on the INFRA JIRA Pat I'm quite clear what was granted and > if it's not already in an Apache repo it was not granted by that SGA. > > Sure, Simon would be a reasonable place to start for a new SGA discussion. > I have no idea what he's up to, I'm not his keeper. > > On Tue, Aug 16, 2016 at 3:36 PM, Pat Ferrel <p...@occamsmachete.com> wrote: > > > AFAIK Salesforce owns the code and Simon must have filled out the > original > > PIO grant, which may cover all the templates already. He also started > this > > discussion so I think we start with Simon unless someone knows better. Is > > he on vacation? > > > > > > On Aug 16, 2016, at 3:30 PM, Andrew Purtell <apurt...@apache.org> wrote: > > > > I see that Pat filed INFRA-12441 ( > > https://issues.apache.org/jira/browse/INFRA-12441) which I read asks to > > import code from GitHub repositories under the old PIO organization not > yet > > granted to the ASF. > > > > This presents you with a great opportunity to learn how software grants > > work. (smile) Even when you are out of incubation this process will still > > be necessary for imports of third party code not covered by an existing > > SGA, CCLA, or ICLA. The procedure is pretty simple, assuming a single > > rights holder (which is the case I believe for the scope of this > request). > > I encourage the PPMC to work out who will contact the rights holder to > > execute a SGA (https://www.apache.org/licenses/software-grant.txt) that > > covers all of the code you would like to import. When the granted code is > > coming from a GitHub repository, Exhibit A should list all repository > URLs > > and exact SHAs desired for import covered by the grant. > > > > I'm happy to assist but the PPMC should take the lead. Good luck! > > > > > > On Tue, Aug 16, 2016 at 2:27 PM, Andrew Purtell <apurt...@apache.org> > > wrote: > > > >> Go to https://issues.apache.org/jira/ and log in. Find the read > 'Create' > >> button. There's a drop down menu immediately to the right of it. Open > > that > >> menu, then click on 'New Git Repository'. > >> > >> The original request was here: https://issues.apache. > >> org/jira/browse/INFRA-12112 > >> The second request for site was here: https://issues.apache. > >> org/jira/browse/INFRA-12180 > >> > >> > >> On Tue, Aug 16, 2016 at 12:26 PM, Pat Ferrel <p...@occamsmachete.com> > >> wrote: > >> > >>> +1 > >>> > >>> > >>>> On Aug 16, 2016, at 11:35 AM, Donald Szeto <don...@apache.org> wrote: > >>>> > >>>> 1) I’ll volunteer to take a couple templates and put them in their own > >>> repos if we can get some created. > >>>> Sure. I believe Chan might have some converted repos as well. > >>>> > >>>> 2) do we have a gallery page yet? we had a good proposal, is it > >>> implemented? > >>>> It's already been merged in develop. Once we release the old template > >>> gallery will become a redirection to the new static page. > >>> > >>> This is needed only for historical reasons, right? The big blue > Template > >>> button will go there directly after release, I assume. > >>> > >>>> > >>>> 3) What templates are worth inclusion? Seems like some of the ALS > >>> recommender ones are supersets of others do we need them all? > >>>> We should start with a core set of templates and one or a couple that > >>> focuses on a use case (since they are popular): vanilla, recommendation > >>> (both Scala and Java), similar product, classification, e-commerce, and > >>> text classification. > >>> > >>> sounds good, that is 7. @chan have you scrubbed any of these? > >>> > >>>> > >>>> 4) do we need “release” of these except through Apache git and Github? > >>> Since they are all built by users I suspect the normal Apache release > >>> process can be avoided for them, the full push to maven, binary > hosting, > >>> etc. > >>>> I vote for maintaining the above set of templates to be at least > >>> working and passing integration tests for the main release. They do not > >>> necessarily go into the final binary distribution, but they should all > > be > >>> tagged and tested against with every release of PredictionIO. > >>> > >>> +1 > >>> > >>>> > >>>> 5) We need someone to file Infra Jira’s to get repos. If someone can > >>> coach me on this I will do it. > >>>> My guess is we can just file an infrastructure ticket to spawn some > >>> discussion. > >>>> > >>> > >>> Who did the original request for repo? Can someone point me to the > Jira, > >>> I’ll take it from there > >>> > >>>> > >>>> This might only add a week or so to the release date. If we don’t do > it > >>> I bet it will be much more time spent in support and fixing later. > >>>> Agree. If we all agree let's make this the final major thing to do > >>> before 0.10.0 release to avoid feature creep. > >>>> > >>> > >>> +1, with the possible exception of fixing install.sh > >>> https://issues.apache.org/jira/browse/PIO-22 One option is to remove > it > >>> from the release, which I favor, discussion on the jira. > >>> > >>> > >>> > >> > >> > >> -- > >> Best regards, > >> > >> - Andy > >> > >> Problems worthy of attack prove their worth by hitting back. - Piet Hein > >> (via Tom White) > >> > > > > > > > > -- > > Best regards, > > > > - Andy > > > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > > (via Tom White) > > > > > > > -- > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White) > > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
