Closed thisisobate closed 2 months ago
This issue is currently awaiting triage.
If cloud-provider-aws contributors determine this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
We use mkdocs
to generate that site, is there a recommended way to add this in our mkdocs.yml
config?
Looks like we have a few options (copyright
, social
links, etc.): https://squidfunk.github.io/mkdocs-material/setup/setting-up-the-footer
But there's also a "custom copyright" option that requires extending the standard mkdocs theme. It'd be handy if that could be provided by the techdocs team, if mkdocs is used by more than a few of the packages flagged in that issue 😄
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
@cartermckinnon unfortunately, the only way to fix this is by setting a "custom copyright" option. If you want the CNCF to assist you in creating one, I would advise you open a ticket on our servicedesk platform. Hope that helps!
Makes sense, I'll see what I can do! 👍
/assign
As part of our ongoing effort to https://github.com/cncf/techdocs/issues/198, we noticed that the website does not pass the trademark criteria on CLOMonitor.
To fix this: Head to the source code of the website. In the
<footer>
section, add a disclaimer or link to the Linux foundation trademark disclaimer page:Disclaimer
Link