ApacheCon is Coming 9-12 Sept. 2019 - Las Vegas The Apache Software Foundation
Apache 20th Anniversary Logo

Community-led development "The Apache Way"

Apache Support Logo

This was extracted (@ 2020-09-29 22:10) from a list of minutes which have been approved by the Board.
Please Note The Board typically approves the minutes of the previous meeting at the beginning of every Board meeting; therefore, the list below does not normally contain details from the minutes of the most recent Board meeting.

Meeting times vary, the exact schedule is available to ASF Members and Officers, search for "calendar" in the Foundation's private index page (svn:foundation/private-index.html).

MesaTEE

18 Dec 2019

MesaTEE is the next-gen solution to enable general computing service for
security-critical scenarios. It will allow even the most sensitive data to
be securely processed to enable offshore businesses without leakage.

MesaTEE has been incubating since 2019-08-19.

### Three most important unfinished issues to address before graduating:

  1. Finish the initial setup for MesaTEE and its sub-repos.
  2. Choose a suitable name for MesaTEE and rename the repos.
  3. Make the access control mechanism and RPC framework more scalable and
  ergonomic.

### Are there any issues that the IPMC or ASF Board need to be aware of?

  Regarding to the CI system, we do have some problem with migrating the
  webhooks. MesaTEE definitely requires CI runs on customized hardware.
  However, the Apache INFRA team is pretty conservative on adopting novel CI
  systems which support customized hardware and self-hosted agent, such as
  Github Action, Drone etc. We observed that Apache projects depending on CI
  running on customized hardware, such as incubator-tvm, experienced
  difficulty to migrate its webhooks and was challenged several times on the
  reason of using customized hardware in CI. Besides, we observed that
  Apache Spark is using Github Action, while we are blocked on it (see
  INFRA-19381).

  The bootstrapping process seems slow due to the above problem. We have a
  temporary workaround to use our Drone CI system. It leverages a sync bot
  which automatically sync up incubator-mesatee and a testing fork and
  triggers the webook of the testing fork. For management, we force the
  developers to put the link of CI status for each PR in their PR message.
  It works, but we really desire the integration to new CI and self-hosted
  CI agents.

  For the renaming, we found a new name "Teaclave" which is not used
  anywhere.

### How has the community developed since the last report?

  MesaTEE has one more contributor this month, and merged 50+ PRs from 13
  contributors.

### How has the project developed since the last report?

  We implemented the new access control system in MesaPy, and merged into
  MesaTEE. The new access control system is much more powerful and flexible
  than traditional user/role/group based access control system, and is
  memory-safe and trusted with the help of MesaPy and MesaTEE.

  We improved the MesaTEE infrastructure to make it k8s-friendly. We
  refactored parts of the MesaTEE system and are doing on others.

  We improved the build system. We deprecated the old-fashioned Makefile,
  and only kept the cmake system.

  We figured out a temporary solution for integrating the Drone CI system
  and self-hosted agents by syncing up incubator-mesatee and testing fork,
  and triggering tests on the testing fork.

  We are improving the built-in RPC framework to use prost to automatically
  generate Rust source codes from protobuf's protocol definitions.

  We fixed a couple of bugs reported from the open source community.

### How would you assess the podling's maturity?
Please feel free to add your own commentary.

  - [x] Initial setup
  - [ ] Working towards first release
  - [ ] Community building
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:

  N/A

### When were the last committers or PPMC members elected?

  N/A

### Have your mentors been helpful and responsive?

  We received instructions on the project renaming process from our mentors.
  Thanks to every one!

### Is the PPMC managing the podling's brand / trademarks?

  Yes. We don't find any 3rd parties incorrectly using the podling's name
  and brand for now. Also, PPMC is working on the podling name search.

### Signed-off-by:
 - [x] (MesaTEE) Felix Cheung
        Comments:  sounds like the issue in INFRA-19381 on the way, is that
        still blocked or just need more time?
 - [X] (MesaTEE) Furkan Kamaci
        Comments:
 - [ ] (MesaTEE) Jianyong Dai
        Comments:
 - [X] (MesaTEE) Luciano Resende
        Comments:
 - [ ] (MesaTEE) Matt Sicker
        Comments:
 - [ ] (MesaTEE) Zhijie Shen
        Comments:

### IPMC/Shepherd notes:

20 Nov 2019

MesaTEE is the next-gen solution to enable general computing service for
security-critical scenarios. It will allow even the most sensitive data to
be securely processed to enable offshore businesses without leakage.

MesaTEE has been incubating since 2019-08-19.

### Three most important unfinished issues to address before graduating:

  1. Finish the initial setup for MesaTEE and its sub-repos.
  2. Choose a suitable name for MesaTEE and rename the repos.
  3. Make the access control mechanism and RPC framework more scalable and
  ergonomic.

### Are there any issues that the IPMC or ASF Board need to be aware of?

  Regarding to the CI system, we do have some problem with migrating the
  webhooks. Currently the CI system is managed using drone, an open-sourced
  CI infrastructure. It requires R+W access to the Github organization to
  set up the webhooks. However, the INFRA team does not grant W access to
  3rd party infrastructure. Should we migrate to Github Action, or try to
  get a way to keep using drone? We started a discussion in dev mailing
  list, but the answer from mentor differs from the answer from INFRA team.

  The bootstrapping process seems slow due to the above problem. If we
  cannot find a way to properly set up the CI system, we cannot merge any
  codes after the repo transfer completed. To this end, we are doing our
  best on fitting into Github Action.

  Lack of communication in dev mailing list. We, the PPMC members, realized
  that we cannot only talk offline. So we are starting to use the dev
  mailing list for discussion and issue tracking, and we received lots of
  comments and feedbacks from mentors. Next time I think we will do better
  on the collaboration and be more interactive with the lovely mentors.

  Since Baidu does not donate the brand name "MesaTEE" to ASF, we need a
  new brand name. To solve this, PODLINGNAMESEARCH issue 169 is initiated
  one month ago. And recently the discussion on new name seems come to an
  conclusion in dev mailing list. The next step is to do the rename as
  discussed.

### How has the community developed since the last report?

  Now we have 12 contributors for MesaTEE main repo, and 16 contributors
  for MesaTEE-SGX. Since the first day of incubation, MesaTEE merged 3 PRs
  from the community, and MesaTEE-SGX merged 7 PRs from the community.

### How has the project developed since the last report?

  Since the MesaTEE project joined incubator, we improved its build system,
  SDK, CLI, and fit it to the latest Intel SGX SDK v2.6. MesaTEE-SGX and
  its ecosystem has been periodically updated so as to eliminate
  bugs/vulnerabilities from 3rd party libraries.

  We just finished repo transfer for MesaTEE-SGX, and we are still working
  on repo transfer for MesaTEE main repo.

  It is worth mention that the comprehensive tests of MesaTEE and
  MesaTEE-SGX helped finding bugs in their dependencies, and we managed to fix
  them in upstream libraries. One case is the "official" numeric library family
  of Rust ecosystem: rust-num. It's build script did not work well with
  MesaTEE's build system and we filed [num-traits issue
  139](https://github.com/rust-num/num-traits/issues/139). Then we fixed in
  [PR 140](https://github.com/rust-num/num-traits/pull/140). More fixes in
  this family are pending to merge. Another case is in the official Intel
  SGX SDK. MesaTEE-SGX's CI reported failure after migrating to Intel SGX SDK
  v2.7 release. We created [linux-sgx issue
  457](https://github.com/intel/linux-sgx/issues/457) and Intel resolved it
  a week later in [PR 461](https://github.com/intel/linux-sgx/pull/461).

### How would you assess the podling's maturity?
Please feel free to add your own commentary.

  - [x] Initial setup
  - [ ] Working towards first release
  - [ ] Community building
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:

  N/A

### When were the last committers or PPMC members elected?

  N/A

### Have your mentors been helpful and responsive?

  Luciano helped us a lot. He helped with catching up the schedule and the
  SGA. We learned a lot from him and started managing MesaTEE in Apache's
  style.

  Zhijie Shen helped us a lot with the initial setup, such as signing the
  iCLA, account creation, mailing lists.

  Justin Mclean helped us a lot on this report. We received a lot of
  feedbacks from him and we updated this report according to these
  comments. These comments are really helpful and make us realize how to
  work in the Apache way. Thanks Justin!

  We appreciate the help from the mentor group. Mentors are really
  professional and helpful!

### Signed-off-by:
 - [x] (MesaTEE) Felix Cheung
   Comments:
 - [X] (MesaTEE) Furkan Kamaci
   Comments:
 - [ ] (MesaTEE) Jianyong Dai
   Comments:
 - [x] (MesaTEE) Luciano Resende
   Comments: For the rename, I would recommend only performing the rename
    after a namesearch is completed. Please close the old one, and create a
    new one for the new name.
 - [x] (MesaTEE) Matt Sicker
   Comments: Slow start, but renaming is being done early on to minimize
    problems.
 - [ ] (MesaTEE) Zhijie Shen
   Comments:

### IPMC/Shepherd notes:

16 Oct 2019

MesaTEE is a framework for universal secure computing

MesaTEE has been incubating since 2019-08-20.

### Three most important unfinished issues to address before graduating:

 1.
 2.
 3.

### Are there any issues that the IPMC or ASF Board need to be aware of?

 Slow starting up.

### How has the community developed since the last report?

 Initial committers have not yet signed up to mailing lists
 (only 4 subscribers, all mentors?)

### How has the project developed since the last report?

 Initial setup in incubator (mailing list, whimsy).

### How would you assess the podling's maturity?
Please feel free to add your own commentary.

 - [x] Initial setup
 - [ ] Working towards first release
 - [ ] Community building
 - [ ] Nearing graduation
 - [ ] Other:

### Date of last release:

 (none)

### When were the last committers or PPMC members elected?

 (none)

### Have your mentors been helpful and responsive?
 No answer

### Signed-off-by:

 - [ ] (mesatee) Felix Cheung
    Comments:
 - [X] (mesatee) Furkan Kamaci
    Comments:
 - [ ] (mesatee) Jianyong Dai
    Comments:
 - [X] (mesatee) Luciano Resende
    Comments:  Mailing lists were created Sep 24 and
               Podling roaster is updated. Have requested
               podling members to use mailing list and start
               moving their git repositories.
 - [x] (mesatee) Matt Sicker
    Comments:  I filed the account requests for all the initial
               committers on 3 Oct as well as an initial suitable
               name search ticket.
 - [ ] (mesatee) Zhijie Shen
    Comments:

### IPMC/Shepherd notes:

 The project is just starting up and did not get a report ready this
 month.
 The champion need to work on migrating the initial committers and
 eventually wider developer community to the apache.org mailing lists.
 -stain