
This was extracted (@ 2021-01-21 20: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).
Report was filed, but display is awaiting the approval of the Board minutes.
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, 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: