Skip to content

Latest commit

 

History

History
70 lines (56 loc) · 3.78 KB

Committers.md

File metadata and controls

70 lines (56 loc) · 3.78 KB

Project Committers

NOTE This document will be superseded by the creation of SIGs and WGs.

It is kept for now as the discussion and definition of the new governance process is ongoing.

List of Committers

The following people have been granted commit permissions (that is, write access) to the Open Enclave SDK by the Community Governance Committee. The area column describes which technical areas each committer is most interested in, and therefore should usually be consulted for changes relating to that area.

Name GitHub Alias Area
Amaury Chamayou achamayou Build, CCF Integration
Anand Krishnamoorthi anakrish Debugging, SGX, EDL, Dev Tools
Brian Telfer Britel TrustZone, Attestation
Chris Yan cyandevs Build, CI, Scripts
Dave Thaler dthaler TrustZone, APIs, Dev Tools
Akash Gupta gupta-ak SGX, Attestation, APIs
Hernan Gatta HernanGatta TrustZone
Sergio Wong jazzybluesea Attestation, SGX
Xuejun Yang jxyang SGX
Mike Brasher mikbras SGX, APIs, EDL
Ming-Wei Shih mingweishih SGX, Dev tools, EDL
Paul Allen paulcallen TrustZone
Radhika Jandhyala radhikaj SGX, APIs, Website
Rob Sanchez rs-- Build, CI, Scripts
Shanwei Cen shnwc Attestation, SGX
Shruti Ratnam shruti25ratnam Attestation
Cheng-mean Liu soccerGB Attestation, SGX
Andy Chen anche-is-andy Attestation, SGX

Current Expectations

However, it is up to each committer to determine who should review which PR, and when to merge it. It is up to each committer to decide when to accept a contribution.

It is recommended that each committer take the Linux Foundation course Inclusive Open Source Community Orientation and follow its principles to ensure that Open Enclave has an open and inclusive community.

Current Challenges

As the project has grown, some community members are frustrated with the current GitHub workflows and reviewer expectations. The structure described above is not programatically enforced, and not represented through any of the development tools (ie, GitHub itself).

As more developers join the community and bring domain-specific knowledge, there is no way to delegate domain ownership, authority or autonomy over changes to code. And as the community itself grows, the current communication channels do not support rapid iteration, or facilitate remote and open collaboration.

Specific challenges:

  • any change to commit rights must be done through a manual GitHub UI process, which is not tracked in the project's git history
  • commit rights are not granular (every Committer in the list above has commit rights on the entire code base, rather than their "Area")
  • integration of third-party test systems (downstream CI/CD) is difficult and not documented
  • permission to initiate a test run is limited to committers and requires an out-of-tree action to change