You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@teaclave.apache.org by Mingshen Sun <ms...@apache.org> on 2022/01/04 21:44:38 UTC
Re: Podling Teaclave Report Reminder - January 2022
Dear Teaclave community,
I'll work on this today. Sorry for the delay.
Mingshen
On Thu, Dec 23, 2021 at 10:20 PM <jm...@apache.org> wrote:
>
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 19 January 2022.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, January 05).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> ----------------------
>
> Your report should contain the following:
>
> * Your project name
> * A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> * A list of the three most important issues to address in the move
> towards graduation.
> * Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> * How has the community developed since the last report
> * How has the project developed since the last report.
> * How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/January2022
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Note: The format of the report has changed to use markdown.
>
> Mentors
> -------
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@teaclave.apache.org
> For additional commands, e-mail: dev-help@teaclave.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@teaclave.apache.org
For additional commands, e-mail: dev-help@teaclave.apache.org
Re: Podling Teaclave Report Reminder - January 2022
Posted by Matt Sicker <bo...@gmail.com>.
Looks good to me!
—
Matt Sicker
> On Jan 12, 2022, at 13:16, Mingshen Sun <ms...@apache.org> wrote:
>
> Hi mentors,
>
> Sorry for the late reply. I have complete the report and uploaded to
> the wiki page: https://cwiki.apache.org/confluence/display/INCUBATOR/January2022#teaclave
>
> Also, please kindly help to sign off the report if everything looks
> good to you. Thanks!
>
> Mingshen Sun
>
> Here is the report:
>
> ## 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)
>
>> On Tue, Jan 4, 2022 at 1:44 PM Mingshen Sun <ms...@apache.org> wrote:
>>
>> Dear Teaclave community,
>>
>> I'll work on this today. Sorry for the delay.
>>
>> Mingshen
>>
>>> On Thu, Dec 23, 2021 at 10:20 PM <jm...@apache.org> wrote:
>>>
>>> Dear podling,
>>>
>>> This email was sent by an automated system on behalf of the Apache
>>> Incubator PMC. It is an initial reminder to give you plenty of time to
>>> prepare your quarterly board report.
>>>
>>> The board meeting is scheduled for Wed, 19 January 2022.
>>> The report for your podling will form a part of the Incubator PMC
>>> report. The Incubator PMC requires your report to be submitted 2 weeks
>>> before the board meeting, to allow sufficient time for review and
>>> submission (Wed, January 05).
>>>
>>> Please submit your report with sufficient time to allow the Incubator
>>> PMC, and subsequently board members to review and digest. Again, the
>>> very latest you should submit your report is 2 weeks prior to the board
>>> meeting.
>>>
>>> Candidate names should not be made public before people are actually
>>> elected, so please do not include the names of potential committers or
>>> PPMC members in your report.
>>>
>>> Thanks,
>>>
>>> The Apache Incubator PMC
>>>
>>> Submitting your Report
>>>
>>> ----------------------
>>>
>>> Your report should contain the following:
>>>
>>> * Your project name
>>> * A brief description of your project, which assumes no knowledge of
>>> the project or necessarily of its field
>>> * A list of the three most important issues to address in the move
>>> towards graduation.
>>> * Any issues that the Incubator PMC or ASF Board might wish/need to be
>>> aware of
>>> * How has the community developed since the last report
>>> * How has the project developed since the last report.
>>> * How does the podling rate their own maturity.
>>>
>>> This should be appended to the Incubator Wiki page at:
>>>
>>> https://cwiki.apache.org/confluence/display/INCUBATOR/January2022
>>>
>>> Note: This is manually populated. You may need to wait a little before
>>> this page is created from a template.
>>>
>>> Note: The format of the report has changed to use markdown.
>>>
>>> Mentors
>>> -------
>>>
>>> Mentors should review reports for their project(s) and sign them off on
>>> the Incubator wiki page. Signing off reports shows that you are
>>> following the project - projects that are not signed may raise alarms
>>> for the Incubator PMC.
>>>
>>> Incubator PMC
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@teaclave.apache.org
>>> For additional commands, e-mail: dev-help@teaclave.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@teaclave.apache.org
> For additional commands, e-mail: dev-help@teaclave.apache.org
>
Re: Podling Teaclave Report Reminder - January 2022
Posted by Mingshen Sun <ms...@apache.org>.
Hi mentors,
Sorry for the late reply. I have complete the report and uploaded to
the wiki page: https://cwiki.apache.org/confluence/display/INCUBATOR/January2022#teaclave
Also, please kindly help to sign off the report if everything looks
good to you. Thanks!
Mingshen Sun
Here is the report:
## 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)
On Tue, Jan 4, 2022 at 1:44 PM Mingshen Sun <ms...@apache.org> wrote:
>
> Dear Teaclave community,
>
> I'll work on this today. Sorry for the delay.
>
> Mingshen
>
> On Thu, Dec 23, 2021 at 10:20 PM <jm...@apache.org> wrote:
> >
> > Dear podling,
> >
> > This email was sent by an automated system on behalf of the Apache
> > Incubator PMC. It is an initial reminder to give you plenty of time to
> > prepare your quarterly board report.
> >
> > The board meeting is scheduled for Wed, 19 January 2022.
> > The report for your podling will form a part of the Incubator PMC
> > report. The Incubator PMC requires your report to be submitted 2 weeks
> > before the board meeting, to allow sufficient time for review and
> > submission (Wed, January 05).
> >
> > Please submit your report with sufficient time to allow the Incubator
> > PMC, and subsequently board members to review and digest. Again, the
> > very latest you should submit your report is 2 weeks prior to the board
> > meeting.
> >
> > Candidate names should not be made public before people are actually
> > elected, so please do not include the names of potential committers or
> > PPMC members in your report.
> >
> > Thanks,
> >
> > The Apache Incubator PMC
> >
> > Submitting your Report
> >
> > ----------------------
> >
> > Your report should contain the following:
> >
> > * Your project name
> > * A brief description of your project, which assumes no knowledge of
> > the project or necessarily of its field
> > * A list of the three most important issues to address in the move
> > towards graduation.
> > * Any issues that the Incubator PMC or ASF Board might wish/need to be
> > aware of
> > * How has the community developed since the last report
> > * How has the project developed since the last report.
> > * How does the podling rate their own maturity.
> >
> > This should be appended to the Incubator Wiki page at:
> >
> > https://cwiki.apache.org/confluence/display/INCUBATOR/January2022
> >
> > Note: This is manually populated. You may need to wait a little before
> > this page is created from a template.
> >
> > Note: The format of the report has changed to use markdown.
> >
> > Mentors
> > -------
> >
> > Mentors should review reports for their project(s) and sign them off on
> > the Incubator wiki page. Signing off reports shows that you are
> > following the project - projects that are not signed may raise alarms
> > for the Incubator PMC.
> >
> > Incubator PMC
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@teaclave.apache.org
> > For additional commands, e-mail: dev-help@teaclave.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@teaclave.apache.org
For additional commands, e-mail: dev-help@teaclave.apache.org