diff --git a/content/foundation/license-faq.md b/content/foundation/license-faq.md index 0e26870f3..039d5cede 100644 --- a/content/foundation/license-faq.md +++ b/content/foundation/license-faq.md @@ -163,6 +163,14 @@ as they cause confusion. Creating a new license is a non-trivial task. If you do that we recommend that you get your own legal advice. +Some modifications are trivial or purely cosmetic in nature and do not alter the +license in any meaningful way. In such cases, the result would still be considered +the Apache License, and you do not need to change the name in these cases. Using +"https:" for the URL in the license header instead of "http:", or changing the font +or line spacing to make the license more readable, are examples of such changes. If +you are uncertain whether your changes are trivial, you should seek your own legal +advice. + ## I've made improvements to the Apache code; may I distribute the modified result? {#Distribute-changes} Absolutely -- subject to the [terms of the Apache license](/licenses/LICENSE-2.0#redistribution), diff --git a/content/legal/src-headers.md b/content/legal/src-headers.md index 8a243227e..ac4a8b708 100644 --- a/content/legal/src-headers.md +++ b/content/legal/src-headers.md @@ -44,7 +44,7 @@ This section refers only to works submitted directly to the ASF by the copyright
  • provide written permission for the ASF to make such removal or relocation of the notices.
  • -
  • Each source file should include the following license header -- note that there should be no copyright notice in the header: +
  • Each source file should include the following license header -- note that there should be no copyright notice in the header and https is acceptable in place of http for the URL: Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file