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 4da2307ed chore: update words and format (#32)
4da2307ed is described below
commit 4da2307ed84de83bfb45e454965ee64dc772d806
Author: tison <[email protected]>
AuthorDate: Wed Jul 30 10:22:37 2025 +0800
chore: update words and format (#32)
Signed-off-by: tison <[email protected]>
---
site/blog/2019-08-20-apache-incubation-proposal.md | 357 ++++++++++-----------
site/blog/2025-07-08-repo-reorg-community-focus.md | 2 +-
site/docs/community/becoming-a-member.md | 4 +-
site/docs/community/community.md | 2 +-
site/docs/community/contributing.md | 8 +-
site/docs/community/contributors.md | 76 ++---
site/docs/community/maturity.md | 109 +++----
site/docs/community/release-guide.md | 2 +-
site/docs/overview.md | 21 +-
9 files changed, 293 insertions(+), 288 deletions(-)
diff --git a/site/blog/2019-08-20-apache-incubation-proposal.md
b/site/blog/2019-08-20-apache-incubation-proposal.md
index 71c82f0ef..ee0c098af 100644
--- a/site/blog/2019-08-20-apache-incubation-proposal.md
+++ b/site/blog/2019-08-20-apache-incubation-proposal.md
@@ -4,14 +4,13 @@ date: 2019-08-20
author: The Teaclave PPMC
---
-```
MesaTEE Apache Incubation Proposal
-= Abstract =
+## Abstract
MesaTEE is a framework for universal secure computing.
-= Proposal =
+## Proposal
MesaTEE is the next-gen solution to enable general computing service for
security-critical scenarios. It will allow even the most sensitive data to
@@ -21,13 +20,13 @@ The solution combines the advanced Hybrid Memory Safety
(HMS) model and the
power of the Trusted Computing technologies (e.g., TPM) as well as the
Confidential Computing technologies (e.g., Intel SGX).
- * Code base:
- * https://github.com/mesalock-linux/mesatee
- * https://github.com/baidu/rust-sgx-sdk
- * Website: https://mesatee.org
- * Documentation: https://mesatee.org/doc/mesatee_sdk/
+* Code base:
+ * https://github.com/mesalock-linux/mesatee
+ * https://github.com/baidu/rust-sgx-sdk
+* Website: https://mesatee.org
+* Documentation: https://mesatee.org/doc/mesatee_sdk/
-= Background =
+## Background
The emerging technologies of big data analytics, machine learning, cloud/edge
computing, and blockchain are significantly boosting our productivity, but at
@@ -67,7 +66,7 @@ greatly accelerate the development of the next generation of
big data business
applications, and it is also of great importance to promoting AI in all
business
areas.
-= Rationale =
+## Rationale
MesaTEE stack redefines future AI and big data analytics by providing a trusted
and secure offshore computing environment. The confidentiality and privacy of
@@ -81,7 +80,7 @@
https://github.com/mesalock-linux/mesatee/blob/master/docs/case_study.md.
We believe that Apache way of open source community empowers MesaTEE to attract
a diverse set of contributors who can bring new ideas into the project.
-= Initial Goals =
+## Initial Goals
* Move the existing codebase, website, documentation, and mailing lists to an
Apache-hosted infrastructure.
@@ -89,7 +88,7 @@ a diverse set of contributors who can bring new ideas into
the project.
* Ensure all dependencies are compliant with Apache License version 2.0.
* Incrementally develop and release per Apache guidelines.
-= Current Status =
+## Current Status
The MesaTEE project (and its sub-project Rust SGX SDK) has been designed and
developed at Baidu since 2017, and was open sourced under the Apache License,
@@ -98,7 +97,7 @@ Version 2.0 in 2019. The source code is currently hosted at
github.com
https://github.com/baidu/rust-sgx-sdk), which will seed the Apache git
repository.
-== Meritocracy ==
+### Meritocracy
We are fully committed to open, transparent, and meritocratic interactions with
our community. In fact, one of the primary motivations for us to enter the
@@ -107,11 +106,11 @@ ensure meritocracy. This will eventually help incorporate
the best ideas back
into the project and enable contributors to continue investing their time in
the
project. We already have some guidelines to help external contributors:
- *
https://github.com/mesalock-linux/mesatee/blob/master/docs/rust_guideline.md
- *
https://github.com/mesalock-linux/mesatee/blob/master/docs/how_to_add_your_function.md
- * https://github.com/mesalock-linux/mesatee/blob/master/CODE_OF_CONDUCT.md
+* https://github.com/mesalock-linux/mesatee/blob/master/docs/rust_guideline.md
+*
https://github.com/mesalock-linux/mesatee/blob/master/docs/how_to_add_your_function.md
+* https://github.com/mesalock-linux/mesatee/blob/master/CODE_OF_CONDUCT.md
-== Community ==
+### Community
The MesaTEE community is fairly young. Since our sub-project (Rust SGX SDK) was
open sourced in 2017, we received many contributions from various companies and
@@ -119,12 +118,12 @@ individual researchers
(https://github.com/baidu/rust-sgx-sdk/pulls). Our
primary goal during the incubation would be to grow the community and groom our
existing active contributors for committers.
-== Core Developers ==
+### Core Developers
Current core developers work at Baidu. We are confident that incubation will
help us grow a diverse community in an open and collaborative way.
-== Alignment ==
+### Alignment
MesaTEE is designed as a framework for universal secure computing. This is
complementary to the Apache's projects, providing a trusted and secure
computing
@@ -135,16 +134,16 @@ to drive the future of the project in alignment with the
other Apache projects
for the benefit of thousands of organizations that already leverage these
projects.
-= Known Risks =
+## Known Risks
-== Orphaned Products ==
+### Orphaned Products
The risk of abandonment of MesaTEE is low. MesaTEE has been incubated at Baidu
for over two years. Baidu is committed to the further development of the
project
and will keep investing resources towards the Apache processes and community
building, during the incubation period.
-== Inexperience with Open Source ==
+### Inexperience with Open Source
Even though the initial committers are new to the Apache world, some have
considerable open source experience - Yu Ding, Yiming Jing, Mingshen Sun. We
@@ -152,18 +151,18 @@ have been successfully managing the current open source
community, answering
questions, and taking feedback already. Moreover, we hope to obtain guidance
and
mentorship from current ASF members to help us succeed in the incubation.
-== Length of Incubation ==
+### Length of Incubation
We expect the project to be in incubation for 2 years or less.
-== Homogenous Developers ==
+### Homogenous Developers
Currently, the lead developers for MesaTEE are from Baidu. However, we have an
active set of early contributors/collaborators from Alibaba and other
companies,
which we hope will increase the diversity going forward. Once again, a primary
motivation for the incubation is to facilitate this in the Apache way.
-== Reliance on Salaried Developers ==
+### Reliance on Salaried Developers
Both the current committers and early contributors have several years of core
expertise around designing trusted computing systems. Current committers are
@@ -173,7 +172,7 @@ expect they will be able to actively engage in the project
either because they
will be working in similar areas even with newer employers or out of belief in
the project.
-== Relationships with Other Apache Products ==
+### Relationships with Other Apache Products
To the best of our knowledge, there are no directly competing projects with
MesaTEE that offer all of the feature set - memory safety, secure computing,
@@ -183,220 +182,218 @@ collaboration with such Apache projects and
incorporating changes to MesaTEE or
contributing patches to other projects, with the goal of making it easier for
the community at large, to adopt these open source technologies.
-== Excessive Fascination with the Apache Brand ==
+### Excessive Fascination with the Apache Brand
The Apache Brand is very respected. We are very honored to have the opportunity
to join ASF, with the understanding that its brand policies shall be respected.
And we hope Apache can help us build the ecosystem around MesaTEE and attract
more developers.
-= Documentation =
+### Documentation
- * Detailed documentation: https://github.com/mesalock-linux/mesatee
- * MesaTEE SDK API documentation: https://mesatee.org/doc/mesatee_sdk/
+* Detailed documentation: https://github.com/mesalock-linux/mesatee
+* MesaTEE SDK API documentation: https://mesatee.org/doc/mesatee_sdk/
-= Initial Source =
+## Initial Source
The codebase is currently hosted on Github:
- * https://github.com/mesalock-linux/mesatee
- * https://github.com/baidu/rust-sgx-sdk
+* https://github.com/mesalock-linux/mesatee
+* https://github.com/baidu/rust-sgx-sdk
During incubation, the codebase will be migrated to an Apache infrastructure.
The source code of MesaTEE is under Apache version 2.0 License, while Rust SGX
SDK is under BSD 3-Clauses License.
-= Source and Intellectual Property Submission Plan =
+## Source and Intellectual Property Submission Plan
We will work with the committers to get ICLAs signed. We will provide a
Software
Grant Agreement from an authorized signer per
https://www.apache.org/licenses/software-grant-template.pdf
-= External Dependencies =
+## External Dependencies
MesaTEE directly depends on these third-party Rust crates:
- * adler32, 1.0.3, BSD-3-Clause
- * aho-corasick, 0.7.4, Unlicense/MIT
- * array_tool, 1.0.3, MIT
- * assert_matches, 1.3.0, MIT/Apache-2.0
- * autocfg, 0.1.4, Apache-2.0/MIT
- * base64, 0.10.1, MIT/Apache-2.0
- * bincode, 1.1.4, MIT
- * bit-vec, 0.6.1, MIT/Apache-2.0
- * bitflags, 1.1.0, MIT/Apache-2.0
- * byteorder, 1.3.2, MIT/Unlicense
- * bytes, 0.5.0, MIT
- * cc, 1.0.37, MIT/Apache-2.0
- * cfg-if, 0.1.9, MIT/Apache-2.0
- * chrono, 0.4.7, MIT/Apache-2.0
- * color_quant, 1.0.1, MIT
- * crc32fast, 1.2.0, MIT
- * ctor, 0.1.9, Apache-2.0
- * deflate, 0.7.20, MIT/Apache-2.0
- * either, 1.5.2, MIT/Apache-2.0
- * env_logger, 0.6.2, MIT/Apache-2.0
- * erased-serde, 0.3.9, MIT
- * fnv, 1.0.6, Apache-2.0
- * getrandom, 0.1.6, MIT
- * ghost, 0.1.0, MIT/Apache-2.0
- * gif, 0.10.2, MIT/Apache-2.0
- * gzip-header, 0.3.0, MIT/Apache-2.0
- * half, 1.3.0, MIT/Apache-2.0
- * hashbrown, 0.3.1, Apache-2.0/MIT
- * heapsize, 0.4.2, MIT/Apache-2.0
- * hex, 0.3.2, MIT
- * http, 0.1.17, MIT/Apache-2.0
- * httparse, 1.3.4, MIT/Apache-2.0
- * humantime, 1.2.0, MIT/Apache-2.0
- * image, 0.21.0, MIT
- * inflate, 0.4.5, MIT
- * inventory, 0.1.3, MIT
- * inventory-impl, 0.1.3, MIT
- * iovec, 0.2.0, MIT/Apache-2.0
- * itertools, 0.8.0, MIT/Apache-2.0
- * itoa, 0.4.4, MIT
- * jpeg-decoder, 0.1.15, MIT
- * lazy_static, 1.3.0, MIT/Apache-2.0
- * libc, 0.2.59, MIT
- * linked-hash-map, 0.5.2, MIT/Apache-2.0
- * log, 0.4.7, MIT
- * lzw, 0.10.0, MIT/Apache-2.0
- * matrixmultiply, 0.2.2, MIT/Apache-2.0
- * md5, 0.6.1, Apache-2.0/MIT
- * memchr, 2.2.1, Unlicense/MIT
- * memory_units, 0.3.0, MPL-2.0
- * net2, 0.2.33, MIT/Apache-2.0
- * num, 0.2.0, MIT/Apache-2.0
- * num-bigint, 0.2.2, MIT/Apache-2.0
- * num-complex, 0.2.3, MIT/Apache-2.0
- * num-integer, 0.1.41, MIT/Apache-2.0
- * num-iter, 0.1.39, MIT/Apache-2.0
- * num-rational, 0.2.2, MIT/Apache-2.0
- * num-traits, 0.2.8, MIT/Apache-2.0
- * parity-wasm, 0.31.3, MIT/Apache-2.0
- * png, 0.14.1, MIT/Apache-2.0
- * proc-macro2, 0.4.30, MIT/Apache-2.0
- * profiler_builtins, 0.1.0, profiler_builtins
- * quick-error, 1.2.2, MIT/Apache-2.0
- * quote, 0.3.15, MIT
- * quote, 0.6.13, MIT
- * rand, 0.6.5, MIT/Apache-2.0
- * rand_core, 0.4.0, MIT/Apache-2.0
- * rand_hc, 0.1.0, MIT/Apache-2.0
- * rand_pcg, 0.1.2, MIT/Apache-2.0
- * rawpointer, 0.1.0, MIT/Apache-2.0
- * regex, 1.1.9, MIT/Apache-2.0
- * regex-syntax, 0.6.8, MIT/Apache-2.0
- * ring, 0.14.6, ISC-style
- * rulinalg, 0.4.2, MIT
- * rustls, 0.15.2, Apache-2.0/ISC/MIT
- * rusty-machine, 0.5.4, MIT
- * ryu, 1.0.0, Apache-2.0
- * sct, 0.5.0, Apache-2.0/ISC/MIT
- * serde, 1.0.94, MIT
- * serde_cbor, 0.10.0, MIT/Apache-2.0
- * serde_derive, 1.0.94, MIT
- * serde_json, 1.0.40, MIT
- * sha1, 0.6.0, BSD-3-Clause
- * sha2, 0.8.0, sha2
- * spin, 0.5.0, MIT
- * syn, 0.11.11, MIT
- * syn, 0.15.39, MIT
- * synom, 0.11.3, MIT/Apache-2.0
- * termcolor, 1.0.5, Unlicense
- * thread_local, 0.3.6, Apache-2.0/MIT
- * tiff, 0.3.1, MIT
- * toml, 0.5.1, MIT/Apache-2.0
- * typetag, 0.1.3, MIT
- * typetag-impl, 0.1.3, MIT
- * ucd-util, 0.1.3, MIT/Apache-2.0
- * unicode-xid, 0.0.4, MIT/Apache-2.0
- * unicode-xid, 0.1.0, MIT/Apache-2.0
- * utf8-ranges, 1.0.3, Unlicense/MIT
- * uuid, 0.7.4, Apache-2.0
- * wabt, 0.6.0, Apache-2.0
- * wasmi, 0.5.0, MIT/Apache-2.0
- * wasmi-validation, 0.1.0, MIT/Apache-2.0
- * webpki, 0.19.1, ISC-style
- * webpki-roots, 0.16.0, MPL-2.0
- * winapi, 0.3.7, MIT/Apache-2.0
- * winapi-i686-pc-windows-gnu, 0.4.0, MIT/Apache-2.0
- * winapi-util, 0.1.2, Unlicense/MIT
- * winapi-x86_64-pc-windows-gnu, 0.4.0, MIT/Apache-2.0
- * wincolor, 1.0.1, Unlicense/MIT
- * yasna, 0.3.1, MIT/Apache-2.0
+* adler32, 1.0.3, BSD-3-Clause
+* aho-corasick, 0.7.4, Unlicense/MIT
+* array_tool, 1.0.3, MIT
+* assert_matches, 1.3.0, MIT/Apache-2.0
+* autocfg, 0.1.4, Apache-2.0/MIT
+* base64, 0.10.1, MIT/Apache-2.0
+* bincode, 1.1.4, MIT
+* bit-vec, 0.6.1, MIT/Apache-2.0
+* bitflags, 1.1.0, MIT/Apache-2.0
+* byteorder, 1.3.2, MIT/Unlicense
+* bytes, 0.5.0, MIT
+* cc, 1.0.37, MIT/Apache-2.0
+* cfg-if, 0.1.9, MIT/Apache-2.0
+* chrono, 0.4.7, MIT/Apache-2.0
+* color_quant, 1.0.1, MIT
+* crc32fast, 1.2.0, MIT
+* ctor, 0.1.9, Apache-2.0
+* deflate, 0.7.20, MIT/Apache-2.0
+* either, 1.5.2, MIT/Apache-2.0
+* env_logger, 0.6.2, MIT/Apache-2.0
+* erased-serde, 0.3.9, MIT
+* fnv, 1.0.6, Apache-2.0
+* getrandom, 0.1.6, MIT
+* ghost, 0.1.0, MIT/Apache-2.0
+* gif, 0.10.2, MIT/Apache-2.0
+* gzip-header, 0.3.0, MIT/Apache-2.0
+* half, 1.3.0, MIT/Apache-2.0
+* hashbrown, 0.3.1, Apache-2.0/MIT
+* heapsize, 0.4.2, MIT/Apache-2.0
+* hex, 0.3.2, MIT
+* http, 0.1.17, MIT/Apache-2.0
+* httparse, 1.3.4, MIT/Apache-2.0
+* humantime, 1.2.0, MIT/Apache-2.0
+* image, 0.21.0, MIT
+* inflate, 0.4.5, MIT
+* inventory, 0.1.3, MIT
+* inventory-impl, 0.1.3, MIT
+* iovec, 0.2.0, MIT/Apache-2.0
+* itertools, 0.8.0, MIT/Apache-2.0
+* itoa, 0.4.4, MIT
+* jpeg-decoder, 0.1.15, MIT
+* lazy_static, 1.3.0, MIT/Apache-2.0
+* libc, 0.2.59, MIT
+* linked-hash-map, 0.5.2, MIT/Apache-2.0
+* log, 0.4.7, MIT
+* lzw, 0.10.0, MIT/Apache-2.0
+* matrixmultiply, 0.2.2, MIT/Apache-2.0
+* md5, 0.6.1, Apache-2.0/MIT
+* memchr, 2.2.1, Unlicense/MIT
+* memory_units, 0.3.0, MPL-2.0
+* net2, 0.2.33, MIT/Apache-2.0
+* num, 0.2.0, MIT/Apache-2.0
+* num-bigint, 0.2.2, MIT/Apache-2.0
+* num-complex, 0.2.3, MIT/Apache-2.0
+* num-integer, 0.1.41, MIT/Apache-2.0
+* num-iter, 0.1.39, MIT/Apache-2.0
+* num-rational, 0.2.2, MIT/Apache-2.0
+* num-traits, 0.2.8, MIT/Apache-2.0
+* parity-wasm, 0.31.3, MIT/Apache-2.0
+* png, 0.14.1, MIT/Apache-2.0
+* proc-macro2, 0.4.30, MIT/Apache-2.0
+* profiler_builtins, 0.1.0, profiler_builtins
+* quick-error, 1.2.2, MIT/Apache-2.0
+* quote, 0.3.15, MIT
+* quote, 0.6.13, MIT
+* rand, 0.6.5, MIT/Apache-2.0
+* rand_core, 0.4.0, MIT/Apache-2.0
+* rand_hc, 0.1.0, MIT/Apache-2.0
+* rand_pcg, 0.1.2, MIT/Apache-2.0
+* rawpointer, 0.1.0, MIT/Apache-2.0
+* regex, 1.1.9, MIT/Apache-2.0
+* regex-syntax, 0.6.8, MIT/Apache-2.0
+* ring, 0.14.6, ISC-style
+* rulinalg, 0.4.2, MIT
+* rustls, 0.15.2, Apache-2.0/ISC/MIT
+* rusty-machine, 0.5.4, MIT
+* ryu, 1.0.0, Apache-2.0
+* sct, 0.5.0, Apache-2.0/ISC/MIT
+* serde, 1.0.94, MIT
+* serde_cbor, 0.10.0, MIT/Apache-2.0
+* serde_derive, 1.0.94, MIT
+* serde_json, 1.0.40, MIT
+* sha1, 0.6.0, BSD-3-Clause
+* sha2, 0.8.0, sha2
+* spin, 0.5.0, MIT
+* syn, 0.11.11, MIT
+* syn, 0.15.39, MIT
+* synom, 0.11.3, MIT/Apache-2.0
+* termcolor, 1.0.5, Unlicense
+* thread_local, 0.3.6, Apache-2.0/MIT
+* tiff, 0.3.1, MIT
+* toml, 0.5.1, MIT/Apache-2.0
+* typetag, 0.1.3, MIT
+* typetag-impl, 0.1.3, MIT
+* ucd-util, 0.1.3, MIT/Apache-2.0
+* unicode-xid, 0.0.4, MIT/Apache-2.0
+* unicode-xid, 0.1.0, MIT/Apache-2.0
+* utf8-ranges, 1.0.3, Unlicense/MIT
+* uuid, 0.7.4, Apache-2.0
+* wabt, 0.6.0, Apache-2.0
+* wasmi, 0.5.0, MIT/Apache-2.0
+* wasmi-validation, 0.1.0, MIT/Apache-2.0
+* webpki, 0.19.1, ISC-style
+* webpki-roots, 0.16.0, MPL-2.0
+* winapi, 0.3.7, MIT/Apache-2.0
+* winapi-i686-pc-windows-gnu, 0.4.0, MIT/Apache-2.0
+* winapi-util, 0.1.2, Unlicense/MIT
+* winapi-x86_64-pc-windows-gnu, 0.4.0, MIT/Apache-2.0
+* wincolor, 1.0.1, Unlicense/MIT
+* yasna, 0.3.1, MIT/Apache-2.0
Note that this is not an exhaustive dependency list and only direct
-dependencies
-of MesaTEE's trusted libs are included.
+dependencies of MesaTEE's trusted libs are included.
-== Cryptography ==
+### Cryptography
MesaTEE uses following cryptographic libraries:
- * ring (https://github.com/briansmith/ring): a Rust crypto library based on
-BoringSSL
- * rustls: a Rust TLS library
- * sgx_tcrypto in Intel SGX SDK (https://software.intel.com/en-us/sgx/sdk)
+* ring (https://github.com/briansmith/ring): a Rust crypto library based on
BoringSSL
+* rustls: a Rust TLS library
+* sgx_tcrypto in Intel SGX SDK (https://software.intel.com/en-us/sgx/sdk)
-= Required Resources =
+## Required Resources
-== Mailing lists ==
+### Mailing lists
- * [email protected] (with moderated subscriptions)
- * [email protected]
- * [email protected]
- * [email protected]
+* [email protected] (with moderated subscriptions)
+* [email protected]
+* [email protected]
+* [email protected]
-== Git Repositories ==
+### Git Repositories
Upon entering incubation, we want to transfer the existing repos from
https://github.com/mesalock-linux/mesatee and
https://github.com/baidu/rust-sgx-sdk to Apache organization in GitHub like:
- * https://github.com/apache/incubator-mesatee
- * https://github.com/apache/incubator-mesatee-rust-sgx-sdk
+* https://github.com/apache/incubator-mesatee
+* https://github.com/apache/incubator-mesatee-rust-sgx-sdk
-== Issue Tracking ==
+### Issue Tracking
-MesaTEE currently uses GitHub to track issues. Would like to continue doing
-so.
+MesaTEE currently uses GitHub to track issues. Would like to continue doing so.
-== Continuous Integration Service ==
+## Continuous Integration Service
MesaTEE currently uses self-hosted continuous integration (CI) service which
can
help developers to automatically test commits. The CI service involves several
nodes which support Intel SGX. We would like to continue doing so.
-= Initial Committers =
+## Initial Committers
The list is sorted alphabetically:
- * Mingshen Sun <mssun at mesatee.org>
- * Pei Wang <wangpei at mesatee.org>
- * Rundong Zhou <rundongzhou at mesatee.org>
- * Tao Wei <lenx at mesatee.org>
- * Tongxin Li <litongxin at mesatee.org>
- * Yiming Jing <jingyiming at mesatee.org>
- * Yu Ding <d at mesatee.org>
- * Yulong Zhang <ylzhang at mesatee.org>
- * Zhaofeng Chen <zf at mesatee.org>
+```
+* Mingshen Sun <mssun at mesatee.org>
+* Pei Wang <wangpei at mesatee.org>
+* Rundong Zhou <rundongzhou at mesatee.org>
+* Tao Wei <lenx at mesatee.org>
+* Tongxin Li <litongxin at mesatee.org>
+* Yiming Jing <jingyiming at mesatee.org>
+* Yu Ding <d at mesatee.org>
+* Yulong Zhang <ylzhang at mesatee.org>
+* Zhaofeng Chen <zf at mesatee.org>
+```
-= Sponsors =
+## Sponsors
-== Champion ==
+### Champion
* Zhijie Shen <[email protected]>
-== Nominated Mentors ==
+### Nominated Mentors
* Jianyong Dai <[email protected]>
* Luciano Resende <[email protected]>
* Matt Sicker
* Furkan Kamaci
-== Sponsoring Entity ==
+### Sponsoring Entity
The Incubator PMC
-```
diff --git a/site/blog/2025-07-08-repo-reorg-community-focus.md
b/site/blog/2025-07-08-repo-reorg-community-focus.md
index 60d67a40d..38b296b46 100644
--- a/site/blog/2025-07-08-repo-reorg-community-focus.md
+++ b/site/blog/2025-07-08-repo-reorg-community-focus.md
@@ -6,7 +6,7 @@ author: [email protected]
---
-Teaclave was originally created with a broad vision to explore the
possibilities of confidential computing. It consisted of multiple components,
including SDKs supporting Intel SGX and Arm TrustZone, a general-purpose
application framework (FaaS), and experimental verification efforts, spanning
several repositories under the Apache Incubator.
+Apache Teaclave™ (incubating) was originally created with a broad vision to
explore the possibilities of confidential computing. It consisted of multiple
components, including SDKs supporting Intel SGX and Arm TrustZone, a
general-purpose application framework (FaaS), and experimental verification
efforts, spanning several repositories under the Apache Incubator.
Over the years, as the field of confidential computing evolved, we observed a
clear trend: developers increasingly preferred building their own Trusted
Applications using SDKs directly, rather than relying on a general-purpose FaaS
framework. This organic shift in usage has also been reflected in our
contributor activities. Most community engagement and active development now
center around the SDKs, especially the Rust-based TrustZone and SGX SDKs.
diff --git a/site/docs/community/becoming-a-member.md
b/site/docs/community/becoming-a-member.md
index 24d120112..33b3a6dd1 100644
--- a/site/docs/community/becoming-a-member.md
+++ b/site/docs/community/becoming-a-member.md
@@ -4,7 +4,7 @@ permalink: /becoming-a-member
# Becoming a Committer or PPMC Member of Apache Teaclave™
-Apache Teaclave™ is an open and inclusive community that welcomes all forms of
+Apache Teaclave™ (incubating) is an open and inclusive community that welcomes
all forms of
contributions—from code and documentation to design discussions and community
support. We follow the Apache Way and recognize sustained and meaningful
contributions with committership or PPMC membership. These roles reflect
trust,
@@ -39,7 +39,7 @@ growth, not just commit access.
## Become a PPMC Member of Apache Teaclave™
-Project Management Committee (PMC) members help guide the project's vision and
+Podling Project Management Committee (PPMC) members help guide the project's
vision and
governance. PPMC members are usually experienced committers who've shown
leadership, deep engagement, and a long-term commitment to Teaclave. We value
contributions across CoPDoC areas, with an emphasis on community maturity and
diff --git a/site/docs/community/community.md b/site/docs/community/community.md
index 85fff556f..5565c0713 100644
--- a/site/docs/community/community.md
+++ b/site/docs/community/community.md
@@ -4,7 +4,7 @@ permalink: /community
# Community
-Welcome to the Apache Teaclave™ community. Here are several ways that you can
get involved.
+Welcome to the Apache Teaclave™ (incubating) community. Here are several ways
that you can get involved.
## Mailing Lists
diff --git a/site/docs/community/contributing.md
b/site/docs/community/contributing.md
index 43eed4b40..e4d95a967 100644
--- a/site/docs/community/contributing.md
+++ b/site/docs/community/contributing.md
@@ -4,7 +4,8 @@ permalink: /contributing
# Contributing
-Teaclave is open source and follows [The Apache
Way](https://www.apache.org/theapacheway/).
+Apache Teaclave™ (incubating) is open source and follows
+[The Apache Way](https://www.apache.org/theapacheway/).
We aim to create a project that is maintained and owned by the
community. All kinds of contributions are welcome.
@@ -31,7 +32,8 @@ in the repo.
For bug reports, please use the GitHub "Issues" tab in the relevant
repository. Timely responses and triage will be performed by the maintainers.
We recommend using the following format when reporting:
-```
+
+```markdown
## Environment:
- OS and version
- Hardware and platform
@@ -85,4 +87,4 @@ coordinate effectively.
Teaclave follows the [Apache Code of
Conduct](https://www.apache.org/foundation/policies/conduct).
We expect all contributors to adhere to it.
-Thank you for your interest in contributing to Teaclave!
\ No newline at end of file
+Thank you for your interest in contributing to Apache Teaclave™!
\ No newline at end of file
diff --git a/site/docs/community/contributors.md
b/site/docs/community/contributors.md
index e5701282b..eb7b2cd99 100644
--- a/site/docs/community/contributors.md
+++ b/site/docs/community/contributors.md
@@ -4,7 +4,7 @@ permalink: /contributors
# Contributors
-Teaclave adopts [The Apache Way](https://www.apache.org/theapacheway/).
+Apache Teaclave™ (incubating) adopts [The Apache
Way](https://www.apache.org/theapacheway/).
Everyone is more than welcome to contribute and make the project better.
We add tag along with committer name to show areas that they are familiar with.
We do encourage everyone to work anything they are interested in.
@@ -17,40 +17,39 @@ committers or PPMC of Teaclave.
Teaclave is now part of the Apache Incubator. We are fortunate to have the
following mentors.
-| Name | Apache ID | GitHub ID
|
-|:--------------|:------------|:----------------------------------------------------|
-| Daniel Dai | daijy | -
|
-| Felix Cheung | felixcheung | felixcheung
|
-| Furkan Kamaci | kamaci | kamaci
|
-| Gordon King | garyw |
[bigdata-memory](https://github.com/bigdata-memory) |
-| Matt Sicker | mattsicker | jvz
|
-| Zhijie Shen | zjshen | zjshen14
|
-| Xuanwo | xuanwo | xuanwo
|
-| Zili Chen | tison | tisonkun
|
-| Willem Jiang | ningjiang | willemjiang
|
+| Name | Apache ID | GitHub ID |
+| :------------ | :---------- | :------------- |
+| Daniel Dai | daijy | - |
+| Felix Cheung | felixcheung | felixcheung |
+| Furkan Kamaci | kamaci | kamaci |
+| Gordon King | garyw | bigdata-memory |
+| Matt Sicker | mattsicker | jvz |
+| Zhijie Shen | zjshen | zjshen14 |
+| Xuanwo | xuanwo | xuanwo |
+| Zili Chen | tison | tisonkun |
+| Willem Jiang | ningjiang | willemjiang |
## Podling Project Management Committee
-The role of
-[Podling Project Management
Committee](https://incubator.apache.org/guides/ppmc.html)
+The role of [Podling Project Management
Committee](https://incubator.apache.org/guides/ppmc.html)
(PPMC) is to help to govern the project and is directly responsible for the
oversight of Teaclave.
-| Name | Apache ID | GitHub ID
| Tag |
-| :-------------- | :-------------- |
:-------------------------------------------------- | :------------------ |
-| He Sun | hsun |
[henrysun007](https://github.com/henrysun007) | `teaclave-faas` |
-| Mingshen Sun | mssun | [mssun](https://github.com/mssun)
| `all` |
-| Pei Wang | uraj | [uraj](https://github.com/uraj)
| - |
-| Ran Duan | rduan |
[volcano0dr](https://github.com/volcano0dr) | `sgx-sdk` |
-| Rundong Zhou | rdzhou | [rdzhou](https://github.com/rdzhou)
| - |
-| Shaojun Wang | shaojunwang |
[superajun-wsj](https://github.com/superajun-wsj) | `java-tee-sdk` |
-| Tao Wei | lenxwei | -
| - |
-| Tongxin Li | litongxin1991 |
[litongxin1991](https://github.com/litongxin1991) | - |
-| Yiming Jing | yjing | -
| - |
-| Yu Ding | dingelish |
[dingelish](https://github.com/dingelish) | `sgx-sdk` |
-| Yuan Zhuang | yuanz |
[DemesneGH](https://github.com/DemesneGH) | `trustzone-sdk` |
-| Yulong Zhang | yulongzhang |
[yulongzhang](https://github.com/yulongzhang) | - |
-| Zhaofeng Chen | zfc |
[m4sterchain](https://github.com/m4sterchain) | `all` |
+| Name | Apache ID | GitHub ID
| Tag |
+| :------------ | :------------ |
:------------------------------------------------ | :-------------- |
+| He Sun | hsun |
[henrysun007](https://github.com/henrysun007) | `teaclave-faas` |
+| Mingshen Sun | mssun | [mssun](https://github.com/mssun)
| `all` |
+| Pei Wang | uraj | [uraj](https://github.com/uraj)
| - |
+| Ran Duan | rduan | [volcano0dr](https://github.com/volcano0dr)
| `sgx-sdk` |
+| Rundong Zhou | rdzhou | [rdzhou](https://github.com/rdzhou)
| - |
+| Shaojun Wang | shaojunwang |
[superajun-wsj](https://github.com/superajun-wsj) | `java-tee-sdk` |
+| Tao Wei | lenxwei | -
| - |
+| Tongxin Li | litongxin1991 |
[litongxin1991](https://github.com/litongxin1991) | - |
+| Yiming Jing | yjing | -
| - |
+| Yu Ding | dingelish | [dingelish](https://github.com/dingelish)
| `sgx-sdk` |
+| Yuan Zhuang | yuanz | [DemesneGH](https://github.com/DemesneGH)
| `trustzone-sdk` |
+| Yulong Zhang | yulongzhang |
[yulongzhang](https://github.com/yulongzhang) | - |
+| Zhaofeng Chen | zfc |
[m4sterchain](https://github.com/m4sterchain) | `all` |
## Committers
@@ -58,15 +57,15 @@ oversight of Teaclave.
Committers are people who have made substantial contribution to the project and
being active.
-| Name | Apache ID | GitHub ID
| Tag |
-| :------------ | :---------- |
:------------------------------------------------ | :--------------------------
|
-| Hongbo Chen | ya0guang | [ya0guang](https://github.com/ya0guang)
| `webassembly`, `executor` |
-| Lei Yu | yulei | [yuleil](https://github.com/yuleil)
| `java-tee-sdk` |
-| Qinkun Bao | qinkun | [qinkunbao](https://github.com/qinkunbao)
| `teaclave-faas` |
-| Rong Fan | fanrong | [fanrong1992](https://github.com/fanrong1992)
| `trustzone-sdk` |
-| Sanhong Li | sanhongli | -
| `java-tee-sdk` |
-| Zehui Chen | ivila | [ivila](https://github.com/ivila)
| `trustzone-sdk` |
-| Ziyi Lin | ziyilin | [ziyilin](https://github.com/ziyilin)
| `java-tee-sdk` |
+| Name | Apache ID | GitHub ID |
Tag |
+| :---------- | :-------- | :-------------------------------------------- |
:------------------------ |
+| Hongbo Chen | ya0guang | [ya0guang](https://github.com/ya0guang) |
`webassembly`, `executor` |
+| Lei Yu | yulei | [yuleil](https://github.com/yuleil) |
`java-tee-sdk` |
+| Qinkun Bao | qinkun | [qinkunbao](https://github.com/qinkunbao) |
`teaclave-faas` |
+| Rong Fan | fanrong | [fanrong1992](https://github.com/fanrong1992) |
`trustzone-sdk` |
+| Sanhong Li | sanhongli | - |
`java-tee-sdk` |
+| Zehui Chen | ivila | [ivila](https://github.com/ivila) |
`trustzone-sdk` |
+| Ziyi Lin | ziyilin | [ziyilin](https://github.com/ziyilin) |
`java-tee-sdk` |
## Contributors
@@ -127,6 +126,7 @@ SDK and Teaclave TrustZone SDK (in alphabetical order):
- [zEqueue](https://github.com/z1queue)
More people tracked in GitHub:
+
-
[Teaclave](https://github.com/apache/incubator-teaclave/graphs/contributors)
- [Teaclave SGX
SDK](https://github.com/apache/incubator-teaclave-sgx-sdk/graphs/contributors)
- [Teaclave TrustZone
SDK](https://github.com/apache/incubator-teaclave-trustzone-sdk/graphs/contributors)
diff --git a/site/docs/community/maturity.md b/site/docs/community/maturity.md
index b0af914a0..6b2c07082 100644
--- a/site/docs/community/maturity.md
+++ b/site/docs/community/maturity.md
@@ -4,7 +4,7 @@ permalink: /maturity
# Maturity Assessment For The Apache Teaclave™ Ecosystem
-This is a maturity assessment of Apache Teaclave™ based on the ASF project
+This is a maturity assessment of Apache Teaclave™ (incubating) based on the
ASF project
[maturity
model](https://community.apache.org/apache-way/apache-project-maturity-model.html).
It is used to evaluate the overall maturity for the project and the codebase
@@ -13,6 +13,7 @@ community, Incubator PMC, and ASF Board of Directors on
Teaclave's graduation
to a top-level Apache project.
## Status of this Document
+
The project has been filled out by the PPMC members of Apache Teaclave™ and
welcomes any updates if necessary.
@@ -20,78 +21,78 @@ welcomes any updates if necessary.
### Code Development (CD)
-| ID | Description | Status |
-|----|-------------|--------|
-| CD10 | The project produces Open Source software for distribution to the
public, at no charge. | **YES** The project's source code is licensed under
Apache License 2.0. |
-| CD20 | Anyone can easily discover and access the project's code. | **YES**
The [official website](https://teaclave.apache.org/) includes a GitHub link
that can access the project's repository on GitHub directly. |
-| CD30 | Anyone using standard, widely-available tools, can build the code in
a reproducible way. | **YES** Comprehensive documentation is available in the
[Quick Navigation Links](https://teaclave.apache.org/overview), guiding users
through reproducible builds of the code.|
-| CD40 | The full history of the project's code is available via a source code
control system, in a way that allows anyone to recreate any released version. |
**YES** The project uses `git`, and anyone can view the full history of the
project via commit logs. |
+| ID | Description
| Status
|
+| ---- |
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
+| CD10 | The project produces Open Source software for distribution to the
public, at no charge.
| **YES** The project's source code is licensed
under Apache License 2.0.
|
+| CD20 | Anyone can easily discover and access the project's code.
| **YES** The [official
website](https://teaclave.apache.org/) includes a GitHub link that can access
the project's repository on GitHub directly.
|
+| CD30 | Anyone using standard, widely-available tools, can build the code in
a reproducible way.
| **YES** Comprehensive documentation is available in
the [Quick Navigation Links](https://teaclave.apache.org/overview), guiding
users through reproducible builds of the code. |
+| CD40 | The full history of the project's code is available via a source code
control system, in a way that allows anyone to recreate any released version.
| **YES** The project uses `git`, and anyone can view
the full history of the project via commit logs.
|
| CD50 | The source code control system establishes the provenance of each
line of code in a reliable way, based on strong authentication of the
committer. When third parties contribute code, commit messages provide reliable
information about the code provenance. | **YES** The project uses GitHub and is
managed by Apache Infra, ensuring provenance of each line of code to a
committer. Third-party contributions follow the contributing guidelines. |
### Licenses and Copyright (LC)
-| ID | Description | Status |
-|----|-------------|--------|
-| LC10 | The Apache License, version 2.0, covers the released code. | **YES**
The LICENSE is in the GitHub repository. All source files are checked with CI
to ensure that no LICENSE files are missing. |
-| LC20 | Libraries that are mandatory dependencies of the project's code do
not create more restrictions than the Apache License does. | **YES** All
dependencies are listed. |
-| LC30 | The libraries mentioned in LC20 are available as Open Source
software. | **YES** All dependencies listed are available as open-source
software. |
-| LC40 | Committers are bound by an Individual Contributor Agreement (the
"Apache iCLA") that defines which code they may commit and how they need to
identify code that is not their own. | **YES** All committers have iCLAs. |
-| LC50 | The project clearly defines and documents the copyright ownership of
everything that the project produces. | **YES** All source files include an
Apache License 2.0 header. |
+| ID | Description
| Status
|
+| ---- |
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
----------------------------------------------------------------------------------------------------------------------------------
|
+| LC10 | The Apache License, version 2.0, covers the released code.
| **YES** The LICENSE is in the GitHub repository.
All source files are checked with CI to ensure that no LICENSE files are
missing. |
+| LC20 | Libraries that are mandatory dependencies of the project's code do
not create more restrictions than the Apache License does.
| **YES** All dependencies are listed.
|
+| LC30 | The libraries mentioned in LC20 are available as Open Source
software.
| **YES** All dependencies listed are
available as open-source software.
|
+| LC40 | Committers are bound by an Individual Contributor Agreement (the
"Apache iCLA") that defines which code they may commit and how they need to
identify code that is not their own. | **YES** All committers have iCLAs.
|
+| LC50 | The project clearly defines and documents the copyright ownership of
everything that the project produces.
| **YES** All source files include an Apache
License 2.0 header.
|
### Releases (RE)
-| ID | Description | Status |
-|----|-------------|--------|
-| RE10 | Releases consist of source code, distributed using standard and open
archive formats that are expected to stay readable in the long term. | **YES**
Source releases are distributed via dist.apache.org and linked from the
download page. |
-| RE20 | The project's PMC (Project Management Committee, see CS10) approves
each software release in order to make the release an act of the Foundation. |
**YES** All releases have been voted on at `[email protected]` and
`[email protected]`, and have at least 3 PMC members' votes. |
-| RE30 | Releases are signed and/or distributed along with digests that anyone
can reliably use to validate the downloaded archives. | **YES** All releases
are signed, and the
[KEYS](https://downloads.apache.org/incubator/teaclave/KEYS) are available. |
-| RE40 | The project can distribute convenience binaries alongside source
code, but they are not Apache Releases, they are provided with no guarantee. |
**YES** Our releases contain source code only and do not include any
convenience binaries. We are aware of the ASF policy regarding non-source
distributions and follow it accordingly. |
-| RE50 | The project documents a repeatable release process so that someone
new to the project can independently generate the complete set of artifacts
required for a release. | **YES** We document the Release Guide that the
community can follow to make a new Apache Teaclave™ release. |
+| ID | Description
| Status
|
+| ---- |
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
+| RE10 | Releases consist of source code, distributed using standard and open
archive formats that are expected to stay readable in the long term.
| **YES** Source releases are distributed via dist.apache.org
and linked from the download page.
|
+| RE20 | The project's PMC (Project Management Committee, see CS10) approves
each software release in order to make the release an act of the Foundation.
| **YES** All releases have been voted on at
`[email protected]` and `[email protected]`, and have at
least 3 PMC members' votes. |
+| RE30 | Releases are signed and/or distributed along with digests that anyone
can reliably use to validate the downloaded archives.
| **YES** All releases are signed, and the
[KEYS](https://downloads.apache.org/incubator/teaclave/KEYS) are available.
|
+| RE40 | The project can distribute convenience binaries alongside source
code, but they are not Apache Releases, they are provided with no guarantee.
| **YES** Our releases contain source code only and do
not include any convenience binaries. We are aware of the ASF policy regarding
non-source distributions and follow it accordingly. |
+| RE50 | The project documents a repeatable release process so that someone
new to the project can independently generate the complete set of artifacts
required for a release. | **YES** We document the Release Guide that the
community can follow to make a new Apache Teaclave™ release.
|
### Quality (QU)
-| ID | Description | Status |
-|----|-------------|--------|
-| QU10 | The project is open and honest about the quality of its code. Various
levels of quality and maturity for various modules are natural and acceptable
as long as they are clearly communicated. | **YES** We encourage users to
[report issues](https://teaclave.apache.org/contributing/#bug-reports). |
-| QU20 | The project puts a very high priority on producing secure software. |
**YES** All security-related issues are handled with high priority. |
-| QU30 | The project provides a well-documented, secure and private channel to
report security issues, along with a documented way of responding to them. |
**YES** The GitHub project page provides a security page. |
-| QU40 | The project puts a high priority on backwards compatibility and aims
to document any incompatible changes and provide tools and documentation to
help users transition to new features. | **YES** We try our best to follow
backwards compatibility. If there is an incompatible API change, we provide a
migration guide. |
-| QU50 | The project strives to respond to documented bug reports in a timely
manner. | **YES** The project has resolved 400+ issues and 800+ pull requests
so far, with very prompt responses. |
+| ID | Description
| Status
|
+| ---- |
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
--------------------------------------------------------------------------------------------------------------------------------
|
+| QU10 | The project is open and honest about the quality of its code. Various
levels of quality and maturity for various modules are natural and acceptable
as long as they are clearly communicated. | **YES** We encourage users to
[report issues](https://teaclave.apache.org/contributing/#bug-reports).
|
+| QU20 | The project puts a very high priority on producing secure software.
| **YES** All security-related issues
are handled with high priority.
|
+| QU30 | The project provides a well-documented, secure and private channel to
report security issues, along with a documented way of responding to them.
| **YES** The GitHub project page
provides a security page.
|
+| QU40 | The project puts a high priority on backwards compatibility and aims
to document any incompatible changes and provide tools and documentation to
help users transition to new features. | **YES** We try our best to
follow backwards compatibility. If there is an incompatible API change, we
provide a migration guide. |
+| QU50 | The project strives to respond to documented bug reports in a timely
manner.
| **YES** The project has resolved
400+ issues and 800+ pull requests so far, with very prompt responses.
|
### Community (CO)
-| ID | Description | Status |
-|----|-------------|--------|
-| CO10 | The project has a well-known homepage that points to all the
information required to operate according to this maturity model. | **YES** The
[official website](https://teaclave.apache.org/) includes all information users
need to run the project. |
-| CO20 | The community welcomes contributions from anyone who acts in good
faith and in a respectful manner, and who adds value to the project. | **YES**
The community welcomes and respects contributions in different aspects of the
project. |
-| CO30 | Contributions include source code, documentation, constructive bug
reports, constructive discussions, marketing and generally anything that adds
value to the project. | **YES** We detail various contributing methods in our
[contributing](https://teaclave.apache.org/contributing/) doc. |
-| CO40 | The community strives to be meritocratic and gives more rights and
responsibilities to contributors who, over time, add value to the project. |
**YES** Based on meritocracy, the community has elected 8 new committers during
incubation. |
-| CO50 | The project documents how contributors can earn more rights such as
commit access or decision power, and applies these principles consistently. |
**YES** The community has clear docs on nominating committers and PPMC members.
|
-| CO60 | The community operates based on consensus of its members (see CS10)
who have decision power. Dictators, benevolent or not, are not welcome in
Apache projects. | **YES** Teaclave community operates based on consensus. All
discussions and votes are transparent in the mailing list. |
-| CO70 | The project strives to answer user questions in a timely manner. |
**YES** Teaclave community prioritizes user support by promptly addressing
questions through mailing lists and GitHub issues. |
+| ID | Description
| Status
|
+| ---- |
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
-----------------------------------------------------------------------------------------------------------------------------
|
+| CO10 | The project has a well-known homepage that points to all the
information required to operate according to this maturity model.
| **YES** The [official
website](https://teaclave.apache.org/) includes all information users need to
run the project. |
+| CO20 | The community welcomes contributions from anyone who acts in good
faith and in a respectful manner, and who adds value to the project.
| **YES** The community welcomes and respects
contributions in different aspects of the project.
|
+| CO30 | Contributions include source code, documentation, constructive bug
reports, constructive discussions, marketing and generally anything that adds
value to the project. | **YES** We detail various contributing methods in our
[contributing](https://teaclave.apache.org/contributing/) doc. |
+| CO40 | The community strives to be meritocratic and gives more rights and
responsibilities to contributors who, over time, add value to the project.
| **YES** Based on meritocracy, the community has elected 8
new committers during incubation. |
+| CO50 | The project documents how contributors can earn more rights such as
commit access or decision power, and applies these principles consistently.
| **YES** The community has clear docs on nominating
committers and PPMC members. |
+| CO60 | The community operates based on consensus of its members (see CS10)
who have decision power. Dictators, benevolent or not, are not welcome in
Apache projects. | **YES** Teaclave community operates based on
consensus. All discussions and votes are transparent in the mailing list.
|
+| CO70 | The project strives to answer user questions in a timely manner.
| **YES** Teaclave community prioritizes user support by
promptly addressing questions through mailing lists and GitHub issues. |
### Consensus Building (CS)
-| ID | Description | Status |
-|----|-------------|--------|
-| CS10 | The project maintains a public list of its contributors who have
decision power. The project's PMC (Project Management Committee) consists of
those contributors. | **YES** The
[website](https://teaclave.apache.org/contributors) contains a full list of
committers and PPMC members. |
-| CS20 | Decisions require a consensus among PMC members and are documented on
the project's main communications channel. The PMC takes community opinions
into account, but the PMC has the final word. | **YES** Teaclave community has
been making important decisions and discussions on the dev mailing list. |
-| CS30 | The project uses documented voting rules to build consensus when
discussion is not sufficient. | **YES** The project uses the standard ASF
voting rules. Voting rules are clearly stated before each vote. |
-| CS40 | In Apache projects, vetoes are only valid for code commits. The
person exercising the veto must justify it with a technical explanation, as per
the Apache voting rules defined in CS30. | **YES** Vetoes are only permitted
during code review and must be based strictly on technical or code quality
considerations. |
-| CS50 | All "important" discussions happen asynchronously in written form on
the project's main communications channel. Offline, face-to-face or private
discussions that affect the project are also documented on that channel. |
**YES** Teaclave community has been making every important decision on mailing
lists. |
+| ID | Description
| Status
|
+| ---- |
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
----------------------------------------------------------------------------------------------------------------------------
|
+| CS10 | The project maintains a public list of its contributors who have
decision power. The project's PMC (Project Management Committee) consists of
those contributors. |
**YES** The [website](https://teaclave.apache.org/contributors) contains a full
list of committers and PPMC members. |
+| CS20 | Decisions require a consensus among PMC members and are documented on
the project's main communications channel. The PMC takes community opinions
into account, but the PMC has the final word. |
**YES** Teaclave community has been making important decisions and discussions
on the dev mailing list. |
+| CS30 | The project uses documented voting rules to build consensus when
discussion is not sufficient.
|
**YES** The project uses the standard ASF voting rules. Voting rules are
clearly stated before each vote. |
+| CS40 | In Apache projects, vetoes are only valid for code commits. The
person exercising the veto must justify it with a technical explanation, as per
the Apache voting rules defined in CS30. |
**YES** Vetoes are only permitted during code review and must be based strictly
on technical or code quality considerations. |
+| CS50 | All "important" discussions happen asynchronously in written form on
the project's main communications channel. Offline, face-to-face or private
discussions that affect the project are also documented on that channel. |
**YES** Teaclave community has been making every important decision on mailing
lists. |
### Independence (IN)
-| ID | Description | Status |
-|----|-------------|--------|
-| IN10 | The project is independent from any corporate or organizational
influence. | **YES** Apache Teaclave™ maintains complete independence from
corporate or organizational influence, with individual contributors shaping the
community solely through transparent contributions. |
-| IN20 | Contributors act as themselves, not as representatives of a
corporation or organization. | **YES** The committers and contributors act
independently on their own initiative. |
+| ID | Description
| Status
|
+| ---- |
----------------------------------------------------------------------------------------
|
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
+| IN10 | The project is independent from any corporate or organizational
influence. | **YES** Apache Teaclave™ maintains complete
independence from corporate or organizational influence, with individual
contributors shaping the community solely through transparent contributions. |
+| IN20 | Contributors act as themselves, not as representatives of a
corporation or organization. | **YES** The committers and contributors act
independently on their own initiative.
|
### Trademark and Branding (TB)
-| ID | Description | Status |
-|-----|-------------|--------|
-| TB10 | The project uses "Apache Foo™" as the project and software product
name consistently, with appropriate trademark attributions. | **YES** We
consistently use the name "Apache Teaclave™" across all official materials,
including the logo, with proper trademark attribution. |
-| TB20 | The project's primary homepage is at projectname.apache.org. When
exceptions exist to use alternate domains for any purpose, any non-apache.org
domain names are owned by the ASF. | **YES** The official homepage is located
at [https://teaclave.apache.org](https://teaclave.apache.org), fully complying
with ASF domain usage policies. |
-| TB30 | The ASF has trademark rights, including any registrations, to the
project name, logo, and any other major branding elements. | **YES** The Apache
Software Foundation owns the rights to the "Apache Teaclave™" name and branding
under the standard ASF trademark policies. We defer to ASF Brand Management for
any formal registrations. |
-| TB40 | The project monitors for any major misuses of their project's brand
by others, and reports any potential misuses to Brand Management. | **YES** We
periodically monitor for potential brand misuse (e.g., through online searches)
and report any identified cases to ASF Brand Management. |
+| ID | Description
| Status
|
+| ---- |
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
+| TB10 | The project uses "Apache Foo™" as the project and software product
name consistently, with appropriate trademark attributions.
| **YES** We consistently use the name "Apache
Teaclave™" across all official materials, including the logo, with proper
trademark attribution.
|
+| TB20 | The project's primary homepage is at projectname.apache.org. When
exceptions exist to use alternate domains for any purpose, any non-apache.org
domain names are owned by the ASF. | **YES** The official homepage is located
at [https://teaclave.apache.org](https://teaclave.apache.org), fully complying
with ASF domain usage policies.
|
+| TB30 | The ASF has trademark rights, including any registrations, to the
project name, logo, and any other major branding elements.
| **YES** The Apache Software Foundation owns
the rights to the "Apache Teaclave™" name and branding under the standard ASF
trademark policies. We defer to ASF Brand Management for any formal
registrations. |
+| TB40 | The project monitors for any major misuses of their project's brand
by others, and reports any potential misuses to Brand Management.
| **YES** We periodically monitor for potential
brand misuse (e.g., through online searches) and report any identified cases to
ASF Brand Management. |
diff --git a/site/docs/community/release-guide.md
b/site/docs/community/release-guide.md
index f49889408..6f0dc2bb7 100644
--- a/site/docs/community/release-guide.md
+++ b/site/docs/community/release-guide.md
@@ -13,7 +13,7 @@ the complete workflow and necessary operations to achieve
that goal.
## For New Release Managers
-### 0. Become a member of the Apache Teaclave™ community
+### 0. Become a member of the Apache Teaclave™ (incubating) community
The release manager must be a member of the Apache Teaclave™ project. This
ensures they have the necessary permissions, including access to the Apache
diff --git a/site/docs/overview.md b/site/docs/overview.md
index f3c55aad6..dd94a43fe 100644
--- a/site/docs/overview.md
+++ b/site/docs/overview.md
@@ -2,7 +2,7 @@
permalink: /overview
---
-# Apache Teaclave™: Empowering Memory-Safe Development for TEEs
+# Apache Teaclave™ (incubating): Empowering Memory-Safe Development for TEEs
Welcome to the official website of Teaclave, an open-source initiative under
the [Apache Incubator](https://incubator.apache.org/). Teaclave empowers
developers to build memory-safe Trusted Applications across diverse
confidential computing platforms, including Intel SGX and Arm TrustZone.
@@ -14,7 +14,7 @@ This page serves as an overview and entry point to the entire
Teaclave ecosystem
## 🔧 The Apache Teaclave™ Ecosystem
-The Apache Teaclave™ ecosystem consists of several independently maintained
repositories, each targeting a specific Trusted Execution Environment (TEE).
These SDKs and supporting libraries provide essential tooling for building
secure applications in constrained environments using modern memory-safe
languages like Rust.
+The Teaclave ecosystem consists of several independently maintained
repositories, each targeting a specific Trusted Execution Environment (TEE).
These SDKs and supporting libraries provide essential tooling for building
secure applications in constrained environments using modern memory-safe
languages like Rust.
---
@@ -26,8 +26,8 @@ This SDK adheres to the GlobalPlatform TEE specifications,
ensuring broad compat
**📄 Quick Navigation Links**
- [📘 Teaclave TrustZone Docs](/trustzone-sdk-docs)
-- [📚 API Doc For (Normal World) Host
Application](https://teaclave.apache.org/api-docs/trustzone-sdk/optee_teec/)
-- [📚 API Doc For (Secure World) Trust
Application](https://teaclave.apache.org/api-docs/trustzone-sdk/optee_utee/)
+- [📚 API Doc For (Normal World) Host
Application](/api-docs/trustzone-sdk/optee_teec/)
+- [📚 API Doc For (Secure World) Trust
Application](/api-docs/trustzone-sdk/optee_utee/)
- [🚀 Quick Start: TA Development on
QEMU](/trustzone-sdk-docs/emulate-and-dev-in-docker.md)
- [🚀 Overview of OP-TEE Rust
Examples](/trustzone-sdk-docs/overview-of-optee-rust-examples)
- [🔗 OP-TEE with Rust (using Teaclave TrustZone
SDK)](https://optee.readthedocs.io/en/latest/building/optee_with_rust.html)
@@ -41,8 +41,9 @@ The Teaclave SGX SDK brings memory-safe Rust programming to
Intel SGX, enabling
The SDK offers a complete SGX-compatible runtime and tooling suite, bridging
the gap between native SGX support and idiomatic Rust development. It allows
developers to adopt Rust’s ownership model, type system, and concurrency safety
even within the limitations of SGX.
**📄 Quick Navigation Links**
+
- [📘 Teaclave SGX Docs](/sgx-sdk-docs/)
-- [📚 SGX Enclave API Doc](https://teaclave.apache.org/api-docs/sgx-sdk/)
+- [📚 SGX Enclave API Doc](/api-docs/sgx-sdk/)
- [🚀 Setting up your SGX Development
Environment](/sgx-sdk-docs/environment-setup)
---
@@ -56,6 +57,7 @@ This repository now provides project overview for the entire
Teaclave ecosystem
The repository maintains separate directories for TrustZone, SGX, and Crates
ecosystems, each containing showcases and examples that demonstrate the
capabilities of the respective SDKs. This structure makes it easy for
developers to explore practical implementations across different TEE platforms.
**📄 Quick Navigation Links**
+
- [🚀 Teaclave TrustZone Ecosystem Showcase](/teaclave-docs/trustzone/)
- [🚀 Teaclave SGX Ecosystem Showcase](/teaclave-docs/sgx/)
@@ -70,6 +72,7 @@ As the field of confidential computing evolved, the Teaclave
community naturally
Although now considered **legacy**, the FaaS platform remains a valuable
milestone in Teaclave’s evolution into an SDK-focused ecosystem. Its
architecture demonstrates how to build a high-level, privacy-preserving compute
service on top of hardware-enforced TEEs. We preserve its documentation and
codebase history so that developers can continue to learn from its design and
implementation.
**📄 Quick Navigation Links**
+
- [📘 Teaclave FaaS (legacy) Docs](/docs/)
- [📘 Papers, Talks, and Related Articles](/docs/papers-talks)
@@ -84,6 +87,7 @@ By supporting a modular structure with clear separation
between host-side and en
> ⚠️ Note: This SDK is still in an experimental stage.
**📄 Quick Navigation Links**
+
- [📘 Java TEE SDK Proposal](/blog/2022/10/08/accepting-java-enclave-proposal)
---
@@ -98,11 +102,12 @@ This repository serves as a security-reviewed foundation
for TEE application dev
## 👥 Community Management
-We welcome all contributors to help grow the Teaclave project and ecosystem.
Whether you're new to trusted computing or an experienced contributor, your
involvement is highly valued.
+We welcome all contributors to help grow the Apache Teaclave™ project and
ecosystem. Whether you're new to trusted computing or an experienced
contributor, your involvement is highly valued.
Please visit the [**Community**](/community) page for more details on how to
participate and contribute.
**📄 Quick Navigation Links**
-- [🚀 How to Contribute to Teaclave](/contributing)
-- [🚀 How to Become a Member of Teaclave](/becoming-a-member)
+
+- [🚀 How to Contribute to Apache Teaclave™](/contributing)
+- [🚀 How to Become a Member of Apache Teaclave™](/becoming-a-member)
- [🚀 How to Make a Release](/release-guide)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
