There is a repo incubator-predictionio-site created for hosting artifacts for gitpubsub. I asked the PPMC if you wanted a separate repo and you said yes. This was discussed on private@ during the podling setup period.
I have also mentioned multiple times in emails to the PPMC that this repo is ready and waiting for someone to commit static site docs to an 'asf-site' branch, at which point we can ask infra to turn on gitpubsub. They are waiting for you. > On Jul 18, 2016, at 8:41 AM, Pat Ferrel <[email protected]> wrote: > > After a little looking around I can see that we have not decided where to > store the git docs repo or alt least I see no mirror on github. > > I propose we make docs part of the main repo so we don’t have to create > another one. The docs/ sub-firectory contains the old site contents and some > things that seem to have been deprecated as well as java and scala docs. I > propose we move this to something like docs-history to get it out of the way > and create a new docs/ for the pio apache docs. > > If that seems ok I can do this. This guide > http://incubator.apache.org/guides/sites.html says we should have a site at > http://predictionio.incubator.apache.org/ Has a Jira been filed for infra to > create this? If not I can do this. > > > On Jul 17, 2016, at 6:22 PM, Pat Ferrel <[email protected]> wrote: > > Not sure how to subscribe to the Google group from > [email protected], I had to sign in to Google to > subscribe iirc, maybe the owner can do it? I guess we can just include the GG > address as above. > > If we had one page describing status and how to sign up to the mailing lists > it would be super helpful for users. I thought it was suggesting we not edit > the wiki but maybe I heard wrong. Can someone point me to instructions or a > closed Jira? I’ve used the CMS but not gitpubsub. Agree with the do-ocracy so > I’ll do something if pointed in the right direction. > > (BTW read carefully, not pointing at infra. only saying it’s part of the > process) > > On Jul 17, 2016, at 2:30 PM, Andrew Purtell <[email protected]> wrote: > > Because we are incubating, much at issue with respect to Apache policy found > with a release will not block it, as long as we promise to fix it for the > next one, but it may take a couple of release candidates to get a minimum > viable release out. I'd advise in general making the attempt at an Apache > branded release right away. > > >> On Jul 17, 2016, at 12:40 PM, Donald Szeto <[email protected]> wrote: >> >> I will take a shot at putting up a site on Apache this week. The effort in >> trying to restore services that rely on the old domain is not up to speed. >> >> I'd also suggest releasing a quick patch release for this change. I'll help >> start a new thread on dev@. >> >>> On Sun, Jul 17, 2016 at 10:03 AM, Andrew Purtell <[email protected]> >>> wrote: >>> Some of the initial delay is my responsibility. I waited after the >>> acceptance vote to file tickets to get things moving until I had a good >>> personal sense there would be no problem (at least on the Salesforce side) >>> with transfer of the PIO trademark and also discussed the matter with the >>> IPMC. >>> >>> I agree, though, now the onus is on Apache PredictionIO to start moving. >>> Unless, like I mentioned in my other email, there is some kind of blocker >>> in your workflow. Even then nothing will resolve if you're not making noise >>> about it. >>> >>> >>>> On Jul 17, 2016, at 9:54 AM, Suneel Marthi <[email protected]> wrote: >>>> >>>> PRedictionIO is all set up as an Apache project, the reason the website is >>>> not up has more to do with new Apache PredictionIO PMC not moving fast and >>>> has nothing to do with Apache Infra team, so stop pointing fingers at >>>> Apache Infra and how slow things are. >>>> >>>> Apache Pirk project was started < 10 days ago and they have everything up >>>> and running including the website - http://pirk.incubator.apache.org/ and >>>> the mailing lists are active. >>>> >>>> As far as Apache goes I think they have fulfilled all requests that were >>>> asked of them, the onus is now on PMC to jump start the project. >>>> >>>> Let's stop pointing fingers at Apache Infra and do what it takes to >>>> jumpstart the project. >>>> >>>> >>>> >>>>> On Sun, Jul 17, 2016 at 12:01 PM, Pat Ferrel <[email protected]> >>>>> wrote: >>>>> TLDR; rely on ActionML.com because we offer commercial support for >>>>> PredictionIO and use >>>>> https://groups.google.com/forum/#!forum/actionml-user but watch for >>>>> developments on the Apache mailing list here: >>>>> [email protected] >>>>> >>>>> The prediction.io site is not being maintained during the transition to >>>>> Apache and the Apache site is not functional yet. This Google Groups >>>>> forum will be retired in favor of an Apache mailing list that we can’t >>>>> document until we get an Apache site running. >>>>> >>>>> As to a schedule, the code is already donated to the ASF so there is no >>>>> question that it is an ASF project. But it takes time for the ASF >>>>> infrastructure people to set up site, mailing lists, etc., and more time >>>>> to get things moved over. Also consider that it’s vacation season so hard >>>>> to get everyone on the same page. >>>>> >>>>> Sorry for the confusion but rest assured that ASF, and ActionML plan to >>>>> support PIO in the long term and we (ActionML) are doing commercial >>>>> installations and customizations constantly during this period. >>>>> >>>>> BTW can someone document how to subscribe to >>>>> [email protected] ? >>>>> >>>>> >>>>> On Jul 17, 2016, at 2:57 AM, Евгений Шувалов <[email protected]> wrote: >>>>> >>>>> ATM install script doesn't work, template building\training doesn't work >>>>> (ssl problem?), some people are pointing to ActionML, main github repo >>>>> redirects to apache-incubator, what is going on? >>>>> It's clearly to me and others that there are some migration issues >>>>> because of Salesforce, but there should be some roadmap or readme >>>>> explaining what is going on and when it will be fixed. >>>>> I tried PredictionIO couple of months ago and it was fine, so we decided >>>>> to choose it for our needs. But now it does not work, what should we do? >>>>> Search another product? Or wait? Please explain > >
