Add IP Policy guidance

The goal of this IP Policy guidance is to make it really simple for
projects to comply with the Foundation's IP Policy.

This document is non-exhaustive by design. It is meant to address
the most common scenarios, not every corner-case.

It is also opinionated: it favors community norms and best practices
in areas where the Foundation's IP Policy provides leeway to do so.

This document is based on prior work from CNCF, available here:
https://github.com/cncf/foundation/blob/master/copyright-notices.md,
an earlier pull request by @brianwarner, available here:
#414,
and community input.

Committer: Tobie Langel <tobie@unlockopen.com>

IP_POLICY_GUIDANCE.md

@@ -0,0 +1,71 @@
+# OpenJS Foundation IP Policy Guidance
+
+The purpose of this guide is to make it straightforward for projects
+to follow the [OpenJS Foundation IP Policy][IP Policy].
+
+Of course, the source of truth remains the [IP Policy][].
+
+If in doubt about anything related to IP after reading this document,
+first read the [IP Policy][], and then [ask for help](#getting-help).
+
+## Basic requirements
+
+There are three key requirements for all OpenJS Foundation projects:
+
+1. [Licensing](#1-licensing),
+2. [copyright notices](#2-copyright-notices), and
+3. displaying the [standard website footer](#3-standard-website-footer) on the project's website.
+
+Additionally, projects may decide to adopt the [OpenJS Foundation Contributor License Agreement (CLA)](#contributor-license-agreement-cla).
+
+### 1. Licensing
+
+Code may be licensed under:
+  * [Apache, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0)
+  * [MIT](https://opensource.org/licenses/MIT)
+  * [2-Clause BSD](https://opensource.org/licenses/BSD-2-Clause)
+  * [3-Clause BSD](https://opensource.org/licenses/BSD-3-Clause)
+
+Documentation may be licensed under:
+  * [CC BY 4.0](http://creativecommons.org/licenses/by/4.0/)
+  * [MIT](https://opensource.org/licenses/MIT)
+
+If you need to use a license which isn't in the list,
+you will need to obtain permission from the Board to do so.
+
+### 2. Copyright notices
+
+The recommendation is to use a general copyright statement
+of the following form (where XYZ is the project's name):
+
+- **Copyright The XYZ Authors.**
+- **Copyright The XYZ Contributors.**
+- **Copyright Contributors to the XYZ project.**
+
+By using this format, the project avoids having to deal with
+names of copyright holders, years or ranges of years,
+and variations on the (c) symbol.
+
+_Please note that you **must not** change or remove existing copyright lines
+unless you put them there **and** have the right to do so.
+If there are existing copyright lines just
+add the recommended copyright statement below the existing copyright lines.
+You may however update copyright lines that say
+"JS Foundation" or "Node.js Foundation" to "OpenJS Foundation"
+as this simply reflects the merged status of the organizations._
+
+### 3. Standard website footer
+
+All project websites need to have a [standard website footer][].
+
+### Contributor License Agreement (CLA)
+
+Projects may decide to adopt the [OpenJS Foundation CLA][CLA] but may not use other CLAs.
+
+## Getting help
+
+If you have a question about this policy or how to implement it, please reach out to [legal-questions@lists.openjsf.org](mailto:legal-questions@lists.openjsf.org).
+
+[IP Policy]: https://ip-policy.openjsf.org
+[CLA]: https://cla.openjsf.org
+[standard website footer]: https://github.com/openjs-foundation/artwork#copyright-notices-for-project-website-footers