[CentOS-devel] Opensourcing the CentOS brand creative work, licensing thoughts

Sat Aug 27 16:54:24 UTC 2022
Alain Reguera Delgado <alain.reguera at gmail.com>

Dear community,

I would like to bring up this topic once again because it is relevant
for the well-being of CentOS visual identity, and its future
improvements on the long-term. This mail is probably for Red Hat
Liaison, considering the legalities involved in relation to CentOS
branding matters. Nevertheless, I would like to keep the discussion
open to collect the vast majority of opinions possible about it.

Considering the CentOS brand is presently a registered trademark of Red
Hat, the exact questions are:

1. Related to CentOS brand changes, and design improvements: What does
Red Hat allow the CentOS community to do, and not to do? Here, please,
consider the legal and not-legal matters.

2. Would it be possible for Red Hat to explicitly set the license under
which the CentOS brand (creative/design) work is released, so to
grantee its openness inside the CentOS community? If not, please,
elaborate why, and share the expected process to follow in order to
keep the brand design relevant through time.

I deliberately have collected some thoughts[1] about the recent CentOS
brand actualization process but am not sure if they are aligned with
Red Hat needs and expectations. The goal here would be to make a very
clean and simple statement about how much autonomy does the CentOS
community have over its own brand. Also, complement the CentOS
Trademark Guidelines[2] document with such information, since there
isn't mention of it at the moment.

[1] https://gitlab.com/areguera/centos-brand
[2] https://www.centos.org/legal/trademarks/

Appreciate your comments.

Best regards.

-- 
Alain Reguera Delgado <alain.reguera at gmail.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20220827/e7b3e6fb/attachment-0002.sig>