Yes, it is not clearly documented right now, but the idea is that gh-pages branch of current code repository have site sources and and deployment is a manual commit to svnpubsub of the build artefacts (_site dir).
Actually Drill was a really helpfull example for us: http://zeppelin-project.org is a preview hosted from on GH too. And of course patches are welcome for documentation and build automation as that is something we look into improving. On Sat, Feb 14, 2015 at 10:40 AM, Ted Dunning <[email protected]> wrote: > Drill has machinery to do this. They even use the gh-pages branch > mechanism that git uses so that they can use github to preview changes. > > > > On Fri, Feb 13, 2015 at 5:32 PM, Roman Shaposhnik <[email protected]> > wrote: > > > On Wed, Feb 11, 2015 at 11:02 PM, Eric Charles <[email protected]> wrote: > > > "How to contribute" [1] does not mention how to change the site code in > > > SVN [2]. > > > > > > Are you expecting some JIRA to welcome contributions? > > > > > > The svnpubsub mechanism requires SNV, OK, but the zeppelin incubator > > > project page [3] mentions that GIT will be used. Any tough about this? > > > > > > > > > [1] http://zeppelin-project.org/docs/development/howtocontribute.html > > > [2] http://svn.apache.org/viewvc/incubator/zeppelin/site/ > > > [3] http://incubator.apache.org/projects/zeppelin.html > > > [4] https://git.apache.org/incubator-zeppelin.git > > > > I think it would be super useful to document it, or better yet -- to > > automate > > site updates via mvn. > > > > Thanks, > > Roman. > > >
