+1 (non-binding) to switching to a git-based website +0 (non-binding) to switching to Hugo
While I'm more familiar with Jekyll than Hugo, the switch to a git-based website creates a *super* low bar to contribute to now for Apache Accumulo, the primary project I contribute to at Apache, that I think all projects should do it. It's now so easy that any committer can easily and automatically stage updates to our site by merely merging a pull request on GitHub. Publish from staging to production is trivial with a one-liner git command (https://github.com/apache/accumulo-website/blob/master/README.md#publishing). My main concern for ComDev here is for the use of Hugo over Jekyll, because 1) I'm not familiar with Hugo at all (though I know it is still Markdown-based), and 2) I don't know if INFRA supports automated Hugo builds like it does for Pelican and now Jekyll. If INFRA's .asf.yaml buildbot features can support the Hugo build automation like Pelican or Jekyll, I'm wholeheartedly in favor of ComDev leveraging it. Otherwise, I'd recommend using Pelican or Jekyll instead. On Sat, Feb 22, 2020 at 6:11 AM 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
