Sure, I’ll update the report. On Sat, Oct 10, 2020 at 9:18 AM Matt Sicker <boa...@gmail.com> wrote:
> Could be updated now to reflect the status of the release. > > On Wed, Oct 7, 2020 at 17:55 Mingshen Sun <ms...@apache.org> wrote: > > > Hi all, > > > > Since the last report, we have mainly focused on the first release. For > > mentors, please sign-off at here [1] if this looks good to you. Thanks. > > > > [1] > > > https://cwiki.apache.org/confluence/display/INCUBATOR/October2020#teaclave > > > > Here is the report: > > > > ## Teaclave > > > > Teaclave is a universal secure computing platform, making computation on > > privacy-sensitive data safe and simple. > > > > Teaclave has been incubating since 2019-08-20. > > > > ### Three most important unfinished issues to address before graduating: > > > > 1. Improve project structure and documentation > > 2. Grow the community (attracting more committers, contributors, users) > > 3. 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 received contributions from a new contributor. > We > > also received many issue reports and questions regarding the usages, > bugs, > > and roadmap of Teaclave. Also, we presented the Teaclave project in > recent > > ApacheCon to the community and received some useful feedback. > > > > ### How has the project developed since the last report? > > > > The main goal of development since the last report is to resolve > logistics > > towards the first Apache release. This includes license checking, > building > > system improvement, documentation and write-ups. On Oct 6, the Teaclave > > community passed 0.1.0 release voting. The voting with the incubator > > community > > is still ongoing. > > > > ### How would you assess the podling's maturity? > > Please feel free to add your own commentary. > > > > - [ ] Initial setup > > - [x] Working towards first release > > - [x] 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 focuses on the first Apache release. We'll switch to community > > building in the next quarter. Currently, we already have potential > > candidates for the new PPMC members election. > > > > ### Have your mentors been helpful and responsive? > > > > Yes. They have been helpful and very responsive for the first public > > release. > > > > ### 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 Sat, Sep 19, 2020 at 6:13 PM Mingshen Sun <ms...@apache.org> wrote: > > > > > Hi all, > > > > > > I'll prepare the report in these days. Thanks. > > > > > > Best, > > > Mingshen > > > > > > On Sat, Sep 19, 2020 at 6:07 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, 21 October 2020. > > >> 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, October 07). > > >> > > >> 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/October2020 > > >> > > >> 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 > > >> > > > > > > -- > Matt Sicker <boa...@gmail.com> >
