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 2021/04/28 12:15:39 UTC
svn commit: r1889263 -
/infrastructure/site/trunk/content/foundation/marks/faq/index.mdtext
Author: andreww
Date: Wed Apr 28 12:15:39 2021
New Revision: 1889263
URL: http://svn.apache.org/viewvc?rev=1889263&view=rev
Log:
minor text edits
Modified:
infrastructure/site/trunk/content/foundation/marks/faq/index.mdtext
Modified: infrastructure/site/trunk/content/foundation/marks/faq/index.mdtext
URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/content/foundation/marks/faq/index.mdtext?rev=1889263&r1=1889262&r2=1889263&view=diff
==============================================================================
--- infrastructure/site/trunk/content/foundation/marks/faq/index.mdtext (original)
+++ infrastructure/site/trunk/content/foundation/marks/faq/index.mdtext Wed Apr 28 12:15:39 2021
@@ -16,17 +16,15 @@ Notice: Licensed to the Apache Softwa
specific language governing permissions and limitations
under the License.
-This document answers some of the Frequently Asked Questions about the
-ASF's trademarks and their allowable uses. Please be sure to review our
-[formal Trademark Policy](http://www.apache.org/foundation/marks/) document
-as well, which outlines other important requirements for any uses of Apache project
+This document answers some of Frequently asked questions (FAQs) about the
+ASF's trademarks and their allowable uses. Be sure to review our
+[formal Trademark Policy](http://www.apache.org/foundation/marks/) document, which outlines important requirements for any uses of Apache project
marks.
The following information helps ensure our marks and logos are used in
approved ways, while making it easy for the community to understand the
-guidelines. If you have any questions about the use of logos or trademarks
-that are not addressed in these guidelines, see our [trademark resources][resources]
-or please [contact us][contact].
+guidelines. If you have any questions about the use of logos or trademarks, see our [trademark resources][resources]
+or [contact us][contact].
**Contents**
@@ -40,25 +38,24 @@ See Also: [Trademark Resources Site Map]
# Are Apache® project names and logos trademarks? # {#obvious}
Yes, the names of all Apache® projects, software products, and their logos are trademarks
-owned by the Apache Software Foundation on behalf of our project communities. Note that
+that the Apache Software Foundation owns on behalf of our project communities. Note that
while some Apache project names and logos are registered in the US and various countries, even unregistered names and logos
are still trademarks of the ASF and should be treated with respect.
# How should I refer to Apache software product names? # {#guide}
-Apache projects are named in the form "Apache *Projectname*", for
-example Apache Hadoop® or Apache OpenOffice®. Read our
+Apache project names have the form "Apache *Projectname*", for
+example Apache Hadoop® and Apache OpenOffice®. Read our
[detailed guide for referring to Apache project and product names](//www.apache.org/foundation/marks/guide).
-Properly using the full "Apache *Projectname*" helps ensure that our volunteer
+Using the full "Apache *Projectname*" helps ensure that our volunteer
project communities get the credit they deserve.
# How should I provide attributions of Apache marks? # {#attribution}
-To properly attribute Apache marks - and to ensure that the volunteer
-communities that build Apache software get the credit they deserve -
-you should place prominent trademark attributions wherever
-Apache marks are used. On websites, hyperlinks to the relevant
-project homepage and to the ASF should be added. For example, to
+To properly attribute Apache marks, and to ensure that the volunteer
+communities that build Apache software get the credit they deserve,
+place prominent trademark attributions wherever you use Apache marks. On websites, add hyperlinks to the relevant
+project homepage and to the ASF. For example, to
provide an attribution for Apache Hadoop and its yellow elephant logo
(using basic HTML with hyperlinks):
@@ -71,26 +68,25 @@ In text, use Apache Lucene® in the f
some other Apache project names like Apache Zookeeper™ are unregistered
but are still considered trademarks of the ASF.
-A complete [list of trademarks claimed by the ASF][1] is published.
+Here is a complete [list of trademarks claimed by the ASF][1].
# May I use Apache marks in the title or cover of published books? # {#booktitle}
In general, yes, as long as you comply with the rest of Apache trademark
policies, in particular in regard to not claiming association or endorsement
-of/for/by the ASF. For more details or for explicit permissions,
-please [contact us][contact].
+of/for/by the ASF. For more details or for explicit permissions, [contact us][contact].
-- The ASF generally requires that Apache products are referred to using the
-full "Apache Tomcat®" form of its name, especially in such prominent places as
-book titles. However we do understand that some publishing houses may
-have specific standards for book titles that prevent this when producing
+- The ASF generally requires that you refer to Apache products using the
+full "Apache Tomcat®" form of its name, especially in prominent places like
+book titles. However, we do understand that some publishing houses may
+have specific standards for book titles that prevent this for
traditionally printed and bound books. In that case, and only for traditionally
printed and bound books,
-the use of the bare product name as "Tomcat®" is acceptable as long as there is
+using the bare product name as "Tomcat®" is acceptable as long as there is
clear attribution of both forms of the name.
- You must include a trademark attribution on the obverse title page or
-wherever other trademarks and copyrights are normally acknowledged. A
+wherever you acknowledge other trademarks and copyrights. A
preferred attribution would be:
> Apache®, Apache Tomcat, Tomcat®</a>,
@@ -99,19 +95,19 @@ preferred attribution would be:
in the United States and/or other countries. No endorsement by
The Apache Software Foundation is implied by the use of these marks.
-- The title or presentation of the book's cover, front matter, or other
-contents must not be used to imply association with, endorsement of/by, or
+- You may not use the title or presentation of the book's cover, front matter, or other
+contents to imply association with, endorsement of/by, or
any other exclusive or special connection with the ASF or the project's
community or product.
-- No royalties are required from the use of Apache marks or other IP in
+- We do not require the payment of a royalty for the use of Apache marks or other IP in
regularly published books. We certainly do appreciate royalty donations,
-and a number of publishers have setup systems to donate royalties from their
+and a number of publishers have set up systems to donate royalties from their
books back to the ASF. You can read more about [Donating to the
ASF](http://www.apache.org/foundation/contributing.html).
-# May I display Apache product logos on my website or in my own marketing materials where I reference ASF software products that my organization's software integrates with or provides support for? # {#integrateswith}
+# May I display Apache product logos on my website or marketing materials for ASF software products that my organization's software integrates with or supports? # {#integrateswith}
Yes, as long as you follow the rest of our [formal Trademark
Policy](http://www.apache.org/foundation/marks/). Note that you may [not use
@@ -128,20 +124,20 @@ form of its name.
- Do not visually combine the ASF product logo with any other images, and
do not change the appearance of ASF product logos except in cases where
- it is **required** by a specific printing restriction (e.g. printing paper in black and white).
+ it is **required** by a specific printing restriction (e.g. printing on paper in black and white).
-- On your website make any Apache project logo link to the homepage for that Apache project on
+- On your website link any Apache project logo to the homepage for that Apache project on
the apache.org website.
- Include a trademark attribution to Apache Software Foundation in an
-appropriate place on every page where your own trademarks are identified.
+appropriate place on every page where you identify your own trademarks.
- Ensure that your website and marketing materials do not imply ASF
endorsement or the affiliation of your products, services, or organization
with ASF.
-- Ensure that your website and marketing materials will not confuse the
-average user about the source of ASF products nor imply that ASF is
+- Ensure that your website and marketing materials do not confuse the
+average user about the source of ASF products or imply that ASF is
associated with your products or services in any way.
See also the [Powered By Apache logo](https://www.apache.org/foundation/press/kit/) program.
@@ -149,10 +145,9 @@ See also the [Powered By Apache logo](ht
# May I use Apache marks (names, logos) in software product names? # {#products}
-No, Apache trademarks - the names of any project or software product releases from the ASF-
- may *not* be used in the primary or secondary branding of
-any third party product or service names. For example, it is not permitted
-to name a product either "BigCo *Project* Thing", "BigCo distribution of *Project*",
+No, you may **not** use Apache trademarks - the names of any project or software product releases from the ASF -
+ in the primary or secondary branding of
+any third party product or service names. For example, you may **not** name a product either "BigCo *Project* Thing", "BigCo distribution of *Project*",
or any similar kind of name where *Project* is any Apache mark or project name.
The primary mission of the ASF is to provide free software for the public
@@ -163,8 +158,8 @@ products, the name and logo association
project communities and products is important to us.
We understand the importance in our ecosystem of third parties building
-software products atop Apache products or in conjunction with them. If you
-build such software products, please see the [next question about our
+software products on or in conjunction with Apache products. If you
+build such software products, see the [next question about our
"Powered by..." program](#poweredby).
@@ -177,15 +172,15 @@ Apache project names and the Powered By.
Powered By Apache around the outside) of their logos.
- Third parties providing products or services that are supersets of the
-functionality of an Apache product, or services are run atop Apache products,
+functionality of an Apache product, or services that run atop Apache products,
may use any "Powered by..." form of the Apache brand name of the related
product. For example, "BigCo SuperThing, Powered by Apache Spark" would be
-acceptable, provided that **all** of the other requirements are met:
+acceptable, provided that you meet **all** of the other requirements:
- Any primary product home pages or landing pages for the SuperThing product must include a
link from the homepage named "Apache *Spark*" pointing to the actual Apache
- project home page at http://*spark*.apache.org/ Note that inclusion of the
- "Apache" before the product mark is **required**.
+ project home page at http://*spark*.apache.org/ Note that you **must** include
+ "Apache" before the product mark.
- You product name **must** consistently use the "Apache Spark" version of the Apache
product name and follow the [Apache *Project* brand usage guide][guide].
@@ -193,7 +188,7 @@ acceptable, provided that **all** of the
- Do not visually combine the ASF product's Powered by... logo with any
other images, or change the logo in any way other than ways **required** by printing restrictions.
- - On your website make any Powered by... logo link to the homepage for
+ - On your website link any Powered by... logo to the homepage for
the ASF project on the apache.org website.
- Include a [trademark attribution](#attribution) to the Apache Software Foundation
@@ -203,69 +198,66 @@ acceptable, provided that **all** of the
endorsement or the affiliation of your products, services, or organization
with ASF.
- - Ensure that your website and marketing materials will not confuse the
- average user about the source of ASF products nor imply that ASF is
+ - Ensure that your website and marketing materials do not confuse the
+ average user about the source of ASF products or imply that ASF is
associated with your products or services in any way, other than the
fact that your product is built atop/to work with the Apache product.
- See also the [Apache *Project* brand usage guide][guide] for more requirements.
-Various Apache projects include a "Powered by..." specific logo for
+Various Apache projects include a "Powered by..."-specific logo for
their product(s). If the product you are interested in doesn't provide
-a Powered by... logo, please ask the relevant PMC to consider creating one.
+a Powered by... logo, ask the relevant PMC to consider creating one.
-**NOTE:** Use of an Apache product's normal logo (i.e. the non-Powered by) is
+**NOTE:** Use of an Apache product's normal logo (i.e. the *non* Powered-by) is
**not** permissible to directly denote products or services, even those
-built atop an Apache product. Apache product's normal logos must not be
-visually combined or directly associated with third party product logos.
+built atop an Apache product. You must not visually combine or directly associate Apache products' normal logos with third-party product logos.
See also the [Powered By Apache logo](https://www.apache.org/foundation/press/kit/)
page for details about logo usage.
-# May I use the Apache feather logo on the cover/title of published books, articles, or other similar publications? # {#titlefeather}
+# May I use the Apache feather logo on the cover/title of published books, articles, or other publications? # {#titlefeather}
No. The Apache feather logo (old horizontal version, or new vertical version) is a special trademark to the members of the Apache
-Software Foundation. Use of the feather logo on the external cover or title pages
-of books or similar printed materials is not allowed.
+Software Foundation. You may **not** use the feather logo on the external covers or title pages
+of books or similar printed materials.
-# May I use Apache product logos on the cover/title of published books, articles, or other similar publications? # {#titlelogo}
+# May I use Apache product logos on the cover/title of published books, articles, or other publications? # {#titlelogo}
Use of Apache project logos on the external cover or title pages of books or
similar printed materials is allowed only with permission; to request
-this please provide a mockup of the cover and other details about your
-publication and please [contact us][contact].
+this, [contact us][contact] with a mockup of the cover and other details about your
+publication.
We understand the importance in our ecosystem of authors publishing
informational books about Apache products, and the value that can bring
-in terms of new contributors to our communities. However care must be
-taken to use Apache product logos in descriptive ways, without
+in terms of new contributors to our communities. However, you must take care to use Apache product logos in descriptive ways, without
implying any association or endorsement, and without implying that
your book is an official or sole source of information about any
Apache product.
-# May I use Apache marks, screenshots, or program output within published books, articles, or other similar publications? # {#insidebook}
+# May I use Apache marks, screenshots, or program output within published books, articles, or other publications? # {#insidebook}
-In general, yes, as long as you comply with the rest of Apache trademark
+In general, yes, as long as you comply with the rest of the Apache trademark
policies, in particular in regard to not claiming association or endorsement
-of/for/by the ASF. For more details or for explicit permissions when legally required,
-please [contact us][contact].
+of/for/by the ASF. For more details or for explicit permissions when legally required, [contact us][contact].
-- The ASF prefers that Apache products are referred to using the
-full "Apache *Ignite*" form of its name, at least in the first or most
-prominent uses within a book, chapter, or article, or other section
+- The ASF prefers that you refer to Apache products using the
+full "Apache *Ignite*" form of the product name, at least in the first or most
+prominent uses within a book, chapter, article, or other section
of a larger published work; see the [Apache *Project* brand usage guide][guide] for details.
-- Screenshots, program output, and other displays created by or taken
-of Apache products in use may be used in any descriptive ways in the
+- You may use screenshots, program output, and other displays created by or taken
+of Apache products in use in descriptive ways in the
content of publications. Such use may include Apache product logos
-when they are normally displayed by the product in question.
+as they normally display in the product in question.
- You must include a trademark attribution on the obverse title page or
-wherever other trademarks and copyrights are normally acknowledged. A
+wherever you acknowledge other trademarks and copyrights. A
preferred attribution would be:
> Apache®, Apache Ignite, Ignite</a>,
@@ -274,59 +266,56 @@ preferred attribution would be:
in the United States and/or other countries. No endorsement by
The Apache Software Foundation is implied by the use of these marks.
-- No royalties are required from the use of Apache marks or other IP in
-regularly published books. We certainly do appreciate non-targeted donations,
-and a number of publishers have setup systems to donate royalties from their
-books back to the ASF. You can read more about [Donating to the
+- ASF does not require royalties for the use of Apache marks or other IP in
+regularly-published books. We certainly do appreciate non-targeted donations,
+and a number of publishers have set up systems to donate all or part of the royalties from their
+books to the ASF. Read more about [Donating to the
ASF](http://www.apache.org/foundation/contributing.html).
-# May I use Apache marks, screenshots, or program output within academic papers or articles, or similar non-profit scholarly publications? # {#insideuniv}
+# May I use Apache marks, screenshots, or program output in academic papers, articles, or similar non-profit scholarly publications? # {#insideuniv}
Yes, as long as you comply with the rest of Apache trademark
policies, in particular in regard to not claiming association or endorsement
-of/for/by the ASF. For more details or for explicit permissions when legally required,
-please [contact us][contact].
+of/for/by the ASF. For more details or for explicit permissions when legally required, [contact us][contact].
As long as uses of Apache trademarks or logos are clear in referring to the software
products produced by the ASF, the ASF position is that this FAQ should constitute sufficient
permissions for non-profit academic and scholarly papers and publications to use
our trademarks in all respectful ways. We appreciate the researchers and students
-who use Apache software products to further human knowledge and who want
-to use our code to do so.
+who want to use Apache software products to further human knowledge.
# Should we donate project trademarks along with the code when we submit to the Apache Incubator? # {#incubator}
That depends on your goals. Many groups donate existing projects to the
-[Apache Incubator][incubator], to become podlings and hopefully eventually official Apache
-projects. When you have a pre-existing project that has a well-known brand
+[Apache Incubator][incubator], to become podlings and, we hope eventually become official Apache top level
+projects (TLPs). When you have an existing project that has a well-known brand
and associated trademarks or registrations, the **donor** needs to decide if they
also wish to donate all trademarks with the project, or if they will keep the
-trademarks, and have the new podling choose a new name and brand. To graduate,
-the ASF must own all trademark rights to a podling's brand.
+trademarks, and have the new podling choose a new name and brand. For a podling to graduate and become a TLP,
+the ASF must own all trademark rights to the podling's brand.
- If you donate the brand with the project, the ASF must have full legal ownership
of all brand elements before graduation. It becomes an Apache brand, and the
donor will not be allowed to claim any special relationship with the trademarks going forward.
-- If you keep the brand, the podling will then need to choose a new name as they are
-starting the incubation process. This allows you to keep the goodwill from your
+- If you keep the brand, the podling will need to choose a new name as it starts the incubation process. This allows you to keep the goodwill from your
existing brand, but means that the podling will likely have to work harder to grow
the diverse community that the Incubation process is designed to show.
# How do we transfer trademark rights when submitting a project to the Apache Incubator # {#podlingxfer}
-One of the *graduation* criteria for podlings is that the ASF owns **all** trademark rights
+One of the *graduation* criteria for podlings to TLP status is that the ASF own **all** trademark rights
and goodwill to the podling's brand. Since the incubation process takes a number of
months, the recommended way to transfer trademarks and any pre-existing registrations is:
- In the incubation proposal, explicitly note that the donor organization is planning
-to donate all trademarks and goodwill. Be sure to include a list of all trademarks,
+to donate all trademarks and goodwill. Include a list of all trademarks,
especially any registrations or applications outstanding.
-- After the podling has been accepted for incubation, has imported the code, and
+- After the ASF accepts the podling for incubation, has imported the code, and
published a website, have an officer of the donating organization [contact us][contact]
via email to explicitly state that you will be transferring all trademarks. This gives
the ASF assurance of the transfer, but does not require the donor to legally assign
@@ -336,8 +325,8 @@ created as part of the incubation proces
- Before the podling is ready to graduate, have donor counsel [contact us][contact]
to sign a standard trademark transfer agreement in the US, where the ASF is
-headquartered. As a non-profit, any assistance in processing the transfer, especially
-of applications in process is appreciated. The legal transfer must be signed before
+headquartered. As the ASF is a non-profit, we appreciate any assistance in processing the transfer, especially
+of applications in process. The legal transfer must be signed before
the podling can formally graduate, typically at a monthly board meeting.
- A **best practice** is for a donor to submit a US or local country trademark
@@ -348,16 +337,16 @@ once the podling graduates. **IMPORTANT
----
-# Other Trademark Guidelines # {#other}
+# Other trademark guidelines # {#other}
-Please see our [formal Trademark Policy](http://www.apache.org/foundation/marks/)
+See our [formal Trademark Policy](http://www.apache.org/foundation/marks/)
and our [site map of all Trademark resources][resources].
# Important Note # {#notes}
**Nothing in this ASF policy statement shall be interpreted to allow any
third party to claim any association with the Apache Software Foundation or
-any of its projects or to imply any approval or support by ASF for any
+any of its projects, or to imply any approval or support by ASF for any
third party products, services, or events.**
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org