I support this as long as (1) the site content remains in a separate repo from the source code, and (2) the documentation gets updated.
(1) is important because the generated site is large and changes frequently, and I don’t want to bloat the size of our source code repo (which gets copied into every contributor’s machine). And also because, as a software engineer, committing generated code to a source code repo makes me profoundly uncomfortable. I trust that the basic process of updating the site in the source repo (committing to the “site” branch, and cherry-picking to/from the “master” branch as appropriate) will not be affected by this change. Julian > On Feb 12, 2019, at 4:59 AM, Stamatis Zampetakis <zabe...@gmail.com> wrote: > > +1 > > Having one vcs to deal with, is good; automating the publication of the > site is great! > > Στις Δευ, 11 Φεβ 2019 στις 8:00 μ.μ., ο/η Michael Mior <mm...@apache.org> > έγραψε: > >> +1 for me as well and another +1 for automation if we can have this >> happen from the "site" branch. >> -- >> Michael Mior >> mm...@apache.org >> >> Le lun. 11 févr. 2019 à 05:01, Francis Chuang >> <francischu...@apache.org> a écrit : >>> >>> Hey all, >>> >>> ASF project sites have the ability to use git instead of subversion as >>> their repository for web site content [1]. It has been available since >>> 2015 and appears to be quite stable. Quite a few other projects have >>> also moved their websites to git and subsequently, Gitbox (for using >>> Github as their source of truth. As an example, see the Arrow project >> [2]. >>> >>> I myself would love to see this as I find gits interface and ux to be >>> much easier to use compared to svn. It also reduces the need to context >>> switch between Git and svn when editing and pushing the site. >>> >>> My overall goal is to find a way to automate the publishing and build of >>> our websites either via Jenkins builds (there are some projects are >>> doing this already when I searched infra) or the new Github actions [3]. >>> Having the site hosted in Git would make this process much easier to >>> automate. I will need to get in touch with infra to clarify a few things >>> and to see if this is feasible, but I think this is a worthwhile >> endeavor. >>> >>> How do you guys feel about moving our site's repository from svn to >> GitBox? >>> >>> Francis >>> >>> >>> [1] https://blogs.apache.org/infra/entry/git_based_websites_available >>> [2] https://issues.apache.org/jira/browse/INFRA-17655 >>> [3] https://github.com/features/actions >>
