Upcoming changes to structure of Intel DCAP-related GitHub repositories

[bgotowal]

Starting with the upcoming 1.24 release of Intel DCAP, we plan to make the following changes to the structure of Intel DCAP-related GitHub repositories to facilitate more efficient collaboration with the community and improve the consumption of our code:

• Instead of using a single commit on every release (e.g., “release 1.24”), Intel contributions will be itemized and directly visible to the community as individual commits.
  • As a result, it will be easier for the community to understand the changes.
  • Intel is still committed to deliver consolidated and pre-validated releases marked by corresponding tags and GitHub releases.
  • After a tagged release, Intel will continue to incrementally publish new features and bug fixes, which will combine to eventually comprise another tagged release at a future point.
• Several self-contained components will gradually be extracted to standalone GitHub repositories so that Intel can collaborate with the community on a smaller set of changes and iterate faster.
  • This allows the direct consumption of self-contained components without pulling unrelated code.
  • The extracted components will be reintegrated into the original repository as a git submodules. Hence, they are still available via the consolidated DCAP repository and accessible via the same Makefile build targets. Note that the DCAP repository is using submodules already, so the process should be familiar to you and will be seamless.
  • If you haven’t utilized submodules before and prefer to continue consuming the consolidated codebase, please ensure you run git submodule update --init after cloning the DCAP code.
  • DCAP 1.24 will feature extraction of the Provisioning Certificate Caching Service (PCCS) to its dedicated project hosted at intel/confidential-computing.tee.dcap.pccs (also available via the DCAP project).

These changes will be rolled out gradually and affect source code only. Binary releases will remain available through existing delivery channels.

Please let us know of any concerns.