This is in the context of this proposed Fedora 39 Change: https://fedoraproject.org/wiki/Changes/ToolbxReleaseBlocker
We want to ensure that there are up to date fedora-toolbox OCI images published on registry.fedoraproject.org as release-blocking deliverables at critical points in the development schedule, just like the installation ISOs for the Editions from download.fedoraproject.org.
The Changes policy says:
If your Change may require trademark approval (for example, if it is a new Spin), file a ticket requesting trademark approval from the Fedora Council.
This isn't a new Spin, but still a new release-blocking deliverable. So, I wanted to be sure, just in case.
Do you think the fedora-toolbox images should have a separate VARIANT_ID in os-release(5)?
fedora-toolbox
VARIANT_ID
I've created a topic on Fedora Discussion for this ticket.
Please keep this ticket focused. Discuss there, and record votes and decisions here. Thanks!
Metadata Update from @jflory7: - Issue tagged with: trademarks
+1
+1 to having this as release-blocking.
+100 to separate variant_id. :)
variant_id
This use of the Fedora trademark is approved.
Also, please do use a new variant_id. That doesn't need Council approval, and should be standard practice for any new spin or variant.
What's the next step to using a new VARIANT_ID? Should I go ahead and start filing pull requests to the appropriate RPM packages and such?
Discussed in 2023-06-07 Council meeting.
The Fedora Council agreed (+3/0/-0) that this trademark use request for fedora-toolbox and the additional request of a new VARIANT_ID is approved. @rishi is authorized to go forward with necessary changes.
We also noted that while the trademark request is a matter of Council business, the VARIANT_ID falls more to the purview and authority of FESCo. FESCo should be consulted for guidance on the best implementation approach for the new VARIANT_ID.
I am closing this trademark ticket as approved.
approved
@rishi wrote… What's the next step to using a new VARIANT_ID? Should I go ahead and start filing pull requests to the appropriate RPM packages and such?
This is where I would consult FESCo for advice. I think some Council members may have opinions on this, but the majority of the Council is not the right body of expertise to guide you on this technical implementation aspect.
Metadata Update from @jflory7: - Issue close_status updated to: approved - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.