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/05/02 18:13:11 UTC
svn commit: r1889422 -
/infrastructure/site/trunk/content/foundation/marks/responsibility.mdtext
Author: andreww
Date: Sun May 2 18:13:11 2021
New Revision: 1889422
URL: http://svn.apache.org/viewvc?rev=1889422&view=rev
Log:
minor text edits
Modified:
infrastructure/site/trunk/content/foundation/marks/responsibility.mdtext
Modified: infrastructure/site/trunk/content/foundation/marks/responsibility.mdtext
URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/content/foundation/marks/responsibility.mdtext?rev=1889422&r1=1889421&r2=1889422&view=diff
==============================================================================
--- infrastructure/site/trunk/content/foundation/marks/responsibility.mdtext (original)
+++ infrastructure/site/trunk/content/foundation/marks/responsibility.mdtext Sun May 2 18:13:11 2021
@@ -18,17 +18,17 @@ Notice: Licensed to the Apache Softwa
Apache Project Management Committees (PMC) are directly responsible for promoting and protecting their project's
brand and trademarks while following Apache Trademark policies. This document
-is an overview of PMC responsibilities with pointers to specific policies
+is an overview of PMC responsibilities, with pointers to specific policies
or procedures PMCs must follow.
These responsibilities are in addition to the
[Project Website Branding Requirements](pmcs.html) document, which primarily focuses on website display,
-and with the [Apache Trademark Reporting Guidelines](reporting.html), which detail how users and
+and to the [Apache Trademark Reporting Guidelines](reporting.html), which detail how users and
committers may report issues involving Apache brand uses.
-**Podlings (PPMCs)** must liaise with the Incubator PMC prior to taking any
+**Podling (PPMCs)** must liaise with the Incubator PMC prior to taking any
external action (such as emailing an external party). The Incubator PMC should
-loop in trademarks@ if there are any questions
+loop in trademarks@ if there are any questions.
**Contents**
@@ -42,7 +42,7 @@ See Also: [Trademark Resources Site Map]
This document defines the board's expectation that PMCs manage
their own project's brand: how the project displays its own brand
in public; how the project responds to obvious
-uses of the project's brand by third parties; and to comply with the
+uses of the project's brand by third parties; and how the PMC is to comply with the
Apache Trademark Policy and the Project Website Branding Requirements.
The Apache Software Foundation owns all Apache® marks,
and administers them on behalf of all Apache projects. PMCs are expected to
@@ -50,22 +50,20 @@ actively manage their project's brand, a
Brand Management or Legal Affairs when necessary.
**Questions?** Please [contact the Trademarks committee](http://www.apache.org/foundation/marks/contact#pmc)
-with general questions. This document is focused on members of all Apache PMCs, and
+with general questions. This document is for members of Apache PMCs, and
is probably best read in conjunction with the [Apache Project Branding
-Requirements](http://www.apache.org/foundation/marks/pmcs) defining the details
-of how projects should treat and display trademarks, and with the
-[PMC Guide](http://www.apache.org/dev/pmc.html) which covers other, non-brand
-related responsibilities and procedures related to PMC membership.
+Requirements](http://www.apache.org/foundation/marks/pmcs), which define how projects should treat and display trademarks; and with the
+[PMC Guide](http://www.apache.org/dev/pmc.html), which covers other, non-brand-related responsibilities and procedures related to PMC membership.
-# PMCs Are Responsible For Their Brand # {#responsible}
+# PMCs are responsible for their brand # {#responsible}
-Much like PMCs are stewards of their communities and project code, PMCs are
+Much as PMCs are stewards of their communities and their project code, PMCs are
also responsible for managing their own project's brand. This includes
-all the obvious aspects of a brand: the project's name and logo; the display
-of the main project website; the appearance and functionality of their product.
+all the obvious aspects of a brand: the project's name and logo, the display
+of the main project website, and the appearance and functionality of their product.
Much of the work that PMC members do improving code, updating the website,
and promoting their product to help bring more users and developers into
-their community also helps to maintain the brand, or overall public expectation
+their community also helps to maintain the brand, and overall public expectation
of the quality and functionality of the software products that this project provides for download.
While the Apache License encourages third parties to use our code, it does **not**
@@ -79,7 +77,7 @@ source of Apache software. In particula
PMCs need to be aware of their brand and its use in the broader world, and
should work to ensure that when the public hears about their project - for
-example, Hadoop - that the main association is to the actual Apache Hadoop
+example, Hadoop - the main association is to the actual Apache Hadoop
project itself, and not to a third party or other organization besides Apache.
Managing your brand requires a little extra thought than most activities
@@ -93,7 +91,7 @@ next time you read news coverage of your
it, consider how a newcomer will see your project's name, and its relationship
both to the ASF and to other companies and technologies.
-# Ensure Project Websites Treat Trademarks Appropriately # {#website}
+# Ensure project websites treat trademarks appropriately # {#website}
PMCs are directly responsible for ensuring all of their project's web content
complies with the [Apache Project Branding Requirements](http://www.apache.org/foundation/marks/pmcs).
@@ -108,7 +106,7 @@ is an important one to all Apache projec
sure to use it properly on apache.org websites, especially in relation to
Apache projects and products.
-# Present An Independent Face To Your Project # {#independent}
+# Present an independent face for your project # {#independent}
Part of the Apache Way is the concept of hats - when PMC members do work on
Apache lists, they are expected to act as individuals, wearing their PMC hat;
@@ -116,8 +114,7 @@ i.e. on behalf of their PMC's project, a
Likewise, it is important that your [project as a whole is run
independently of commercial influence](http://community.apache.org/projectIndependence.html), and presents the public perception
that the project is run independently. There should be no question in the minds
-of average users on the website or the mailing lists that the project is
-run solely by the PMC, and not by any other organizations.
+of average users on the website or the mailing lists that the PMC solely runs the project, and not any other organizations.
Projects must ensure that their average user can find all information and code
necessary to use the product in its common use cases solely on the project's
@@ -131,19 +128,19 @@ third party influence to affect the futu
organizations.
Note that per-project Thanks and Support pages are allowed to recognize
-specific vendors who have donated services or licenses to the project, or who
-are well-known vendors who provide outside support for the project. However
+specific vendors that have donated services or licenses to the project, or that
+are well-known vendors that provide outside support for the project. However,
these must be factual entries, not advertisements, and must not show favoritism
to any particular vendor(s). Recommended best practices for
[Thanks and Support pages](https://www.apache.org/foundation/marks/linking) are provided.
-# Address Improper Third Party Uses Of Apache Marks # {#police}
+# Address improper third-party use of Apache marks # {#police}
PMCs are responsible for evaluating and if needed addressing any infringing use of their project's
-marks by third parties that are reported to them. The PMC must work to contact
+marks by third parties that come to their attention. The PMC must work to contact
potentially infringing parties to ask them to respect Apache marks and
attribute them to the ASF. In many cases, a friendly note reminding a third
-party that Apache project names are our trademarks, and they are important
+party that Apache project names are our trademarks and that they are important
to us is sufficient to get third parties to respect our marks. PMCs and committers should use the
[Apache Trademark Use Reporting Guidelines](http://www.apache.org/foundation/marks/reporting.html)
in deciding how to contact third parties.
@@ -155,64 +152,63 @@ contact. Templates are available at
PMCs are expected to manage this process. If a third party does
not respond favorably to the PMC's requests, or responds in a hostile or
-legalistic manner, please [report to Brand Management](#report).
+legalistic manner, [report to Brand Management](#report).
-As stewards of their project and those most familiar with their technology,
-PMCs are the best group to understand their brand's uses within the
+As stewards of their project and the group most familiar with their technology,
+PMCs are best-positioned to understand their brand's uses within the
greater marketplace. However, PMCs are not authorized to license infringing
uses of their brand(s) to third parties without explicit approval from the
VP, Brand Management.
-# Report Trademark Issues To Brand Management # {#report}
+# Report trademark issues to Brand Management # {#report}
-Detailed procedures are in the [Apache Trademark Reporting Guidelines](reporting.html).
+Detailed reporting procedures are in the [Apache Trademark Reporting Guidelines](reporting.html).
-In cases where there is a significant legal issue, or where the efforts of the
+If there is a significant legal issue, or the efforts of the
PMC (and especially the project chair and VP, as an officer of the ASF) are
not successful, the PMC should work with VP, Brand Management to get assistance.
-Please address trademark and legal questions to the [correct lists](http://www.apache.org/foundation/marks/contact#pmc):
+Address trademark and legal questions to the [correct lists](http://www.apache.org/foundation/marks/contact#pmc):
-- General or hypothetical legal questions that are not about private matters
- should be sent to the legal-discuss@ publicly archived mailing list.
+- Send general or hypothetical legal questions that are not about private matters
+ to the legal-discuss@ publicly-archived mailing list.
-- Specific requests for legal advice from ASF counsel on matters relating to
+- Send specific requests for legal advice from ASF counsel on matters relating to
any Apache project, or for legal questions that should not be made public,
- should be sent to the legal-internal@ privately archived mailing list.
+ to the legal-internal@ privately archived mailing list.
-- General questions about trademarks, or about Apache branding policies,
- or about any potential trademark infringements or issues
- should be sent to the privately archived trademarks@ list.
+- Send general questions about trademarks, Apache branding policies,
+ or any potential trademark infringements or issues
+ to the privately archived trademarks@ list.
-Reminder: in any cases where a third party's legal counsel contacts a PMC,
-please ensure the PMC works with legal-internal@ to get advice from
-ASF Counsel before making any response.
+Reminder: if a third-party's legal counsel contacts a PMC,
+ensure the PMC works with legal-internal@ to get advice from
+ASF Counsel before making any response.
-# Comply With Apache Brand Policy # {#compliance}
+# Comply with Apache brand policy # {#compliance}
-All PMCs are required to comply with the Apache Project
+All PMCs must comply with the Apache Project
Branding Requirements. If your project does not comply, or is having issues
in determining compliance, including a recognition of this
-set of PMC responsibilities to handle brand issues, then you must work
+set of PMC responsibilities to handle brand issues, work
with trademarks@ to resolve the issue.
-Much like complying with Apache legal policy to ensure that our software is
+Much as complying with Apache legal policy ensures that our software is
safely covered under our license, projects must follow the branding requirements
-to ensure that our projects' brands and the Apache brand - and public reputations - are maintained
-for the future benefit of all of Apache projects.
+to ensure that we maintain our projects' brands and the Apache brand - and public reputations - for the future benefit of all of Apache projects.
-# Other Trademark Guidelines # {#other}
+# Other trademark guidelines # {#other}
-For more information about Apache marks, please see our [formal Trademark
+For more information about Apache marks, see our [formal Trademark
Policy](http://www.apache.org/foundation/marks/).
-# Important Note # {#notes}
+# 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
-third party products, services, or events.**
+third-party products, services, or events.**
-# Policy Version # {#version}
+# Policy version # {#version}
This is version 1.1 of this Apache policy document, published in <s>May 2011</s> November 2013.
Significant changes will be marked with a new version number.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org