Using CP icons

I know you are busy Michelle so I’ll have a try at this.

6 Likes

I appreciate it very much, thank you!

2 Likes

Note about ForkAwesome:
there are two icons: fa-classicpress and fa-classicpress-circle.
image

5 Likes

One thing I am seeing with a few projects similar to CP is the need to request permission before any usage of the logo… ie it must be approved before it can be used.

Do we want to go down this path, or is that too onerous?

1 Like

You might have some always approved usages, so that you’re not buried in requests for every little thing. But then add the caviat that if people want to use it in another way they need to ask permission so you can look at edge cases and not outright ban everything you can’t put into words. The question then is, who gets to decide? Company Directers? Community lead? Marketing lead? Any committee member?

3 Likes

I think this can be handled by few internal rules, like:

  • If the request is some sort of trouble the committee would be involved
  • If the request is similar to another approved one any committee member can approve

Just as an example.

I’m with you with this. It’s time to spread…

2 Likes

Just for clarification. That first one refers to the entire committee being involved?

Yes, I was thinking at something like “I’ll give you one billion dollars to sell t-shirt with your logo” :wink:

2 Likes

Extreme exmple, but I get your point.

1 Like

Suggestions? Nothing clear-cut comes immediately to mind.

1 Like

The current guidelines have some approved cases right?

Just some ideas…

  • Articles, videos, and podcasts that portray ClassicPress in a positive or neutral way. (from here)
  • In your advertising material, where stating that your plugin/theme is compatible with CP
  • In your advertising material, where stating that your web agency can use CP to build sites
  • In your advertising material, where stating that your hosting service supports CP
  • In a website (see logo usage guidelines to see if the site is allowed to), stating that is built with CP

In any case:

  • You must follow logo usage guidelines
  • CP logo must not be prominent
  • The logo must be used in a way that doesn’t suggest ClassicPress endorsement or affiliation

Possibly in a better english than mine :man_facepalming:

3 Likes

Yes, but only editorial usage.

1 Like

I hadn’t even seen this one.

Third-Party Usage Permissions
ClassicPress welcomes articles, videos, and podcasts that portray ClassicPress in a positive or neutral way. ClassicPress permits the use of our logo solely for editorial or information purposes. By using our logo, you agree to adhere to our brand guidelines.
No ClassicPress logo may be used or diplayed in any manner that discredits ClassicPress or tarnishes its reputation and goodwill; in any manner that infringes, dilutes, depreciates the value, or impairs the rights of ClassicPress, in any manner that is false or misleading; in connection with any pornography, illegal activities, or other materials that are defamatory, libelous, obscene, or otherwise objectionable; in any manner that violates the trademarks, copyright, or any other intellectual property rights of others; or in any manner that violates any law, regulations, or other public policy.
If you have any questions, or have a specific need, please contact the ClassicPress Design Team Lead.

3 Likes

Partly off-topic, tagging @BlueSkyPhoenix here!

A grayscale version of the logo may be used only when other variants are not appropriate. ClassicPress text should be at 65%. The gradient for the feather uses the same angle and locations; the darkest shade should be at 80% and the lightest shade should be at 50%, with a midpoint of 65%.

Can be changed with:
A plain version of the feather logo or feather coin may be used only when other variants are not appropriate.

This for allowing the use of fork-awesome’s icons.

4 Likes

I would go with a plain or grayscale, as they are appropriate for different circumstances

This is a variation of the WP guidelines, which I think are probably the most suitable. Note they still say you require permission, but they do give a fairly clear idea of the sort of situations that will be given approval. I’m still not sure how to fit the fork awesome logos in here as this information covers more general usage. Maybe that would come under the Logo Usage Guidelines (which is a separate document) and talks about things like not modifying the colours and keeping white space, and so on. We could have a clause in there like: A plain version of the feather logo or feather coin may be used only when other variants are not appropriate.

Trademark Policy

ClassicPress is registered as a Limited by Guarantee company based in the United Kingdom (Registration #11549088). ClassicPress retains the copyright for all brand assets and collateral created for ClassicPress, and owns and oversees the trademarks for the ClassicPress name and logos. This trademark usage policy has been developed with the following three goals in mind:

  1. To make it easy for anyone to use the ClassicPress name or logo for community-oriented efforts that will help promote and improve ClassicPress.

  2. To make it clear how ClassicPress-related businesses and projects can (and cannot) use the ClassicPress name and logo.

  3. To make it hard for anyone to use the ClassicPress name and logo to unfairly profit from, trick or confuse people who are looking for official ClassicPress resources.

ClassicPress Trademark Usage Policy

Permission from ClassicPress is required to use the ClassicPress name or logo as part of any project, product, service, domain name, or company name.

We will grant permission to use the ClassicPress name and logo for projects that meet the following criteria:

  1. The primary purpose of your project is to promote the spread and improvement of the ClassicPress software.

  2. Your project is non-commercial in nature (it can make money to cover its costs or contribute to non-profit entities, but it cannot be run as a for-profit project or business).

  3. Your project neither promotes nor is associated with entities that currently fail to comply with the GPL license under which ClassicPress is distributed.

If your project meets these criteria, you will be permitted to use the ClassicPress name and logo to promote your project in any way you see fit with one exception: Please do not use ClassicPress as part of a domain name.

All other ClassicPress-related businesses or projects can use the ClassicPress name and logo to refer to and explain their services, but they cannot use them as part of a product, project, service, domain name, or company name and they cannot use them in any way that suggests an affiliation with or endorsement by ClassicPress or the ClassicPress open source project.

For example, a consulting company can describe its business as “123 Web Services, offering ClassicPress consulting for small businesses,” but cannot call its business “The ClassicPress Consulting Company.” Similarly, a business related to ClassicPress themes can describe itself as “XYZ Themes, the world’s best ClassicPress themes,” but cannot call itself “The ClassicPress Theme Portal.”

Similarly, it’s OK to use the ClassicPress logo as part of a page that describes your products or services, but it is not OK to use it as part of your company or product logo or branding itself. Under no circumstances is it permitted to use ClassicPress as part of a domain name or top-level domain name.

If you are using the ClassicPress logo please observe the Logo Usage Guidelines [link].

We do not allow the use of the trademark in advertising, including AdSense/AdWords.

Please note that it is not the goal of this policy to limit commercial activity around ClassicPress. We encourage ClassicPress-based businesses.

The abbreviation “CP” is not covered by the ClassicPress trademarks and you are free to use it in any way you see fit.

When in doubt about your use of the ClassicPress name or logo, please contact xxxxx for clarification.

1 Like

I thought everyone around the world had agreed that plain means without sprinkles. :cupcake: I like grayscale, though. :slight_smile:

4 Likes

I like this policy so far – it needs some tweaking because we don’t hold the trademark, but it’s good otherwise. I agree that a brand guidelines doc would be the right place to give examples of do’s and don’ts and handle things like the ForkAwesome guidelines.

4 Likes

Tweak away! :smiley:

(I wasn’t really sure of all the legal details)

4 Likes