Codeberg/Design
Archived
23
51
Fork
You've already forked Design
4

settle on a logo license #16

Closed
opened 2020年07月30日 15:57:10 +02:00 by mray · 19 comments
Collaborator
Copy link

As noted by @lhinderberger #3 (comment) there are a couple of questions that need to be resolved before deciding on a license for the logo.

In my opinion it should meet the requirements of being practical for the community to make use of it, compatible with all sorts of uses in software and on project websites, but also make sure we remain in control in case of a dispute.

Mixing licenses and adding an exception to how they apply seems to work for other projects, but what licenses are those and what exceptions would we need?

As noted by @lhinderberger https://codeberg.org/Codeberg/Design/issues/3#issuecomment-72364 there are a couple of questions that need to be resolved before deciding on a license for the logo. In my opinion it should meet the requirements of being practical for the community to make use of it, compatible with all sorts of uses in software and on project websites, but also make sure we remain in control in case of a dispute. Mixing licenses and adding an exception to how they apply seems to work for other projects, but what licenses are those and what exceptions would we need?
Collaborator
Copy link

A quick sum-up of the positions in #3

  • An early idea was to put the logo under a permissive license, such as CC0 or CC-BY
  • So far, the idea of using a permissive license seemed to resonate well with the posters in #3, especially since it allows for easy wide-spread usage for example on t-shirts and slides
  • There are mixed opinions about whether an attribution requirement would be necessary or superfluous.
  • The Creative Commons FAQ takes a critical stance towards putting logos and trademarks under either license: https://creativecommons.org/faq/#could-i-use-a-cc-license-to-share-my-logo-or-trademark
  • Another question is, whether we already have a trademark on Codeberg automatically, like with copyright or whether that would mean additional costs and effort to register and uphold a trademark
A quick sum-up of the positions in #3 - An early idea was to put the logo under a permissive license, such as CC0 or CC-BY - So far, the idea of using a permissive license seemed to resonate well with the posters in #3, especially since it allows for easy wide-spread usage for example on t-shirts and slides - There are mixed opinions about whether an attribution requirement would be necessary or superfluous. - The Creative Commons FAQ takes a critical stance towards putting logos and trademarks under either license: https://creativecommons.org/faq/#could-i-use-a-cc-license-to-share-my-logo-or-trademark - Another question is, whether we already have a trademark on Codeberg automatically, like with copyright or whether that would mean additional costs and effort to register and uphold a trademark
Collaborator
Copy link

A possible compromise could be to prefer using an open license over potential trademark protection loss and to use a license with attribution requirement to at least retain some control.

A possible compromise could be to prefer using an open license over potential trademark protection loss and to use a license with attribution requirement to at least retain some control.
Collaborator
Copy link

Disclaimer: I am not a lawyer

  • Debian has a free-to-use version of its logo, dual-licensed under LGPLv3 or later and CC-BY-SA 3.0 Unported (https://www.debian.org/logos/) and they refer to their logo as an Open-source brand
  • Apache focuses on trademark law to protect their names and logos: https://www.apache.org/foundation/marks/resources
  • The page above also contains an extensive list of general FOSS-trademark related resources
  • Wikimedia uses CC-BY-SA 3.0 for their Wikipedia logo, with an additional trademark policy.

Maybe that might be the way to go for us too - use a CC license for the copyright aspect of the logo but always together with a notice that refers to (yet-to-be-written) trademark usage guidelines. Model guidelines would be available under http://modeltrademarkguidelines.org

Disclaimer: [I am not a lawyer](https://en.wikipedia.org/wiki/IANAL) - Debian has a free-to-use version of its logo, dual-licensed under LGPLv3 or later and CC-BY-SA 3.0 Unported (https://www.debian.org/logos/) and they refer to their logo as an [Open-source brand](https://en.wikipedia.org/wiki/Open-source_brand) - Apache focuses on trademark law to protect their names and logos: https://www.apache.org/foundation/marks/resources - The page above also contains an extensive list of general FOSS-trademark related resources - Wikimedia uses CC-BY-SA 3.0 for their Wikipedia logo, with an additional trademark policy. Maybe that might be the way to go for us too - use a CC license for the copyright aspect of the logo but always together with a notice that refers to (yet-to-be-written) trademark usage guidelines. Model guidelines would be available under http://modeltrademarkguidelines.org
Author
Collaborator
Copy link

I like all the information you're pulling together here! I'm glad we are not coming to conclusions too hasty.

Something that just crossed my mind and might be relevant too is the fact that Codeberg isn't a product, but a service (different to gitea), making some comparison more or less approriate.

I like all the information you're pulling together here! I'm glad we are not coming to conclusions too hasty. Something that just crossed my mind and might be relevant too is the fact that Codeberg isn't a product, but a service (different to gitea), making some comparison more or less approriate.
Collaborator
Copy link

I like all the information you're pulling together here!

Thanks, I'm glad you like it :)

Something that just crossed my mind and might be relevant too is the fact that Codeberg isn't a product, but a service (different to gitea), making some comparison more or less approriate.

True, it's mainly a service (and mainly mainly a non-profit organization 😄).
There are some components that are more product-like (software developed by Codeberg for example, and in the future it might be things like Codeberg CI or Codeberg Packages, which probably will be both product and service), so in the end we have to take everything into account.

> I like all the information you're pulling together here! Thanks, I'm glad you like it :) > Something that just crossed my mind and might be relevant too is the fact that Codeberg isn't a product, but a service (different to gitea), making some comparison more or less approriate. True, it's mainly a service (and mainly mainly a non-profit organization :smile:). There are some components that are more product-like (software developed by Codeberg for example, and in the future it might be things like Codeberg CI or Codeberg Packages, which probably will be both product and service), so in the end we have to take everything into account.
Collaborator
Copy link

What would we need to get this issue resolved quickly?

What would we need to get this issue resolved quickly?

There is a guide on trademarks for free software projects at https://softwarefreedom.org/resources/2008/foss-primer.html#x1-600005

(I was an employee at SFLC when my colleagues put together that resource, but I am not myself a lawyer.)

The plan above sounds like a reasonable starting point.

There is a guide on trademarks for free software projects at https://softwarefreedom.org/resources/2008/foss-primer.html#x1-600005 (I was an employee at SFLC when my colleagues put together that resource, but I am not myself a lawyer.) The plan [above](https://codeberg.org/Codeberg/Design/issues/16#issuecomment-73320) sounds like a reasonable starting point.
Author
Collaborator
Copy link

I guess an intersting question is how trademark applies to us, where it applies and what we have to register it.

If we quickly want to move forward we don't have to decide on this very fast. Just going with a simple and save decision will work for now. Early requests (if any arise) to use the logo can even be handled privately.

I guess an intersting question is how trademark applies to us, where it applies and what we have to register it. If we quickly want to move forward we don't have to decide on this very fast. Just going with a simple and save decision will work for now. Early requests (if any arise) to use the logo can even be handled privately.
Collaborator
Copy link

Can CC-BY 4.0 with a notice like "Codeberg and the Codeberg Logo are trademarks of Codeberg e.V." be considered a simple and safe option?

That way, we wouldn't need to write trademark guidelines right away. Where trademark-related questions arise, people could then be encouraged to just ask for now :)

Can CC-BY 4.0 with a notice like "Codeberg and the Codeberg Logo are trademarks of Codeberg e.V." be considered a simple and safe option? That way, we wouldn't need to write trademark guidelines right away. Where trademark-related questions arise, people could then be encouraged to just ask for now :)
Author
Collaborator
Copy link

CC-BY 4.0 with a notice like "Codeberg and the Codeberg Logo are trademarks of Codeberg e.V."

If that's ok, then I'll embed this in the logo metadata, too and start working on a downloadable logo-kit.

> CC-BY 4.0 with a notice like "Codeberg and the Codeberg Logo are trademarks of Codeberg e.V." If that's ok, then I'll embed this in the logo metadata, too and start working on a downloadable logo-kit.
Collaborator
Copy link

@hw Are there objections from your side? :)

@hw Are there objections from your side? :)
Member
Copy link

not at all!

not at all!
Collaborator
Copy link

Well that's great :)

@mray - may I already use your logo as published in build-deploy-gitea under CC-BY 4.0 so that I can finish the documentation site?

Well that's great :) @mray - may I already use your logo as published in `build-deploy-gitea` under CC-BY 4.0 so that I can finish the documentation site?
Author
Collaborator
Copy link

@mray - may I already use your logo...

sure, we should try to make a switch as coherent as possible, though. Confusion is the last thing we want to associate with the logo :)

Is your site ready now?

> @mray - may I already use your logo... sure, we should try to make a switch as coherent as possible, though. Confusion is the last thing we want to associate with the logo :) Is your site ready now?
Author
Collaborator
Copy link

so it is:

CC-BY 4.0 international

&

"Codeberg and the Codeberg Logo are trademarks of Codeberg e.V."

so it is: CC-BY 4.0 international & "Codeberg and the Codeberg Logo are trademarks of Codeberg e.V."
Collaborator
Copy link

Is your site ready now?

Yes, I'm replacing the filler content with the actual content now as I prepare the pull request :)

> Is your site ready now? Yes, I'm replacing the filler content with the actual content now as I prepare the pull request :)
Member
Copy link

ping us when time has come for initial deployment to https://codeberg-test.org

ping us when time has come for initial deployment to https://codeberg-test.org
Collaborator
Copy link
https://codeberg.org/Codeberg/Documentation/pulls/20 is now available and can be tested under https://cb-docs-prototype.lhinderberger.com
Member
Copy link

cool! give us a few days now

cool! give us a few days now
Commenting is not possible because the repository is archived.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
Kind: Breaking
Kind: Bug
Kind: Documentation
Kind: Enhancement
Kind: Feature
Kind: Maintenance
Kind: Public Relations

Design relevant outside of Codeberg
Kind: Question
Kind: Security
Kind: Testing
Kind: Web Design
Part: Color Palette
Part: Design Kit

Codeberg Design Kit
Part: Fonts
Part: Logo
Part: Navbar

Codeberg's navigation bar
Part: Themes

Gitea themes
Priority: Critical

The priority is critical
Priority: High

The priority is high
Priority: Low

The priority is low
Priority: Medium

The priority is medium
Reviewed: Confirmed

Something has been confirmed
Reviewed: Duplicate

Something exists already
Reviewed: Invalid

Something was marked as invalid
Reviewed: Wontfix

Something won't be fixed
Status: Blocked
Status: Completed

Work is complete
Status: Help wanted
Status: In progress

Work is in progress
Status: Needs feedback

Feedback is needed
Status: Stale
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Design#16
Reference in a new issue
Codeberg/Design
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?