I think the CMS is still used but backed by git instead of SVN and so the history is all available as it was with SVN. I could be wrong, we’ll have to try it to see. On May 6, 2015, at 7:40 AM, Andrew Musselman <[email protected]> wrote:
The markup and publish process is what I wonder about; the current CMS may be klunky but it does work and provide staging and checkpointing. On Wednesday, May 6, 2015, Pat Ferrel <[email protected]> wrote: > https://docs.prediction.io/resources/intellij/ > Notice the blue edit button, bottom right. All it does is take you to the > page on github but hitting edit there leads you through editing and creates > the correct PR to their “livedocs” branch. No idea what their publish > process is, but with a PR it seems like we can do a merge to the ASF git > repo and get it published through the ASF process. > > On May 5, 2015, at 10:25 AM, Ted Dunning <[email protected] > <javascript:;>> wrote: > > Can you give a pointer to such an icon? > > > > On Tue, May 5, 2015 at 6:16 PM, Pat Ferrel <[email protected] > <javascript:;>> wrote: > >> I asked to sign us up when this was first announced but haven’t heard >> back. On another project I hit an “edit” icon on their site, which >> automatically sent me to the page on github, where I was allowed to edit. >> This automatically created a branch in my repo and a pr to the correct >> branch of their repo. Very convenient. That way an edit icon can be put > on >> every Mahout CMS page and users will find requesting some rewording quite >> easy. Notice that no write access is required since edits go through a > PR. >> >> Not sure if the ASF implementation does this, but would be nice. >> >> On May 3, 2015, at 9:58 AM, Ted Dunning <[email protected] > <javascript:;>> wrote: >> >> https://blogs.apache.org/infra/entry/git_based_websites_available >> >> This might be nice to get rid of the svn step in web site updates. It >> would involve an alternative workflow for updates rather than the CMS >> process. >> >> > >
