Hi,

Members/organizations in TF-M community may have diverse policies regarding this copyright format. It might be more flexible to at first make this copyright change optional as Anton suggests. If contributors are required to follow current copyright format, it is still accepted.

Best regards, Hu Ziji

From: Andrej Butok via TF-M tf-m@lists.trustedfirmware.org Sent: Friday, February 3, 2023 10:19 PM To: Ken Liu Ken.Liu@arm.com; tf-m@lists.trustedfirmware.org Cc: nd nd@arm.com Subject: [TF-M] Re: TF-M copyright year update

Hi,

OK. Let's send the permission request to all contributors. Ideally, to have the most clean approach used by MbedTLS: * Copyright The <project name> Contributors * SPDX-License-Identifier: <License name>

Thanks, Andrej

From: Ken Liu via TF-M <tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org> Sent: Friday, February 3, 2023 4:32 AM To: tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org Cc: nd <nd@arm.commailto:nd@arm.com> Subject: [TF-M] Re: TF-M copyright year update

One question: is mixed style allowed, in case some copyright holders do not reply in time?

And one proposal: Let's gather the permission (or willingness) first, maybe all stakeholders would response quickly? Then we can do the next step.

/Ken

From: Anton Komlev via TF-M <tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org> Sent: Thursday, February 2, 2023 11:57 PM To: tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org Cc: nd <nd@arm.commailto:nd@arm.com> Subject: [TF-M] TF-M copyright year update

Hi,

This is a continue of discussion started on today's forum on the value of copyright year update on every change. I proposed to let such update being optional and do not track it in review. There was no objection during forum but an alternative proposal to adopt the Linux Foundation guidancehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linuxfoundation.org%2Fblog%2Fblog%2Fcopyright-notices-in-open-source-software-projects&data=05%7C01%7Candrey.butok%40nxp.com%7C1401503efbc8464772d908db0597548d%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C638109919741123479%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0XrBvk0Ij%2FtJyvFgd37d6AJ5JcFkSMQ8%2B6thQmT69wo%3D&reserved=0, where all authors and contributors are listed in a separate while source and documentation are free from it. For example MbedTLS doing that way, although it has side effects:

* Need to modify all files in 6 repositories. * Gather permission from all copyright holders.

Looking for more opinions on the topic.

Thanks, Anton

Hi,

Interesting idea and it could be true. It leads to mixed rules and requires more consideration to apply such a big change in a mature project like TF-M. Meanwhile, it is not in conflict with my proposal and having no objections or further comments I conclude to community agreement that:

The requirement for Copyright year update on every change is optional and reviewers shall not verify it.

I will add such statement to TF-M contribution guide.

Thanks, Anton

From: Andrej Butok via TF-M tf-m@lists.trustedfirmware.org Sent: Monday, February 6, 2023 8:16 AM To: David Hu David.Hu@arm.com; Ken Liu Ken.Liu@arm.com; tf-m@lists.trustedfirmware.org Cc: nd nd@arm.com Subject: [TF-M] Re: TF-M copyright year update

Hi,

The common TFM source code is mainly developed by ARM & Linaro, so it should be no issue here. The source code in the chip vendors "port" folder can get an exception to avoid the mentioned conflict.

Thanks, Andrej

From: David Hu <David.Hu@arm.commailto:David.Hu@arm.com> Sent: Monday, February 6, 2023 3:43 AM To: Andrej Butok <andrey.butok@nxp.commailto:andrey.butok@nxp.com>; Ken Liu <Ken.Liu@arm.commailto:Ken.Liu@arm.com>; tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org Cc: nd <nd@arm.commailto:nd@arm.com> Subject: RE: TF-M copyright year update

Hi,

Members/organizations in TF-M community may have diverse policies regarding this copyright format. It might be more flexible to at first make this copyright change optional as Anton suggests. If contributors are required to follow current copyright format, it is still accepted.

Best regards, Hu Ziji

From: Andrej Butok via TF-M <tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org> Sent: Friday, February 3, 2023 10:19 PM To: Ken Liu <Ken.Liu@arm.commailto:Ken.Liu@arm.com>; tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org Cc: nd <nd@arm.commailto:nd@arm.com> Subject: [TF-M] Re: TF-M copyright year update

Hi,

OK. Let's send the permission request to all contributors. Ideally, to have the most clean approach used by MbedTLS: * Copyright The <project name> Contributors * SPDX-License-Identifier: <License name>

Thanks, Andrej

From: Ken Liu via TF-M <tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org> Sent: Friday, February 3, 2023 4:32 AM To: tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org Cc: nd <nd@arm.commailto:nd@arm.com> Subject: [TF-M] Re: TF-M copyright year update

One question: is mixed style allowed, in case some copyright holders do not reply in time?

And one proposal: Let's gather the permission (or willingness) first, maybe all stakeholders would response quickly? Then we can do the next step.

/Ken

From: Anton Komlev via TF-M <tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org> Sent: Thursday, February 2, 2023 11:57 PM To: tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org Cc: nd <nd@arm.commailto:nd@arm.com> Subject: [TF-M] TF-M copyright year update

Hi,

This is a continue of discussion started on today's forum on the value of copyright year update on every change. I proposed to let such update being optional and do not track it in review. There was no objection during forum but an alternative proposal to adopt the Linux Foundation guidancehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linuxfoundation.org%2Fblog%2Fblog%2Fcopyright-notices-in-open-source-software-projects&data=05%7C01%7Candrey.butok%40nxp.com%7C27f20ba56b534e2e02ea08db07ebd825%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C638112481754234524%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gwzoJo%2FDIr9G4wfqyveNwCFe%2BvmG8krOojaMYP5CQrM%3D&reserved=0, where all authors and contributors are listed in a separate while source and documentation are free from it. For example MbedTLS doing that way, although it has side effects:

* Need to modify all files in 6 repositories. * Gather permission from all copyright holders.

Looking for more opinions on the topic.

Thanks, Anton