You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by an...@apache.org on 2020/01/17 20:46:08 UTC
svn commit: r1872934 -
/infrastructure/site/trunk/content/foundation/marks/pmcs.mdtext
Author: andreww
Date: Fri Jan 17 20:46:07 2020
New Revision: 1872934
URL: http://svn.apache.org/viewvc?rev=1872934&view=rev
Log:
Many small text edits for clarity.
Modified:
infrastructure/site/trunk/content/foundation/marks/pmcs.mdtext
Modified: infrastructure/site/trunk/content/foundation/marks/pmcs.mdtext
URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/content/foundation/marks/pmcs.mdtext?rev=1872934&r1=1872933&r2=1872934&view=diff
==============================================================================
--- infrastructure/site/trunk/content/foundation/marks/pmcs.mdtext (original)
+++ infrastructure/site/trunk/content/foundation/marks/pmcs.mdtext Fri Jan 17 20:46:07 2020
@@ -16,7 +16,7 @@ Notice: Licensed to the Apache Softwa
specific language governing permissions and limitations
under the License.
-This **Apache® Project Website Branding Policy** define how Apache projects
+This **Apache® Project Website Branding Policy** defines how Apache projects
must refer to trademarks and requires a few specific elements on websites.
The [site map of trademark resources][resources] is also helpful.
@@ -24,7 +24,7 @@ The [site map of trademark resources][re
This document defines the branding and trademark policies for
how Apache® projects are required to display certain elements
-on their websites, and to treat all trademarks - Apache's and other
+on their websites, and to treat all trademarks - Apache's and those of other
organizations - appropriately. [The PMC Branding Responsibilities](responsibility.html) also explains
how PMC members must manage their project's brands in other ways.
@@ -39,21 +39,21 @@ See Also: [Trademark Resources Site Map]
- Apache projects must host official website content on an
`apache.org` domain. This includes content overseen by the
- project's PMC (including top level website, downloads, wikis, etc.),
- and ensures both that the ASF infrastructure team can maintain the
- services, as well informing any users that the content is official
- and comes from the ASF and the project's PMC, and not a third party.
+ project's PMC (including the top level website, downloads, and wikis),
+ and ensures that the ASF infrastructure team can maintain the
+ services while informing users that the content is official
+ and comes from the ASF and the project's PMC, and not from a third party.
- The homepage for any *ProjectName* must be served from
`http[s]://ProjectName.apache.org`, both to ensure consistent branding
and to allow for automatically generated links (like
[https://projects.apache.org](https://projects.apache.org)). All
primary links to the project as a whole must point directly to the
- homepage, and not to alternate sites or domains.
+ homepage, and not to alternative sites or domains.
- Projects are free to use any [infrastructure supported
- technology][1] for managing and deploying their websites, and are
- free to use any look and feel in their designs. In the future, we
+ technology][1] to manage and deploy their websites, and are
+ free to use any look and feel in its design. In the future, we
may ask projects to add a specific style or graphical element
(from a choice of several variants) for their link back to
www.apache.org that will help give users a better sense of
@@ -71,41 +71,39 @@ yet been reviewed and merged into this p
- <a id="projectname"></a>The primary branding for any project or product
name must be in the form of "Apache *Projectname*". This ensures that the project or
product is associated with the ASF as a whole in the minds of
-users, as well as to ensure third parties cannot as easily misuse our project names.
+users, and ensures that third parties cannot as easily misuse our project names.
The first and most prominent references to a project or product on
every page, and uses in page titles or headers, must use the "Apache *Projectname*" form of its name. Other references may
use either "Apache *Projectname*" or "*Projectname*" as appropriate for the subject matter.
- - <a id="markdesc"></a>Every product homepage and any overview download pages
+ - <a id="markdesc"></a>Every product homepage and any overview download page
for the product must include a prominent reference to the product as
-"Apache Foo software", and must include a brief one sentence description of the
+"Apache Foo software", and must include a brief one-sentence description of the purpose and
function of the software product itself. For example:
>The Apache Xerces XML parsing library software provides a complete
implementation of the XML 1.0 parsing specification, and is easily configurable and
compliant with current standards.
-This description is both useful for new readers to your page, and is
-important for the ASF to maintain an overall list of trademarks for our
+This description is useful for new readers to your page, and helps the ASF to maintain an overall list of trademarks for our
software products. A trademark is only important when associated with a
specific kind of goods: in our case with the actual downloadable software products
that the ASF and our PMCs provide.
-Note that it's helpful to pass the sample description by trademarks@, to
+Note that it's helpful to share the proposed sample description with trademarks@, to
ensure it's a proper trademark goods description. For
-example, in the past Apache Tomcat's website said it is an
-"implementation" and a "collaboration", not as a product with functionality. Apache SpamAssassin's website
-described itself as a "project" and a "version" and otherwise refers to the
-software as "it". Neither of these contains a proper trademark goods
-description (i.e. computer software that performs a function). While
+example, in the past Apache Tomcat's website said it was an
+"implementation" and a "collaboration", not a product with functionality. Apache SpamAssassin's website
+described itself as a "project" and a "version" and otherwise referred to the
+software as "it". Neither of these contained a proper trademark goods
+description (i.e. computer software that performs a function). While
this trademark description style may sometimes seem clumsy in technical
-documentation, it is a critical way that we can enforce our trademarks -
-plus, it only needs to be done in one prominent place on the website.
+documentation, it is a critical way that we can enforce our trademarks. It only needs to be done in one prominent place on the website for each project.
- - <a id="adjective"></a>Project and product names should always be referred to in a consistent
-casing and used as an adjective, and never as a noun or verb, like any
-trademark should be used. This is important to do on your project
+ - Always present the <a id="adjective"></a>project and product names in a consistent
+casing and as an adjective, and never as a noun or verb, which is how any
+trademark should be used. This is important to do on your project
homepage and on the download page; at other places on the website
or in technical product documentation it's not required.
@@ -117,7 +115,7 @@ Foo" should be exclusive to the ASF.
**Terminology:** a **project** or **subproject** is a community and any
associated products that are managed by a PMC; the same brand guidelines
apply to both. A **product** is a specific, downloadable software product
-that our users might want to use in some way. There are a few extra
+that our users might want to use in some way. There are a few
specific requirements for product branding. Note that *most* projects and
subprojects release a product with the same name (i.e. the Apache Foo
project releases a software product called Apache Foo).
@@ -142,20 +140,20 @@ users may securely report potential vuln
- All projects must feature some prominent link back to the main ASF
homepage at `www.apache.org`. This
-may either be a featured link in your main navigation system, or may be a
+may either be a featured link in your main navigation system or a
text link in your Main homepage text. A best practice is to include a short
sentence or paragraph on the homepage noting that this project is an Apache
project, and is part of a larger community of developers and users.
-If you have alternate suggestions for the text for links pointing back to
+If you have suggestions for the texts for links pointing back to
the main ASF pages that better fit with
your project's web presence, please let trademarks@ know.
-**Including "Thanks" links to third parties** - if your project has
-typically companies that donate software licenses or support to
+**Including "Thanks" links to third parties** - if your project
+typically has companies that donate software licenses or support to
project committers, please follow the [Corporate Recognition Guidelines][2].
It is important to ensure any such pages are presented publicly in a
-manner that is distinctly different than the formal Sponsorship program.
+manner that is distinctly different from material related to the formal Sponsorship program.
# https or http? # {#httphttps}
@@ -186,21 +184,21 @@ Software Foundation in the United States
- At the top of each project or product homepage, and on the top banner of
each page where the project name appears, you should include the appropriate ™ or ® symbol
next to the **first** main occurrence of the "Apache Foo" project name, both
-in header/title text and in the first place in running text.
+in header/title text and at the name's first appearance in running text.
This highlights our trademark claim and emphasizes its importance to us.
- <a id="othermarks"></a>Proper attribution must be given to any other
organization's trademarks that are referred to on our websites. All non-ASF
trademarks must be attributed to their owners when displayed on ASF project
-websites. This may be done specifically, for each other referred mark, or
+websites. This may be done specifically, for each referred mark, or
generically, and is typically done in the footer of a webpage. For a
specific example:
>FooBar and the FooBar logo are trademarks of Yoyodyne, Inc.
-To provide a generic trademark attribution (either to cover cases where a
+To provide a generic trademark attribution (to cover cases where a
large number of marks are used, or in case we're not sure which words are
-other organization's marks), you can add instead:
+other organizations' marks), you can add instead:
>All other marks mentioned may be trademarks or registered trademarks of
their respective owners.
@@ -214,8 +212,8 @@ graphic or immediately adjacent to it. F
logo on them, ensure you mention "... and the Project logo are
trademarks..." in the attribution.
- - Projects may may choose to use the Apache feather in their logo if they
-wish. For details on the proper [Apache visual identity and feather graphics][3],
+ - Projects may choose to use the Apache feather in their logo if they
+wish. For details on the proper [Apache visual identity and feather graphics][3],
please work with press@.
# Powered By... Logos # {#poweredby}
@@ -263,7 +261,7 @@ registering their marks, please [follow
## Project-Related Non-apache.org Domain Names # {#nonapache}
-To ensure consistent branding and assure users that content is official
+To ensure consistent branding and assure users that content is official and
from the ASF and our PMCs, all existing projects must host all content managed
by the PMC on the ProjectName.apache.org domain.
@@ -281,27 +279,27 @@ once the podling graduates to TLP.
- During Incubation, the PPMC must work with Apache Infrastructure
to formally transfer any needed domain name registrations to the ASF.
As a non-profit, the ASF expects that these will be donated.
- Creating an INFRA Jira ticket to officially request that the
+ Create an INFRA Jira ticket to officially request that the
ASF take over the donated domain name ownership.
-- The PPMC should send their plan of how they plan to use their
+- The PPMC should send their plan of how they intend to use their
non-apache.org domains to Brand Management/trademarks@ for approval.
- During Incubation, the PPMC must transition all development-oriented
information as well as the primary project homepage to the
- official ProjectName.apache.org homepage. This is required
+ official ProjectName.apache.org homepage. This is required
before a project may graduate.
**Factors to consider for use of non-apache.org domains**
-- The primary development homepage - i.e. all the common things that a
-potential contributor would need to find out about to join the project -
+- The primary development homepage, which includes all the common things that a
+potential contributor would need to find out about before deciding whether to join the project,
must be hosted at *ProjectName*.apache.org.
- Major links promoting the project to likely contributors should always
-point to *ProjectName*.apache.org resources directly, and not non-apache.org domains.
+point to *ProjectName*.apache.org resources directly, and not to non-apache.org domains.
-- In most cases, non-apache.org domains should simply redirect to someplace within
+- In most cases, non-apache.org domains should simply redirect to some place within
ProjectName.apache.org/path domain, unless the podling has *each* of these really
good reasons to use a non-apache.org domain:
@@ -320,22 +318,22 @@ etc. etc.
These are exceptions, and are not the case for the majority of new projects:
- openoffice.org is a user-facing portal with a huge history and millions of
-users on it. Continuing that as a user portal is important to serve the
+users on it. Continuing that as a user portal is important to serve the
existing non-technical users.
-- groovy-lang.org is long-running user facing portal. This domain is
+- groovy-lang.org is long-running user facing portal. This domain is
still used as an end-user portal with information about the Groovy
- language itself. Developer information (i.e. for contributors to the
+ language itself. Developer information (for contributors to the
Groovy codebase itself), discussions, and downloads are all on the
expected groovy.apache.org website.
# Project Branding Checklist # {#checklist}
All Apache top level projects should be fully compliant with these guidelines.
-Any projects which are not compliant must work with trademarks@ to ensure that they are.
-All Incubator podlings must either comply with all requirements before graduation, or must
+Any projects which are not compliant must work with trademarks@ to ensure that they become compliant.
+All Incubator podlings must either comply with all requirements before graduation, or
have a specific and short-term action plan to complete compliance in short order after
-graduation (in case there are technical issues with website updates, etc.)
+graduation (in case there are technical issues with website updates, etc.).
Contact trademarks@ directly with branding questions - there is no
longer any need to include this in your board reports.
@@ -355,15 +353,15 @@ included in footers, etc.
- [Logos and Graphics](#graphics) : include TM, use consistent product
logo on your site
-- [Project Metadata](#metadata) : DOAP file checkedin and up to date
+- [Project Metadata](#metadata) : DOAP file checked in and up to date
- [Read PMC Branding Responsibilities](responsibility.html)
# Rationale # {#rationale}
-This policy is helps to promote and improve the image of all
-projects that are part of the ASF, as well as to show that all
-Apache® projects are part of "community of
+This policy helps to promote and improve the image of all
+projects that are part of the ASF, and shows that all
+Apache® projects are part of the "community of
developers and users" that we believe is an important factor in our
success. While each of our projects manages their own affairs within the
broad guidelines of the Apache Way, a consistent public branding and web
@@ -371,22 +369,22 @@ presence that ties all of our projects t
`www.apache.org` homepage benefits all of us by ensuring that
end users and future contributors know how to find official project resources.
-Similarly, properly displaying Apache names and logos on our project pages
+Similarly, displaying Apache names and logos properly on our project pages
helps to maintain our legal rights to the trademarks they embody.
-Using the appropriate ⢠and ® symbols, and properly using trademarks to
-refer to our actual software products are key ways that we tell the
+Using the appropriate ⢠and ® symbols, and using trademarks properly to
+refer to our actual software products, are key ways that we tell the
world (and lawyers) that these trademarks are valuable to us.
**Questions?** Apache committers with questions can [contact the Trademarks Committee](//www.apache.org/foundation/marks/contact#pmc). The [formal
Trademark Policy](//www.apache.org/foundation/marks/) explains
-how other organizations should refer to Apache project trademarks and logos. A [list of ASF
+how other organizations should refer to Apache project trademarks and logos. A [list of ASF
trademarks](//www.apache.org/foundation/marks/list) and
[guidelines for reporting potential misuses of trademarks](reporting.html) are also available.
**Incubator Podlings** in the Apache
Incubator have their own [detailed Podling branding
-guidelines](//incubator.apache.org/guides/branding.html), questions go to the
-general@incubator list. Podlings must comply with all Project Branding
+guidelines](//incubator.apache.org/guides/branding.html). Direct questions about these guidelines to the
+general@incubator list. Podlings must comply with all Project Branding
Requirements *before* graduation to a top level project.
# Important Note # {#notes}
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: svn commit: r1872934 - /infrastructure/site/trunk/content/foundation/marks/pmcs.mdtext
Posted by Fantri Fitriani <fa...@gmail.com>.
Pada tanggal Sab, 18 Jan 2020 04.46, <an...@apache.org> menulis:
> Author: andreww
> Date: Fri Jan 17 20:46:07 2020
> New Revision: 1872934
>
> URL: http://svn.apache.org/viewvc?rev=1872934&view=rev
> Log:
> Many small text edits for clarity.
>
> Modified:
> infrastructure/site/trunk/content/foundation/marks/pmcs.mdtext
>
> Modified: infrastructure/site/trunk/content/foundation/marks/pmcs.mdtext
> URL:
> http://svn.apache.org/viewvc/infrastructure/site/trunk/content/foundation/marks/pmcs.mdtext?rev=1872934&r1=1872933&r2=1872934&view=diff
>
> ==============================================================================
> --- infrastructure/site/trunk/content/foundation/marks/pmcs.mdtext
> (original)
> +++ infrastructure/site/trunk/content/foundation/marks/pmcs.mdtext Fri Jan
> 17 20:46:07 2020
> @@ -16,7 +16,7 @@ Notice: Licensed to the Apache Softwa
> specific language governing permissions and limitations
> under the License.
>
> -This **Apache® Project Website Branding Policy** define how Apache
> projects
> +This **Apache® Project Website Branding Policy** defines how Apache
> projects
> must refer to trademarks and requires a few specific elements on websites.
> The [site map of trademark resources][resources] is also helpful.
>
> @@ -24,7 +24,7 @@ The [site map of trademark resources][re
>
> This document defines the branding and trademark policies for
> how Apache® projects are required to display certain elements
> -on their websites, and to treat all trademarks - Apache's and other
> +on their websites, and to treat all trademarks - Apache's and those of
> other
> organizations - appropriately. [The PMC Branding
> Responsibilities](responsibility.html) also explains
> how PMC members must manage their project's brands in other ways.
>
> @@ -39,21 +39,21 @@ See Also: [Trademark Resources Site Map]
>
> - Apache projects must host official website content on an
> `apache.org` domain. This includes content overseen by the
> - project's PMC (including top level website, downloads, wikis, etc.),
> - and ensures both that the ASF infrastructure team can maintain the
> - services, as well informing any users that the content is official
> - and comes from the ASF and the project's PMC, and not a third party.
> + project's PMC (including the top level website, downloads, and wikis),
> + and ensures that the ASF infrastructure team can maintain the
> + services while informing users that the content is official
> + and comes from the ASF and the project's PMC, and not from a third
> party.
>
> - The homepage for any *ProjectName* must be served from
> `http[s]://ProjectName.apache.org`, both to ensure consistent
> branding
> and to allow for automatically generated links (like
> [https://projects.apache.org](https://projects.apache.org)). All
> primary links to the project as a whole must point directly to the
> - homepage, and not to alternate sites or domains.
> + homepage, and not to alternative sites or domains.
>
> - Projects are free to use any [infrastructure supported
> - technology][1] for managing and deploying their websites, and are
> - free to use any look and feel in their designs. In the future, we
> + technology][1] to manage and deploy their websites, and are
> + free to use any look and feel in its design. In the future, we
> may ask projects to add a specific style or graphical element
> (from a choice of several variants) for their link back to
> www.apache.org that will help give users a better sense of
> @@ -71,41 +71,39 @@ yet been reviewed and merged into this p
> - <a id="projectname"></a>The primary branding for any project or
> product
> name must be in the form of "Apache *Projectname*". This ensures that the
> project or
> product is associated with the ASF as a whole in the minds of
> -users, as well as to ensure third parties cannot as easily misuse our
> project names.
> +users, and ensures that third parties cannot as easily misuse our project
> names.
> The first and most prominent references to a project or product on
> every page, and uses in page titles or headers, must use the "Apache
> *Projectname*" form of its name. Other references may
> use either "Apache *Projectname*" or "*Projectname*" as appropriate for
> the subject matter.
>
> - - <a id="markdesc"></a>Every product homepage and any overview download
> pages
> + - <a id="markdesc"></a>Every product homepage and any overview download
> page
> for the product must include a prominent reference to the product as
> -"Apache Foo software", and must include a brief one sentence description
> of the
> +"Apache Foo software", and must include a brief one-sentence description
> of the purpose and
> function of the software product itself. For example:
>
> >The Apache Xerces XML parsing library software provides a complete
> implementation of the XML 1.0 parsing specification, and is easily
> configurable and
> compliant with current standards.
>
> -This description is both useful for new readers to your page, and is
> -important for the ASF to maintain an overall list of trademarks for our
> +This description is useful for new readers to your page, and helps the
> ASF to maintain an overall list of trademarks for our
> software products. A trademark is only important when associated with a
> specific kind of goods: in our case with the actual downloadable software
> products
> that the ASF and our PMCs provide.
>
> -Note that it's helpful to pass the sample description by trademarks@, to
> +Note that it's helpful to share the proposed sample description with
> trademarks@, to
> ensure it's a proper trademark goods description. For
> -example, in the past Apache Tomcat's website said it is an
> -"implementation" and a "collaboration", not as a product with
> functionality. Apache SpamAssassin's website
> -described itself as a "project" and a "version" and otherwise refers to
> the
> -software as "it". Neither of these contains a proper trademark goods
> -description (i.e. computer software that performs a function). While
> +example, in the past Apache Tomcat's website said it was an
> +"implementation" and a "collaboration", not a product with functionality.
> Apache SpamAssassin's website
> +described itself as a "project" and a "version" and otherwise referred to
> the
> +software as "it". Neither of these contained a proper trademark goods
> +description (i.e. computer software that performs a function). While
> this trademark description style may sometimes seem clumsy in technical
> -documentation, it is a critical way that we can enforce our trademarks -
> -plus, it only needs to be done in one prominent place on the website.
> +documentation, it is a critical way that we can enforce our trademarks.
> It only needs to be done in one prominent place on the website for each
> project.
>
>
> - - <a id="adjective"></a>Project and product names should always be
> referred to in a consistent
> -casing and used as an adjective, and never as a noun or verb, like any
> -trademark should be used. This is important to do on your project
> + - Always present the <a id="adjective"></a>project and product names in
> a consistent
> +casing and as an adjective, and never as a noun or verb, which is how any
> +trademark should be used. This is important to do on your project
> homepage and on the download page; at other places on the website
> or in technical product documentation it's not required.
>
> @@ -117,7 +115,7 @@ Foo" should be exclusive to the ASF.
> **Terminology:** a **project** or **subproject** is a community and any
> associated products that are managed by a PMC; the same brand guidelines
> apply to both. A **product** is a specific, downloadable software product
> -that our users might want to use in some way. There are a few extra
> +that our users might want to use in some way. There are a few
> specific requirements for product branding. Note that *most* projects and
> subprojects release a product with the same name (i.e. the Apache Foo
> project releases a software product called Apache Foo).
> @@ -142,20 +140,20 @@ users may securely report potential vuln
>
> - All projects must feature some prominent link back to the main ASF
> homepage at `www.apache.org`. This
> -may either be a featured link in your main navigation system, or may be a
> +may either be a featured link in your main navigation system or a
> text link in your Main homepage text. A best practice is to include a
> short
> sentence or paragraph on the homepage noting that this project is an
> Apache
> project, and is part of a larger community of developers and users.
>
> -If you have alternate suggestions for the text for links pointing back to
> +If you have suggestions for the texts for links pointing back to
> the main ASF pages that better fit with
> your project's web presence, please let trademarks@ know.
>
> -**Including "Thanks" links to third parties** - if your project has
> -typically companies that donate software licenses or support to
> +**Including "Thanks" links to third parties** - if your project
> +typically has companies that donate software licenses or support to
> project committers, please follow the [Corporate Recognition
> Guidelines][2].
> It is important to ensure any such pages are presented publicly in a
> -manner that is distinctly different than the formal Sponsorship program.
> +manner that is distinctly different from material related to the formal
> Sponsorship program.
>
>
> # https or http? # {#httphttps}
> @@ -186,21 +184,21 @@ Software Foundation in the United States
> - At the top of each project or product homepage, and on the top banner
> of
> each page where the project name appears, you should include the
> appropriate ™ or ® symbol
> next to the **first** main occurrence of the "Apache Foo" project name,
> both
> -in header/title text and in the first place in running text.
> +in header/title text and at the name's first appearance in running text.
> This highlights our trademark claim and emphasizes its importance to us.
>
> - <a id="othermarks"></a>Proper attribution must be given to any other
> organization's trademarks that are referred to on our websites. All
> non-ASF
> trademarks must be attributed to their owners when displayed on ASF
> project
> -websites. This may be done specifically, for each other referred mark, or
> +websites. This may be done specifically, for each referred mark, or
> generically, and is typically done in the footer of a webpage. For a
> specific example:
>
> >FooBar and the FooBar logo are trademarks of Yoyodyne, Inc.
>
> -To provide a generic trademark attribution (either to cover cases where a
> +To provide a generic trademark attribution (to cover cases where a
> large number of marks are used, or in case we're not sure which words are
> -other organization's marks), you can add instead:
> +other organizations' marks), you can add instead:
>
> >All other marks mentioned may be trademarks or registered trademarks of
> their respective owners.
> @@ -214,8 +212,8 @@ graphic or immediately adjacent to it. F
> logo on them, ensure you mention "... and the Project logo are
> trademarks..." in the attribution.
>
> - - Projects may may choose to use the Apache feather in their logo if
> they
> -wish. For details on the proper [Apache visual identity and feather
> graphics][3],
> + - Projects may choose to use the Apache feather in their logo if they
> +wish. For details on the proper [Apache visual identity and feather
> graphics][3],
> please work with press@.
>
> # Powered By... Logos # {#poweredby}
> @@ -263,7 +261,7 @@ registering their marks, please [follow
>
> ## Project-Related Non-apache.org Domain Names # {#nonapache}
>
> -To ensure consistent branding and assure users that content is official
> +To ensure consistent branding and assure users that content is official
> and
> from the ASF and our PMCs, all existing projects must host all content
> managed
> by the PMC on the ProjectName.apache.org domain.
>
> @@ -281,27 +279,27 @@ once the podling graduates to TLP.
> - During Incubation, the PPMC must work with Apache Infrastructure
> to formally transfer any needed domain name registrations to the ASF.
> As a non-profit, the ASF expects that these will be donated.
> - Creating an INFRA Jira ticket to officially request that the
> + Create an INFRA Jira ticket to officially request that the
> ASF take over the donated domain name ownership.
>
> -- The PPMC should send their plan of how they plan to use their
> +- The PPMC should send their plan of how they intend to use their
> non-apache.org domains to Brand Management/trademarks@ for approval.
>
> - During Incubation, the PPMC must transition all development-oriented
> information as well as the primary project homepage to the
> - official ProjectName.apache.org homepage. This is required
> + official ProjectName.apache.org homepage. This is required
> before a project may graduate.
>
> **Factors to consider for use of non-apache.org domains**
>
> -- The primary development homepage - i.e. all the common things that a
> -potential contributor would need to find out about to join the project -
> +- The primary development homepage, which includes all the common things
> that a
> +potential contributor would need to find out about before deciding
> whether to join the project,
> must be hosted at *ProjectName*.apache.org.
>
> - Major links promoting the project to likely contributors should always
> -point to *ProjectName*.apache.org resources directly, and not
> non-apache.org domains.
> +point to *ProjectName*.apache.org resources directly, and not to
> non-apache.org domains.
>
> -- In most cases, non-apache.org domains should simply redirect to
> someplace within
> +- In most cases, non-apache.org domains should simply redirect to some
> place within
> ProjectName.apache.org/path domain, unless the podling has *each* of
> these really
> good reasons to use a non-apache.org domain:
>
> @@ -320,22 +318,22 @@ etc. etc.
> These are exceptions, and are not the case for the majority of new
> projects:
>
> - openoffice.org is a user-facing portal with a huge history and
> millions of
> -users on it. Continuing that as a user portal is important to serve the
> +users on it. Continuing that as a user portal is important to serve the
> existing non-technical users.
>
> -- groovy-lang.org is long-running user facing portal. This domain is
> +- groovy-lang.org is long-running user facing portal. This domain is
> still used as an end-user portal with information about the Groovy
> - language itself. Developer information (i.e. for contributors to the
> + language itself. Developer information (for contributors to the
> Groovy codebase itself), discussions, and downloads are all on the
> expected groovy.apache.org website.
>
> # Project Branding Checklist # {#checklist}
>
> All Apache top level projects should be fully compliant with these
> guidelines.
> -Any projects which are not compliant must work with trademarks@ to
> ensure that they are.
> -All Incubator podlings must either comply with all requirements before
> graduation, or must
> +Any projects which are not compliant must work with trademarks@ to
> ensure that they become compliant.
> +All Incubator podlings must either comply with all requirements before
> graduation, or
> have a specific and short-term action plan to complete compliance in
> short order after
> -graduation (in case there are technical issues with website updates, etc.)
> +graduation (in case there are technical issues with website updates,
> etc.).
>
> Contact trademarks@ directly with branding questions - there is no
> longer any need to include this in your board reports.
> @@ -355,15 +353,15 @@ included in footers, etc.
> - [Logos and Graphics](#graphics) : include TM, use consistent product
> logo on your site
>
> -- [Project Metadata](#metadata) : DOAP file checkedin and up to date
> +- [Project Metadata](#metadata) : DOAP file checked in and up to date
>
> - [Read PMC Branding Responsibilities](responsibility.html)
>
> # Rationale # {#rationale}
>
> -This policy is helps to promote and improve the image of all
> -projects that are part of the ASF, as well as to show that all
> -Apache® projects are part of "community of
> +This policy helps to promote and improve the image of all
> +projects that are part of the ASF, and shows that all
> +Apache® projects are part of the "community of
> developers and users" that we believe is an important factor in our
> success. While each of our projects manages their own affairs within the
> broad guidelines of the Apache Way, a consistent public branding and web
> @@ -371,22 +369,22 @@ presence that ties all of our projects t
> `www.apache.org` homepage benefits all of us by ensuring that
> end users and future contributors know how to find official project
> resources.
>
> -Similarly, properly displaying Apache names and logos on our project
> pages
> +Similarly, displaying Apache names and logos properly on our project
> pages
> helps to maintain our legal rights to the trademarks they embody.
> -Using the appropriate ™ and ® symbols, and properly using trademarks
> to
> -refer to our actual software products are key ways that we tell the
> +Using the appropriate ™ and ® symbols, and using trademarks properly
> to
> +refer to our actual software products, are key ways that we tell the
> world (and lawyers) that these trademarks are valuable to us.
>
> **Questions?** Apache committers with questions can [contact the
> Trademarks Committee](//www.apache.org/foundation/marks/contact#pmc). The
> [formal
> Trademark Policy](//www.apache.org/foundation/marks/) explains
> -how other organizations should refer to Apache project trademarks and
> logos. A [list of ASF
> +how other organizations should refer to Apache project trademarks and
> logos. A [list of ASF
> trademarks](//www.apache.org/foundation/marks/list) and
> [guidelines for reporting potential misuses of
> trademarks](reporting.html) are also available.
>
> **Incubator Podlings** in the Apache
> Incubator have their own [detailed Podling branding
> -guidelines](//incubator.apache.org/guides/branding.html), questions go
> to the
> -general@incubator list. Podlings must comply with all Project Branding
> +guidelines](//incubator.apache.org/guides/branding.html). Direct
> questions about these guidelines to the
> +general@incubator list. Podlings must comply with all Project Branding
> Requirements *before* graduation to a top level project.
>
> # Important Note # {#notes}
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>
>