+1

I suggest taking a snapshot of the current website (e.g. tag SVN) so
the page names/content can be compared with the new site.

On Mon, 24 Feb 2020 at 14:57, Rich Bowen <rbo...@rcbowen.com> wrote:
>
>
>
> On 2/22/20 6:11 AM, Roy Lenferink wrote:
> > Hi all,
> >
> > After this week's proposal [1] I'd like to start a formal vote on moving 
> > over community.a.o from the
> > current Apache CMS/SVN to Hugo/Git.
> >
> > Involved steps:
> > - Create a comdev-site gitbox repository which will be synced with the 
> > current comdev-site repo on
> > GitHub.
> > - Rename 'trunk' to 'master' and set 'master' as default branch (git repo)
> > - Create a Jenkins job which generates the actual site to the 'asf-site' 
> > branch
> > - Move serving of community.a.o from svn to git
> > - Remove 'community' from the CMS
> > - Add a MOVED_TO_GIT file to the svn repo making clear the the directory 
> > contents have moved
> > to git.
> >
> > Please vote:
> > [ ] +1 for moving over from the CMS/svn to Hugo/git.
> > [ ] -1 for not moving over, in this case please explain why
>
> +1
>
> I am not a fan of git, but am not going to get in the way of people who
> are doing (have already done) the work.
>
> --
> Rich Bowen - rbo...@rcbowen.com
> http://rcbowen.com/
> @rbowen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Reply via email to