Community-led development "The Apache Way"
This was extracted (@ 2021-04-07 00: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).
Teaclave is a universal secure computing platform.
Teaclave has been incubating since 2019-08-20.
### Three most important unfinished issues to address before graduating:
1. Improve project structure and documentation
2. Grow the community (attracting more committers, contributors, users)
3. Publish more Apache releases
### Are there any issues that the IPMC or ASF Board need to be aware of?
None.
### How has the community developed since the last report?
- We received contributions from a new external contributor.
- We found a new project using Teaclave SGX SDK called Veracruz, which is
a
framework for defining and deploying collaborative, privacy-preserving
computations amongst a group of mutually mistrusting individuals.
- We summarized the community and projects powered by Teaclave and
published
a blog on our homepage.
- Rust TrustZone SDK will be accepted in Teaclave as a subproject. The
community
is discussing and voting the acceptance.
- The community has accepted a new committer.
### How has the project developed since the last report?
- Add PCA function in the builtin executor.
- Add exposed password checking function in the builtin executor.
- Add the attestation subcommand to display attestation reports form the
Intel attestation service.
- Add document to support deploying on Azure confidential computing VM.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2020-10-09 (version 0.1.0)
### When were the last committers or PPMC members elected?
2020-10-22 (Ran Duan, commiter, rduan@apache)
### Have your mentors been helpful and responsive?
Yes, our mentors are very helpful and responsive on our discussion about
security reporting and new projects acceptance voting.
### Is the PPMC managing the podling's brand / trademarks?
We don't find any 3rd parties incorrectly using the podling's name and
brand.
The VP, Brand has approved the project name. (PODLINGNAMESEARCH-175)
### Signed-off-by:
- [x] (teaclave) Felix Cheung
Comments:
- [X] (teaclave) Furkan Kamaci
Comments:
- [ ] (teaclave) Jianyong Dai
Comments:
- [ ] (teaclave) Matt Sicker
Comments:
- [ ] (teaclave) Zhijie Shen
Comments:
### IPMC/Shepherd notes:
Teaclave is a universal secure computing platform, making computation on
privacy-sensitive data safe and simple.
Teaclave has been incubating since 2019-08-20.
### Three most important unfinished issues to address before graduating:
1. Improve project structure and documentation
2. Grow the community (attracting more committers, contributors, users)
3. Publish Apache releases (resolving logistics on Apache release)
### Are there any issues that the IPMC or ASF Board need to be aware of?
None.
### How has the community developed since the last report?
Since the last report, we received contributions from a new contributor.
We also received many issue reports and questions regarding the usages, bugs,
and roadmap of Teaclave. Also, we presented the Teaclave project in recent
ApacheCon to the community and received some useful feedback.
### How has the project developed since the last report?
The main goal of development since the last report is to resolve logistics
towards the first Apache release. This includes license checking, building
system improvement, documentation and write-ups. On Oct 9th, the Teaclave
community and incubator has passed 0.1.0 release voting.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2020-10-09
### When were the last committers or PPMC members elected?
We haven't started new committers or PPMC members elections yet.
Currently,
our work focuses on the first Apache release. We'll switch to community
building in the next quarter. Currently, we already have potential
candidates for the new PPMC members election.
### Have your mentors been helpful and responsive?
Yes. They have been helpful and very responsive for the first public
release.
### Is the PPMC managing the podling's brand / trademarks?
We don't find any 3rd parties incorrectly using the podling's name and
brand. The VP, Brand has approved the project name.
(PODLINGNAMESEARCH-175)
### Signed-off-by:
- [X] (teaclave) Felix Cheung
Comments: congrats on the first release
- [X] (teaclave) Furkan Kamaci
Comments:
- [ ] (teaclave) Jianyong Dai
Comments:
- [ ] (teaclave) Luciano Resende
Comments:
- [ ] (teaclave) Matt Sicker
Comments:
- [ ] (teaclave) Zhijie Shen
Comments:
### IPMC/Shepherd notes:
Teaclave is a universal secure computing platform, making computation
on privacy-sensitive data safe and simple.
Teaclave has been incubating since 2019-08-20.
### Three most important unfinished issues to address before graduating:
1. Improve project structure and documentation
2. Grow the community (attracting more committers, contributors, users)
3. Publish Apache releases (resolving logistics on Apache release)
### Are there any issues that the IPMC or ASF Board need to be aware of?
No.
### How has the community developed since the last report?
Since the last report, we started to reach out to people using the
project and collect suggestions and encourage them to join in the
community. We have found four organizations and eight projects that
are using either the Teaclave platform and Teaclave's Rust SGX SDK.
We also created a website for the project:
https://teaclave.apache.org/, which contains project description,
community, contributors, documentations and blog posts.
We started a thread to discuss the logo design, but haven't received
any proposal for now. We will drive this issue in the next few weeks.
We observed more people posting feature suggestions and
build/deployment issues. More than five new contributors begin to
contribute bug fixes and introduce new examples.
We started preparing the first Apache release such as logistics on
licenses of third-party libraries.
### How has the project developed since the last report?
Since the last report, we have completed the development roadmap
towards the first public release
(https://github.com/apache/incubator-teaclave/issues/121) proposed
last year. We began to put more efforts on improving documents and
building community.
We wrote many documents in recent weeks including:
- Try: Tutorials on using the Teaclave platform.
- Design: Some explanations of design choices we made.
- Contribute: Documents on contributing to Teaclave, such as
debugging tips and Rust development guideline.
- Codebase: Documents for each sub-directory (i.e., libraries in
Teaclave).
- API Docs: Generated API documentations like APIs of Client SDK.
We also provided more examples to help beginners to understand the
basic usages of the projects.
### How would you assess the podling's maturity?
- [ ] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
N/A
### When were the last committers or PPMC members elected?
We haven't started new committers or PPMC members elections yet.
Currently, our work focuses on improving the documents to make the
project more approachable for newcomers. Additionally, we see some
regular contributors recently mainly focus on helping to improve
examples, SDK, etc.
### Have your mentors been helpful and responsive?
Yes, our mentors help us with the website development and logo design.
Also, our mentors provided valuable thoughts regarding Intel's recent
security issues.
### Is the PPMC managing the podling's brand / trademarks?
We don't find any 3rd parties incorrectly using the podling's name and
brand. The VP, Brand has approved the project name.
(PODLINGNAMESEARCH-175)
### Signed-off-by:
- [X] (teaclave) Felix Cheung
Comments: good progress!
- [X] (teaclave) Furkan Kamaci
Comments:
- [ ] (teaclave) Jianyong Dai
Comments:
- [X] (teaclave) Luciano Resende
Comments:
- [ ] (teaclave) Matt Sicker
Comments:
- [ ] (teaclave) Zhijie Shen
Comments:
### IPMC/Shepherd notes:
Teaclave is a universal secure computing platform.
Teaclave has been incubating since 2019-08-20.
### Three most important unfinished issues to address before graduating:
1. Improving project structure and documentation
2. Grow the community (committers, contributors, users)
3. Publish Apache release
### Are there any issues that the IPMC or ASF Board need to be aware of?
No.
### How has the community developed since the last report?
- Since last report, one external contributor has became our regular
contributor.
- Compared to the last report, we have seen more pull request from
external contributors.
- We received emails from some companies which are interested in the
project and willing to make some contributions for the secure computing
community.
- Since we are mainly working on GitHub, with the help of the INFRA team,
we can sync the notifications of GitHub with our mailing list.
### How has the project developed since the last report?
- Since last report, the whole project has been refactored to be more
functional, as well as readable and approachable for new contributors.
- We have rewrote the framework for implementing enclave services. Also,
we have redesigned current services into seven core services
including access control, authentication, execution, frontend,
management,
scheduler, and storage service. Communication protocols between services
are defined in protobuf.
- RPC between services has been redesigned to supported TLS-based
attestation.
- We have added DCAP attestation algorithm in the platform so that people
can deploy the system in environments without Intel's attestation service.
- Communication between app and enclave has been also redesigned
with better APIs.
- All updates is currently in the `develop` branch. We plan to merge
into `master` when main refactoring is done.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [X] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
N/A
### When were the last committers or PPMC members elected?
We haven't started new committers or PPMC members elections yet.
Currently, our
work focus on improving the design and documents to make the project more
approachable for newcomers.
### Have your mentors been helpful and responsive?
Yes, our mentors help use to resolve the mailing list moderator issues.
### Is the PPMC managing the podling's brand / trademarks?
We don't find any 3rd parties incorrectly using the podling's name and
brand.
The VP, Brand has approved the project name. (PODLINGNAMESEARCH-175)
### Signed-off-by:
- [X] (teaclave) Felix Cheung
Comments:
- [X] (teaclave) Furkan Kamaci
Comments:
- [ ] (teaclave) Jianyong Dai
Comments:
- [ ] (teaclave) Luciano Resende
Comments:
- [ ] (teaclave) Matt Sicker
Comments:
- [ ] (teaclave) Zhijie Shen
Comments:
### IPMC/Shepherd notes:
Teaclave is a universal secure computing platform.
Teaclave has been incubating since 2019-08-20.
### Three most important unfinished issues to address before graduating:
1. Improving project structure and documentation
2. Grow the community (committers, contributors, users)
3. Publish Apache release
### Are there any issues that the IPMC or ASF Board need to be aware of?
No.
### How has the community developed since the last report?
- Since last report, we planned to schedule an online meetup recently.
- We have also received contributions of two new contributors.
- We draft a roadmap RFC for discussion.
- We use GitHub issues to track bugs, features, enhancements. Issues
labeled with "good first issues" is more approachable for newcomers.
### How has the project developed since the last report?
- Resolve all renaming issues of INFRA (INFRA-19532)
- Refactor four core components
- Rewrite README.md to clearly explain the project's highlights in
security, functionality, and usability.
- Start to use protobuf for RPC definition
- SGX SDK starts to use Intel SGX SDK v2.7.1
### How would you assess the podling's maturity?
- [ ] Initial setup
- [x] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
N/A
### When were the last committers or PPMC members elected?
We haven't started new committers or PPMC members elections yet.
Currently, our work focus on improving the design and documents to
make the project more approachable for newcomers.
### Have your mentors been helpful and responsive?
Yes. Last month, we changed name from MesaTEE to Teaclave. There are a
lot of changes need to be done. The mentors and infra teams help us a
lot on the transfer.
### Is the PPMC managing the podling's brand / trademarks?
We don't find any 3rd parties incorrectly using the podling's name and
brand. The VP, Brand has approve the project name.
(PODLINGNAMESEARCH-175)
### Signed-off-by:
- [ ] (teaclave) Felix Cheung
Comments:
- [X] (teaclave) Furkan Kamaci
Comments:
- [ ] (teaclave) Jianyong Dai
Comments:
- [X] (teaclave) Luciano Resende
Comments:
- [X] (teaclave) Matt Sicker
Comments: Thanks to some mailing list configuration updates,
communication is happening more often on-list.
- [ ] (teaclave) Zhijie Shen
Comments:
### IPMC/Shepherd notes: