Jan Høydahl wrote on 11/13/21 5:10 PM:
I'm happy to provide fallback code or some "alt tag". I just copy-pasted the
HTML from https://www.apachecon.com/event-images/ so either the checker is wrong or the
event html is wrong :)
...snip...
Thanks Jan - don't worry about it, this is for Whimsy to fix.
The checker currently scans the HTML to match with a list of regexes, to
try to find strings or elements that match various policy requirements.
Most of these are in traditional kinds of links: for example, we
expect the word "License" to physically appear for the link to our
software license, since that's a fundamental part of our model.
But some projects want to use different ways to expose required
data/links - just like conferences apparently does now with the JS
snippet.
So we need to update the events checker to also check for this snippet
as a "fallback", i.e. assuming that if you've implemented an <a... with
class="acevent" then you're doing what conferences asked, which is
plenty for a project to do.
I was wondering if this is just adding another regex to the events
checker, or if we should eventually have a concept of "alternate"
passing. I.e. if you find the actual text "License", it passes (as
expected having a visible link). But if someone wanted to expose that
link differently, they could use class="realApacheLicenseLink" or
whatever, and we'd mark that as pass, but using an alternate method.
I.e. do we care to track projects that use the "regular" way, or an
alternate way? Or just fix individual scanner to pass both and not care
how it passed?
--
- Shane
Whimsy PMC
The Apache Software Foundation
