License and Attribution of the Solidity Logo?

[hwhsu1231]

Hello, Solidity Team,

I am the author of the @localizethedocs organization, which focuses on manufacturing l10n projects for documentation of open-source projects. For example:

• cmake-docs-l10n,
• conan-docs-l10n,
• ros2-docs-l10n,
• and more.

Currently, the solidity-docs-l10n project is in the incubation phase. To place the Solidity logo at the top of the README, I need to upload the logo to the static repository and then access them via jsDelivr. I found the logo SVG files here:

• https://github.com/argotorg/solidity/blob/11be2f4881d1644f15b026d1022388f06a034a34/docs/_static/img/logo.svg
• https://github.com/argotorg/solidity/blob/11be2f4881d1644f15b026d1022388f06a034a34/docs/_static/img/logo-dark.svg

However, I would like to confirm the license of this logo and what attribution is required.

Based on the Solidity Brand Guide and the Wikimedia, how about the following attribution?

Code:

<tr>
  <td><code>mark/solidity-dark.svg</code></td>
  <td><img src="mark/solidity-dark.svg" alt="solidity-dark" width="100"/></td>
  <td><a href="https://github.com/argotorg/solidity/blob/11be2f4881d1644f15b026d1022388f06a034a34/docs/_static/img/logo.svg">Link</a></td>
  <td>By <a href="https://ethereum.foundation/">Ethereum Foundation</a>, licensed under <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>.</td>
</tr>
<tr>
  <td><code>mark/solidity-light.svg</code></td>
  <td><img src="mark/solidity-light.svg" alt="solidity-light" width="100"/></td>
  <td><a href="https://github.com/argotorg/solidity/blob/11be2f4881d1644f15b026d1022388f06a034a34/docs/_static/img/logo-dark.svg">Link</a></td>
  <td>By <a href="https://ethereum.foundation/">Ethereum Foundation</a>, licensed under <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>.</td>
</tr>

Preview:

[hwhsu1231]

AFAIK, the Solidity Documentation Translations community, @solidity-docs, has been established. However, its maintenance approach involves directly translating the original .rst files, rather than utilizing Sphinx's Internationalization with Gettext feature.

1. The former method is easy to set up initially but is highly labor-intensive for long-term maintenance.
2. The latter method is slightly more complex to set up but allows for automation via command-line tools.

The infrastructure designed by my organization, @localizethedocs, utilizes the latter. And, I saw the following "Help Needed" message for Automation in this issue:

Automation - Help Needed!

Optimally, we would like to have a bot similar to the reactjs-translation-bot, which would create PRs with new content that needs to be translated every time the original documentation is updated.

Currently we have nobody who can set this up, so if you have experience in setting something like this up and want to help, please reach out! :)

While the infrastructure I designed is completely different from the one currently maintained by @solidity-docs, mine utilizes CMake scripts and GitHub Workflows to achieve automation. Therefore, I believe my project, solidity-docs-l10n, should satisfy the requirement for automation.