Re: [PATCH] docs: set canonical base URL for HTML output

["Rito Rhymes" <rito@ritovision.com>]

This is about protecting source authority in indexed search results,
which Linux kernel documentation very much exists in already.

Linux protects its trademarks, uses official marks and domains to
distinguish the project’s identity from copies and forks, and uses
provenance mechanisms such as sigstore for verifying the origin and
authenticity of software artifacts. A canonical URL is a different
angle to cover.

Indexed search results are an important distribution surface for
documentation, and it is also a hostile environment. For a
project like the Linux kernel, where its material is widely
copied, mirrored, archived, rehosted, and referenced across many
alternate paths and contexts, the stakes are higher and
protecting source authority matters more. Given the other ways
Linux already protects project identity, canonical URLs are a
small low-cost measure that supports its source authority for
indexing providers by indicating the preferred official URL for
a given resource.

The documentation site appears agnostic toward search engine
indexing because it neither opts out of indexed search for
compliant crawlers nor explicitly adds directives aimed at
optimizing for it. By being on the open web and not opting out,
it by default participates in the indexed web as a valid and standard
distribution surface for documentation. In that context, if
the site is part of the indexed web whether or not it actively
courts it, then using a low-cost standard signal like a canonical
URL is simply part of managing that reality responsibly.


> ...and how does it help all of the people who do their
> own docs builds?

You accepted the favicon fix earlier but you could argue something
similar about it:

"After someone downloads the Linux repo and runs the documentation
site locally, how does having the little logo visible in the browser
help them? Without it, will they not know they are viewing the Linux
documentation site?"

They are clearly different but what's in common is that they're
low-cost signals supporting the Linux identity on the web.

Rito