Thanks, Matt. Let me copy the draft to the wiki. Feel free to tell me if there are any missing parts.
On Mon, Dec 30, 2019 at 10:34 AM Matt Sicker <boa...@gmail.com> wrote: > > Looks good to me! The level of detail about what components were refactored > might be too much, but I don’t think it’s a problem. > > On Mon, Dec 30, 2019 at 01:08 Mingshen Sun <ms...@apache.org> wrote: > > > Hi all, > > > > I drafted a report for this month. Feel free to reply if I miss > > something. Thanks. > > > > Mingshen > > > > > > ## Teaclave > > > > Teaclave is a universal secure computing platform. > > > > Teaclave has been incubating since 2019-08-20. > > > > ### Three most important unfinished issues to address before graduating: > > > > 1. Improving project structure and documentation > > 2. Grow the community (committers, contributors, users) > > 3. Publish Apache release > > > > ### Are there any issues that the IPMC or ASF Board need to be aware of? > > > > No. > > > > ### How has the community developed since the last report? > > > > - Since last report, we planned to schedule an online meetup recently. > > - We have also received contributions of two new contributors. > > - We draft a roadmap RFC for discussion. > > - We use GitHub issues to track bugs, features, enhancements. Issues > > labeled with "good first issues" is more approachable for newcomers. > > > > ### How has the project developed since the last report? > > > > - Resolve all renaming issues of INFRA (INFRA-19532) > > - Refactor components: `teaclave_utils`, `teaclave_config`, > > `teaclave_cli`, `teaclave_binder` > > - Rewrite README.md to clearly explain the project's highlights in > > security, functionality, and usability. > > - Start to use protobuf for RPC definition > > - SGX SDK starts to use Intel SGX SDK v2.7.1 > > > > ### How would you assess the podling's maturity? > > > > - [ ] Initial setup > > - [x] Working towards first release > > - [ ] Community building > > - [ ] Nearing graduation > > - [ ] Other: > > > > ### Date of last release: > > > > N/A > > > > ### When were the last committers or PPMC members elected? > > > > We haven't started new committers or PPMC members elections yet. > > Currently, our work focus on improving the design and documents to > > make the project more approachable for newcomers. > > > > ### Have your mentors been helpful and responsive? > > > > Yes. Last month, we changed name from MesaTEE to Teaclave. There are a > > lot of changes need to be done. The mentors and infra teams help us a > > lot on the transfer. > > > > ### Is the PPMC managing the podling's brand / trademarks? > > > > We don't find any 3rd parties incorrectly using the podling's name and > > brand. The VP, Brand has approve the project name. > > (PODLINGNAMESEARCH-175) > > > > > > On Sun, Dec 29, 2019 at 10:30 AM Mingshen Sun <ms...@apache.org> wrote: > > > > > > Hi Furkan, thanks for asking. I'll work on the report today. > > > > > > On Sun, Dec 29, 2019 at 10:29 AM Furkan KAMACI <furkankam...@gmail.com> > > wrote: > > > > > > > > Hi All, > > > > > > > > Is there anybody working on report? Let me know if you need help. > > > > > > > > Kind Regards, > > > > Furkan KAMACI > > > > > > > > On Sat, Dec 28, 2019 at 8:11 AM <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 January 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, January 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/January2020 > > > > > > > > > > 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> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
