This is an automated email from the ASF dual-hosted git repository.
zfc pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-teaclave-website.git
The following commit(s) were added to refs/heads/master by this push:
new 4903af736 blog: polish display and remove podling reports
4903af736 is described below
commit 4903af7367adc25f348672dc1a5e472a93da4eb1
Author: Zhaofeng Chen <[email protected]>
AuthorDate: Sat Jul 19 02:42:16 2025 +0000
blog: polish display and remove podling reports
---
...0-01-01-podling-teaclave-report-january-2020.md | 70 ------------
...020-04-01-podling-teaclave-report-april-2020.md | 80 --------------
...2020-06-29-podling-teaclave-report-july-2020.md | 95 -----------------
...0-10-12-podling-teaclave-report-october-2020.md | 64 -----------
...1-01-01-podling-teaclave-report-january-2021.md | 68 ------------
...021-04-10-podling-teaclave-report-april-2021.md | 79 --------------
...21-08-02-podling-teaclave-report-august-2021.md | 83 ---------------
...1-10-06-podling-teaclave-report-october-2021.md | 96 -----------------
.../2022-01-12-podling-teaclave-report-jan-2022.md | 86 ---------------
.../2022-05-01-podling-teaclave-report-may-2022.md | 93 ----------------
...2024-05-31-podling-teaclave-report-june-2024.md | 91 ----------------
...025-04-02-podling-teaclave-report-april-2025.md | 69 ------------
...2025-07-02-podling-teaclave-report-july-2025.md | 118 ---------------------
site/src/css/custom.css | 10 ++
14 files changed, 10 insertions(+), 1092 deletions(-)
diff --git a/site/blog/2020-01-01-podling-teaclave-report-january-2020.md
b/site/blog/2020-01-01-podling-teaclave-report-january-2020.md
deleted file mode 100644
index 8382098c2..000000000
--- a/site/blog/2020-01-01-podling-teaclave-report-january-2020.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: Podling Teaclave Report - January 2020
-date: 2020-01-01
-author: Mingshen Sun
----
-
-
-## 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. 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 components: `teaclave_utils`, `teaclave_config`,
-`teaclave_cli`, `teaclave_binder`
- - 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)
diff --git a/site/blog/2020-04-01-podling-teaclave-report-april-2020.md
b/site/blog/2020-04-01-podling-teaclave-report-april-2020.md
deleted file mode 100644
index 09fb6b317..000000000
--- a/site/blog/2020-04-01-podling-teaclave-report-april-2020.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: Podling Teaclave Report - April 2020
-date: 2020-04-01
-author: Mingshen Sun
----
-
-
-## 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. 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, one external contributor has became our regular
- contributor.
- - Compared to the last report, we have seen more pull request from external
- contributors.
- - We received emails from some companies which are interested in the
- project and willing to make some contributions for the secure computing
- community.
- - Since we are mainly working on GitHub, with the help of the INFRA team,
- we can sync the notifications of GitHub with our mailing list.
-
-### How has the project developed since the last report?
-
- - Since last report, the whole project has been refactored to be more
- functional, as well as readable and approachable for new contributors.
- - We have rewrote the framework for implementing enclave services. Also, we
- have redesigned current services into seven core services
-including access control,
- authentication, execution, frontend, management, scheduler, and storage
- service. Communication protocols between services are defined in protobuf.
- - RPC between services has been redesigned to supported TLS-based
attestation.
- - We have added DCAP attestation algorithm in the platform so that people can
- deploy the system in environments without Intel's attestation service.
- - Communication between app and enclave has been also redesigned
-with better APIs.
- - All updates is currently in the `develop` branch. We plan to merge
-into `master`
- when main refactoring is done.
-
-### How would you assess the podling's maturity?
-Please feel free to add your own commentary.
-
- - [ ] 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, our mentors help use to resolve the mailing list moderator 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 approve the project name. (PODLINGNAMESEARCH-175)
diff --git a/site/blog/2020-06-29-podling-teaclave-report-july-2020.md
b/site/blog/2020-06-29-podling-teaclave-report-july-2020.md
deleted file mode 100644
index 258f0c7e1..000000000
--- a/site/blog/2020-06-29-podling-teaclave-report-july-2020.md
+++ /dev/null
@@ -1,95 +0,0 @@
----
-title: Podling Teaclave Report - July 2020
-date: 2020-06-29
-author: Mingshen Sun
----
-
-## 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?
-
-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)
diff --git a/site/blog/2020-10-12-podling-teaclave-report-october-2020.md
b/site/blog/2020-10-12-podling-teaclave-report-october-2020.md
deleted file mode 100644
index 52481754a..000000000
--- a/site/blog/2020-10-12-podling-teaclave-report-october-2020.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Podling Teaclave Report - October 2020
-date: 2020-10-12
-author: Mingshen Sun
----
-
-## 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 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)
diff --git a/site/blog/2021-01-01-podling-teaclave-report-january-2021.md
b/site/blog/2021-01-01-podling-teaclave-report-january-2021.md
deleted file mode 100644
index e876c51eb..000000000
--- a/site/blog/2021-01-01-podling-teaclave-report-january-2021.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: Podling Teaclave Report - January 2021
-date: 2021-01-01
-author: Mingshen Sun
----
-
-## 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 report 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)
diff --git a/site/blog/2021-04-10-podling-teaclave-report-april-2021.md
b/site/blog/2021-04-10-podling-teaclave-report-april-2021.md
deleted file mode 100644
index c1d5ef6d5..000000000
--- a/site/blog/2021-04-10-podling-teaclave-report-april-2021.md
+++ /dev/null
@@ -1,79 +0,0 @@
----
-title: Podling Teaclave Report - April 2021
-date: 2021-04-10
-author: Mingshen Sun
----
-
-## 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:
-
-- 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 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, Ran Duan (rduan), Committer
-
-### 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)
diff --git a/site/blog/2021-08-02-podling-teaclave-report-august-2021.md
b/site/blog/2021-08-02-podling-teaclave-report-august-2021.md
deleted file mode 100644
index ff11b8e99..000000000
--- a/site/blog/2021-08-02-podling-teaclave-report-august-2021.md
+++ /dev/null
@@ -1,83 +0,0 @@
----
-title: Podling Teaclave Report - August 2021
-date: 2021-08-02
-author: Mingshen Sun
----
-
-## 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:
-
-- 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 the last report, we have organized three monthly virtual meetups. 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 #4:
<https://teaclave.apache.org/blog/2021-04-29-teaclave-meetup-4/>
- - Teaclave Meetup #5:
<https://teaclave.apache.org/blog/2021-06-24-teaclave-meetup-5/>
- - Teaclave Meetup #6:
<https://teaclave.apache.org/blog/2021-07-29-teaclave-meetup-6/>
-
-We also have two new members:
- - 2021-07-09, Hongbo Chen (ya0guang), Commiter
- - 2021-07-25, Gordon King (garyw), Mentor
-
-### How has the project developed since the last report?
-
-Here are the summaries of recent progress of our three sub-projects:
-
-Teaclave:
- - Change the executor's payload type from `String` to `Vec<u8>`.
- - Unify the launch of teaclave services.
- - Add WebAssembly Executor and corresponding examples.
- - Upgrade Intel SGX SDK to the latest release (SGX 2.14.100.2, DCAP
1.11.100.2).
- - Some minor fixes of the building system and documentation.
-
-Teaclave SGX SDK:
- - Minor bug fixes.
-
-Teaclave TrustZone SDK:
- - Release the first Apache Incubator version 0.1.0: [Announcing Apache
Teaclave TrustZone SDK (Incubating)
0.1.0](https://teaclave.apache.org/blog/2021-06-16-announcing-teaclave-trustzone-sdk-0-1-0/).
- - Update to OP-TEE 3.13.0.
- - Implement the `iSocket` APIs and corresponding examples.
- - Implement loadable plugin for TA and corresponding examples.
- - Some minor fixes and repository cleanups.
-
-### 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-06-10: Apache Teaclave TrustZone SDK (incubating) 0.1.0
-
-### When were the last committers or PPMC members elected?
-
- 2021-07-25, Gordon King (garyw), Mentor
-
-### Have your mentors been helpful and responsive?
-
- Yes, our mentors work responsively to help us with electing new mentors,
proposing new features, 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)
diff --git a/site/blog/2021-10-06-podling-teaclave-report-october-2021.md
b/site/blog/2021-10-06-podling-teaclave-report-october-2021.md
deleted file mode 100644
index f0ab8d578..000000000
--- a/site/blog/2021-10-06-podling-teaclave-report-october-2021.md
+++ /dev/null
@@ -1,96 +0,0 @@
----
-title: Podling Teaclave Report - October 2021
-date: 2021-10-06
-author: Mingshen Sun
----
-
-## 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:
-
- - 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 the last report, we have organized one monthly virtual meetup (we
skipped one due to the public holiday). For each meetup, we have minutes
write-up published on the Teaclave blog.
- - Teaclave Meetup #7:
<https://teaclave.apache.org/blog/2021-08-26-teaclave-meetup-7/>
-
-Starting from this meetup, we use Google Calendar to show the meetup schedule
and location (i.e., the Zoom link).
- - Teaclave Community Calendar:
<https://calendar.google.com/calendar/u/0/[email protected]>
-
-We also have two new members elected since the last report:
- - 2021-09-20: Yuan Zhuang (Apache ID: TBD), Committer
- - 2021-09-20: Rong Fan (Apache ID: TBD), Commiter
-
-### How has the project developed since the last report?
-
-Here are the summaries of recent progress:
-
-Teaclave Faas Platform
-
- - Add TVM MNIST example
- - Add IDE helper script
- - Add license header and include SkyWalking Eyes in CI for automatic checking
- - Release v0.3.0: https://teaclave.apache.org/download/#teaclave
- - Consolidate `docker-compose` scripts for servers with different SGX drivers
-
-Teaclave TrustZone SDK
-
- - TEE Socket APIs and examples
- - Upgrade building docker to Ubuntu 20.04
- - Switch to GitHub Actions
- - Add -rs to examples and update test scripts
- - Update to OP-TEE 3.14.0
-
-Teaclave SGX SDK
-
- - Intel SGX SDK 2.14
- - Move wiki pages to the document directory for homepage rendering
- - Better project template
-
-Website
-
- - [blog] 使用 Teaclave SGX SDK 开发 SGX 应用 · Aug 24 2021:
<https://teaclave.apache.org/blog/2021-08-25-developing-sgx-application-with-teaclave-sgx-sdk/>
- - [blog] Announcing Apache Teaclave (incubating) 0.3.0 · Sep 30 2021:
<https://teaclave.apache.org/blog/2021-10-01-announcing-teaclave-0-3-0/>
- - [style] Update the contributors page to include Apache ID and tags for
each committers
-
-Community Collaboration
-
- - Teaclave/Intel: Integrating Graphene as a new Library OS executor
- - Teaclave/OP-TEE: Integrating examples in Rust TrustZone SDK in OP-TEE
-
-### 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-08-23: Apache Teaclave (incubating) 0.3.0
-
-### When were the last committers or PPMC members elected?
-
- - 2021-09-20: Yuan Zhuang (Apache ID: TBD), Committer
- - 2021-09-20: Rong Fan (Apache ID: TBD), Committer
-
-### 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)
diff --git a/site/blog/2022-01-12-podling-teaclave-report-jan-2022.md
b/site/blog/2022-01-12-podling-teaclave-report-jan-2022.md
deleted file mode 100644
index 754740799..000000000
--- a/site/blog/2022-01-12-podling-teaclave-report-jan-2022.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: Podling Teaclave Report - Jan 2022
-date: 2022-01-12
-author: Mingshen Sun
----
-
-## 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 the last report, we have organized two monthly virtual meetups. For each
meetup, we have write-ups published on the Teaclave blog.
- - Teaclave Meetup #8:
<https://teaclave.apache.org/blog/2021-10-14-teaclave-meetup-8/>
- - Teaclave Meetup #9:
<https://teaclave.apache.org/blog/2021-11-30-teaclave-meetup-9/>
-
-We also published a security advisory on a recent vulnerability on Intel SGX
SDK.
- - SECURITY ADVISORY OF SMASHEX AND CVE-2021-0186:
<https://teaclave.apache.org/blog/2021-10-25-security-advisory-of-smashex-and-cve-2021-0186/>
-
-To promote the recent TrustZone SDK in the Chinese community, we published a
blog on getting started with the SDK for newcomers.
- - 使用 TEACLAVE TRUSTZONE SDK 开发 TRUSTZONE 应用:
<https://teaclave.apache.org/blog/2021-10-15-developing-teaclave-application-with-teaclave-trustzone-sdk/>
-
-### How has the project developed since the last report?
-
-Here are the summaries of recent progress:
-
-Teaclave Faas Platform
-
- - [docker] start Teaclave docker services with auto-detection mechanism
- - Support selectively including executors (#574)
- - Optimize RPC memory footprint of serde (#577)
- - Persistent MockDB in test mode. (#580)
- - Flush DB and compact_range after dequeue operation
- - API updates (#588): UpdateFunction, ListFunciton, DeleteFunction,
UserUpdate, UserRegister, UserUpdate
- - Introduce role-based user management and access control
- - Bug fixes and code refactoring
-
-Teaclave TrustZone SDK
-
- - Update Rust toolchain to nightly-2021-09-20 an std to 1.56.1
-
-Teaclave SGX SDK
-
- - Support Intel SGX SDK 2.15, DCAP 1.12
- - Update rust toolchain to nightly-2021-11-01
-
-Website
-
- - [blog] Teaclave Meetup #8:
<https://teaclave.apache.org/blog/2021-10-14-teaclave-meetup-8/>
- - [blog] Teaclave Meetup #9:
<https://teaclave.apache.org/blog/2021-11-30-teaclave-meetup-9/>
- - [blog] SECURITY ADVISORY OF SMASHEX AND CVE-2021-0186:
<https://teaclave.apache.org/blog/2021-10-25-security-advisory-of-smashex-and-cve-2021-0186/>
- - [blog] 使用 TEACLAVE TRUSTZONE SDK 开发 TRUSTZONE 应用:
<https://teaclave.apache.org/blog/2021-10-15-developing-teaclave-application-with-teaclave-trustzone-sdk/>
-
-### 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-08-23: Apache Teaclave (incubating) 0.3.0
-
-### When were the last committers or PPMC members elected?
-
- - 2021-09-20: Yuan Zhuang (Apache ID: yuanz), Committer
- - 2021-09-20: Rong Fan (Apache ID: fanrong), Committer
-
-### 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)
diff --git a/site/blog/2022-05-01-podling-teaclave-report-may-2022.md
b/site/blog/2022-05-01-podling-teaclave-report-may-2022.md
deleted file mode 100644
index f7266192d..000000000
--- a/site/blog/2022-05-01-podling-teaclave-report-may-2022.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-title: Podling Teaclave Report - May 2022
-date: 2022-05-01
-author: Mingshen Sun
----
-
-## 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 the last report, we have organized three monthly virtual
-meetups. For each meetup, we have write-ups published on the Teaclave
-blog.
- - Teaclave Meetup #10:
-<https://teaclave.apache.org/blog/2022-02-24-teaclave-meetup-10/>
- - Teaclave Meetup #11:
-<https://teaclave.apache.org/blog/2022-03-31-teaclave-meetup-11/>
- - Teaclave Meetup #12:
-<https://teaclave.apache.org/blog/2022-04-28-teaclave-meetup-12/>
-
-We also released two versions of the Teaclave platform and Teaclave
-TrustZone seperately:
- - Teaclave 0.4.0:
-<https://teaclave.apache.org/blog/2022-04-18-announcing-teaclave-0-4-0/>
- - Teaclave TrustZone SDK 0.2.0:
-<https://teaclave.apache.org/blog/2022-04-18-announcing-teaclave-trustzone-sdk-0-2-0/>
-
-### How has the project developed since the last report?
-
-Here are the summaries of recent progress:
-
-Teaclave Faas Platform:
- - Merged PRs:
-<https://github.com/apache/incubator-teaclave/pulls?q=is%3Apr+is%3Aclosed+merged%3A2022-01-01..2022-05-01+base%3Amaster>
-
-Teaclave TrustZone SDK
- - Merged PRs:
-<https://github.com/apache/incubator-teaclave-trustzone-sdk/pulls?q=is%3Apr+is%3Aclosed+merged%3A2022-01-01..2022-05-01+base%3Amaster+>
-
-Teaclave SGX SDK
- - Merged PRs:
-<https://github.com/apache/incubator-teaclave-sgx-sdk/pulls?q=is%3Apr+is%3Aclosed+merged%3A2022-01-01..2022-05-01+base%3Amaster+>
-
-Website
-
- - [blog] Teaclave Meetup #10:
-<https://teaclave.apache.org/blog/2022-02-24-teaclave-meetup-10/>
- - [blog] Teaclave Meetup #11:
-<https://teaclave.apache.org/blog/2022-03-31-teaclave-meetup-11/>
- - [blog] Teaclave Meetup #12:
-<https://teaclave.apache.org/blog/2022-04-28-teaclave-meetup-12/>
- - [blog] Announcing Apache Teaclave (incubating) 0.4.0:
-<https://teaclave.apache.org/blog/2022-04-18-announcing-teaclave-0-4-0/>
- - [blog] Announcing Apache Teaclave TrustZone SDK (incubating)
-0.2.0:
<https://teaclave.apache.org/blog/2022-04-18-announcing-teaclave-trustzone-sdk-0-2-0/>
-
-### How would you assess the podling's maturity?
-
- - [ ] Initial setup
- - [ ] Working towards first release
- - [x] Community building
- - [ ] Nearing graduation
- - [ ] Other:
-
-### Date of last release:
-
- 2021-04-18: Apache Teaclave (incubating) TrustZone SDK 0.2.0
-
-### When were the last committers or PPMC members elected?
-
- - 2022-04-26: Qinkun Bao (Apache ID: qinkun), Committer
-
-### 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)
diff --git a/site/blog/2024-05-31-podling-teaclave-report-june-2024.md
b/site/blog/2024-05-31-podling-teaclave-report-june-2024.md
deleted file mode 100644
index ce28e3663..000000000
--- a/site/blog/2024-05-31-podling-teaclave-report-june-2024.md
+++ /dev/null
@@ -1,91 +0,0 @@
----
-
-title: Podling Teaclave Report - June 2024
-date: 2024-05-31
-author: Yuan Zhuang
-
----
-
-## 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 the last report, we have organized three monthly virtual
- meetups. For each meetup, we have write-ups published on the Teaclave
- blog <https://teaclave.apache.org/blog/>.
- - Teaclave Meetup #13:
- <https://teaclave.apache.org/blog/2022-06-29-teaclave-meetup-13/>
- - Teaclave Meetup #14:
- <https://teaclave.apache.org/blog/2022-12-14-teaclave-meetup-14/>
- - Teaclave Meetup #15:
- <https://teaclave.apache.org/blog/2022-12-21-teaclave-meetup-15/>
-
-
- Additionally, we introduced a new project Teaclave Java TEE SDK to
- our community:
-
<https://teaclave.apache.org/blog/2022-10-18-accepting-java-enclave-proposal/>
-
-### How has the project developed since the last report?
-
- Here are the summaries of recent progress:
-
-#### Teaclave Faas Platform:
- - New release 0.6.0:
- <https://github.com/apache/incubator-teaclave/releases/tag/v0.6.0>
- - Merged PRs:
-
<https://github.com/apache/incubator-teaclave/pulls?q=is%3Apr+is%3Aclosed+merged%3A2022-05-01..2024-05-31+base%3Amaster>
-
-#### Teaclave TrustZone SDK
- - New 'no-std' branch (set as recommended):
- <https://lists.apache.org/thread/f3l82o89hb0w43n27nw77oqcpo829qjd>
- - Merged PRs:
-
<https://github.com/apache/incubator-teaclave-trustzone-sdk/pulls?q=is%3Apr+is%3Aclosed+merged%3A2022-05-01..2024-05-31+base%3Amaster+>
-
-#### Teaclave SGX SDK
- - Preparing release v2.0.0:
- <https://github.com/apache/incubator-teaclave-sgx-sdk/tree/v2.0.0-preview>
- - Merged PRs:
-
<https://github.com/apache/incubator-teaclave-sgx-sdk/pulls?q=is%3Apr+is%3Aclosed+merged%3A2022-05-01..2024-05-31+base%3Amaster+>
-
-#### [NEW] Teaclave Java TEE SDK
- - The first release v0.1.0:
-
https://github.com/apache/incubator-teaclave-java-tee-sdk/releases/tag/v0.1.0
-
-
-### How would you assess the podling's maturity?
-
- - [ ] Initial setup
- - [ ] Working towards first release
- - [x] Community building
- - [ ] Nearing graduation
- - [ ] Other:
-
-### Date of last release:
-
- 2023-06-26: Apache Teaclave (incubating) FaaS Platfrom 0.6.0
-
-### When were the last committers or PPMC members elected?
-
- 2023-05-04: He Sun (Apache ID: hsun), 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)
diff --git a/site/blog/2025-04-02-podling-teaclave-report-april-2025.md
b/site/blog/2025-04-02-podling-teaclave-report-april-2025.md
deleted file mode 100644
index 402074712..000000000
--- a/site/blog/2025-04-02-podling-teaclave-report-april-2025.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
-
-title: Podling Teaclave Report - April 2025
-date: 2025-04-02
-author: [email protected]
-
----
-
-# Podling Teaclave Report - April 2025
-
-##
[Teaclave](https://cwiki.apache.org/confluence/display/INCUBATOR/April2025#teaclave)
-Teaclave is a universal secure computing platform, enabling writing
-memory-safe trusted applications in Rust running inside Trusted Execution
-Environment.
-
-Teaclave has been incubating since 2019-08-20.
-The Teaclave community is now working towards graduation.
-
-### [Three most important unfinished issues to address before
graduating:](https://cwiki.apache.org/confluence/display/INCUBATOR/April2025#three-most-important-unfinished-issues-to-address-before-graduating-13)
-
-- Practice future releases by adhering to the newly proposed quarterly
- release schedule.
-- Finalize discussions with the community to assess the project's overall
- maturity and readiness for graduation.
-- Conduct a thorough self-assessment to ensure all Apache graduation
- criteria are met.
-
-### [Are there any issues that the IPMC or ASF Board need to be aware
of?](https://cwiki.apache.org/confluence/display/INCUBATOR/April2025#are-there-any-issues-that-the-ipmc-or-asf-board-need-to-be-aware-of-13)
-As the Teaclave community is working toward graduation, we appreciate any
-guidance on the process. Please let us know if there are any additional
-steps we should take beyond our current plan. Thank you.
-
-### [How has the community developed since the last
report?](https://cwiki.apache.org/confluence/display/INCUBATOR/April2025#how-has-the-community-developed-since-the-last-report-13)
-
-- A new committer was elected.
-- Three new participants joined, and seven new projects were forked on
- GitHub.
-- Initiated collaboration with the OP-TEE community.
-
-### [How has the project developed since the last
report?](https://cwiki.apache.org/confluence/display/INCUBATOR/April2025#how-has-the-project-developed-since-the-last-report-13)
-
-- Made a release of the Teaclave TrustZone SDK with significant features.
-- Established a quarterly release plan aligned with the OP-TEE community.
-- Added Web3 use cases for building trusted applications using the
- Teaclave TrustZone SDK.
-
-### [Date of last
release:](https://cwiki.apache.org/confluence/display/INCUBATOR/April2025#date-of-last-release-13)
-
-We are in the process of releasing Apache Teaclave TrustZone SDK
-(incubating) v0.4.0 and are currently seeking binding votes from PMC
-members on the following thread:
-https://lists.apache.org/thread/8mstnqpoo0hy1sy8f96dyrkyrmcdwz2z
-
-### [When were the last committers or PPMC members
elected?](https://cwiki.apache.org/confluence/display/INCUBATOR/April2025#when-were-the-last-committers-or-ppmc-members-elected-13)
-
-2025-01-21
-
-### Have your mentors been helpful and responsive?
-
-We appreciate our mentors' support. However, we need help from PMC members
-to vote on our release, as delays in securing votes slow down the release
-process.
-
-### [Is the PPMC managing the podling's brand /
trademarks?](https://cwiki.apache.org/confluence/display/INCUBATOR/April2025#is-the-ppmc-managing-the-podlings-brand--trademarks-13)
-
-Are 3rd parties respecting and correctly using the podlings name and brand? If
not what actions has the PPMC taken to correct this? Has the VP, Brand approved
the project name?
-
-Yes.
-#
\ No newline at end of file
diff --git a/site/blog/2025-07-02-podling-teaclave-report-july-2025.md
b/site/blog/2025-07-02-podling-teaclave-report-july-2025.md
deleted file mode 100644
index cebcd9e43..000000000
--- a/site/blog/2025-07-02-podling-teaclave-report-july-2025.md
+++ /dev/null
@@ -1,118 +0,0 @@
----
-
-title: Podling Teaclave Report - July 2025
-date: 2025-07-02
-author: [email protected]
-
----
-
-# Podling Teaclave Report - July 2025
-
-##
[Teaclave](https://cwiki.apache.org/confluence/display/INCUBATOR/July2025#teaclave)
-Teaclave is a universal secure computing platform, enabling writing
-memory-safe trusted applications in Rust running inside Trusted Execution
-Environment.
-
-Teaclave has been incubating since 2019-08-20.
-The Teaclave community is now working towards graduation.
-
-### [Three most important unfinished issues to address before
graduating:](https://cwiki.apache.org/confluence/display/INCUBATOR/July2025#three-most-important-unfinished-issues-to-address-before-graduating-13)
-
-- Complete all requirements of the Project Maturity Assessment.
-- Practice future releases by adhering to a quarterly release schedule.
-- Conduct a thorough self-assessment to ensure all Apache graduation criteria
are met.
-
-### [Are there any issues that the IPMC or ASF Board need to be aware
of?](https://cwiki.apache.org/confluence/display/INCUBATOR/July2025#are-there-any-issues-that-the-ipmc-or-asf-board-need-to-be-aware-of-13)
-
-As the Teaclave community works toward graduation, we welcome guidance
-along the process. We also invite any active IPMC members interested in the
-project to consider becoming mentors. Thank you.
-
-
-### [How has the community developed since the last
report?](https://cwiki.apache.org/confluence/display/INCUBATOR/July2025#how-has-the-community-developed-since-the-last-report-13)
-
-- We have a new mentor joining the project.
-- We have a new participant contributing to the project.
-- We have a new release manager working on the Teaclave TrustZone SDK v0.5.0
release.
-
-
-### [How has the project developed since the last
report?](https://cwiki.apache.org/confluence/display/INCUBATOR/July2025#how-has-the-project-developed-since-the-last-report-13)
-
-- Initiated releasing Teaclave TrustZone SDK v0.5.0, pending for collecting
binding votes in the general incubator mailing list.
-- Working on the Teaclave Maturity Assessment. During the assessment, we
identified several areas for improvement, including the website page and
repository reorganization. Work is in progress to address these and meet all
requirements.
-
-
-
-
-### [Date of last
release:](https://cwiki.apache.org/confluence/display/INCUBATOR/July2025#date-of-last-release-13)
-
-2025-06-03
-
-### [When were the last committers or PPMC members
elected?](https://cwiki.apache.org/confluence/display/INCUBATOR/July2025#when-were-the-last-committers-or-ppmc-members-elected-13)
-
-2025-01-21
-
-### Have your mentors been helpful and responsive?
-
-We have faced challenges with slow release cycles, partly due to the limited
number of binding votes from mentors. To address this, we have invited new
mentors to join the community and are actively engaging with contributors to
ensure smoother release processes. We have also reached out to existing mentors
and received positive responses and renewed support. We plan to continue this
proactive approach in future releases to ensure timely and successful outcomes.
-
-### [Is the PPMC managing the podling's brand /
trademarks?](https://cwiki.apache.org/confluence/display/INCUBATOR/July2025#is-the-ppmc-managing-the-podlings-brand--trademarks-13)
-
-Are 3rd parties respecting and correctly using the podlings name and brand? If
not what actions has the PPMC taken to correct this? Has the VP, Brand approved
the project name?
-
-Yes.
-
-##
[Teaclave](https://cwiki.apache.org/confluence/display/INCUBATOR/July2025#teaclave)
-Teaclave is a universal secure computing platform, enabling writing
-memory-safe trusted applications in Rust running inside Trusted Execution
-Environment.
-
-Teaclave has been incubating since 2019-08-20.
-The Teaclave community is now working towards graduation.
-
-### [Three most important unfinished issues to address before
graduating:](https://cwiki.apache.org/confluence/display/INCUBATOR/July2025#three-most-important-unfinished-issues-to-address-before-graduating-13)
-
-- Complete all requirements of the Project Maturity Assessment.
-- Practice future releases by adhering to a quarterly release schedule.
-- Conduct a thorough self-assessment to ensure all Apache graduation criteria
are met.
-
-### [Are there any issues that the IPMC or ASF Board need to be aware
of?](https://cwiki.apache.org/confluence/display/INCUBATOR/July2025#are-there-any-issues-that-the-ipmc-or-asf-board-need-to-be-aware-of-13)
-
-As the Teaclave community works toward graduation, we welcome guidance
-along the process. We also invite any active IPMC members interested in the
-project to consider becoming mentors. Thank you.
-
-
-### [How has the community developed since the last
report?](https://cwiki.apache.org/confluence/display/INCUBATOR/July2025#how-has-the-community-developed-since-the-last-report-13)
-
-- We have a new mentor joining the project.
-- We have a new participant contributing to the project.
-- We have a new release manager working on the Teaclave TrustZone SDK v0.5.0
release.
-
-
-### [How has the project developed since the last
report?](https://cwiki.apache.org/confluence/display/INCUBATOR/July2025#how-has-the-project-developed-since-the-last-report-13)
-
-- Initiated releasing Teaclave TrustZone SDK v0.5.0, pending for collecting
binding votes in the general incubator mailing list.
-- Working on the Teaclave Maturity Assessment. During the assessment, we
identified several areas for improvement, including the website page and
repository reorganization. Work is in progress to address these and meet all
requirements.
-
-
-
-
-### [Date of last
release:](https://cwiki.apache.org/confluence/display/INCUBATOR/July2025#date-of-last-release-13)
-
-2025-06-03
-
-### [When were the last committers or PPMC members
elected?](https://cwiki.apache.org/confluence/display/INCUBATOR/July2025#when-were-the-last-committers-or-ppmc-members-elected-13)
-
-2025-01-21
-
-### Have your mentors been helpful and responsive?
-
-We have faced challenges with slow release cycles, partly due to the limited
number of binding votes from mentors. To address this, we have invited new
mentors to join the community and are actively engaging with contributors to
ensure smoother release processes. We have also reached out to existing mentors
and received positive responses and renewed support. We plan to continue this
proactive approach in future releases to ensure timely and successful outcomes.
-
-### [Is the PPMC managing the podling's brand /
trademarks?](https://cwiki.apache.org/confluence/display/INCUBATOR/July2025#is-the-ppmc-managing-the-podlings-brand--trademarks-13)
-
-Are 3rd parties respecting and correctly using the podlings name and brand? If
not what actions has the PPMC taken to correct this? Has the VP, Brand approved
the project name?
-
-Yes.
-
diff --git a/site/src/css/custom.css b/site/src/css/custom.css
index 2bc6a4cfd..4a83e5403 100644
--- a/site/src/css/custom.css
+++ b/site/src/css/custom.css
@@ -28,3 +28,13 @@
--ifm-color-primary-lightest: #4fddbf;
--docusaurus-highlighted-code-line-bg: rgba(0, 0, 0, 0.3);
}
+
+/* Hide year headings in blog sidebar - targeting the specific class */
+.yearGroupHeading_ndGK {
+ display: none !important;
+}
+
+/* Alternative: Hide year headings in blog sidebar using general selector */
+.blog-sidebar h3 {
+ display: none !important;
+}
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
