Should we pay & support a comfort of regimes which built walls against the rest of the world? That is their choice.

 

From: David Hu <David.Hu@arm.com>
Sent: Tuesday, March 22, 2022 9:56 AM
To: Andrej Butok <andrey.butok@nxp.com>; Anton Komlev <Anton.Komlev@arm.com>
Cc: tf-m@lists.trustedfirmware.org
Subject: RE: TF-M on GitHub opinions collection

 

Yep.

If Github becomes the only working repo, users from China mainland have to either always use VPN, or maintain local mirrors time by time.

 

Best regards,

Hu Ziji

 

From: Andrej Butok <andrey.butok@nxp.com>
Sent: Tuesday, March 22, 2022 4:51 PM
To: David Hu <David.Hu@arm.com>; Anton Komlev <Anton.Komlev@arm.com>
Cc: tf-m@lists.trustedfirmware.org
Subject: RE: TF-M on GitHub opinions collection

 

It should be an issue for China mainland users, as they have to use VPN for all other open-source project present on GitHub (MbedTls, Zephyr, FreeRTOS, CMSIS, PSA Arch Tests and etc.)

 

From: David Hu via TF-M <tf-m@lists.trustedfirmware.org>
Sent: Tuesday, March 22, 2022 9:46 AM
To: David Hu <David.Hu@arm.com>; Anton Komlev <Anton.Komlev@arm.com>; tf-m@lists.trustedfirmware.org
Cc: nd <nd@arm.com>
Subject: [TF-M] Re: TF-M on GitHub opinions collection

 

Sorry for typo. China mainland. 😊

 

From: David Hu via TF-M <tf-m@lists.trustedfirmware.org>
Sent: Tuesday, March 22, 2022 4:40 PM
To: Anton Komlev <Anton.Komlev@arm.com>; tf-m@lists.trustedfirmware.org
Cc: nd <nd@arm.com>
Subject: [TF-M] Re: TF-M on GitHub opinions collection

 

Hi all,

 

It is difficult for developers from China mainline to directly access Github.

Option 3 looks more reliable.

 

Best regards,

Hu Ziji

 

From: Anton Komlev via TF-M <tf-m@lists.trustedfirmware.org>
Sent: Monday, March 21, 2022 8:35 PM
To: tf-m@lists.trustedfirmware.org
Cc: nd <nd@arm.com>
Subject: [TF-M] TF-M on GitHub opinions collection

 

Hello,

 

Quite some time ago there was a proposal to move TF-M into GitHub. The main motivation is: more convenient review process, the Wiki for knowledge sharing and issue tracking facility.

This idea had been discussed multiple times in TSC. The following options were considered:

  1. Hybrid: Add TF-M on GitHub with 2 ways synchronization between GitHub and existing Git/Gerrit
  2. GitHub only: Move to GitHub completely and drop Gerrit.
  3. Mirror: Create a read-only mirror on GitHub. TF-M review process stays in Gerrit but Wiki and issue tracking are on GitHub.
  4. Nothing: Stay on Gerrit as good enough solution.

The options are ordered by complexity and cost each has pros and cons. The Mirror option (3) seeing as the best compromise and practically affordable in a short time.

 

Please share your opinion and comments on the topic with any dependencies or specific requirements to be considered.

 

Thanks,

Anton