OAI / OAI/Overlay-Specification

Proposal: Add a canonical icon for OpenAPI Overlay

Open
#358 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
121
Forks
38
Avg merge
53m
Merged PRs (30d)
6

Description

I would like to donate the attached icon for the OpenAPI Overlay Specification, with the goal of giving OpenAPI Overlay a canonical visual identity.

The asset is an SVG, so it should be possible to extract just the icon and omit the Overlay text if maintainers prefer an icon-only version.

OpenAPI Overlay icon proposal

My intent is to contribute this as an OpenAPI Overlay icon. If accepted, I am happy for the asset to be copied into this repository and maintained by the OpenAPI Initiative as the canonical icon for Overlay.

Provenance disclosure:

The icon was produced using an image-generation-capable model. The prompt was to create an OpenAPI Overlay icon, and the Overlay Specification was attached as context. I do not have the original prompt text, seed, model metadata, or generation history available.

I have used this icon in a number of my open-source projects to graphically represent overlays.

To the best of my knowledge, I am not aware of any third-party logo, trademark, or copyrighted work that this icon intentionally copies or derives from.

Rights / licensing:

I am willing to contribute whatever rights I have in the asset under the repository’s existing license terms, or under another license or contribution process preferred by the OpenAPI Initiative or Linux Foundation. If a CLA, DCO sign-off, trademark review, or additional written statement is required, I am happy to provide it.

Suggested next steps:

  • Maintainers review whether the icon is appropriate as a canonical OpenAPI Overlay mark.
  • Maintainers advise whether the missing AI-generation provenance is acceptable.
  • If acceptable, I can open a pull request adding the SVG asset and any README/documentation references requested.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with issue #358 and review the attached SVG proposal, including the option to use an icon-only version. Check the stated provenance, licensing, CLA/DCO, and trademark considerations with maintainers. Done means maintainers accept the mark and its provenance and specify the requested asset and documentation changes for a pull request.

Written by the indexing model from the issue text.

Assessment

Domain
design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.