Re: Podling Teaclave Report Reminder - May 2022
Dear Teaclave community, Sorry for the late reply. I'm done with the report and submitted to the wiki. [1] Mingshen [1] https://cwiki.apache.org/confluence/display/INCUBATOR/May2022 ## 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) On Sun, May 8, 2022 at 12:58 PM Felix Cheung wrote: > > Reminder > > From: johndam...@apache.org > Sent: Wednesday, April 27, 2022 5:50:12 PM > To: d...@teaclave.incubator.apache.org > Subject: Podling Teaclave Report Reminder - May 2022 > > 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, 18 May 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, May 04). > > 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 assu
Re: Podling Teaclave Report Reminder - May 2022
Reminder From: johndam...@apache.org Sent: Wednesday, April 27, 2022 5:50:12 PM To: d...@teaclave.incubator.apache.org Subject: Podling Teaclave Report Reminder - May 2022 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, 18 May 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, May 04). 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/May2022 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-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: Podling Teaclave Report Reminder - May 2022
Hi Furkan, Sorry, I overlooked this email. I’ll prepare the report tomorrow. Thanks! Mingshen On Tue, May 3, 2022 at 4:15 PM Furkan KAMACI wrote: > Hi, > > Is there anybody working on the report? Feel free to ask if you need help. > > Kind Regards, > Furkan KAMACI >
Podling Teaclave Report Reminder - May 2022
Hi, Is there anybody working on the report? Feel free to ask if you need help. Kind Regards, Furkan KAMACI
Podling Teaclave Report Reminder - May 2022
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, 18 May 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, May 04). 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/May2022 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-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org