kubernetes
Website does not have the correct trademark disclaimer
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
<footer>
<p>The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation,
please see our <a href="https://www.linuxfoundation.org/legal/trademark-usage">Trademark Usage page</a>.
</p>
</footer>
Link
<footer>
<ul>
<li><a href="https://www.linuxfoundation.org/legal/trademark-usage">Trademarks</a></li>
</ul>
</footer>
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.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
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:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/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!
