Add a branding checklist to the handbook
Submitted by Wayne Beaton @wbeaton
Link to original bug (#505741)
Description
e.g.
- Project web site must be hosted at eclipse.org
- First reference to project name needs to be Eclipse
<project name> - Project web site needs to include the standard Eclipse footer
Blocking
Activity
@wbeatonsaid:Is this just part of the release review checklist? I'm making this a blocker bug 485704 while we consider it.
Making multiple checklists spread throughout the document strikes me as a bit of a fail.
@mmilinkovichsaid:(In reply to Wayne Beaton from comment 0)
e.g.
- Project web site must be hosted at eclipse.org
- First reference to project name needs to be Eclipse
<project name> - Project web site needs to include the standard Eclipse footer
I just noticed this sentence in the handbook: " If the webpage features an otherwise prominent reference to the project or product (e.g. in a callout), that reference should also use the formal name."
Is there a reason we went with "should" instead of "must"?
@wbeatonsaid:Include a link to the artwork page [1]
@wbeatonsaid:Project logos must include a trademark mark ("tm").
Project logos do not necessarily need to include "Eclipse".
Project logos that incorporate the Eclipse Logo or are otherwise a derivative of the Eclipse Logo require board approval. Send a note to license@eclipse.org or create a bug under Community/EMO Approvals.
PMI Page title must include "Eclipse" in project, and first occurrence in description, scope, and other page leading text.
Link to official project website must point to www.eclipse.org/
<project>(not offsite).Community page links are permissible, but must open a new browser tab/page.
@wbeatonsaid:What about copyright statements on websites?
By default, all pages state the copyright is owned by the EF with all rights reserved. This is true even for content generated by the project team members.
Certainly, the trademark cannot be held by the project itself as it is not a legal entity.
In general, though, this is content that has not been authored or contributed by the EF. Should the copyright statement on websites be along the lines of "(c) Copyright Random Company and others.
<project>is a trademark of the Eclipse Foundation."Should we not put an explicit license on webpage content?
@wbeatonsaid:I've created a new section for the handbook that rolls some of the existing "release" guidelines in with branding guidelines.
http://git.eclipse.org/c/dash/org.eclipse.dash.handbook.git/tree/source/chapters/checklist.adoc
I'll take another pass over it tomorrow and push it out.
@geniesaid:This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.
If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
-- The automated Eclipse Genie.
@geniesaid:This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.
If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
-- The automated Eclipse Genie.
