On Sun, 18 Feb 2024 at 19:12, Craig Russell <apache....@gmail.com> wrote: > > I was just looking at the web site check tool and I've added a board > discussion about the hundreds of failures.
OK, but out of scope for Whimsy. > I also clicked on one link > https://whimsy.apache.org/site/project/aries > and followed it to > https://aries.apache.org/documentation/index.html > and then to > https://github.com/apache/aries-antora-site/edit/master/modules/ROOT/pages/index.adoc > > This repository must be forked in order to propose changes. AFAICT that is normal. Only project committers can create branches in ASF git repos, and PRs need branches. > Here's what I think needs to be done: > check for a link to the source code to the web site repository; if not, > yellow flag Whimsy only checks the index page, which would imply that all websites would need to link to the website repo (which might also be in SVN) from the main index page. It would be useful if every page had an Edit button, but that may not be easy to do, depending on the website repo and build process. I think it would be a mistake to make that mandatory. > check that the repository is at least readable for the public That is potentially possible to check, though I think it is unnecessary. AFAICT Infra does not use any authn to fetch the websites for display, so problems will be immediately apparent. > and read/write for committers of that project; if not, yellow flag I think that is out of scope for Whimsy. In any case, if project committers cannot update the website I'm sure they will complain. > I also think that policy should mandate a link to the repository and > read/write access by project committers. That is outside the scope of the Whimsy project. > Craig L Russell > c...@apache.org >
