Add license info guidance to docs
Extends the Contributing page to provide more guidance on adding
and updating license and copyright information. Added link to
coding style page where some example license and copyright comment
blocks have been added.
Signed-off-by: Julian Hall <julian.hall@arm.com>
Change-Id: I139f1300420d32c04686ddf1dbf450fa5a7484e8
diff --git a/docs/project/contributing.rst b/docs/project/contributing.rst
index d9760d9..836502c 100644
--- a/docs/project/contributing.rst
+++ b/docs/project/contributing.rst
@@ -23,18 +23,18 @@
- Make sure your commit messages are in the proper format. Please keel the 50/72 rule (for details see `Tim Popes blog entry`_.)
- Where appropriate, please update the documentation.
- - Consider whether the this document or other in-source documentation
- needs updating.
+ - Consider which documents or other in-source documentation needs updating.
- Ensure that each changed file has the correct copyright and license information. Files that entirely consist of
contributions to this project should have a copyright notice and BSD-3-Clause SPDX license identifier of the form
- as shown in :ref:`license`. Files that contain changes to imported Third Party IP files should retain their
- original copyright and license notices. For significant contributions you may add your own copyright notice in
- following format::
+ as shown in :ref:`license`. Example copyright and license comment blocks are shown in :ref:`Coding Style & Guidelines`.
+ Files that contain changes to imported Third Party IP files should retain their original copyright and license
+ notices. For significant contributions you may add your own copyright notice in following format::
Portions copyright (c) [XXXX-]YYYY, <OWNER>. All rights reserved.
where XXXX is the year of first contribution (if different to YYYY) and YYYY is the year of most recent
contribution. *<OWNER>* is your name or your company name.
+ - For any change, ensure that YYYY is updated if a contribution is made in a year more recent than the previous YYYY.
- If you are submitting new files that you intend to be the technical sub-maintainer for (for example, a new platform
port), then also update the :ref:`maintainers` file.
- For topics with multiple commits, you should make all documentation changes (and nothing else) in the last commit
@@ -83,6 +83,6 @@
.. _`Tim Popes blog entry`: https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
-*Copyright (c) 2020-2021, Arm Limited and Contributors. All rights reserved.*
+*Copyright (c) 2020-2022, Arm Limited and Contributors. All rights reserved.*
SPDX-License-Identifier: BSD-3-Clause