Dear community, Sorry for the late submission.
Below is the report, I'll also submit to the wiki page (https://cwiki.apache.org/confluence/display/INCUBATOR/April2021#teaclave). Please reply if I miss anything important. Thanks! ## Teaclave 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 have started monthly virtual meetups for three times. Many people from the community share their usage experience of Teaclave. Also, we invited some contributors to talk about some technical details of the design and implementation. For each meetup, we have minutes write-up published on the Teaclave blog. - Teaclave Meetup #1: https://teaclave.apache.org/blog/2021-01-27-teaclave-meetup-1/ - Teaclave Meetup #2: https://teaclave.apache.org/blog/2021-02-24-teaclave-meetup-2/ - Teaclave Meetup #3: https://teaclave.apache.org/blog/2021-03-24-teaclave-meetup-3/ In addition, we have one more project (Crust Network) powered by Teaclave joined in our "Powered By" page on the Teaclave homepage. - https://teaclave.apache.org/powered-by/ ### How has the project developed since the last report? During this period, we also accepted the Rust OP-TEE TrustZone SDK project to Teaclave as a sub-project, named as Teaclave TrustZone SDK. Similar to Teaclave SGX SDK, Teaclave TrustZone SDK will be the foundation of the Teaclave FaaS platform to support multiple trusted execution environments. - Welcome Rust OP-TEE TrustZone SDK TO Teaclave: https://teaclave.apache.org/blog/2021-03-14-welcome-rust-optee-trustzone-sdk/ We published a project roadmap in 2021: - Roadmap in 2021: Project Maturity and Community Buildup: https://teaclave.apache.org/blog/2021-01-19-roadmap-in-2021-project-maturity-and-community-buildup/ We also announce the 0.2.0 release. In 0.2.0, we focus on various components including built-in functions, SDKs in different languages, docker, command line interface, documents, etc. - Announcing Apache Teaclave (incubating) 0.2.0: https://teaclave.apache.org/blog/2021-03-01-announcing-teaclave-0-2-0/ ### 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: 2021-03-02: Apache Teaclave (incubating) 0.2.0 ### When were the last committers or PPMC members elected? 2020-10-22 ### Have your mentors been helpful and responsive? Yes, our mentors work responsively to help us with accepting new project donation into Teaclave. ### 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) Best, Mingshen On Fri, Apr 9, 2021 at 12:29 PM Mingshen Sun <ms...@apache.org> wrote: > > Sorry, I missed this email. I’ll work on it today. Thanks for the reminder. > > Mingshen > > On Fri, Apr 9, 2021 at 12:28 PM Furkan KAMACI <furkankam...@gmail.com> wrote: >> >> Hi, >> >> Is there anybody working on the report? Feel free to ask if you have any >> questions. >> >> Kind Regards, >> Furkan KAMACI >> >> On Tue, Mar 30, 2021 at 8:45 AM <jmcl...@apache.org> wrote: >> >> > Dear podling, >> > >> > This email was sent by an automated system on behalf of the Apache >> > Incubator PMC. It is an initial reminder to give you plenty of time to >> > prepare your quarterly board report. >> > >> > The board meeting is scheduled for Wed, 21 April 2021. >> > The report for your podling will form a part of the Incubator PMC >> > report. The Incubator PMC requires your report to be submitted 2 weeks >> > before the board meeting, to allow sufficient time for review and >> > submission (Wed, April 07). >> > >> > Please submit your report with sufficient time to allow the Incubator >> > PMC, and subsequently board members to review and digest. Again, the >> > very latest you should submit your report is 2 weeks prior to the board >> > meeting. >> > >> > Candidate names should not be made public before people are actually >> > elected, so please do not include the names of potential committers or >> > PPMC members in your report. >> > >> > Thanks, >> > >> > The Apache Incubator PMC >> > >> > Submitting your Report >> > >> > ---------------------- >> > >> > Your report should contain the following: >> > >> > * Your project name >> > * A brief description of your project, which assumes no knowledge of >> > the project or necessarily of its field >> > * A list of the three most important issues to address in the move >> > towards graduation. >> > * Any issues that the Incubator PMC or ASF Board might wish/need to be >> > aware of >> > * How has the community developed since the last report >> > * How has the project developed since the last report. >> > * How does the podling rate their own maturity. >> > >> > This should be appended to the Incubator Wiki page at: >> > >> > https://cwiki.apache.org/confluence/display/INCUBATOR/April2021 >> > >> > Note: This is manually populated. You may need to wait a little before >> > this page is created from a template. >> > >> > Note: The format of the report has changed to use markdown. >> > >> > Mentors >> > ------- >> > >> > Mentors should review reports for their project(s) and sign them off on >> > the Incubator wiki page. Signing off reports shows that you are >> > following the project - projects that are not signed may raise alarms >> > for the Incubator PMC. >> > >> > Incubator PMC >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org >> > For additional commands, e-mail: dev-h...@teaclave.apache.org >> > >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
