Thanks a lot for the feedback.

The report has been added to the Board Meeting Agenda and approved by the
Shepherd.

The next report will be due next month.

Best,
Zhaofeng

On Tue, Sep 9, 2025 at 12:14 PM Gordon <[email protected]> wrote:

> LGTM as well, thanks
>
> On Mon, Sep 8, 2025 at 8:42 PM Mingshen Sun <[email protected]> wrote:
>
> > Thanks! I don't have any issue with this report.
> >
> > On Mon, Sep 8, 2025 at 8:35 PM Zhaofeng Chen <[email protected]> wrote:
> > >
> > > Dear community,
> > >
> > > As part of our responsibilities as a newly graduated Top-Level Project,
> > we
> > > need to submit our first report to the Apache Board this month. I have
> > > drafted a report as attached.
> > >
> > > Please take a look and share any comments or suggestions. In
> particular,
> > > let me know if:
> > > - There are corrections or updates needed for project activity,
> releases,
> > > or community changes.
> > > - Anything should be highlighted more (or less) for the Board’s
> > attention.
> > >
> > > The submitted content is editable until Sep.10th, so any feedback
> before
> > > then would be appreciated.
> > >
> > > Thanks,
> > > Zhaofeng
> > >
> > > =============== Submitted Draft =============
> > > # Apache Teaclave Board Report - September 2025
> > >
> > > ## Description
> > > Apache Teaclave provides SDKs for building memory-safe applications on
> > > Trusted
> > > Execution Environments.
> > >
> > > ## Project Status
> > > **Status:** New
> > > Apache Teaclave graduated as a Top-Level Project on August 21,
> > > 2025. Since graduation, the community has completed the transition to
> TLP
> > > infrastructure, including GitHub repositories, distribution servers,
> > website
> > > updates, and project documentation.
> > >
> > > ## Summary of Project Health and Status
> > > Since graduation, Apache Teaclave has completed the transition from
> > > incubation, updated all references to reflect TLP status, and is
> > preparing
> > > its
> > > first release as a TLP. The community remains active with steady
> > development
> > > and moderate mailing list discussions. Current focus is on completing
> the
> > > v0.6.0 release and strengthening developer tooling for building
> > applications
> > > on TEEs.
> > >
> > > ## Issues for Board Attention
> > > There are no Board-level issues at this time.
> > >
> > > ## Recent Releases
> > > - 2025-07-17: Teaclave TrustZone SDK v0.5.0
> > > - WIP: Teaclave TrustZone SDK v0.6.0 (first release as a TLP)
> > >
> > > ## Project Activity
> > >
> > > ### Development Activity
> > > - Ongoing work to improve build/test environment for TEE applications.
> > > - Introduced new branches showcasing Web3 use cases, with plans to
> merge
> > > into
> > >   the main branch.
> > > - Active effort to eliminate all `cargo clippy` warnings and enforce
> > > stricter
> > >   CI checks.
> > > - ~30–40 commits merged this quarter.
> > >
> > > ### Community Activity
> > > - Developer mailing list: moderate activity (~20 threads since
> > graduation).
> > > - No new committers or PMC members since graduation.
> > >
> > > ## Current Plans
> > > - **Short term:**
> > >   - Release Teaclave TrustZone SDK v0.6.0.
> > >   - Enforce strict CI checks (clippy, lint, tests) to enhance codebase
> > >     quality.
> > >
> > > - **Medium term:**
> > >   - Open source additional real-world SDK use cases (e.g., Web3
> > scenarios).
> > >   - Align release cadence with OP-TEE’s quarterly releases.
> > >
> > > ## Community Changes
> > > - At graduation: 18 initial PMC members.
> > > - Current: 18 PMC members, no new additions.
> > > - No new committers or PMC members elected since graduation.
> > > - PMC membership represents a healthy diversity of organizations.
> > >
> > > ## Project Branding
> > > - No branding issues.
> > > - Website and download pages comply with Apache branding requirements.
> > >
> > > ## Legal Issues
> > > - No legal issues to report.
> > >
> > > ## Infrastructure
> > > - No infrastructure concerns at this time.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
>

Reply via email to