+1 for moving to git -0 for hugo, as I believe we would have a bigger set of familiar people comfortable contributing to Jekyll based website based on its wide adoption at other places ata Apache.
On Sat, Feb 22, 2020 at 12:11 Roy Lenferink <rlenfer...@apache.org> 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 > > Best, > Roy > > [1] > https://lists.apache.org/thread.html/r338baf731f509c6ae833600469c2b247cafe02022c1687a705a66012%40%3Cdev.community.apache.org%3E > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > > -- Sent from my Mobile device
