Dear Teaclave community, Here is the report for 2020 Q4. Feel free to comment on the report. Thanks.
To mentors, I have uploaded the report to the wiki page. [1] Best, Mingshen [1] https://cwiki.apache.org/confluence/display/INCUBATOR/January2021#teaclave ## Teaclave 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 ### When were the last committers or PPMC members elected? 2020-10-22 ### 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) On Wed, Jan 6, 2021 at 10:48 AM Mingshen Sun <ms...@apache.org> wrote: > > Hi Dave, > > Thanks for the reminder. Don't know why I missed this email. > > To mentors, I will prepare the report today. > > Best, > Mingshen > > On Wed, Jan 6, 2021 at 10:44 AM Dave Fisher <w...@apache.org> wrote: > > > > A reminder to discuss and submit a report. > > > > Thanks, > > Dave > > > > On 2020/12/24 00:35:06, 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, 20 January 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, January 06). > > > > > > 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/January2021 > > > > > > 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 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
