Looks good to me! Nice details. On Wed, Mar 25, 2020 at 14:28 Mingshen Sun <ms...@apache.org> wrote:
> Hi folks, > > I have an initial version of the report. Feel free to comment if > something is missing. > > ## 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) > > Best, > Mingshen > > On Thu, Mar 19, 2020 at 8:18 PM <jmcl...@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, 15 April 2020, 10:30 am PDT. > > 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, April 01). > > > > 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/April2020 > > > > 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 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > For additional commands, e-mail: dev-h...@teaclave.apache.org > > -- Matt Sicker <boa...@gmail.com>
