On Fri, 4 Apr 2025 at 08:04, Hervé Boutemy <hbout...@apache.org> wrote: > > Attic website is currently in svn: > https://svn.apache.org/repos/asf/attic/site/ > > with Git read-only mirror > https://github.com/apache/attic-site/ > > we are facing 2 issues: > - viewvc is not working any more on svn, which makes svn even less usable
Hoever, the Git mirror helps here. > nowadays than ever before: https://svn.apache.org/viewvc/attic > - people propose PRs on Git as it is common knowledge nowadays (who remembers > how to do Jira issue with svn patch attached? who takes time to do it?) > > > I'd like that we switch to Git read-write for site's source maintenance > particularly the xdocs source > https://svn.apache.org/repos/asf/attic/site/xdocs/ > Git does not store empty directories, so that would require a change to the way the flagged/ tree is maintained. (note that the enitre flagged/ tree is missing from the mirror under xdocs and docs) Not a blocker, but it would have to be sorted first. > and choose what we do with the html output in doc: either keep it in svn for > svnpubsub or switch it to Git branch for GitPubSub (or any name this mechanism > has nowadays) The site is currently built using buildbot, which assumes SVN for source and target. That would also have to be fixed. > = https://svn.apache.org/repos/asf/attic/site/docs/ > What is important to me is to split the source xdocs from the generated HTML Why? > docs to clarify: whatever we choose should not impact user workflow, then I > think we should do what is easiest from a migration perspective Moving to Git will definitely affect the workfllow, so I don't understand the above paragraph. > WDYT? Also, what about the current JIRA workflow that Attic uses? Would that be moved to Git somehow? Note that Attic would still need to use Jira for raising Infra issues. > Regards, > > Hervé > > > >
