On Tue, 27 Apr 2021 at 02:10, Gilles Sadowski <gillese...@gmail.com> wrote: > > >>> [...] > > > > > > OK to create the > > > commons-site > > > "git" repository? > > > > Are you offering to do the work? > > If the option is still on the table, I could test the > website-related feature of ".asf.yaml": > > https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#git.asf.yamlfeatures-BranchProtection
Please do NOT attempt to use the 'publish' feature. As I already wrote that will likely mangle the current website and may require Infa assistance to untangle. Removal of a publish entry from .asf.yaml does not undo the checkout, and only Infra have direct access to the TLP server. However, you could experiment with the 'staging' feature, and see how easy it is to publish the site to the asf-site branch. Just don't attempt to publish that branch. > > > > BTW, I have found out that it is possible to combine site content from > > SVN and Git repos in order to create the website checkout. > > So there is no need to convert to Git. > > Is it the solution straightforwardly applicable to the current > setup of the Commons web site? [So that ".asf.yaml" should > not be used for the projects' sites.] AFAICT, yes. The website is currently taken from: https://svn-master.apache.org/repos/infra/websites/production/commons This is done as a single checkout. This could be changed to take the top-level website from its own location, and the dormant, sandbox and proper trees could be checked out into the relevant subdirectories. This should be fine so long as the top-level site does not have any files in those 3 subdirectories. For an example of this, go to https://infra-reports.apache.org/site-source/ and enter 'ant.apache.org' in the search box 'Find a web site' You should see 4 entries at different levels derived from different SVN URLs. Note that in each case the parent SVN tree does not have an entry for its children. E.g. The SVN location for ant.apache.org does not have a directory easyant or ivy. Note that .asf.yaml does not apply to SVN checkouts. If we were to determine that Git was better for the proper websites, we would need to ensure that the existing site is removed from SVN before trying to replace it with one from Git. > > > > == > > > > If there is a desire to use Git for the component websites, I suggest > > you try creating a couple of branches in the commons-math repository: > > asf-staging and asf-site. > > > > See if it is easy to create the staging site and then commit it to the > > asf-site branch. > > Did I misunderstand that the above documentation assumes a > dedicated "git" repository for the web site's contents? Not sure what documentation you are referring to. But AFAIK it does not matter if there is a separate Git repo with the asf-site and asf-staging branches, just as long as they can be separately checked out. > Or is this suggested only for an overhaul of how the sites are > built? I.e. do we need/want something like > https://gitbox.apache.org/repos/asf?p=logging-site.git > https://gitbox.apache.org/repos/asf?p=logging-log4j-site.git;a=tree > or not? > > Strangely, there is something there: > https://commons.staged.apache.org/ That is part of the CMS, and will be going away. > > > > I suspect it won't be significantly easier than the current process. > > > > However do *not* publish the asf-site branch as that will likely mess > > up the commons website; this may require Infra involvement to recover > > things. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
