Hi Mingshen,

Thanks for preparing the report!

Kind Regards,
Furkan KAMACI

On Sun, Jun 28, 2020 at 1:15 AM Mingshen Sun <ms...@apache.org> wrote:

> Hi all,
>
> Here is the report on 2020 Q2. Feel free to comment here if I miss
> anything. Thanks.
>
> Best,
> Mingshen
>
>
> ## 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?
>
> No.
>
> ### How has the community developed since the last report?
>
> Since the last report, we started to reach out to people using the
> project and collect suggestions and encourage them to join in the
> community. We have found four organizations and eight projects that
> are using either the Teaclave platform and Teaclave's Rust SGX SDK.
>
> We also created a website for the project:
> https://teaclave.apache.org/, which contains project description,
> community, contributors, documentations and blog posts.
>
> We started a thread to discuss the logo design, but haven't received
> any proposal for now. We will drive this issue in the next few weeks.
>
> We observed more people posting feature suggestions and
> build/deployment issues. More than five new contributors begin to
> contribute bug fixes and introduce new examples.
>
> We started preparing the first Apache release such as logistics on
> licenses of third-party libraries.
>
> ### How has the project developed since the last report?
>
> Since the last report, we have completed the development roadmap
> towards the first public release
> (https://github.com/apache/incubator-teaclave/issues/121) proposed
> last year. We began to put more efforts on improving documents and
> building community.
>
> We wrote many documents in recent weeks including:
>
>   - Try: Tutorials on using the Teaclave platform.
>   - Design: Some explanations of design choices we made.
>   - Contribute: Documents on contributing to Teaclave, such as
> debugging tips and Rust development guideline.
>   - Codebase: Documents for each sub-directory (i.e., libraries in
> Teaclave).
>   - API Docs: Generated API documentations like APIs of Client SDK.
>
> We also provided more examples to help beginners to understand the
> basic usages of the projects.
>
> ### How would you assess the podling's maturity?
>
>   - [ ] 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 improving the documents to make the
> project more approachable for newcomers. Additionally, we see some
> regular contributors recently mainly focus on helping to improve
> examples, SDK, etc.
>
> ### Have your mentors been helpful and responsive?
>
> Yes, our mentors help us with the website development and logo design.
> Also, our mentors provided valuable thoughts regarding Intel's recent
> security 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 approved the project name.
> (PODLINGNAMESEARCH-175)
>
> On Wed, Jun 24, 2020 at 8:39 PM Mingshen Sun <ms...@apache.org> wrote:
> >
> > Hi all,
> >
> > I will work on the report tomorrow. Thanks.
> >
> > Best,
> > Mingshen
> >
> > On Wed, Jun 24, 2020 at 8:37 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 July 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, July 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/July2020
> > >
> > > 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
>
>

Reply via email to