Hi folks,

I propose that we move our website repo from svn
<https://svn.apache.org/repos/asf/mesos/site> to git.

The main motivation for this is to automate the website building process!

I know this has been a pain in the past for release managers. Moving to git
allows us to leverage ASF Jenkins to auto publish website on a daily /
release basis without worrying about credentials. One less thing to worry
about while doing releases!

I had a long chat with Gavin from ASF infra today and looks like moving to
git will be the easiest way to automate this.

Of course, a side benefit is that we deal with one version control system
(git) and repo instead of two systems and repos.

*Implementation details: *

We have an option to move to
1) a standalone git repo (say "mesos-site") which will be mirrored on
github.
2) just use our "mesos" git repo and publish a "asf-site" branch with
website contents (say at 'site/publish' directory)

I'm leaning towards 2) because that allows us to deal with single repo
instead of two.

I already have a local branch for automating the website build. Just need
to hook it up to ASF Jenkins. I will also volunteer to update the website
building docs as part of this effort.

Let me know if you have any objections or questions. If none, I will put
the wheels in motion to start the move.

Thanks,
Vinod

Reply via email to