On Wed, 9 Apr 2025 at 12:35, Niall Pemberton <niall.pember...@gmail.com> wrote: > > 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 > > 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/ > > > > > > 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) > > = https://svn.apache.org/repos/asf/attic/site/docs/ > > What is important to me is to split the source xdocs from the generated > > HTML > > docs to clarify: whatever we choose should not impact user workflow, then > > I > > think we should do what is easiest from a migration perspective > > > > > > WDYT? > > > > Personally I would be in favour of moving the website to a more supported > toolset (markdown & Jekyll or Pelican?) and away from ant/anakia/xdocs and
Note that the website build relies on Anakia code (e.g. xdocs/stylesheets/site.vsl) to construct the pages from XML sources. Someone would need to design, code, test and document a replacement, and update the scripts that generate the sources. > split out the two "flagged" parts that the banner stuff relies on That would be easier to do, but needs to be co-ordinated with Puppet changes to ensure continuity. I agree that things could be simplified, but it all currently works. > Niall > > > > > > > Regards, > > > > Hervé > > > > > > > > > >
