Re: [RESULT][VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
I agree the PR [1] is ready to be merged (no conflicts anymore and minor differences are resolved as well now). Also, merging the pull requests doesn't automatically switch over serving of community.a.o from svn to git. It will only be served from git after [2] is merged. So what I'd suggest: - merge [1], - create a Jenkins job which updates the asf-site branch after changes to the 'master' branch are made (I'll do this) - then merge [2] and start serving community.a.o from git :) [1] https://github.com/apache/comdev-site/pull/5 [2] https://github.com/apache/infrastructure-puppet/pull/1753 On 2020/03/31 13:42:53, Rich Bowen wrote: > So ... bringing it back to the list. > > We chatted about this on Slack briefly, and we are still in the forklift > process. There's a MASSIVE PR here - > https://github.com/apache/comdev-site/pull/5 > > I have recommended we just merge it, and then deal with the fallout of > the handful of things that will probably break. But that's just one > opinion. (FWIW, Shane agreed with me.) > > But, the summary is, this is happening, and life gets in the way. So I > just need to be patient. > > HOWEVER, if you want to help test, the git repo is as above, and Hugo > (our new site framework) lives here: > https://github.com/gohugoio/hugo/releases/tag/v0.63.2. > > --Rich > > On 3/31/20 9:13 AM, Rich Bowen wrote: > > Can you update us as to where this is? > > > > Specifically, I'm trying to make an edit to the site, and it turns out I > > don't know how. Can you please update > > https://community.apache.org/about/#about-this-website and > > https://community.apache.org/newbiefaq.html#websitecms with the info > > necessary for me to make edits? > > > > Thanks! > > > > --Rich > > > > On 3/10/20 2:27 PM, Roy Lenferink wrote: > >> Hi, > >> > >> The community has voted on moving over the current > >> community.apache.org website from the > >> CMS/SVN to be Git/Hugo based [1] > >> > >> The vote passed with the following results: > >> +1 Rich Bowen (binding) > >> +1 Sebb (binding) > >> > >> +1 Austin Bennett (non-binding) > >> +1 Aizhamal Nurmamat kyzy (non-binding) > >> +1 Willem Ning Jiang (non-binding) > >> +1 Kamil Breguła (non-binding) > >> +1 Liang Zhang (non-binding) > >> +1 Jarek Potiuk (non-binding) > >> +1 Aditya Sharma (non-binding) > >> +1 Tomasz Urbaszek (non-binding) > >> +1 Manish Sharma (non-binding) > >> +1 Xin Wang (non-binding) > >> +1 Ming Wen (non-binding) > >> +1 Roy Lenferink (non-binding) > >> > >> +1 Christopher Tubbs (non-binding) to switching to a git-based website > >> +0 Christopher Tubbs (non-binding) to switching to Hugo > >> > >> +1 Luciano Resende (binding) for moving to git > >> -0 Luciano Resende (binding) for hugo > >> > >> I'll start to get things moving. > >> > >> Regards, > >> Roy > >> > >> [1] > >> https://lists.apache.org/thread.html/rd5f62582ac2feb0d707cde413cc9288d681cb17b9f37ef71f349e078%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 > >> > > > > -- > 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
Re: [RESULT][VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
On Tue, Mar 31, 2020 at 3:43 PM Rich Bowen wrote: > ...There's a MASSIVE PR here - > https://github.com/apache/comdev-site/pull/5 > > I have recommended we just merge it, and then deal with the fallout of > the handful of things that will probably break... +1 I have stored an archive of the current live site content (html, css etc) at https://github.com/apache/comdev-site/tree/master/archives in case we need to compare or fix things. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [RESULT][VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
+1 to merge I believe it is better to move forward :) On Tue, 31 Mar 2020 at 20:43, Rich Bowen wrote: > So ... bringing it back to the list. > > We chatted about this on Slack briefly, and we are still in the forklift > process. There's a MASSIVE PR here - > https://github.com/apache/comdev-site/pull/5 > > I have recommended we just merge it, and then deal with the fallout of > the handful of things that will probably break. But that's just one > opinion. (FWIW, Shane agreed with me.) > > But, the summary is, this is happening, and life gets in the way. So I > just need to be patient. > > HOWEVER, if you want to help test, the git repo is as above, and Hugo > (our new site framework) lives here: > https://github.com/gohugoio/hugo/releases/tag/v0.63.2. > > --Rich > > On 3/31/20 9:13 AM, Rich Bowen wrote: > > Can you update us as to where this is? > > > > Specifically, I'm trying to make an edit to the site, and it turns out I > > don't know how. Can you please update > > https://community.apache.org/about/#about-this-website and > > https://community.apache.org/newbiefaq.html#websitecms with the info > > necessary for me to make edits? > > > > Thanks! > > > > --Rich > > > > On 3/10/20 2:27 PM, Roy Lenferink wrote: > >> Hi, > >> > >> The community has voted on moving over the current > >> community.apache.org website from the > >> CMS/SVN to be Git/Hugo based [1] > >> > >> The vote passed with the following results: > >> +1 Rich Bowen (binding) > >> +1 Sebb (binding) > >> > >> +1 Austin Bennett (non-binding) > >> +1 Aizhamal Nurmamat kyzy (non-binding) > >> +1 Willem Ning Jiang (non-binding) > >> +1 Kamil Breguła (non-binding) > >> +1 Liang Zhang (non-binding) > >> +1 Jarek Potiuk (non-binding) > >> +1 Aditya Sharma (non-binding) > >> +1 Tomasz Urbaszek (non-binding) > >> +1 Manish Sharma (non-binding) > >> +1 Xin Wang (non-binding) > >> +1 Ming Wen (non-binding) > >> +1 Roy Lenferink (non-binding) > >> > >> +1 Christopher Tubbs (non-binding) to switching to a git-based website > >> +0 Christopher Tubbs (non-binding) to switching to Hugo > >> > >> +1 Luciano Resende (binding) for moving to git > >> -0 Luciano Resende (binding) for hugo > >> > >> I'll start to get things moving. > >> > >> Regards, > >> Roy > >> > >> [1] > >> > https://lists.apache.org/thread.html/rd5f62582ac2feb0d707cde413cc9288d681cb17b9f37ef71f349e078%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 > >> > > > > -- > 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 > > -- WBR Maxim aka solomax
Re: [RESULT][VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
So ... bringing it back to the list. We chatted about this on Slack briefly, and we are still in the forklift process. There's a MASSIVE PR here - https://github.com/apache/comdev-site/pull/5 I have recommended we just merge it, and then deal with the fallout of the handful of things that will probably break. But that's just one opinion. (FWIW, Shane agreed with me.) But, the summary is, this is happening, and life gets in the way. So I just need to be patient. HOWEVER, if you want to help test, the git repo is as above, and Hugo (our new site framework) lives here: https://github.com/gohugoio/hugo/releases/tag/v0.63.2. --Rich On 3/31/20 9:13 AM, Rich Bowen wrote: Can you update us as to where this is? Specifically, I'm trying to make an edit to the site, and it turns out I don't know how. Can you please update https://community.apache.org/about/#about-this-website and https://community.apache.org/newbiefaq.html#websitecms with the info necessary for me to make edits? Thanks! --Rich On 3/10/20 2:27 PM, Roy Lenferink wrote: Hi, The community has voted on moving over the current community.apache.org website from the CMS/SVN to be Git/Hugo based [1] The vote passed with the following results: +1 Rich Bowen (binding) +1 Sebb (binding) +1 Austin Bennett (non-binding) +1 Aizhamal Nurmamat kyzy (non-binding) +1 Willem Ning Jiang (non-binding) +1 Kamil Breguła (non-binding) +1 Liang Zhang (non-binding) +1 Jarek Potiuk (non-binding) +1 Aditya Sharma (non-binding) +1 Tomasz Urbaszek (non-binding) +1 Manish Sharma (non-binding) +1 Xin Wang (non-binding) +1 Ming Wen (non-binding) +1 Roy Lenferink (non-binding) +1 Christopher Tubbs (non-binding) to switching to a git-based website +0 Christopher Tubbs (non-binding) to switching to Hugo +1 Luciano Resende (binding) for moving to git -0 Luciano Resende (binding) for hugo I'll start to get things moving. Regards, Roy [1] https://lists.apache.org/thread.html/rd5f62582ac2feb0d707cde413cc9288d681cb17b9f37ef71f349e078%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 -- 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
Re: [RESULT][VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
On Tue, Mar 31, 2020 at 3:34 PM Bertrand Delacretaz wrote: > ...Turns out the content has moved to Git, see > https://github.com/apache/comdev-site/blob/master/WEBSITE-HOWTO.txt I have started to update the README at https://github.com/apache/comdev-site , if someone has more info please update it. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [RESULT][VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
On Tue, Mar 31, 2020 at 3:20 PM Bertrand Delacretaz wrote: ... > > https://svn.apache.org/repos/asf/comdev/site/trunk/WEBSITE-HOWTO.txt > > should help... Turns out the content has moved to Git, see https://github.com/apache/comdev-site/blob/master/WEBSITE-HOWTO.txt Not sure if and how the website build works now. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [RESULT][VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
On Tue, Mar 31, 2020 at 3:17 PM Bertrand Delacretaz wrote: > https://svn.apache.org/repos/asf/comdev/site/trunk/WEBSITE-HOWTO.txt > should help... I just pushed some unpublished changes via https://cms.apache.org/community/publish?diff=1 so it looks like that's still active. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [RESULT][VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
On Tue, Mar 31, 2020 at 3:13 PM Rich Bowen wrote: > ...Specifically, I'm trying to make an edit to the site, and it turns out I > don't know how... FWIW, If things haven't changed yet (and I haven't seen a mention of actual changes), https://svn.apache.org/repos/asf/comdev/site/trunk/WEBSITE-HOWTO.txt should help. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [RESULT][VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
Can you update us as to where this is? Specifically, I'm trying to make an edit to the site, and it turns out I don't know how. Can you please update https://community.apache.org/about/#about-this-website and https://community.apache.org/newbiefaq.html#websitecms with the info necessary for me to make edits? Thanks! --Rich On 3/10/20 2:27 PM, Roy Lenferink wrote: Hi, The community has voted on moving over the current community.apache.org website from the CMS/SVN to be Git/Hugo based [1] The vote passed with the following results: +1 Rich Bowen (binding) +1 Sebb (binding) +1 Austin Bennett (non-binding) +1 Aizhamal Nurmamat kyzy (non-binding) +1 Willem Ning Jiang (non-binding) +1 Kamil Breguła (non-binding) +1 Liang Zhang (non-binding) +1 Jarek Potiuk (non-binding) +1 Aditya Sharma (non-binding) +1 Tomasz Urbaszek (non-binding) +1 Manish Sharma (non-binding) +1 Xin Wang (non-binding) +1 Ming Wen (non-binding) +1 Roy Lenferink (non-binding) +1 Christopher Tubbs (non-binding) to switching to a git-based website +0 Christopher Tubbs (non-binding) to switching to Hugo +1 Luciano Resende (binding) for moving to git -0 Luciano Resende (binding) for hugo I'll start to get things moving. Regards, Roy [1] https://lists.apache.org/thread.html/rd5f62582ac2feb0d707cde413cc9288d681cb17b9f37ef71f349e078%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 -- 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
[RESULT][VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
Hi, The community has voted on moving over the current community.apache.org website from the CMS/SVN to be Git/Hugo based [1] The vote passed with the following results: +1 Rich Bowen (binding) +1 Sebb (binding) +1 Austin Bennett (non-binding) +1 Aizhamal Nurmamat kyzy (non-binding) +1 Willem Ning Jiang (non-binding) +1 Kamil Breguła (non-binding) +1 Liang Zhang (non-binding) +1 Jarek Potiuk (non-binding) +1 Aditya Sharma (non-binding) +1 Tomasz Urbaszek (non-binding) +1 Manish Sharma (non-binding) +1 Xin Wang (non-binding) +1 Ming Wen (non-binding) +1 Roy Lenferink (non-binding) +1 Christopher Tubbs (non-binding) to switching to a git-based website +0 Christopher Tubbs (non-binding) to switching to Hugo +1 Luciano Resende (binding) for moving to git -0 Luciano Resende (binding) for hugo I'll start to get things moving. Regards, Roy [1] https://lists.apache.org/thread.html/rd5f62582ac2feb0d707cde413cc9288d681cb17b9f37ef71f349e078%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
Re: [VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
Adding my +1 as well On 2020/03/07 03:37:07, Ming Wen wrote: > +1 (non-binding) > > Xin Wang 于2020年3月7日 周六上午11:22写道： > > > +1 (non-binding) > > > > - Xin > > > > Manish Sharma 于2020年3月6日周五 下午11:52写道： > > > > > +1 > > > > > > On Fri, 6 Mar 2020 at 20:49, Tomasz Urbaszek > > wrote: > > > > > > > +1 (no-binding) > > > > > > > > T. > > > > > > > > > > > > On Fri, Mar 6, 2020 at 4:06 PM Aditya Sharma > > > > wrote: > > > > > > > > > > +1 (no-binding) > > > > > > > > > > Thanks and Regards, > > > > > Aditya Sharma > > > > > > > > > > On Fri, 6 Mar 2020 at 19:53, Jarek Potiuk wrote: > > > > > > > > > > > > +1 (non-binding). Hugo is great! Git even more so. > > > > > > > > > > > > On Fri, Mar 6, 2020 at 10:37 AM Liang Zhang > > > > > > wrote: > > > > > > > > > > > > > +1 (no-binding) > > > > > > > I developed ShardingSphere website using Hugo, I like it. > > > > > > > > > > > > > > On 2020/02/22 11:11:15, 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 > > > > > > > > > > > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > +48 660 796 129 > > > > > > > > > > - > > > > > 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 > > > > > > > > > > > > > > > > > -- > > Thanks, > > Xin > > > -- > Thanks, > Ming Wen, Apache APISIX > Twitter: _WenMing > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
+1 (non-binding) Xin Wang 于2020年3月7日 周六上午11:22写道： > +1 (non-binding) > > - Xin > > Manish Sharma 于2020年3月6日周五 下午11:52写道： > > > +1 > > > > On Fri, 6 Mar 2020 at 20:49, Tomasz Urbaszek > wrote: > > > > > +1 (no-binding) > > > > > > T. > > > > > > > > > On Fri, Mar 6, 2020 at 4:06 PM Aditya Sharma > > > wrote: > > > > > > > > +1 (no-binding) > > > > > > > > Thanks and Regards, > > > > Aditya Sharma > > > > > > > > On Fri, 6 Mar 2020 at 19:53, Jarek Potiuk wrote: > > > > > > > > > > +1 (non-binding). Hugo is great! Git even more so. > > > > > > > > > > On Fri, Mar 6, 2020 at 10:37 AM Liang Zhang > > > > wrote: > > > > > > > > > > > +1 (no-binding) > > > > > > I developed ShardingSphere website using Hugo, I like it. > > > > > > > > > > > > On 2020/02/22 11:11:15, 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 > > > > > > > > > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > > -- > > > > > +48 660 796 129 > > > > > > > > - > > > > 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 > > > > > > > > > > > -- > Thanks, > Xin > -- Thanks, Ming Wen, Apache APISIX Twitter: _WenMing
Re: [VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
+1 (non-binding) - Xin Manish Sharma 于2020年3月6日周五 下午11:52写道： > +1 > > On Fri, 6 Mar 2020 at 20:49, Tomasz Urbaszek wrote: > > > +1 (no-binding) > > > > T. > > > > > > On Fri, Mar 6, 2020 at 4:06 PM Aditya Sharma > > wrote: > > > > > > +1 (no-binding) > > > > > > Thanks and Regards, > > > Aditya Sharma > > > > > > On Fri, 6 Mar 2020 at 19:53, Jarek Potiuk wrote: > > > > > > > > +1 (non-binding). Hugo is great! Git even more so. > > > > > > > > On Fri, Mar 6, 2020 at 10:37 AM Liang Zhang > > wrote: > > > > > > > > > +1 (no-binding) > > > > > I developed ShardingSphere website using Hugo, I like it. > > > > > > > > > > On 2020/02/22 11:11:15, 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 > > > > > > > > > > > > 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 > > > > > > > > > > > > > > > > > > -- > > > > +48 660 796 129 > > > > > > - > > > 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 > > > > > -- Thanks, Xin
Re: [VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
+1 On Fri, 6 Mar 2020 at 20:49, Tomasz Urbaszek wrote: > +1 (no-binding) > > T. > > > On Fri, Mar 6, 2020 at 4:06 PM Aditya Sharma > wrote: > > > > +1 (no-binding) > > > > Thanks and Regards, > > Aditya Sharma > > > > On Fri, 6 Mar 2020 at 19:53, Jarek Potiuk wrote: > > > > > > +1 (non-binding). Hugo is great! Git even more so. > > > > > > On Fri, Mar 6, 2020 at 10:37 AM Liang Zhang > wrote: > > > > > > > +1 (no-binding) > > > > I developed ShardingSphere website using Hugo, I like it. > > > > > > > > On 2020/02/22 11:11:15, 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 > > > > > > > > > > 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 > > > > > > > > > > > > > > -- > > > +48 660 796 129 > > > > - > > 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 > >
Re: [VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
+1 (no-binding) T. On Fri, Mar 6, 2020 at 4:06 PM Aditya Sharma wrote: > > +1 (no-binding) > > Thanks and Regards, > Aditya Sharma > > On Fri, 6 Mar 2020 at 19:53, Jarek Potiuk wrote: > > > > +1 (non-binding). Hugo is great! Git even more so. > > > > On Fri, Mar 6, 2020 at 10:37 AM Liang Zhang wrote: > > > > > +1 (no-binding) > > > I developed ShardingSphere website using Hugo, I like it. > > > > > > On 2020/02/22 11:11:15, 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 > > > > > > > > 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 > > > > > > > > > > -- > > +48 660 796 129 > > - > 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
Re: [VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
+1 (no-binding) Thanks and Regards, Aditya Sharma On Fri, 6 Mar 2020 at 19:53, Jarek Potiuk wrote: > > +1 (non-binding). Hugo is great! Git even more so. > > On Fri, Mar 6, 2020 at 10:37 AM Liang Zhang wrote: > > > +1 (no-binding) > > I developed ShardingSphere website using Hugo, I like it. > > > > On 2020/02/22 11:11:15, 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 > > > > > > 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 > > > > > > -- > +48 660 796 129 - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
+1 (non-binding). Hugo is great! Git even more so. On Fri, Mar 6, 2020 at 10:37 AM Liang Zhang wrote: > +1 (no-binding) > I developed ShardingSphere website using Hugo, I like it. > > On 2020/02/22 11:11:15, 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 > > > > 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 > > -- +48 660 796 129
Re: [VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
+1 (no-binding) I developed ShardingSphere website using Hugo, I like it. On 2020/02/22 11:11:15, 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 > > 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
Re: [VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
+1 (no-binding) I developed Airflow website using Hugo. It's fantastic. https://airflow.apache.org/ https://github.com/apache/airflow-site On Wed, Mar 4, 2020 at 2:12 AM Willem Jiang wrote: > > +1 (no-binding) > For moving to a modern website builder :) > > On Sat, Feb 22, 2020 at 7:11 PM 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 > > > > 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 > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
+1 (no-binding) For moving to a modern website builder :) On Sat, Feb 22, 2020 at 7:11 PM 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 > > 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
Re: [VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
+1 (non-binding) Hugo is much easier to manage than Jekyll from my personal experience as a non-developer. On Tue, Mar 3, 2020 at 4:03 PM sebb wrote: > +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 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 > >
Re: [VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
+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 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
Re: [VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
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
Re: [VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
+1 (non-binding) On Sat, Feb 22, 2020 at 4:48 AM Bertrand Delacretaz wrote: > On Sat, Feb 22, 2020 at 12:11 PM Roy Lenferink > wrote: > > [X ] +1 for moving over from the CMS/svn to Hugo/git... > > I'm not familiar with Hugo but it's well known and looking at > https://github.com/apache/comdev-site/pull/5 it doesn't look hard to > manage. > > -Bertrand > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: [VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
On Sat, Feb 22, 2020 at 12:11 PM Roy Lenferink wrote: > [X ] +1 for moving over from the CMS/svn to Hugo/git... I'm not familiar with Hugo but it's well known and looking at https://github.com/apache/comdev-site/pull/5 it doesn't look hard to manage. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
+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 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
Re: [VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
+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 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
[VOTE] Move community.a.o site from CMS/SVN to Hugo/Git
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
Re: Move community.a.o site from CMS/SVN to Hugo/Git
Hi, On Wed, Feb 19, 2020 at 1:52 PM Roy Lenferink wrote: > ...With Hugo I was able to keep all current URLs working... I think keeping existing URLs (or redirecting from them) is an important requirement that we missed earlier. The comdev site has been around for quite some time so we have lots of those in our archives and around the Web, breaking them not be good. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Move community.a.o site from CMS/SVN to Hugo/Git
To be completely clear, I'm NOT saying "don't use Hugo", I'm just wanting to be sure that we aren't going down a road that will make contribution across the Foundation even more of a patchwork. It sounds, from other responses, that Hugo already has wider adoption here, which is awesome. On 2/19/20 7:52 AM, Roy Lenferink wrote: Hi Daniel / Rich, To be honest, I completely forgot the .asf.yaml was able to do such things, my bad. Currently the .asf.yaml supports both Jekyll and Pelican. My previous experience with Jekyll is that it is really slow at incrementally generating content when file changes are made (running on the Ubuntu bash shell on Windows). Also it requires ruby, rubygems, etc. to be installed. After your message I tried Pelican as well [1], I have to say, it is fairly easy to install (note: I already had pip installed). However, one big disadvantage would be that Pelican its output is a bit of a mess. Pelican is storing all its generated content in a single folder (e.g. /output/pages), which kinda breaks every link from an external website to community.a.o, e.g. the http://community.apache.org/newcommitter.html link will be broken as well. IMO we need to try to minimize impact when moving over. Of course we can work with RewriteRules and adding a 'Slug' to pages but that just adds extra maintenance. With Hugo I was able to keep all current URLs working. Generating the comdev site is done in ~226 ms. Hugo contains incremental builds as well (useful for development), which it serves from memory instead of writing the generated files to disk (compared to Pelican). Installing Hugo is just as easy as downloading the specified release, extracting the tarball and you're good to go ;) GitHub statistics: Jekyll: 39.7k stars / 8.7k forks / 893 contributors [2] Hugo: 41.7k stars / 4.7k forks / 606 contributors [3] Pelican: 9.4k stars / 1.6k forks / 347 contributors [4] @ Daniel, maybe I can help Infra to possibly support Hugo builds as well ? :) [1] https://github.com/rlenferink/comdev-site/tree/feature/conversion-to-pelican [2] https://github.com/jekyll/jekyll [3] https://github.com/gohugoio/hugo/ [4] https://github.com/getpelican/pelican On 2020/02/18 19:47:30, Daniel Gruno wrote: There are pelican auto-builds and auto-publishing via .asf.yaml files already, as well as custom build steps being introduced on builbot 2. see https://s.apache.org/asfyaml for starters... On 18/02/2020 13.45, Rich Bowen wrote: I would like to hear more about Hugo, since it's not one that I've heard of before. There are a zillion different content frameworks out there, and I have no preference for any of them except that the underlying file format is standard-ish. Markdown, or something similar that can be easily converted to the next framework-du-jour when Hugo is no longer the latest hotness. I would also strenuously encourage you to include Infra in any such discussion, before we forge our own new path, while Infra is already looking at a CMS replacement. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org -- 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
Re: Move community.a.o site from CMS/SVN to Hugo/Git
On 19/02/2020 06.52, Roy Lenferink wrote: Hi Daniel / Rich, To be honest, I completely forgot the .asf.yaml was able to do such things, my bad. Currently the .asf.yaml supports both Jekyll and Pelican. My previous experience with Jekyll is that it is really slow at incrementally generating content when file changes are made (running on the Ubuntu bash shell on Windows). Also it requires ruby, rubygems, etc. to be installed. After your message I tried Pelican as well [1], I have to say, it is fairly easy to install (note: I already had pip installed). However, one big disadvantage would be that Pelican its output is a bit of a mess. Pelican is storing all its generated content in a single folder (e.g. /output/pages), which kinda breaks every link from an external website to community.a.o, e.g. the http://community.apache.org/newcommitter.html link will be broken as well. IMO we need to try to minimize impact when moving over. Of course we can work with RewriteRules and adding a 'Slug' to pages but that just adds extra maintenance. With Hugo I was able to keep all current URLs working. Generating the comdev site is done in ~226 ms. Hugo contains incremental builds as well (useful for development), which it serves from memory instead of writing the generated files to disk (compared to Pelican). Installing Hugo is just as easy as downloading the specified release, extracting the tarball and you're good to go ;) Fair enough :) Sounds like we'd want Infra adding Hugo as a supported platform then? We could have things be auto-built and -deployed then. GitHub statistics: Jekyll: 39.7k stars / 8.7k forks / 893 contributors [2] Hugo: 41.7k stars / 4.7k forks / 606 contributors [3] Pelican: 9.4k stars / 1.6k forks / 347 contributors [4] @ Daniel, maybe I can help Infra to possibly support Hugo builds as well ? :) [1] https://github.com/rlenferink/comdev-site/tree/feature/conversion-to-pelican [2] https://github.com/jekyll/jekyll [3] https://github.com/gohugoio/hugo/ [4] https://github.com/getpelican/pelican On 2020/02/18 19:47:30, Daniel Gruno wrote: There are pelican auto-builds and auto-publishing via .asf.yaml files already, as well as custom build steps being introduced on builbot 2. see https://s.apache.org/asfyaml for starters... On 18/02/2020 13.45, Rich Bowen wrote: I would like to hear more about Hugo, since it's not one that I've heard of before. There are a zillion different content frameworks out there, and I have no preference for any of them except that the underlying file format is standard-ish. Markdown, or something similar that can be easily converted to the next framework-du-jour when Hugo is no longer the latest hotness. I would also strenuously encourage you to include Infra in any such discussion, before we forge our own new path, while Infra is already looking at a CMS replacement. - 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
Re: Move community.a.o site from CMS/SVN to Hugo/Git
Thanks Bertrand! At Celix we are using Hugo as well, which indeed works pretty well :) https://github.com/apache/celix-site On 2020/02/19 09:49:50, Bertrand Delacretaz wrote: > On Tue, Feb 18, 2020 at 8:09 PM Roy Lenferink wrote: > > ...An example (for demo purposes only) of Hugo its output is available here: > > http://comdev-site.roylenferink.nl/ > > Nice, thank you very much for working on this, I think it's long overdue! > > Us being geeks, it'll be hard to agree on tools, IMHO whoever does the > work decides, within the agreed upon constraints. > > So unless there are concrete benefits to using Pelican (or Jekyll > which is also mentioned at https://s.apache.org/asfyaml) I think what > you suggest works, being based on Markdown, well-known, with a > convenient templating mechanism and already used by other projects > (like https://github.com/apache/airflow-site). > > -Bertrand > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Move community.a.o site from CMS/SVN to Hugo/Git
Hi Daniel / Rich, To be honest, I completely forgot the .asf.yaml was able to do such things, my bad. Currently the .asf.yaml supports both Jekyll and Pelican. My previous experience with Jekyll is that it is really slow at incrementally generating content when file changes are made (running on the Ubuntu bash shell on Windows). Also it requires ruby, rubygems, etc. to be installed. After your message I tried Pelican as well [1], I have to say, it is fairly easy to install (note: I already had pip installed). However, one big disadvantage would be that Pelican its output is a bit of a mess. Pelican is storing all its generated content in a single folder (e.g. /output/pages), which kinda breaks every link from an external website to community.a.o, e.g. the http://community.apache.org/newcommitter.html link will be broken as well. IMO we need to try to minimize impact when moving over. Of course we can work with RewriteRules and adding a 'Slug' to pages but that just adds extra maintenance. With Hugo I was able to keep all current URLs working. Generating the comdev site is done in ~226 ms. Hugo contains incremental builds as well (useful for development), which it serves from memory instead of writing the generated files to disk (compared to Pelican). Installing Hugo is just as easy as downloading the specified release, extracting the tarball and you're good to go ;) GitHub statistics: Jekyll: 39.7k stars / 8.7k forks / 893 contributors [2] Hugo: 41.7k stars / 4.7k forks / 606 contributors [3] Pelican: 9.4k stars / 1.6k forks / 347 contributors [4] @ Daniel, maybe I can help Infra to possibly support Hugo builds as well ? :) [1] https://github.com/rlenferink/comdev-site/tree/feature/conversion-to-pelican [2] https://github.com/jekyll/jekyll [3] https://github.com/gohugoio/hugo/ [4] https://github.com/getpelican/pelican On 2020/02/18 19:47:30, Daniel Gruno wrote: > There are pelican auto-builds and auto-publishing via .asf.yaml files > already, as well as custom build steps being introduced on builbot 2. > > see https://s.apache.org/asfyaml for starters... > > On 18/02/2020 13.45, Rich Bowen wrote: > > I would like to hear more about Hugo, since it's not one that I've heard > > of before. > > > > There are a zillion different content frameworks out there, and I have > > no preference for any of them except that the underlying file format is > > standard-ish. Markdown, or something similar that can be easily > > converted to the next framework-du-jour when Hugo is no longer the > > latest hotness. > > > > I would also strenuously encourage you to include Infra in any such > > discussion, before we forge our own new path, while Infra is already > > looking at a CMS replacement. > > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Move community.a.o site from CMS/SVN to Hugo/Git
On Tue, Feb 18, 2020 at 8:09 PM Roy Lenferink wrote: > ...An example (for demo purposes only) of Hugo its output is available here: > http://comdev-site.roylenferink.nl/ Nice, thank you very much for working on this, I think it's long overdue! Us being geeks, it'll be hard to agree on tools, IMHO whoever does the work decides, within the agreed upon constraints. So unless there are concrete benefits to using Pelican (or Jekyll which is also mentioned at https://s.apache.org/asfyaml) I think what you suggest works, being based on Markdown, well-known, with a convenient templating mechanism and already used by other projects (like https://github.com/apache/airflow-site). -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Move community.a.o site from CMS/SVN to Hugo/Git
hugo is great ,fast ,and simple . content just focus markdown. Tomasz Urbaszek 于2020年2月19日周三 下午5:23写道： > We are using Hugo for https://airflow.apache.org and it works pretty well > :) > > T. > > On Tue, Feb 18, 2020 at 8:47 PM Daniel Gruno wrote: > > > There are pelican auto-builds and auto-publishing via .asf.yaml files > > already, as well as custom build steps being introduced on builbot 2. > > > > see https://s.apache.org/asfyaml for starters... > > > > On 18/02/2020 13.45, Rich Bowen wrote: > > > I would like to hear more about Hugo, since it's not one that I've > heard > > > of before. > > > > > > There are a zillion different content frameworks out there, and I have > > > no preference for any of them except that the underlying file format is > > > standard-ish. Markdown, or something similar that can be easily > > > converted to the next framework-du-jour when Hugo is no longer the > > > latest hotness. > > > > > > I would also strenuously encourage you to include Infra in any such > > > discussion, before we forge our own new path, while Infra is already > > > looking at a CMS replacement. > > > > > > On 2/18/20 2:07 PM, Roy Lenferink wrote: > > >> Hi fellow comdev-ers, > > >> > > >> The e-mail from a few days ago asking to change the year from 2018 -> > > >> 2020 triggered me and I > > >> thought how this could be improved. Also, an 'Edit this page' button > > >> will already help people to > > >> contribute changes to the current website. > > >> > > >> One way of doing this could be to start using a static website as > > >> Hugo. Hugo is a single static binary > > >> being able to generate static websites. More or less similar to what > > >> the Apache CMS is doing, except > > >> it is being used in a quite diverse set of communities (Kubernetes > > >> being one of them). Content written > > >> for the site will remain in markdown. > > >> > > >> This afternoon I had half an hour to spare and tried to convert > > >> community.a.o from the current CMS > > >> style to the style useful for Hugo. This worked out pretty well and > > >> not that much changes were > > >> needed. > > >> > > >> I have just created a pull request to the comdev-site repo on GitHub > > >> so people are able to review > > >> the work I did [1]. > > >> > > >> What I propose when people are okay with this move: > > >> - Request a comdev-site gitbox repository synced with the comdev-site > > >> repo on GitHub. > > >> - Change 'trunk' to 'master' as that matches a bit more with the git > > >> style of working > > >> - Merge the PR I created [1] > > >> - Create a Jenkins job to have the site automatically generated > > >> whenever new commits happen. > > >> - Move over serving community.a.o from svn to git. > > >> > > >> I'd like to hear your opinions on this ;) > > >> > > >> Best, > > >> Roy > > >> > > >> [1] https://github.com/apache/comdev-site/pull/5 > > >> > > >> - > > >> 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 > > > > > -- 独立之思想，自由之精神。 --陈寅恪
Re: Move community.a.o site from CMS/SVN to Hugo/Git
We are using Hugo for https://airflow.apache.org and it works pretty well :) T. On Tue, Feb 18, 2020 at 8:47 PM Daniel Gruno wrote: > There are pelican auto-builds and auto-publishing via .asf.yaml files > already, as well as custom build steps being introduced on builbot 2. > > see https://s.apache.org/asfyaml for starters... > > On 18/02/2020 13.45, Rich Bowen wrote: > > I would like to hear more about Hugo, since it's not one that I've heard > > of before. > > > > There are a zillion different content frameworks out there, and I have > > no preference for any of them except that the underlying file format is > > standard-ish. Markdown, or something similar that can be easily > > converted to the next framework-du-jour when Hugo is no longer the > > latest hotness. > > > > I would also strenuously encourage you to include Infra in any such > > discussion, before we forge our own new path, while Infra is already > > looking at a CMS replacement. > > > > On 2/18/20 2:07 PM, Roy Lenferink wrote: > >> Hi fellow comdev-ers, > >> > >> The e-mail from a few days ago asking to change the year from 2018 -> > >> 2020 triggered me and I > >> thought how this could be improved. Also, an 'Edit this page' button > >> will already help people to > >> contribute changes to the current website. > >> > >> One way of doing this could be to start using a static website as > >> Hugo. Hugo is a single static binary > >> being able to generate static websites. More or less similar to what > >> the Apache CMS is doing, except > >> it is being used in a quite diverse set of communities (Kubernetes > >> being one of them). Content written > >> for the site will remain in markdown. > >> > >> This afternoon I had half an hour to spare and tried to convert > >> community.a.o from the current CMS > >> style to the style useful for Hugo. This worked out pretty well and > >> not that much changes were > >> needed. > >> > >> I have just created a pull request to the comdev-site repo on GitHub > >> so people are able to review > >> the work I did [1]. > >> > >> What I propose when people are okay with this move: > >> - Request a comdev-site gitbox repository synced with the comdev-site > >> repo on GitHub. > >> - Change 'trunk' to 'master' as that matches a bit more with the git > >> style of working > >> - Merge the PR I created [1] > >> - Create a Jenkins job to have the site automatically generated > >> whenever new commits happen. > >> - Move over serving community.a.o from svn to git. > >> > >> I'd like to hear your opinions on this ;) > >> > >> Best, > >> Roy > >> > >> [1] https://github.com/apache/comdev-site/pull/5 > >> > >> - > >> 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 > >
Re: Move community.a.o site from CMS/SVN to Hugo/Git
There are pelican auto-builds and auto-publishing via .asf.yaml files already, as well as custom build steps being introduced on builbot 2. see https://s.apache.org/asfyaml for starters... On 18/02/2020 13.45, Rich Bowen wrote: I would like to hear more about Hugo, since it's not one that I've heard of before. There are a zillion different content frameworks out there, and I have no preference for any of them except that the underlying file format is standard-ish. Markdown, or something similar that can be easily converted to the next framework-du-jour when Hugo is no longer the latest hotness. I would also strenuously encourage you to include Infra in any such discussion, before we forge our own new path, while Infra is already looking at a CMS replacement. On 2/18/20 2:07 PM, Roy Lenferink wrote: Hi fellow comdev-ers, The e-mail from a few days ago asking to change the year from 2018 -> 2020 triggered me and I thought how this could be improved. Also, an 'Edit this page' button will already help people to contribute changes to the current website. One way of doing this could be to start using a static website as Hugo. Hugo is a single static binary being able to generate static websites. More or less similar to what the Apache CMS is doing, except it is being used in a quite diverse set of communities (Kubernetes being one of them). Content written for the site will remain in markdown. This afternoon I had half an hour to spare and tried to convert community.a.o from the current CMS style to the style useful for Hugo. This worked out pretty well and not that much changes were needed. I have just created a pull request to the comdev-site repo on GitHub so people are able to review the work I did [1]. What I propose when people are okay with this move: - Request a comdev-site gitbox repository synced with the comdev-site repo on GitHub. - Change 'trunk' to 'master' as that matches a bit more with the git style of working - Merge the PR I created [1] - Create a Jenkins job to have the site automatically generated whenever new commits happen. - Move over serving community.a.o from svn to git. I'd like to hear your opinions on this ;) Best, Roy [1] https://github.com/apache/comdev-site/pull/5 - 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
Re: Move community.a.o site from CMS/SVN to Hugo/Git
I would like to hear more about Hugo, since it's not one that I've heard of before. There are a zillion different content frameworks out there, and I have no preference for any of them except that the underlying file format is standard-ish. Markdown, or something similar that can be easily converted to the next framework-du-jour when Hugo is no longer the latest hotness. I would also strenuously encourage you to include Infra in any such discussion, before we forge our own new path, while Infra is already looking at a CMS replacement. On 2/18/20 2:07 PM, Roy Lenferink wrote: Hi fellow comdev-ers, The e-mail from a few days ago asking to change the year from 2018 -> 2020 triggered me and I thought how this could be improved. Also, an 'Edit this page' button will already help people to contribute changes to the current website. One way of doing this could be to start using a static website as Hugo. Hugo is a single static binary being able to generate static websites. More or less similar to what the Apache CMS is doing, except it is being used in a quite diverse set of communities (Kubernetes being one of them). Content written for the site will remain in markdown. This afternoon I had half an hour to spare and tried to convert community.a.o from the current CMS style to the style useful for Hugo. This worked out pretty well and not that much changes were needed. I have just created a pull request to the comdev-site repo on GitHub so people are able to review the work I did [1]. What I propose when people are okay with this move: - Request a comdev-site gitbox repository synced with the comdev-site repo on GitHub. - Change 'trunk' to 'master' as that matches a bit more with the git style of working - Merge the PR I created [1] - Create a Jenkins job to have the site automatically generated whenever new commits happen. - Move over serving community.a.o from svn to git. I'd like to hear your opinions on this ;) Best, Roy [1] https://github.com/apache/comdev-site/pull/5 - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org -- 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
Re: Move community.a.o site from CMS/SVN to Hugo/Git
Forgot to mention: An example (for demo purposes only) of Hugo its output is available here: http://comdev-site.roylenferink.nl/ On 2020/02/18 19:07:09, Roy Lenferink wrote: > Hi fellow comdev-ers, > > The e-mail from a few days ago asking to change the year from 2018 -> 2020 > triggered me and I > thought how this could be improved. Also, an 'Edit this page' button will > already help people to > contribute changes to the current website. > > One way of doing this could be to start using a static website as Hugo. Hugo > is a single static binary > being able to generate static websites. More or less similar to what the > Apache CMS is doing, except > it is being used in a quite diverse set of communities (Kubernetes being one > of them). Content written > for the site will remain in markdown. > > This afternoon I had half an hour to spare and tried to convert community.a.o > from the current CMS > style to the style useful for Hugo. This worked out pretty well and not that > much changes were > needed. > > I have just created a pull request to the comdev-site repo on GitHub so > people are able to review > the work I did [1]. > > What I propose when people are okay with this move: > - Request a comdev-site gitbox repository synced with the comdev-site repo on > GitHub. > - Change 'trunk' to 'master' as that matches a bit more with the git style of > working > - Merge the PR I created [1] > - Create a Jenkins job to have the site automatically generated whenever new > commits happen. > - Move over serving community.a.o from svn to git. > > I'd like to hear your opinions on this ;) > > Best, > Roy > > [1] https://github.com/apache/comdev-site/pull/5 > > - > 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
Move community.a.o site from CMS/SVN to Hugo/Git
Hi fellow comdev-ers, The e-mail from a few days ago asking to change the year from 2018 -> 2020 triggered me and I thought how this could be improved. Also, an 'Edit this page' button will already help people to contribute changes to the current website. One way of doing this could be to start using a static website as Hugo. Hugo is a single static binary being able to generate static websites. More or less similar to what the Apache CMS is doing, except it is being used in a quite diverse set of communities (Kubernetes being one of them). Content written for the site will remain in markdown. This afternoon I had half an hour to spare and tried to convert community.a.o from the current CMS style to the style useful for Hugo. This worked out pretty well and not that much changes were needed. I have just created a pull request to the comdev-site repo on GitHub so people are able to review the work I did [1]. What I propose when people are okay with this move: - Request a comdev-site gitbox repository synced with the comdev-site repo on GitHub. - Change 'trunk' to 'master' as that matches a bit more with the git style of working - Merge the PR I created [1] - Create a Jenkins job to have the site automatically generated whenever new commits happen. - Move over serving community.a.o from svn to git. I'd like to hear your opinions on this ;) Best, Roy [1] https://github.com/apache/comdev-site/pull/5 - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
