Ping, any feedback? Otherwise I would start an official VOTE soon. After having a second thought I would also propose to replace svnpubsub (being managed by INFRA manually) by the equivalent for Git which can be controlled through .asf.yaml: https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=git+-+.asf.yaml+features#Git.asf.yamlfeatures-WebsitedeploymentserviceforGitrepositories. This internally relies on https://infra.apache.org/pypubsub.html.
That means that we would generate the HTML for the site in the according subproject: - https://github.com/apache/jackrabbit-filevault/tree/master/src/site - https://github.com/apache/jackrabbit-filevault-package-maven-plugin/tree/master/src/site and - https://github.com/apache/jackrabbit-oak/tree/trunk/oak-doc/src/site in a dedicated branch and just configure the sub directory feature accordingly: https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=git+-+.asf.yaml+features#Git.asf.yamlfeatures-Specifyingasub-directorytopublishto That way each module of the jackrabbit site (JR2, Oak, FileVault, …) is nicely encapsulated and there is no longer the need for cross-repository writes to publish the site. Konrad > On 12. Dec 2023, at 12:33, Konrad Windszus <[email protected]> wrote: > > Hi, > Currently the source for the Jackrabbit website is maintained at > https://svn.apache.org/repos/asf/jackrabbit/site/trunk/. > The Maven site build generates the target site out of that and the > maven-scm-publish-plugin pushes the generated site to > https://svn.apache.org/repos/asf/jackrabbit/site/live/jcr/ afterwards. > The last step is the tool svnpubsub (executed by ASF INFRA) publishing those > files to https://jackrabbit.apache.org/ > > I propose to create a new git repository for the Jackrabbit (2) site source > at https://gitbox.apache.org/repos/asf/jackrabbit-site.git / > https://github.com/apache/jackrabbit-site and let INFRA migrate the SVN > repository location https://svn.apache.org/repos/asf/jackrabbit/site/trunk/ > into that new repo (keeping the history) > That is the last active piece of the puzzle in the Jackrabbit ecosystem which > is still leveraging SVN. > > Note: I don’t propose to change the SVN repository containing the "generated > site” at https://svn.apache.org/repos/asf/jackrabbit/site/live/. That is > currently the target of multiple sources, namely > - https://github.com/apache/jackrabbit-filevault/tree/master/src/site > - > https://github.com/apache/jackrabbit-filevault-package-maven-plugin/tree/master/src/site > and > - https://github.com/apache/jackrabbit-oak/tree/trunk/oak-doc/src/site > > I don’t think there is an urgent need for changing this to Git as well, as > the active work uses the source repository locations only. > > WDYT? > Konrad
