You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@teaclave.apache.org by Duan Ran <rd...@apache.org> on 2022/10/15 19:31:58 UTC
Re: Podling Teaclave Report Reminder - October 2022
Hi kirs
---
title: Podling Teaclave Report - Oct 2022
date: 2022-10-16
author: Ran duan
---
## Teaclave
### Three most important unfinished issues to address before graduating:
- Improve project structure and documentation
- Grow the community (attracting more committers, contributors, users)
- 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 last report, we were pleased to receive a project donation request from en external team. They would like to dontate their projects to teaclave. We are facilitating the donation process and will receive an apache incubation proposal for this project in the near future.
We also have two new PPMC members elected since the last report:
- 2022-08-16: Yuan Zhuang (volcano0dr)
- 2022-08-17: Ran Duan DemesneGH)
### How has the project developed since the last report?
Here are the summaries of recent progress of our three sub-projects:
Teaclave Faas Platform
v0.4.0 new changes:
- Merged PRs: <https://github.com/apache/incubator-teaclave/pulls?q=is%3Apr+is%3Aclosed+merged%3A2022-05-01..2022-10-01+base%3Amaster+>
Teaclave TrustZone SDK
v0.2.0 new changes:
- Add tls server/client example
- Add signature verification example
- Add Building Rust CA as Android ELF documentation
- Add Expanding TA Secure Memory on QEMUv8 documentation
- Merged PRs: <https://github.com/apache/incubator-teaclave-trustzone-sdk/pulls?q=is%3Apr+is%3Aclosed+merged%3A2022-05-01..2022-10-01+base%3Amaster+>
Teaclave SGX SDK
Since the last report, this project is developing v2.0 and maintaining v1.1.
v2.0 is a revamped version. It is much more developer friendly compared to v1.1.
- Supports cargo build + no_std, xargo build and cargo-std-aware mode.
- Refactored Intel's SDK using Rust. Only a small portion of Intel's SDK is required.
- Improved testing framework. sgx_tstd is well tested now.
- No need to maintain 100+ 3rd party dependencies. Most dependencies are use-able without any change.
- Branch: <https://github.com/apache/incubator-teaclave-sgx-sdk/tree/v2.0.0-preview>
v1.1 new changes:
- Version bump to 1.1.5
- Support intel sgx sdk 2.17.1 and and DCAP 1.14
- Support rust-nightly-2022-02-23
- Fix thread_local macro
- Merged PRs: <https://github.com/apache/incubator-teaclave-sgx-sdk/pulls?q=is%3Apr+is%3Aclosed+merged%3A2022-05-01..2022-10-01+base%3Amaster+>
### 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-04-18
### When were the last committers or PPMC members elected?
- 2022-08-16: Yuan Zhuang (Apache ID: yuanz), PPMC
- 2022-08-17: Ran Duan (Apache ID: rduan), PPMC
### Have your mentors been helpful and responsive?
Yes, our mentors work responsively to help us with electing new mentors, developing new features, fixing bugs, and expanding the community.
### 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)
Ran Duan
On 2022/09/30 15:09:11 kirs@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, 19 October 2022.
> 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, October 05).
>
> 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/October2022
>
> 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-unsubscribe@teaclave.apache.org
> For additional commands, e-mail: dev-help@teaclave.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@teaclave.apache.org
For additional commands, e-mail: dev-help@teaclave.apache.org