Re: [DISCUSS] Graduate Apache MXNet (incubating) as a Top Level Project

[Mingshen Sun]

+1 (non-binding)

Nice project, good luck!

Mingshen

On Thu, Jun 2, 2022 at 6:57 PM Goson zhang  wrote:
>
> + 1 （non-binding）
>
> Good luck!
>
> XiaoYu  于2022年6月3日周五 08:38写道：
>
> > + 1 （non-binding）
> >
> > good luck~
> >
> >  于2022年6月3日周五 05:09写道：
> > >
> > > +1
> > >
> > > Thanks,
> > > Qing
> > >
> > > 
> > > From: Xingjian SHI 
> > > Sent: Thursday, June 2, 2022 13:18
> > > To: general@incubator.apache.org 
> > > Subject: Re: [DISCUSS] Graduate Apache MXNet (incubating) as a Top Level
> > Project
> > >
> > > +1
> > >
> > > Get Outlook for iOS<
> > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fo0ukefdata=05%7C01%7C%7C267d068aa1264a2a39bb08da44d51d40%7C84df9e7fe9f640afb435%7C1%7C0%7C637897979361991020%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=FQg8u8eQPmolfLDdunwkcJo84tQWQq364xx4KiLokNM%3Dreserved=0
> > >
> > > 
> > > From: Zhaoqi Zhu 
> > > Sent: Thursday, June 2, 2022 1:17:42 PM
> > > To: general@incubator.apache.org 
> > > Subject: Re: [DISCUSS] Graduate Apache MXNet (incubating) as a Top Level
> > Project
> > >
> > > + 1
> > > Looking forward to it! Thanks Joe for driving the effort!
> > >
> > > On 2022/05/02 17:29:53 Joe Evans wrote:
> > > > Hi Apache Incubator Community,
> > > >
> > > > Apache MXNet (incubating) recently held a community discussion[1] and
> > > > vote[2] to graduate to a top level project. The community vote
> > passed[3]
> > > > and we would like to start a discussion with the incubator community
> > about
> > > > graduating the project.
> > > >
> > > > Here is a brief overview of the progress of the Apache MXNet
> > (incubating)
> > > > project and community since entering the incubator:
> > > >
> > > > Community
> > > >
> > > >-
> > > >
> > > >37 new PPMC members were added, bringing the total number of PPMC
> > > >members to 50
> > > >-
> > > >
> > > >56 new committers were added (which include new PPMC members),
> > bringing
> > > >the total number of committers to 87
> > > >-
> > > >
> > > >The total number of contributors is now 870 and growing.
> > > >
> > > > Project
> > > >
> > > >-
> > > >
> > > >18 releases[4] by 13 different release managers. All compliance
> > issues
> > > >have been resolved with the 1.9.0 and 2.0.beta releases.
> > > >-
> > > >
> > > >MXNet website[5] is now compliant with Apache Project Website
> > > >requirements[6]
> > > >-
> > > >
> > > >MXNet has completed the project maturity self assessment[7]
> > > >
> > > >
> > > > I’ve also attached the proposed board resolution below. We welcome any
> > > > feedback or comments.
> > > >
> > > > This discussion will remain open for at least 72 hours.
> > > >
> > > >
> > > > References:
> > > >
> > > > [1]
> > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fl9h2qgb2vqs2y0cm46wh83sgomr9w190data=05%7C01%7C%7C267d068aa1264a2a39bb08da44d51d40%7C84df9e7fe9f640afb435%7C1%7C0%7C637897979361991020%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=VpTSA77LXB2wP6%2BgrGGOVJHhAwXhzrbVCl7hk6U%2F1l4%3Dreserved=0
> > > >
> > > > [2]
> > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fpy1nw6whov78sch5kkm1gcg7cv3zb2svdata=05%7C01%7C%7C267d068aa1264a2a39bb08da44d51d40%7C84df9e7fe9f640afb435%7C1%7C0%7C637897979361991020%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=UsQehqXMv3cBTT4UyXfGdHg3EWCoa9W8BQdrD0tG36g%3Dreserved=0
> > > >
> > > > [3]
> > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fb8bngc6qcb33n0jo6m1rw0ylwlqzkmgxdata=05%7C01%7C%7C267d068aa1264a2a39bb08da44d51d40%7C84df9e7fe9f640afb435%7C1%7C0%7C637897979361991020%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=Bbo9Sg2udT3rwONWioBHeLcqqZ3bR2OZyueNsRfwIq4%3Dreserved=0
> > > >
> > > > [4]
> > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-mxnet%2Freleasesdata=05%7C01%7C%7C267d068aa1264a2a39bb08da44d51d40%7C84df9e7fe9f640afb435%7C1%7C0%7C637897979361991020%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=7b6LqVFIvg%2Bl70FLrz0iuNiF4ZCugHS1UzcHlMfAMqs%3Dreserved=0
> > > > [5]
> > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmxnet.apache.org%2Fdata=05%7C01%7C%7C267d068aa1264a2a39bb08da44d51d40%7C84df9e7fe9f640afb435%7C1%7C0%7C637897979361991020%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=V3yh%2FeQp3YLZl7HtZG2M8H60kh9OIl1cAdWbI4f0%2FrQ%3Dreserved=0
> > > > 

Re: [VOTE] Graduate Apache InLong(Incubating) as a TLP

[Mingshen Sun]

+1 (no-binding)

Good luck!

On Wed, May 25, 2022 at 10:18 AM Liang Chen  wrote:
>
> +1(binding)
>
> Regards
> Liang
>
> Lidong Dai  于2022年5月25日周三 23:07写道：
>
> > +1 (binding)
> > Good luck!
> >
> > Best Regards
> >
> >
> >
> > ---
> > Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC
> > Lidong Dai
> > lidong...@apache.org
> > Linkedin: https://www.linkedin.com/in/dailidong
> > Twitter: @WorkflowEasy 
> >
> > ---
> >
> >
> > On Wed, May 25, 2022 at 10:09 PM Jean-Baptiste Onofré 
> > wrote:
> >
> > > +1 (binding)
> > >
> > > InLong is a great project, and mature to be a TLP. The team got the
> > > Apache way and is executing smoothly.
> > >
> > > Thanks !
> > > Regards
> > > JB
> > >
> > > On Wed, May 25, 2022 at 8:33 AM Charles Zhang 
> > > wrote:
> > > >
> > > > Dear Apache Incubator Community,
> > > >
> > > >
> > > > The InLong community has a discussion thread [1], passed the community
> > > vote
> > > > [2], and the vote result is published [3]. We have discussed the
> > > graduation
> > > > for InLong in the Incubator Community [4], where no issues were raised
> > > and
> > > > lots of positive responses were received.
> > > >
> > > >
> > > > I would like to start this voting thread to request graduating Apache
> > > > InLong (incubating) from the incubator as a TLP. Please provide your
> > vote
> > > > as one of the following options:
> > > >
> > > > [ ] +1 Yes, I support InLong to graduate from the Apache incubator.
> > > >
> > > > [ ] +0 No opinion.
> > > >
> > > > [ ] -1 No, the InLong project is not ready to graduate, because ...
> > > >
> > > >
> > > > The VOTE will remain open for at least 72 hours.
> > > >
> > > >
> > > > Since incubating in ASF, the project itself has become more mature and
> > > >
> > > > stable. The following is a brief summary of the project and community
> > > >
> > > > during the incubation:
> > > >
> > > >
> > > > - 11 versions were released by 6 different release managers, of which 5
> > > >
> > > > versions are the original TubeMQ, and 6 versions are after the name was
> > > >
> > > > changed to InLong. The release cadence is about 2 months [5].
> > > >
> > > >
> > > > - 10 new Committers and 3 PPMCs were added during incubating, they are
> > > from
> > > >
> > > > 4 different organizations. All PPMCs and Committers are spread across 8
> > > >
> > > > different organizations [6].
> > > >
> > > >
> > > > - 101 unique code developers [7].
> > > >
> > > >
> > > > - Closed more than 2200 issues, with an average of 200 issues per
> > version
> > > >
> > > > [8].
> > > >
> > > >
> > > > - All the dependencies were reviewed and ensured they do not bring any
> > > >
> > > > license issues [9].
> > > >
> > > >
> > > > - Evaluated the InLong project and self-checked the InLong maturity
> > model
> > > >
> > > > [10] and the pre-graduation Check [11].
> > > >
> > > >
> > > > - Well and Complete documentation for contributors and users [12].
> > > >
> > > >
> > > > - Created channels like Email, Slack, Twitter, WeChat, and GitHub
> > > >
> > > > Discussions to communicate, with more than 650 subscribers.
> > > >
> > > >
> > > > - Actively participated in or held more than 15 meetups to increase
> > > >
> > > > community influence.
> > > >
> > > >
> > > > Please see the proposed board resolution below and let us know what you
> > > >
> > > > think. The initial PMC members were passed by the discussion and
> > > invitation
> > > >
> > > > [13].
> > > >
> > > >
> > > > [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> > > >
> > > > [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> > > >
> > > > [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> > > >
> > > > [4] https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t
> > > >
> > > > [5] https://inlong.apache.org/download/main/
> > > >
> > > > [6] https://whimsy.apache.org/roster/ppmc/inlong
> > > >
> > > > [7] https://github.com/apache/incubator-inlong/graphs/contributors
> > > >
> > > > [8]
> > > >
> > > >
> > >
> > https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> > > >
> > > > [9] https://github.com/apache/incubator-inlong/tree/master/licenses
> > > >
> > > > [10]
> > > >
> > > >
> > >
> > https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
> > > >
> > > > [11]
> > > >
> > > >
> > https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
> > > >
> > > > [12] https://inlong.apache.org/docs/next/introduction
> > > >
> > > > [13] https://lists.apache.org/thread/mgl2jgpdojb6dzdhnhoq7dfqs26hj2xc
> > > >
> > > >
> > > >
> > >
> > --
> > > >
> > > > Establish the Apache InLong Project
> > > >
> > > > WHEREAS, the Board of Directors deems it to be in the best interests of
> > > >
> > > > 

Re: Places of storing pre-built assets for CI cache on Apache infra

[Mingshen Sun]

Hi Martin,

Thanks for providing the pointer.

nightlies.apache.org is what we want. We have switched to this. Thanks!


Mingshen

On Tue, May 10, 2022 at 5:24 AM Martin Grigorov  wrote:
>
> Hi,
>
> You could use https://nightlies.apache.org/ for this purpose.
> Check https://nightlies.apache.org/authoring.html for instructions how to
> push things there. There are also instructions how to do this from Jenkins,
> Buildbot and Github Actions.
>
> Martin
>
> On Tue, May 10, 2022 at 6:19 AM Mingshen Sun  wrote:
>
> > Hi community,
> >
> > We are facing an issue of storing some pre-built assets for CI usage.
> >
> > From what I understand, there are two places for hosting these files:
> >   - SVN:
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/assets/xxx.tar.gz
> > (I don't think this is a proper place. Because, normally, this is for
> > storing release source code)
> >   - Homepage: https://teaclave.apache.org/assets/xxx.tar.gz (This is
> > for storing static files for web pages and resources. If using this
> > place, we have to commit the assets to our website repo)
> >
> > Specifically, the asset file is the pre-built QEMU images, which is about
> > 60MB.
> >
> > If you have a better idea of hosting these files, please let me know.
> >
> > Mingshen
> > Apache Teaclave (incubating)
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Places of storing pre-built assets for CI cache on Apache infra

[Mingshen Sun]

Hi community,

We are facing an issue of storing some pre-built assets for CI usage.

>From what I understand, there are two places for hosting these files:
  - SVN: 
https://dist.apache.org/repos/dist/dev/incubator/teaclave/assets/xxx.tar.gz
(I don't think this is a proper place. Because, normally, this is for
storing release source code)
  - Homepage: https://teaclave.apache.org/assets/xxx.tar.gz (This is
for storing static files for web pages and resources. If using this
place, we have to commit the assets to our website repo)

Specifically, the asset file is the pre-built QEMU images, which is about 60MB.

If you have a better idea of hosting these files, please let me know.

Mingshen
Apache Teaclave (incubating)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] graduate Apache Doris (Incubating) as a Top Level Project

[Mingshen Sun]

+1 (non-binding)

Glad to hear this. Good luck!

On Sat, Apr 23, 2022 at 10:42 PM 41108453 <41108...@qq.com.invalid> wrote:
>
> +1 (non-binding)
> good luck！
>
>
>
>
>
> -- Original --
> From: 陈明雨  Date: Sun,Apr 24,2022 10:25 AM
> To: general  Subject: Re: [VOTE] graduate Apache Doris (Incubating) as a Top Level Project
>
>
>
> Dear Incubator Community,
>
> After having the discussion in Doris community[1][2], we have passed the 
> community vote[3].
>
> And then made a discussion in general@incubator[4]. We got a lot of positive 
> responses.
>
> And have responded and addressed all suggestions and comments raised.
>
>
>
>
> I would like to start this voting thread to request graduating the Doris 
> project from the incubator as a TLP.
>
> Please provide your vote as one of the following options:
>
>
>
>
> [ ] +1 - Recommend graduation of Apache Doris as a TLP
>
> [ ] 0 - I don't feel strongly about it, but don't object
>
> [ ] -1 - Do not recommend the graduation of Apache Doris because…
>
>
>
>
> The VOTE will remain open for at least 72 hours.
>
>
>
>
> The following is a brief overview of the progress of the Doris project and 
> community since entering the incubator:
>
> 1. Community
>
> - 9 new PPMC members were added, from five different companies, bringing the 
> total number of PPMC members to 22.
>
> - 20 new Committers were added (including the new PPMC members), bringing the 
> total number of Committers to 33.
>
> - The number of Contributors is now 305 and growing[5].
>
> - The dev@doris mailing list currently has 328 subscribers, and all major 
> project discussions are happening in the dev@doris.
>
>
>
>
> 2. Project
>
> - 7 releases by 6 release managers. All compliance issues have been resolved.
>
> - Doris official website[6] is compliant with Apache Foundation 
> requirements[7].
>
> - Project maturity model is detailed in [8].
>
> - See Doris Project Incubation Status[9] for more info.
>
>
>
>
> [1] https://lists.apache.org/thread/90fd2pd3r6wgn4hnfdo3rd0wqkv23cgr
>
> [2] https://lists.apache.org/thread/xc5qj7m2k1ph0mc97otj0nf8vskdfrzv
>
> [3] https://lists.apache.org/thread/9yklv4vbp39jhrzbcx3qgpcs1osk3lyf
>
> [4] https://lists.apache.org/thread/nbncjl8fdq0bcjop6l4747c8x9c06q00
>
> [5] https://github.com/apache/incubator-doris
>
> [6] http://doris.incubator.apache.org/
>
> [7] https://whimsy.apache.org/pods/project/doris
>
> [8] 
> https://cwiki.apache.org/confluence/display/DORIS/Maturity+Assessment+for+Doris
>
> [9] https://incubator.apache.org/projects/doris.html
>
>
>
>
> ==
>
> Establish the Apache Doris Project
>
>
>
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
>
> the Foundation and consistent with the Foundation's purpose to establish
>
> a Project Management Committee charged with the creation and maintenance
>
> of open-source software, for distribution at no charge to the public,
>
> related to a MPP-based interactive SQL data warehousing for reporting
>
> and analysis.
>
>
>
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>
> (PMC), to be known as the "Apache Doris Project", be and hereby is
>
> established pursuant to Bylaws of the Foundation; and be it further
>
>
>
>
> RESOLVED, that the Apache Doris Project be and hereby is responsible for
>
> the creation and maintenance of software related to a MPP-based
>
> interactive SQL data warehousing for reporting and analysis; and be it
>
> further
>
>
>
>
> RESOLVED, that the office of "Vice President, Apache Doris" be and
>
> hereby is created, the person holding such office to serve at the
>
> direction of the Board of Directors as the chair of the Apache Doris
>
> Project, and to have primary responsibility for management of the
>
> projects within the scope of responsibility of the Apache Doris Project;
>
> and be it further
>
>
>
>
> RESOLVED, that the persons listed immediately below be and hereby are
>
> appointed to serve as the initial members of the Apache Doris Project:
>
>
>
>
> * Bin Ling 
> * Bo Wang 
> * Chaoyong Li 
> * Chun Zhao 
> * Conghui Cai 
> * Dayue Gao 
> * De Li 
> * Hangyuan Liu 
> * Hao Chen 
> * HaoPeng Li 
> * Jiafeng Zhang 
> * Kaisen Kang 
> * Ling Miao 
> * Ming Wen 
> * Mingyu Chen 
> * Ruyue Ma 
> * Shao Feng Shi 
> * Sijie Guo 
> * Willem Ning Jiang 
> * Zheng Shao 
> * Zhengguo Yang 
> * Zuo Wei 
>
>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mingyu Chen be appointed to
>
> the office of Vice President, Apache Doris, to serve in accordance with
>
> and subject to the direction of the Board of Directors and the Bylaws of
>
> the Foundation until death, resignation, retirement, removal or
>
> disqualification, or until a successor is appointed; and be it further
>
>
>
>
> RESOLVED, that the Apache Doris Project be and hereby is tasked with the
>
> migration and rationalization of the Apache Incubator Doris 

Re: May 2022 Podling Reporting Timeline

[Mingshen Sun]

Hi all,

I'm from the Teaclave project. I just noticed that we missed April's
report because of the reminder issue.

Should we add it in May's report also? I see some discussions here but
no conclusion yet.

For Teaclave, we have no problem with adding an additional report in May.

Mingshen


On Thu, Apr 21, 2022 at 5:29 AM John D. Ament  wrote:
>
> Hi Christofer
>
> On Thu, Apr 21, 2022 at 4:47 AM Christofer Dutz 
> wrote:
>
> > Hi John,
> >
> > guess I missed the second part of your email ;-)
> >
> > Well, I am a bit unsure if we really should skip the ones that for example
> > missed to submit last month because nobody reminded them, but I think in
> > such a case it would be half a year of information missing. Even if this
> > might not be too useful for the board, I think it's useful to the IPMC.
> >
>
> Basically, I can't (personally) fault a podling for not reporting when no
> reminders were sent out.  We failed to hold up our side of the agreement in
> my mind.  It's great that some podlings still did the work to get a report
> put together.  Perhaps we review those in the past 3 months of missed
> reports and also report them? I'm not sure.
>
>
> >
> > So, I think podlings that missed filling in their parts in the last 3
> > months, should still report this time. But that's just my opinion.
> >
>
> I agree with you, the problem is that every podling (other than new
> podlings possibly) has missed a report (at least from the board's point of
> view).  While there's the main review the IPMC takes on the podlings'
> reports, the board also reviews them.  Since the IPMC lapsed on maintaining
> this, it may end up over burdening the board to put out a report that has
> every single podling reporting in it.
>
>
> >
> > Chris
> >
> > -Original Message-
> > From: Christofer Dutz 
> > Sent: Donnerstag, 21. April 2022 10:42
> > To: general@incubator.apache.org
> > Subject: RE: May 2022 Podling Reporting Timeline
> >
> > I should also add that some projects have failed to submit in the last 3
> > months, so I would add to this list:
> >
> > - brpc
> > - Annotator
> > - Crail
> > - EventMesh
> > - Flagon
> > - Hivemail
> > - InLong
> > - Liminal
> > - Marvin-AI
> > - Milagro
> > - Nemo
> > - Pony Mail
> > - Spot
> > - Teaclave
> > - Wayang
> >
> > So, we're also expecting these projects to report this month.
> >
> > Chris
> >
> > -Original Message-
> > From: John D. Ament 
> > Sent: Mittwoch, 20. April 2022 18:24
> > To: general 
> > Subject: May 2022 Podling Reporting Timeline
> >
> > Note - I'm sending this a week early per procedure as we have some catch
> > up to do.
> >
> > May 2022 Incubator report timeline:
> >
> > https://cwiki.apache.org/confluence/display/INCUBATOR/May2022
> >
> > Wed May 04 -- Podling reports due by end of day
> > Sun May 08 -- Shepherd reviews due by end of day
> > Sun May 08 -- Summary due by end of day
> > Tue May 10 -- Mentor signoff due by end of day
> > Wed May 11 -- Report submitted to Board
> > Wed May 18 -- Board meeting
> >
> > According to podlings.xml, the following podlings are expected to report:
> > - Training
> > - Heron
> > - Tuweni
> > - Pagespeed
> > - Toree
> > - Livy
> > - NLPCraft
> > - Sedona
> > - Doris
> > - SDAP
> > - Linkis
> >
> > I'm suggesting that right now we keep the current reporting periods as we
> > the Incubator PMC have failed to report to the Board, rather than it
> > necessarily being a failing of podlings.  If your podling is on this list
> > but isn't present on the confluence page, please add it with the necessary
> > sections.  i'll take a look in the next few days and make sure podlings.xml
> > represents reality.
> >
> > - John, your friendly neighborhood Report Manager
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT][VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

[Mingshen Sun]

Hi all,

The vote to release Apache Teaclave (incubating) version 0.4.0 Release
Candidate 1 in general@incuabator is now closed.

Vote thread: https://lists.apache.org/thread/0gz5gwybgk5vfvgnxzxrhkgbhk88fpwd

The vote PASSED with 3 binding +1, 1 non binding +1 and 0 -1 votes:

Binding votes:
- Gordon King
- Furkan KAMACI
- Matt Sicker

Non-binding votes:
- Zhaofeng Chen

I will be working on publishing the artifacts of Apache Teaclave
(incubating) v0.4.0 and post an announcement. Thanks.

Mingshen

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

[Mingshen Sun]

Hi all,

Thanks to everyone that participated. The vote to release Apache
Teaclave (incubating) version 0.4.0 Release Candidate 1 in general@incuabator
is now closed.

Vote thread: https://lists.apache.org/thread/0gz5gwybgk5vfvgnxzxrhkgbhk88fpwd

The vote PASSED with 3 binding +1, 1 non binding +1 and 0 -1 votes:

Binding +1 votes:
- Gordon King
- Furkan KAMACI
- Matt Sicker

Non-binding +1 votes:
- Zhaofeng Chen

I will be working on publishing the artifacts of Apache Teaclave
(incubating) v0.4.0 and post an announcement. Thanks.

Mingshen

On Sun, Apr 17, 2022 at 4:13 PM Mingshen Sun  wrote:
>
> Thanks Matt.
>
> We have another release for Teaclave TrustZone SDK v0.2.0-rc.2 also in
> the voting process. Please help to review and vote for it. Thanks.
>
> Mingshen
>
> [1] [VOTE] Release Apache Teaclave TrustZone SDK (incubating)
> v0.2.0-rc.2: https://lists.apache.org/thread/97w2y3b0ttr3dpnfqf0fzgljrxlgxwn9
>
> On Sun, Apr 17, 2022 at 2:18 PM Matt Sicker  wrote:
> >
> > +1
> >
> > Note that the NOTICE file has a slightly outdated copyright year now and 
> > should be updated.
> > —
> > Matt Sicker
> >
> > > On Mar 26, 2022, at 17:08, Mingshen Sun  wrote:
> > >
> > > Hi all,
> > >
> > > I am pleased to be calling this vote for the third release of
> > > Apache Teaclave (incubating) 0.4.0 (release candidate 1).
> > >
> > > The Apache Teaclave (incubating) community has voted and approved the
> > > release, with six +1 votes from IPMC members (Hongbo Chen, Yulong
> > > Zhang, Ran Duan, Yu Ding, Tongxin Li, Rundong Zhou).
> > >
> > > Vote/result threads:
> > > - https://lists.apache.org/thread/z3q5fhobll794x7d3o7pwzgt2bl2dlhk
> > > - https://lists.apache.org/thread/j8lr7168yp5cfynlfz7zpk9om574d0g9
> > >
> > > The release candidate to be voted over is available at:
> > > - https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.4.0-rc.1/
> > >
> > > The release candidate is signed with a GPG key available at:
> > > - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> > >
> > > The Git commit for this release is:
> > > - 
> > > https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=37b248b2b8a5215fed668b4e71b674ce57b0b352
> > >
> > > The release note is available in:
> > > - https://github.com/apache/incubator-teaclave/releases/tag/v0.4.0-rc.1
> > >
> > > Build guide and get started instructions can be found at:
> > > - 
> > > https://github.com/apache/incubator-teaclave/blob/v0.4.0-rc.1/docs/my-first-function.md
> > >
> > > The short version of building Teaclave from the source tarball:
> > >
> > > ```
> > > $ wget 
> > > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.4.0-rc.1/apache-teaclave-0.4.0-rc.1-incubating.tar.gz
> > > $ tar zxvf apache-teaclave-0.4.0-rc.1-incubating.tar.gz && cd \
> > > apache-teaclave-0.4.0-rc.1-incubating
> > > $ # Instructions to verify the source tar:
> > > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> > >
> > > $ docker run --rm -v $(pwd):/teaclave -w /teaclave \
> > > -it teaclave/teaclave-build-ubuntu-1804-sgx-2.14:latest \
> > > bash -c ". /root/.cargo/env && \
> > > . /opt/sgxsdk/environment && \
> > > mkdir -p build && cd build && \
> > > cmake -DTEST_MODE=ON -DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \
> > > make"
> > > ```
> > >
> > > The vote will be open for at least 72 hours. Everyone is welcome to
> > > vote. Please vote by replying to this thread explicitly.
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > Best,
> > >
> > > Mingshen Sun
> > > Apache Teaclave (incubating) PPMC
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

[Mingshen Sun]

Thanks Matt.

We have another release for Teaclave TrustZone SDK v0.2.0-rc.2 also in
the voting process. Please help to review and vote for it. Thanks.

Mingshen

[1] [VOTE] Release Apache Teaclave TrustZone SDK (incubating)
v0.2.0-rc.2: https://lists.apache.org/thread/97w2y3b0ttr3dpnfqf0fzgljrxlgxwn9

On Sun, Apr 17, 2022 at 2:18 PM Matt Sicker  wrote:
>
> +1
>
> Note that the NOTICE file has a slightly outdated copyright year now and 
> should be updated.
> —
> Matt Sicker
>
> > On Mar 26, 2022, at 17:08, Mingshen Sun  wrote:
> >
> > Hi all,
> >
> > I am pleased to be calling this vote for the third release of
> > Apache Teaclave (incubating) 0.4.0 (release candidate 1).
> >
> > The Apache Teaclave (incubating) community has voted and approved the
> > release, with six +1 votes from IPMC members (Hongbo Chen, Yulong
> > Zhang, Ran Duan, Yu Ding, Tongxin Li, Rundong Zhou).
> >
> > Vote/result threads:
> > - https://lists.apache.org/thread/z3q5fhobll794x7d3o7pwzgt2bl2dlhk
> > - https://lists.apache.org/thread/j8lr7168yp5cfynlfz7zpk9om574d0g9
> >
> > The release candidate to be voted over is available at:
> > - https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.4.0-rc.1/
> >
> > The release candidate is signed with a GPG key available at:
> > - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> >
> > The Git commit for this release is:
> > - 
> > https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=37b248b2b8a5215fed668b4e71b674ce57b0b352
> >
> > The release note is available in:
> > - https://github.com/apache/incubator-teaclave/releases/tag/v0.4.0-rc.1
> >
> > Build guide and get started instructions can be found at:
> > - 
> > https://github.com/apache/incubator-teaclave/blob/v0.4.0-rc.1/docs/my-first-function.md
> >
> > The short version of building Teaclave from the source tarball:
> >
> > ```
> > $ wget 
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.4.0-rc.1/apache-teaclave-0.4.0-rc.1-incubating.tar.gz
> > $ tar zxvf apache-teaclave-0.4.0-rc.1-incubating.tar.gz && cd \
> > apache-teaclave-0.4.0-rc.1-incubating
> > $ # Instructions to verify the source tar:
> > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> >
> > $ docker run --rm -v $(pwd):/teaclave -w /teaclave \
> > -it teaclave/teaclave-build-ubuntu-1804-sgx-2.14:latest \
> > bash -c ". /root/.cargo/env && \
> > . /opt/sgxsdk/environment && \
> > mkdir -p build && cd build && \
> > cmake -DTEST_MODE=ON -DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \
> > make"
> > ```
> >
> > The vote will be open for at least 72 hours. Everyone is welcome to
> > vote. Please vote by replying to this thread explicitly.
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Best,
> >
> > Mingshen Sun
> > Apache Teaclave (incubating) PPMC
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

[Mingshen Sun]

Hi Craig and incubator community,

I did try to reach out to our other mentors in the private@teaclave
mailing list. No response yet.

I hope other IPMC can help with our two recent releases [1, 2].

In the meantime, I'll start another thread to call for more mentors in
case our existings are not available for voting. Thanks.

Mingshen

[1] https://lists.apache.org/thread/0gz5gwybgk5vfvgnxzxrhkgbhk88fpwd
[2] https://lists.apache.org/thread/97w2y3b0ttr3dpnfqf0fzgljrxlgxwn9


On Tue, Apr 12, 2022 at 1:50 PM Mingshen Sun  wrote:
>
> Hi Craig,
>
> Thanks! Gordon and Furkan have voted for the release. Let me check with 
> others.
>
> Mingshen
>
> On Tue, Apr 12, 2022 at 1:46 PM Craig Russell  wrote:
> >
> > Hi,
> >
> > You have six Mentors. Have you asked them to review and vote?
> >
> > Warm regards,
> > Craig
> >
> > > On Apr 12, 2022, at 11:23 AM, Mingshen Sun  wrote:
> > >
> > > Dear Community,
> > >
> > > Sorry for the multiple follow ups. Please help to review this release
> > > (we need more IPMC votes). Thanks!
> > >
> > > Mingshen
> > >
> > > On Tue, Apr 5, 2022 at 4:10 PM Mingshen Sun  wrote:
> > >>
> > >> Thanks!
> > >>
> > >> We still need one more IPMC vote for the final release.
> > >>
> > >>
> > >> Mingshen
> > >>
> > >> On Mon, Apr 4, 2022 at 2:37 PM Furkan KAMACI  
> > >> wrote:
> > >>>
> > >>> Hi,
> > >>>
> > >>> +1 (binding)
> > >>>
> > >>> Kind Regards,
> > >>> Furkan KAMACI
> > >>>
> > >>> On 4 Apr 2022 Mon at 23:29 Mingshen Sun  wrote:
> > >>>
> > >>>> Hi all,
> > >>>>
> > >>>> We still need TWO more IPMC binding votes for this release [1]. Please
> > >>>> let me know if there's anything I can help with. Thanks.
> > >>>>
> > >>>> Mingshen
> > >>>>
> > >>>> [1] https://incubator.apache.org/policy/incubation.html#releases
> > >>>>
> > >>>> On Thu, Mar 31, 2022 at 6:56 PM Gordon  wrote:
> > >>>>>
> > >>>>> LGTM, +1 (binding), Thanks
> > >>>>>
> > >>>>>
> > >>>>> On Thu, Mar 31, 2022 at 6:27 PM Mingshen Sun  wrote:
> > >>>>>
> > >>>>>> Hi all,
> > >>>>>>
> > >>>>>> We need more votes from IPMC for this release. Please kindly help to
> > >>>>>> review this new release. Thanks!
> > >>>>>>
> > >>>>>> Mingshen
> > >>>>>>
> > >>>>>> On Wed, Mar 30, 2022 at 6:13 PM Zhaofeng Chen  
> > >>>>>> wrote:
> > >>>>>>>
> > >>>>>>> +1 (binding)
> > >>>>>>>
> > >>>>>>> I checked
> > >>>>>>> - Include the word incubating in the release filename
> > >>>>>>> - LICENSE and NOTICE files exist
> > >>>>>>> - DISCLAIMER file exist
> > >>>>>>> - Build successfully by following the instruction
> > >>>>>>>
> > >>>>>>> Best,
> > >>>>>>> Zhaofeng
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> On Sat, Mar 26, 2022 at 3:09 PM Mingshen Sun 
> > >>>> wrote:
> > >>>>>>>
> > >>>>>>>> Hi all,
> > >>>>>>>>
> > >>>>>>>> I am pleased to be calling this vote for the third release of
> > >>>>>>>> Apache Teaclave (incubating) 0.4.0 (release candidate 1).
> > >>>>>>>>
> > >>>>>>>> The Apache Teaclave (incubating) community has voted and approved
> > >>>> the
> > >>>>>>>> release, with six +1 votes from IPMC members (Hongbo Chen, Yulong
> > >>>>>>>> Zhang, Ran Duan, Yu Ding, Tongxin Li, Rundong Zhou).
> > >>>>>>>>
> > >>>>>>>> Vote/result threads:
> > >>>>>>>> - https://lists.apache.org/thread/z3q5fhobll794x7d3o7pwzgt2bl2dlhk
> > >>

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

[Mingshen Sun]

Hi Craig,

Thanks! Gordon and Furkan have voted for the release. Let me check with others.

Mingshen

On Tue, Apr 12, 2022 at 1:46 PM Craig Russell  wrote:
>
> Hi,
>
> You have six Mentors. Have you asked them to review and vote?
>
> Warm regards,
> Craig
>
> > On Apr 12, 2022, at 11:23 AM, Mingshen Sun  wrote:
> >
> > Dear Community,
> >
> > Sorry for the multiple follow ups. Please help to review this release
> > (we need more IPMC votes). Thanks!
> >
> > Mingshen
> >
> > On Tue, Apr 5, 2022 at 4:10 PM Mingshen Sun  wrote:
> >>
> >> Thanks!
> >>
> >> We still need one more IPMC vote for the final release.
> >>
> >>
> >> Mingshen
> >>
> >> On Mon, Apr 4, 2022 at 2:37 PM Furkan KAMACI  
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>> +1 (binding)
> >>>
> >>> Kind Regards,
> >>> Furkan KAMACI
> >>>
> >>> On 4 Apr 2022 Mon at 23:29 Mingshen Sun  wrote:
> >>>
> >>>> Hi all,
> >>>>
> >>>> We still need TWO more IPMC binding votes for this release [1]. Please
> >>>> let me know if there's anything I can help with. Thanks.
> >>>>
> >>>> Mingshen
> >>>>
> >>>> [1] https://incubator.apache.org/policy/incubation.html#releases
> >>>>
> >>>> On Thu, Mar 31, 2022 at 6:56 PM Gordon  wrote:
> >>>>>
> >>>>> LGTM, +1 (binding), Thanks
> >>>>>
> >>>>>
> >>>>> On Thu, Mar 31, 2022 at 6:27 PM Mingshen Sun  wrote:
> >>>>>
> >>>>>> Hi all,
> >>>>>>
> >>>>>> We need more votes from IPMC for this release. Please kindly help to
> >>>>>> review this new release. Thanks!
> >>>>>>
> >>>>>> Mingshen
> >>>>>>
> >>>>>> On Wed, Mar 30, 2022 at 6:13 PM Zhaofeng Chen  wrote:
> >>>>>>>
> >>>>>>> +1 (binding)
> >>>>>>>
> >>>>>>> I checked
> >>>>>>> - Include the word incubating in the release filename
> >>>>>>> - LICENSE and NOTICE files exist
> >>>>>>> - DISCLAIMER file exist
> >>>>>>> - Build successfully by following the instruction
> >>>>>>>
> >>>>>>> Best,
> >>>>>>> Zhaofeng
> >>>>>>>
> >>>>>>>
> >>>>>>> On Sat, Mar 26, 2022 at 3:09 PM Mingshen Sun 
> >>>> wrote:
> >>>>>>>
> >>>>>>>> Hi all,
> >>>>>>>>
> >>>>>>>> I am pleased to be calling this vote for the third release of
> >>>>>>>> Apache Teaclave (incubating) 0.4.0 (release candidate 1).
> >>>>>>>>
> >>>>>>>> The Apache Teaclave (incubating) community has voted and approved
> >>>> the
> >>>>>>>> release, with six +1 votes from IPMC members (Hongbo Chen, Yulong
> >>>>>>>> Zhang, Ran Duan, Yu Ding, Tongxin Li, Rundong Zhou).
> >>>>>>>>
> >>>>>>>> Vote/result threads:
> >>>>>>>> - https://lists.apache.org/thread/z3q5fhobll794x7d3o7pwzgt2bl2dlhk
> >>>>>>>> - https://lists.apache.org/thread/j8lr7168yp5cfynlfz7zpk9om574d0g9
> >>>>>>>>
> >>>>>>>> The release candidate to be voted over is available at:
> >>>>>>>> -
> >>>>>> https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.4.0-rc.1/
> >>>>>>>>
> >>>>>>>> The release candidate is signed with a GPG key available at:
> >>>>>>>> - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> >>>>>>>>
> >>>>>>>> The Git commit for this release is:
> >>>>>>>> -
> >>>>>>>>
> >>>>>>
> >>>> https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=37b248b2b8a5215fed668b4e71b674ce57b0b352
> >>>>>>>>
> >>>>>>>> The release note is available in:
> 

Re: [VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.2.0-rc.2

[Mingshen Sun]

Dear Community,

Sorry for the multiple follow ups. Please help to review this release
(we need more IPMC votes). Thanks!

Mingshen

On Tue, Apr 5, 2022 at 4:10 PM Mingshen Sun  wrote:
>
> Thanks!
>
> We still need one more IPMC vote for the final release.
>
> Mingshen
>
> On Mon, Apr 4, 2022 at 2:37 PM Furkan KAMACI  wrote:
> >
> > Hi,
> >
> > +1 (binding)
> >
> > Kind Regards,
> > Furkan KAMACI
> >
> > On 4 Apr 2022 Mon at 23:29 Mingshen Sun  wrote:
> >
> > > Hi all,
> > >
> > > We still need TWO more IPMC binding votes for this release [1]. Please
> > > let me know if there's anything I can help with. Thanks.
> > >
> > > Mingshen
> > >
> > > [1] https://incubator.apache.org/policy/incubation.html#releases
> > >
> > > On Thu, Mar 31, 2022 at 6:58 PM Gordon  wrote:
> > > >
> > > > LGTM, +1 (binding), thanks.
> > > >
> > > > On Thu, Mar 31, 2022 at 6:27 PM Mingshen Sun  wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > We need more votes from IPMC for this release. Please kindly help to
> > > > > review this new release. Thanks!
> > > > >
> > > > > Mingshen
> > > > >
> > > > > On Wed, Mar 30, 2022 at 6:10 PM Zhaofeng Chen  wrote:
> > > > > >
> > > > > > +1 (binding)
> > > > > >
> > > > > > I checked
> > > > > > - LICENSE and NOTICE files exist
> > > > > > - DISCLAIMER file exist
> > > > > > - Include the word incubating in the release filename
> > > > > > - No unexpected binary files
> > > > > > - Build successfully by following the instruction
> > > > > >
> > > > > > Best,
> > > > > > Zhaofeng
> > > > > >
> > > > > > On Sun, Mar 27, 2022 at 7:58 PM Yuan Zhuang 
> > > wrote:
> > > > > >
> > > > > > > Dear community,
> > > > > > >
> > > > > > > I am pleased to be calling this vote for the second release of
> > > Apache
> > > > > > > Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 2).
> > > > > > >
> > > > > > > The Apache Teaclave (incubating) community has voted and approved
> > > the
> > > > > > > release, with seven +1 votes from IPMC members (Mingshen Sun,
> > > Yulong
> > > > > Zhang,
> > > > > > > Yu Ding, Tongxin Li, Rundong Zhou, Duan Ran, Rong Fan).
> > > > > > >
> > > > > > > Vote thread:
> > > > > > >
> > > > > > > - https://lists.apache.org/thread/f1qqf8qrc1wvf6zznzbl7y6rkk0thb9n
> > > > > > >
> > > > > > > Result thread:
> > > > > > >
> > > > > > > - https://lists.apache.org/thread/2m55lk5m6nskdn8rmq4ccgo1vrmklb13
> > > > > > >
> > > > > > >
> > > > > > > The release candidate to be voted over is available at:
> > > > > > >
> > > > > > > -
> > > > > > >
> > > > >
> > > https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.2/
> > > > > > >
> > > > > > > The release candidate is signed with a GPG key available at:
> > > > > > >
> > > > > > > - https://downloads.apache.org/incubator/teaclave/KEYS
> > > > > > >
> > > > > > > The Git commit for this release is:
> > > > > > >
> > > > > > > -
> > > > > > >
> > > > >
> > > https://gitbox.apache.org/repos/asf?p=incubator-teaclave-trustzone-sdk.git;a=commit;h=9250da957b4c9dd9c916d582439cca28a359ec02
> > > > > > >
> > > > > > > The release note is available in:
> > > > > > >
> > > > > > > -
> > > > > > >
> > > > >
> > > https://github.com/apache/incubator-teaclave-trustzone-sdk/releases/tag/v0.2.0-rc.2
> > > > > > >
> > > > > > > Build guide and get started instructions can be found at:
> > > > > > >
> > > > > > > -
> &g

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

[Mingshen Sun]

Dear Community,

Sorry for the multiple follow ups. Please help to review this release
(we need more IPMC votes). Thanks!

Mingshen

On Tue, Apr 5, 2022 at 4:10 PM Mingshen Sun  wrote:
>
> Thanks!
>
> We still need one more IPMC vote for the final release.
>
>
> Mingshen
>
> On Mon, Apr 4, 2022 at 2:37 PM Furkan KAMACI  wrote:
> >
> > Hi,
> >
> > +1 (binding)
> >
> > Kind Regards,
> > Furkan KAMACI
> >
> > On 4 Apr 2022 Mon at 23:29 Mingshen Sun  wrote:
> >
> > > Hi all,
> > >
> > > We still need TWO more IPMC binding votes for this release [1]. Please
> > > let me know if there's anything I can help with. Thanks.
> > >
> > > Mingshen
> > >
> > > [1] https://incubator.apache.org/policy/incubation.html#releases
> > >
> > > On Thu, Mar 31, 2022 at 6:56 PM Gordon  wrote:
> > > >
> > > > LGTM, +1 (binding), Thanks
> > > >
> > > >
> > > > On Thu, Mar 31, 2022 at 6:27 PM Mingshen Sun  wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > We need more votes from IPMC for this release. Please kindly help to
> > > > > review this new release. Thanks!
> > > > >
> > > > > Mingshen
> > > > >
> > > > > On Wed, Mar 30, 2022 at 6:13 PM Zhaofeng Chen  wrote:
> > > > > >
> > > > > > +1 (binding)
> > > > > >
> > > > > > I checked
> > > > > > - Include the word incubating in the release filename
> > > > > > - LICENSE and NOTICE files exist
> > > > > > - DISCLAIMER file exist
> > > > > > - Build successfully by following the instruction
> > > > > >
> > > > > > Best,
> > > > > > Zhaofeng
> > > > > >
> > > > > >
> > > > > > On Sat, Mar 26, 2022 at 3:09 PM Mingshen Sun 
> > > wrote:
> > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > I am pleased to be calling this vote for the third release of
> > > > > > > Apache Teaclave (incubating) 0.4.0 (release candidate 1).
> > > > > > >
> > > > > > > The Apache Teaclave (incubating) community has voted and approved
> > > the
> > > > > > > release, with six +1 votes from IPMC members (Hongbo Chen, Yulong
> > > > > > > Zhang, Ran Duan, Yu Ding, Tongxin Li, Rundong Zhou).
> > > > > > >
> > > > > > > Vote/result threads:
> > > > > > > - https://lists.apache.org/thread/z3q5fhobll794x7d3o7pwzgt2bl2dlhk
> > > > > > > - https://lists.apache.org/thread/j8lr7168yp5cfynlfz7zpk9om574d0g9
> > > > > > >
> > > > > > > The release candidate to be voted over is available at:
> > > > > > > -
> > > > > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.4.0-rc.1/
> > > > > > >
> > > > > > > The release candidate is signed with a GPG key available at:
> > > > > > > - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> > > > > > >
> > > > > > > The Git commit for this release is:
> > > > > > > -
> > > > > > >
> > > > >
> > > https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=37b248b2b8a5215fed668b4e71b674ce57b0b352
> > > > > > >
> > > > > > > The release note is available in:
> > > > > > > -
> > > > > https://github.com/apache/incubator-teaclave/releases/tag/v0.4.0-rc.1
> > > > > > >
> > > > > > > Build guide and get started instructions can be found at:
> > > > > > > -
> > > > > > >
> > > > >
> > > https://github.com/apache/incubator-teaclave/blob/v0.4.0-rc.1/docs/my-first-function.md
> > > > > > >
> > > > > > > The short version of building Teaclave from the source tarball:
> > > > > > >
> > > > > > > ```
> > > > > > > $ wget
> > > > > > >
> > > > >
> > > https://di

Re: [VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.2.0-rc.2

[Mingshen Sun]

Thanks!

We still need one more IPMC vote for the final release.

Mingshen

On Mon, Apr 4, 2022 at 2:37 PM Furkan KAMACI  wrote:
>
> Hi,
>
> +1 (binding)
>
> Kind Regards,
> Furkan KAMACI
>
> On 4 Apr 2022 Mon at 23:29 Mingshen Sun  wrote:
>
> > Hi all,
> >
> > We still need TWO more IPMC binding votes for this release [1]. Please
> > let me know if there's anything I can help with. Thanks.
> >
> > Mingshen
> >
> > [1] https://incubator.apache.org/policy/incubation.html#releases
> >
> > On Thu, Mar 31, 2022 at 6:58 PM Gordon  wrote:
> > >
> > > LGTM, +1 (binding), thanks.
> > >
> > > On Thu, Mar 31, 2022 at 6:27 PM Mingshen Sun  wrote:
> > >
> > > > Hi all,
> > > >
> > > > We need more votes from IPMC for this release. Please kindly help to
> > > > review this new release. Thanks!
> > > >
> > > > Mingshen
> > > >
> > > > On Wed, Mar 30, 2022 at 6:10 PM Zhaofeng Chen  wrote:
> > > > >
> > > > > +1 (binding)
> > > > >
> > > > > I checked
> > > > > - LICENSE and NOTICE files exist
> > > > > - DISCLAIMER file exist
> > > > > - Include the word incubating in the release filename
> > > > > - No unexpected binary files
> > > > > - Build successfully by following the instruction
> > > > >
> > > > > Best,
> > > > > Zhaofeng
> > > > >
> > > > > On Sun, Mar 27, 2022 at 7:58 PM Yuan Zhuang 
> > wrote:
> > > > >
> > > > > > Dear community,
> > > > > >
> > > > > > I am pleased to be calling this vote for the second release of
> > Apache
> > > > > > Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 2).
> > > > > >
> > > > > > The Apache Teaclave (incubating) community has voted and approved
> > the
> > > > > > release, with seven +1 votes from IPMC members (Mingshen Sun,
> > Yulong
> > > > Zhang,
> > > > > > Yu Ding, Tongxin Li, Rundong Zhou, Duan Ran, Rong Fan).
> > > > > >
> > > > > > Vote thread:
> > > > > >
> > > > > > - https://lists.apache.org/thread/f1qqf8qrc1wvf6zznzbl7y6rkk0thb9n
> > > > > >
> > > > > > Result thread:
> > > > > >
> > > > > > - https://lists.apache.org/thread/2m55lk5m6nskdn8rmq4ccgo1vrmklb13
> > > > > >
> > > > > >
> > > > > > The release candidate to be voted over is available at:
> > > > > >
> > > > > > -
> > > > > >
> > > >
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.2/
> > > > > >
> > > > > > The release candidate is signed with a GPG key available at:
> > > > > >
> > > > > > - https://downloads.apache.org/incubator/teaclave/KEYS
> > > > > >
> > > > > > The Git commit for this release is:
> > > > > >
> > > > > > -
> > > > > >
> > > >
> > https://gitbox.apache.org/repos/asf?p=incubator-teaclave-trustzone-sdk.git;a=commit;h=9250da957b4c9dd9c916d582439cca28a359ec02
> > > > > >
> > > > > > The release note is available in:
> > > > > >
> > > > > > -
> > > > > >
> > > >
> > https://github.com/apache/incubator-teaclave-trustzone-sdk/releases/tag/v0.2.0-rc.2
> > > > > >
> > > > > > Build guide and get started instructions can be found at:
> > > > > >
> > > > > > -
> > https://github.com/apache/incubator-teaclave-trustzone-sdk#readme
> > > > > >
> > > > > >
> > > > > > The short version of building Teaclave TrustZone SDK from the
> > source
> > > > > > tarball:
> > > > > >
> > > > > > ```
> > > > > > $ wget
> > > > > >
> > > >
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.2/apache-teaclave-trustzone-sdk-0.2.0-rc.2-incubating.tar.gz
> > > > > >
> > > > > > # Instructions to verify the source tar:
> > > > > > #
> > > >
> > htt

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

[Mingshen Sun]

Thanks!

We still need one more IPMC vote for the final release.


Mingshen

On Mon, Apr 4, 2022 at 2:37 PM Furkan KAMACI  wrote:
>
> Hi,
>
> +1 (binding)
>
> Kind Regards,
> Furkan KAMACI
>
> On 4 Apr 2022 Mon at 23:29 Mingshen Sun  wrote:
>
> > Hi all,
> >
> > We still need TWO more IPMC binding votes for this release [1]. Please
> > let me know if there's anything I can help with. Thanks.
> >
> > Mingshen
> >
> > [1] https://incubator.apache.org/policy/incubation.html#releases
> >
> > On Thu, Mar 31, 2022 at 6:56 PM Gordon  wrote:
> > >
> > > LGTM, +1 (binding), Thanks
> > >
> > >
> > > On Thu, Mar 31, 2022 at 6:27 PM Mingshen Sun  wrote:
> > >
> > > > Hi all,
> > > >
> > > > We need more votes from IPMC for this release. Please kindly help to
> > > > review this new release. Thanks!
> > > >
> > > > Mingshen
> > > >
> > > > On Wed, Mar 30, 2022 at 6:13 PM Zhaofeng Chen  wrote:
> > > > >
> > > > > +1 (binding)
> > > > >
> > > > > I checked
> > > > > - Include the word incubating in the release filename
> > > > > - LICENSE and NOTICE files exist
> > > > > - DISCLAIMER file exist
> > > > > - Build successfully by following the instruction
> > > > >
> > > > > Best,
> > > > > Zhaofeng
> > > > >
> > > > >
> > > > > On Sat, Mar 26, 2022 at 3:09 PM Mingshen Sun 
> > wrote:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > I am pleased to be calling this vote for the third release of
> > > > > > Apache Teaclave (incubating) 0.4.0 (release candidate 1).
> > > > > >
> > > > > > The Apache Teaclave (incubating) community has voted and approved
> > the
> > > > > > release, with six +1 votes from IPMC members (Hongbo Chen, Yulong
> > > > > > Zhang, Ran Duan, Yu Ding, Tongxin Li, Rundong Zhou).
> > > > > >
> > > > > > Vote/result threads:
> > > > > > - https://lists.apache.org/thread/z3q5fhobll794x7d3o7pwzgt2bl2dlhk
> > > > > > - https://lists.apache.org/thread/j8lr7168yp5cfynlfz7zpk9om574d0g9
> > > > > >
> > > > > > The release candidate to be voted over is available at:
> > > > > > -
> > > > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.4.0-rc.1/
> > > > > >
> > > > > > The release candidate is signed with a GPG key available at:
> > > > > > - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> > > > > >
> > > > > > The Git commit for this release is:
> > > > > > -
> > > > > >
> > > >
> > https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=37b248b2b8a5215fed668b4e71b674ce57b0b352
> > > > > >
> > > > > > The release note is available in:
> > > > > > -
> > > > https://github.com/apache/incubator-teaclave/releases/tag/v0.4.0-rc.1
> > > > > >
> > > > > > Build guide and get started instructions can be found at:
> > > > > > -
> > > > > >
> > > >
> > https://github.com/apache/incubator-teaclave/blob/v0.4.0-rc.1/docs/my-first-function.md
> > > > > >
> > > > > > The short version of building Teaclave from the source tarball:
> > > > > >
> > > > > > ```
> > > > > > $ wget
> > > > > >
> > > >
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.4.0-rc.1/apache-teaclave-0.4.0-rc.1-incubating.tar.gz
> > > > > > $ tar zxvf apache-teaclave-0.4.0-rc.1-incubating.tar.gz && cd \
> > > > > > apache-teaclave-0.4.0-rc.1-incubating
> > > > > > $ # Instructions to verify the source tar:
> > > > > >
> > > >
> > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> > > > > >
> > > > > > $ docker run --rm -v $(pwd):/teaclave -w /teaclave \
> > > > > > -it teaclave/teaclave-build-ubuntu-1804-sgx-2.14:latest \
> > > > > > bash -c ". /root/.cargo/env && \
> > > > > > . /opt/sgxsdk/environment &&a

Re: [VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.2.0-rc.2

[Mingshen Sun]

Hi all,

We still need TWO more IPMC binding votes for this release [1]. Please
let me know if there's anything I can help with. Thanks.

Mingshen

[1] https://incubator.apache.org/policy/incubation.html#releases

On Thu, Mar 31, 2022 at 6:58 PM Gordon  wrote:
>
> LGTM, +1 (binding), thanks.
>
> On Thu, Mar 31, 2022 at 6:27 PM Mingshen Sun  wrote:
>
> > Hi all,
> >
> > We need more votes from IPMC for this release. Please kindly help to
> > review this new release. Thanks!
> >
> > Mingshen
> >
> > On Wed, Mar 30, 2022 at 6:10 PM Zhaofeng Chen  wrote:
> > >
> > > +1 (binding)
> > >
> > > I checked
> > > - LICENSE and NOTICE files exist
> > > - DISCLAIMER file exist
> > > - Include the word incubating in the release filename
> > > - No unexpected binary files
> > > - Build successfully by following the instruction
> > >
> > > Best,
> > > Zhaofeng
> > >
> > > On Sun, Mar 27, 2022 at 7:58 PM Yuan Zhuang  wrote:
> > >
> > > > Dear community,
> > > >
> > > > I am pleased to be calling this vote for the second release of Apache
> > > > Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 2).
> > > >
> > > > The Apache Teaclave (incubating) community has voted and approved the
> > > > release, with seven +1 votes from IPMC members (Mingshen Sun, Yulong
> > Zhang,
> > > > Yu Ding, Tongxin Li, Rundong Zhou, Duan Ran, Rong Fan).
> > > >
> > > > Vote thread:
> > > >
> > > > - https://lists.apache.org/thread/f1qqf8qrc1wvf6zznzbl7y6rkk0thb9n
> > > >
> > > > Result thread:
> > > >
> > > > - https://lists.apache.org/thread/2m55lk5m6nskdn8rmq4ccgo1vrmklb13
> > > >
> > > >
> > > > The release candidate to be voted over is available at:
> > > >
> > > > -
> > > >
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.2/
> > > >
> > > > The release candidate is signed with a GPG key available at:
> > > >
> > > > - https://downloads.apache.org/incubator/teaclave/KEYS
> > > >
> > > > The Git commit for this release is:
> > > >
> > > > -
> > > >
> > https://gitbox.apache.org/repos/asf?p=incubator-teaclave-trustzone-sdk.git;a=commit;h=9250da957b4c9dd9c916d582439cca28a359ec02
> > > >
> > > > The release note is available in:
> > > >
> > > > -
> > > >
> > https://github.com/apache/incubator-teaclave-trustzone-sdk/releases/tag/v0.2.0-rc.2
> > > >
> > > > Build guide and get started instructions can be found at:
> > > >
> > > > - https://github.com/apache/incubator-teaclave-trustzone-sdk#readme
> > > >
> > > >
> > > > The short version of building Teaclave TrustZone SDK from the source
> > > > tarball:
> > > >
> > > > ```
> > > > $ wget
> > > >
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.2/apache-teaclave-trustzone-sdk-0.2.0-rc.2-incubating.tar.gz
> > > >
> > > > # Instructions to verify the source tar:
> > > > #
> > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> > > >
> > > > $ tar zxvf apache-teaclave-trustzone-sdk-0.2.0-rc.2-incubating.tar.gz
> > &&
> > > > cd apache-teaclave-trustzone-sdk-0.2.0-rc.2-incubating
> > > >
> > > > # Build the SDK and TAs
> > > > $ docker run -v$(pwd):/teaclave -w /teaclave -it
> > > > teaclave/teaclave-trustzone-sdk-build:0.3.0 bash -c "./setup.sh &&
> > source
> > > > environment && make"
> > > >
> > > > # Test all examples with QEMU
> > > > $ docker run -v$(pwd):/teaclave -w /teaclave -it
> > > > teaclave/teaclave-trustzone-sdk-build:0.3.0 bash -c "cd ci && ./ci.sh"
> > > > ```
> > > >
> > > > The vote will be open for at least 72 hours. Everyone is welcome to
> > vote.
> > > > Please vote by replying to this thread explicitly.
> > > >
> > > >   [ ] +1 approve
> > > >   [ ] +0 no opinion
> > > >   [ ] -1 disapprove with the reason
> > > >
> > > >
> > > >
> > > > Best,
> > > >
> > > > Yuan Zhuang
> > > > Apache Teaclave (incubating) Committer
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

[Mingshen Sun]

Hi all,

We still need TWO more IPMC binding votes for this release [1]. Please
let me know if there's anything I can help with. Thanks.

Mingshen

[1] https://incubator.apache.org/policy/incubation.html#releases

On Thu, Mar 31, 2022 at 6:56 PM Gordon  wrote:
>
> LGTM, +1 (binding), Thanks
>
>
> On Thu, Mar 31, 2022 at 6:27 PM Mingshen Sun  wrote:
>
> > Hi all,
> >
> > We need more votes from IPMC for this release. Please kindly help to
> > review this new release. Thanks!
> >
> > Mingshen
> >
> > On Wed, Mar 30, 2022 at 6:13 PM Zhaofeng Chen  wrote:
> > >
> > > +1 (binding)
> > >
> > > I checked
> > > - Include the word incubating in the release filename
> > > - LICENSE and NOTICE files exist
> > > - DISCLAIMER file exist
> > > - Build successfully by following the instruction
> > >
> > > Best,
> > > Zhaofeng
> > >
> > >
> > > On Sat, Mar 26, 2022 at 3:09 PM Mingshen Sun  wrote:
> > >
> > > > Hi all,
> > > >
> > > > I am pleased to be calling this vote for the third release of
> > > > Apache Teaclave (incubating) 0.4.0 (release candidate 1).
> > > >
> > > > The Apache Teaclave (incubating) community has voted and approved the
> > > > release, with six +1 votes from IPMC members (Hongbo Chen, Yulong
> > > > Zhang, Ran Duan, Yu Ding, Tongxin Li, Rundong Zhou).
> > > >
> > > > Vote/result threads:
> > > > - https://lists.apache.org/thread/z3q5fhobll794x7d3o7pwzgt2bl2dlhk
> > > > - https://lists.apache.org/thread/j8lr7168yp5cfynlfz7zpk9om574d0g9
> > > >
> > > > The release candidate to be voted over is available at:
> > > > -
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.4.0-rc.1/
> > > >
> > > > The release candidate is signed with a GPG key available at:
> > > > - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> > > >
> > > > The Git commit for this release is:
> > > > -
> > > >
> > https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=37b248b2b8a5215fed668b4e71b674ce57b0b352
> > > >
> > > > The release note is available in:
> > > > -
> > https://github.com/apache/incubator-teaclave/releases/tag/v0.4.0-rc.1
> > > >
> > > > Build guide and get started instructions can be found at:
> > > > -
> > > >
> > https://github.com/apache/incubator-teaclave/blob/v0.4.0-rc.1/docs/my-first-function.md
> > > >
> > > > The short version of building Teaclave from the source tarball:
> > > >
> > > > ```
> > > > $ wget
> > > >
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.4.0-rc.1/apache-teaclave-0.4.0-rc.1-incubating.tar.gz
> > > > $ tar zxvf apache-teaclave-0.4.0-rc.1-incubating.tar.gz && cd \
> > > > apache-teaclave-0.4.0-rc.1-incubating
> > > > $ # Instructions to verify the source tar:
> > > >
> > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> > > >
> > > > $ docker run --rm -v $(pwd):/teaclave -w /teaclave \
> > > > -it teaclave/teaclave-build-ubuntu-1804-sgx-2.14:latest \
> > > > bash -c ". /root/.cargo/env && \
> > > > . /opt/sgxsdk/environment && \
> > > > mkdir -p build && cd build && \
> > > > cmake -DTEST_MODE=ON -DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \
> > > > make"
> > > > ```
> > > >
> > > > The vote will be open for at least 72 hours. Everyone is welcome to
> > > > vote. Please vote by replying to this thread explicitly.
> > > >
> > > > [ ] +1 approve
> > > > [ ] +0 no opinion
> > > > [ ] -1 disapprove with the reason
> > > >
> > > > Best,
> > > >
> > > > Mingshen Sun
> > > > Apache Teaclave (incubating) PPMC
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.2.0-rc.2

[Mingshen Sun]

Hi all,

We need more votes from IPMC for this release. Please kindly help to
review this new release. Thanks!

Mingshen

On Wed, Mar 30, 2022 at 6:10 PM Zhaofeng Chen  wrote:
>
> +1 (binding)
>
> I checked
> - LICENSE and NOTICE files exist
> - DISCLAIMER file exist
> - Include the word incubating in the release filename
> - No unexpected binary files
> - Build successfully by following the instruction
>
> Best,
> Zhaofeng
>
> On Sun, Mar 27, 2022 at 7:58 PM Yuan Zhuang  wrote:
>
> > Dear community,
> >
> > I am pleased to be calling this vote for the second release of Apache
> > Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 2).
> >
> > The Apache Teaclave (incubating) community has voted and approved the
> > release, with seven +1 votes from IPMC members (Mingshen Sun, Yulong Zhang,
> > Yu Ding, Tongxin Li, Rundong Zhou, Duan Ran, Rong Fan).
> >
> > Vote thread:
> >
> > - https://lists.apache.org/thread/f1qqf8qrc1wvf6zznzbl7y6rkk0thb9n
> >
> > Result thread:
> >
> > - https://lists.apache.org/thread/2m55lk5m6nskdn8rmq4ccgo1vrmklb13
> >
> >
> > The release candidate to be voted over is available at:
> >
> > -
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.2/
> >
> > The release candidate is signed with a GPG key available at:
> >
> > - https://downloads.apache.org/incubator/teaclave/KEYS
> >
> > The Git commit for this release is:
> >
> > -
> > https://gitbox.apache.org/repos/asf?p=incubator-teaclave-trustzone-sdk.git;a=commit;h=9250da957b4c9dd9c916d582439cca28a359ec02
> >
> > The release note is available in:
> >
> > -
> > https://github.com/apache/incubator-teaclave-trustzone-sdk/releases/tag/v0.2.0-rc.2
> >
> > Build guide and get started instructions can be found at:
> >
> > - https://github.com/apache/incubator-teaclave-trustzone-sdk#readme
> >
> >
> > The short version of building Teaclave TrustZone SDK from the source
> > tarball:
> >
> > ```
> > $ wget
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.2/apache-teaclave-trustzone-sdk-0.2.0-rc.2-incubating.tar.gz
> >
> > # Instructions to verify the source tar:
> > # https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> >
> > $ tar zxvf apache-teaclave-trustzone-sdk-0.2.0-rc.2-incubating.tar.gz &&
> > cd apache-teaclave-trustzone-sdk-0.2.0-rc.2-incubating
> >
> > # Build the SDK and TAs
> > $ docker run -v$(pwd):/teaclave -w /teaclave -it
> > teaclave/teaclave-trustzone-sdk-build:0.3.0 bash -c "./setup.sh && source
> > environment && make"
> >
> > # Test all examples with QEMU
> > $ docker run -v$(pwd):/teaclave -w /teaclave -it
> > teaclave/teaclave-trustzone-sdk-build:0.3.0 bash -c "cd ci && ./ci.sh"
> > ```
> >
> > The vote will be open for at least 72 hours. Everyone is welcome to vote.
> > Please vote by replying to this thread explicitly.
> >
> >   [ ] +1 approve
> >   [ ] +0 no opinion
> >   [ ] -1 disapprove with the reason
> >
> >
> >
> > Best,
> >
> > Yuan Zhuang
> > Apache Teaclave (incubating) Committer
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

[Mingshen Sun]

Hi all,

We need more votes from IPMC for this release. Please kindly help to
review this new release. Thanks!

Mingshen

On Wed, Mar 30, 2022 at 6:13 PM Zhaofeng Chen  wrote:
>
> +1 (binding)
>
> I checked
> - Include the word incubating in the release filename
> - LICENSE and NOTICE files exist
> - DISCLAIMER file exist
> - Build successfully by following the instruction
>
> Best,
> Zhaofeng
>
>
> On Sat, Mar 26, 2022 at 3:09 PM Mingshen Sun  wrote:
>
> > Hi all,
> >
> > I am pleased to be calling this vote for the third release of
> > Apache Teaclave (incubating) 0.4.0 (release candidate 1).
> >
> > The Apache Teaclave (incubating) community has voted and approved the
> > release, with six +1 votes from IPMC members (Hongbo Chen, Yulong
> > Zhang, Ran Duan, Yu Ding, Tongxin Li, Rundong Zhou).
> >
> > Vote/result threads:
> > - https://lists.apache.org/thread/z3q5fhobll794x7d3o7pwzgt2bl2dlhk
> > - https://lists.apache.org/thread/j8lr7168yp5cfynlfz7zpk9om574d0g9
> >
> > The release candidate to be voted over is available at:
> > - https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.4.0-rc.1/
> >
> > The release candidate is signed with a GPG key available at:
> > - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> >
> > The Git commit for this release is:
> > -
> > https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=37b248b2b8a5215fed668b4e71b674ce57b0b352
> >
> > The release note is available in:
> > - https://github.com/apache/incubator-teaclave/releases/tag/v0.4.0-rc.1
> >
> > Build guide and get started instructions can be found at:
> > -
> > https://github.com/apache/incubator-teaclave/blob/v0.4.0-rc.1/docs/my-first-function.md
> >
> > The short version of building Teaclave from the source tarball:
> >
> > ```
> > $ wget
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.4.0-rc.1/apache-teaclave-0.4.0-rc.1-incubating.tar.gz
> > $ tar zxvf apache-teaclave-0.4.0-rc.1-incubating.tar.gz && cd \
> > apache-teaclave-0.4.0-rc.1-incubating
> > $ # Instructions to verify the source tar:
> > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> >
> > $ docker run --rm -v $(pwd):/teaclave -w /teaclave \
> > -it teaclave/teaclave-build-ubuntu-1804-sgx-2.14:latest \
> > bash -c ". /root/.cargo/env && \
> > . /opt/sgxsdk/environment && \
> > mkdir -p build && cd build && \
> > cmake -DTEST_MODE=ON -DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \
> > make"
> > ```
> >
> > The vote will be open for at least 72 hours. Everyone is welcome to
> > vote. Please vote by replying to this thread explicitly.
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Best,
> >
> > Mingshen Sun
> > Apache Teaclave (incubating) PPMC
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

[Mingshen Sun]

Hi all,

I am pleased to be calling this vote for the third release of
Apache Teaclave (incubating) 0.4.0 (release candidate 1).

The Apache Teaclave (incubating) community has voted and approved the
release, with six +1 votes from IPMC members (Hongbo Chen, Yulong
Zhang, Ran Duan, Yu Ding, Tongxin Li, Rundong Zhou).

Vote/result threads:
- https://lists.apache.org/thread/z3q5fhobll794x7d3o7pwzgt2bl2dlhk
- https://lists.apache.org/thread/j8lr7168yp5cfynlfz7zpk9om574d0g9

The release candidate to be voted over is available at:
- https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.4.0-rc.1/

The release candidate is signed with a GPG key available at:
- https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS

The Git commit for this release is:
- 
https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=37b248b2b8a5215fed668b4e71b674ce57b0b352

The release note is available in:
- https://github.com/apache/incubator-teaclave/releases/tag/v0.4.0-rc.1

Build guide and get started instructions can be found at:
- 
https://github.com/apache/incubator-teaclave/blob/v0.4.0-rc.1/docs/my-first-function.md

The short version of building Teaclave from the source tarball:

```
$ wget 
https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.4.0-rc.1/apache-teaclave-0.4.0-rc.1-incubating.tar.gz
$ tar zxvf apache-teaclave-0.4.0-rc.1-incubating.tar.gz && cd \
apache-teaclave-0.4.0-rc.1-incubating
$ # Instructions to verify the source tar:
https://teaclave.apache.org/download/#verify-the-integrity-of-the-files

$ docker run --rm -v $(pwd):/teaclave -w /teaclave \
-it teaclave/teaclave-build-ubuntu-1804-sgx-2.14:latest \
bash -c ". /root/.cargo/env && \
. /opt/sgxsdk/environment && \
mkdir -p build && cd build && \
cmake -DTEST_MODE=ON -DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \
make"
```

The vote will be open for at least 72 hours. Everyone is welcome to
vote. Please vote by replying to this thread explicitly.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Best,

Mingshen Sun
Apache Teaclave (incubating) PPMC

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Please remove superseded releases from dist areas

[Mingshen Sun]

Thanks, Sebb.

Teaclave has resolved this issue and updated the download page.

Mingshen

On Tue, Mar 15, 2022 at 10:50 AM sebb  wrote:
>
> Several podlings have multiple releases under the dist/release area.
> Old versions should please be removed shortly after the next version
> has been released.
>
> The policy can be found at [1] under the "Current and older releases" heading.
>
> The podlings with multiple releases include:
> AGE
> Annotator
> Brpc
> Kyuubi
> Liminal
> Livy
> Milagro
> Mxnet
> NLPCraft
> Nuttx
> Pegasus
> Sedona
> Teaclave
> Tuweni
>
> Please check your release area under [2], and remove any old versions.
> Also please make sure that any release documentation mentions the need
> to tidy up the release area.
>
> Thanks,
> Sebb
> [1]  https://infra.apache.org/release-download-pages.html
> [2]  https://dist.apache.org/repos/dist/release/incubator
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [IMPORTANT] Linkis, Doris, Shenyu, MXNet. Website branding issue

[Mingshen Sun]

Hi all,

I also posted a thread here about the logo wall and powered by page:
https://lists.apache.org/thread/4wr5y6bq57yllf44yjm69vlb393xh2t7

We need to be careful when using other organizations' logos.

Mingshen

On Mon, Dec 13, 2021 at 7:22 AM Sheng Zha  wrote:
>
> ACK, MXNet PPMC will devise a fix within the timeframe.
>
> Thanks,
> Sheng
>
> On Sun, Dec 12, 2021 at 10:19 AM kezhenxu94@apache
>  wrote:
> >
> > Hi the PPMC of
> >
> > - Linkis
> > - Doris
> > - Shenyu
> > - MXNet
> >
> > (And maybe more...)
> >
> > I notice that your website violates the best practice of “thanks pages” / 
> > “Trusted By” / “User Wall” [1] and needs some changes to the homepage. The 
> > "TL;DR;” version is not to list your users in the homepage, you can move 
> > them to a submenu like “Users” or similar, but not list them in homepage. 
> > For more rationale please read [1].
> >
> > Please do not ignore this request and adjust the homepage ideally within 30 
> > days.
> >
> > [1] https://apache.org/foundation/marks/linking#projectthanks
> >
> > —
> > Zhenxu Ke (柯振旭)
> > GitHub @kezhenxu94
> > Apache Incubator PMC
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.2.0-rc.1 (with the correct KEYS link)

[Mingshen Sun]

Hi all,

The vote for releasing Apache Teaclave TrustZone SDK (incubating)
v0.2.0-rc.1 is closed.

We received 7(+1) non-binding votes and 1(-1) binding vote.

Since there are some issues about license review, we will work on this
and prepare for the second release candidate later. Thanks!

Mingshen

On Tue, Nov 30, 2021 at 10:04 PM Justin Mclean  wrote:
>
> Hi,
>
> > Basically, there are two issues in the release tar bar:
> >  1. We are using a customized Rust's standard library and include
> > modified sources and other upstream code in our codebase.
> >  2. We also include code of OP-TEE libraries as our vendored
> > third-party libraries.
> >
> > These two codebases are from other parties and indeed difficult to review.
>
> And it looks like they also contain things that are not compatible with the 
> Apache license. Category B is OK to depend upon, but you can’t have a non 
> optional Category X dependancy (e.g something GPL or LGPL licensed).
>
> > We are releasing in this way to make sure all dependencies are
> > self-contained. Of course, instead of including third-party sources,
> > we can just include patches and download all dependencies during the
> > build time. What do you think?
>
> That would certainly make it easier to review, but you would still need to 
> solve the GPL/GPL dependancy issue.
>
> Note that these issue don't have to be sorted right away, with the correct 
> information in LICENSE and the WIP DISCLAIMER you could make a release. They 
> would need to be corrected before graduation.
>
> Kind Regards,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.2.0-rc.1 (with the correct KEYS link)

[Mingshen Sun]

Hi Justin,

Thanks for the careful screening.

Basically, there are two issues in the release tar bar:
  1. We are using a customized Rust's standard library and include
modified sources and other upstream code in our codebase.
  2. We also include code of OP-TEE libraries as our vendored
third-party libraries.

These two codebases are from other parties and indeed difficult to review.

We are releasing in this way to make sure all dependencies are
self-contained. Of course, instead of including third-party sources,
we can just include patches and download all dependencies during the
build time. What do you think?

Mingshen


On Tue, Nov 30, 2021 at 7:46 PM Justin Mclean  wrote:
>
> Hi,
>
> Sorry but -1 (binding) due to incompatible licenses in source release and 
> those licenses not mentioned. A WIP disclaimer isn’t a blanket exception and 
> you need to note what the issues are and inform the used of what licenses are 
> incompatible. Please see [4]
>
> When voting on releases, it’s also a good idea to indicate if your vote is 
> binding (only IPMC members votes are binding here) and what you checked in 
> the release.
>
> I checked:
> - incubating in name
> - signatures and hashes are fine
> - disclaimer (WIP) exists
> - NOTICE and LICENSE need more work. There seem to be a large number of 
> things missing from LICENSE.
> -  a large number of files do not have have header which make this release 
> very difficult to review
> - Looks likes the release may contain compiled code? [7][8]
> - I didn’t compile from source
>
> With the LICENSE I don’t see these files licensed mentioned [1] This is 
> concerning [2] as these are not mentioned in LICENSE. This license [2] is not 
> compatible with the ALv2. There several other fonts files that are also 
> included in the release. This file [5] is under a Category X  license, as are 
> I assume parts of this file. [6]
>
> Kind Regards,
> Justin
>
> 1.  ./rust/rust/library/stdarch/crates/stdarch-verify/arm-intrinsics.html
> 2. ./rust/rust/COPYRIGHT
> 3. ./rust/rust/src/librustdoc/html/static/fonts/FiraSans-LICENSE.txt
> 4. https://issues.apache.org/jira/browse/LEGAL-469
> 5. ./optee/build/ti/Makefile
> 6 ./optee/optee_os/lib/libutee/arch/arm/gprof/gmon_out.h
> 7. 
> ./rust/rust/library/stdarch/crates/std_detect/src/detect/test_data/linux-rpi3.auxv
> 8 ./rust/rust/src/test/ui/macros/not-utf8.bin
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: About organization/project logos in the "powered by" or "community" page

[Mingshen Sun]

Thanks Justin, this guideline is very helpful.

We should also notify those projects who are not complying with the
guidelines. As a PPMC of the incubating project, I always follow
practices of TLP.

Mingshen

On Mon, Nov 29, 2021 at 8:12 PM Justin Mclean  wrote:
>
> Hi,
>
> > Also, what's the best practice for this? I saw most projects only put
> > a list of names/links.
>
>
> Some care need to be taken in doing this from a branding perspective and ASF 
> policy view. In general this MUST NOT be on the home page.
>
> From a recent email that was sent out:
>
> WHY: the ASF is strictly vendor-neutral. Listing company names and/or logos 
> on a project's home page is disallowed as it can imply "ownership" or 
> preferred status or otherwise imbalanced relationship. Whether this is the 
> case or not, it is not acceptable. The policy is the same as "thanking" 
> companies for their support of a project 
> http://apache.org/foundation/marks/linking#projectthanks 
> 
>
> WHAT WE'RE NOT SAYING: please don't misunderstand the "no third party logos 
> on your homepage" policy. We *love* projects promoting their users! Many of 
> you have commented that we always include user organizations in our press 
> releases --one of the first things that members of the media and analyst 
> community ask is, "who uses you?". We're proud of all our projects and your 
> collective efforts: we want to ensure that everyone is being fairly 
> represented and considered.
>
> I believe a number of project and not complying with the above.
>
> Kind Regards,
> Justin

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

About organization/project logos in the "powered by" or "community" page

[Mingshen Sun]

Hi all,

I saw some projects' websites put a "logo wall" with
organization/project logos in their "powered by" or "community" page
[1,2]. Do we need to have explicit consents from those organizations
before putting their logos?

Also, what's the best practice for this? I saw most projects only put
a list of names/links.

Thanks.

- [1] https://tvm.apache.org/community
- [2] https://mxnet.apache.org

Mingshen

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.2.0-rc.1 (with the correct KEYS link)

[Mingshen Sun]

Hi all,

I am pleased to be calling this vote for the second release of
Apache Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 1).

The Apache Teaclave (incubating) community has voted and approved the
release, with four +1 votes from IPMC members (Yuan Zhuang, Rong Fan,
Rundong Zhou, Tongxin Li).

Vote/result threads:
- https://lists.apache.org/thread/41mpj6r4xo6h49mh5kj0npx6l3o2n2ct
- https://lists.apache.org/thread/66kbrq8rq8f54pq46g6b1wzlmx70jttt

The release candidate to be voted over is available at:
  - 
https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.1/

The release candidate is signed with a GPG key available at:
  - https://downloads.apache.org/incubator/teaclave/KEYS

The Git commit for this release is:
  - 
https://gitbox.apache.org/repos/asf?p=incubator-teaclave-trustzone-sdk.git;a=commit;h=3984789a59fdfe58757a7a60e490a414ca918478

The release note is available in:
  - 
https://github.com/apache/incubator-teaclave-trustzone-sdk/releases/tag/v0.2.0-rc.1

Build guide and get started instructions can be found at:
  - 
https://github.com/apache/incubator-teaclave-trustzone-sdk/blob/release-v0.2.0/docs/getting-started-with-optee-for-qemu-armv8.md

The short version of building Teaclave from the source tarball:

```
$ wget 
https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.1/apache-teaclave-trustzone-sdk-0.2.0-rc.1-incubating.tar.gz

$ # Instructions to verify the source tar: \
https://teaclave.apache.org/download/#verify-the-integrity-of-the-files

$ tar zxvf apache-teaclave-trustzone-sdk-0.2.0-rc.1-incubating.tar.gz && cd \
  apache-teaclave-trustzone-sdk-0.2.0-incubating

$ # Build the SDK and TAs
$ docker run -v`pwd`:/teaclave -w /teaclave -it
teaclave/teaclave-trustzone-sdk-build:0.3.0 \
   bash -c "source environment && make"

$ # Test all examples with QEMU
$ docker run -v`pwd`:/teaclave -w /teaclave -it
teaclave/teaclave-trustzone-sdk-build:0.3.0 \
   bash -c "cd ci && ./ci.sh"
```

The vote will be open for at least 72 hours. Everyone is welcome to
vote. Please vote by replying to this thread explicitly.

  [ ] +1 approve
  [ ] +0 no opinion
  [ ] -1 disapprove with the reason

Anyone can participate in testing and voting, not just committers,
please feel free to try out the release candidate and provide your
votes. Please also reply with things you have checked.

A checklist for reference:
  - 
https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist

Best,

Mingshen Sun
Apache Teaclave (incubating) PPMC
https://mssun.me

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.2.0-rc.1

[Mingshen Sun]

I found that this email is merged with the previous voting thread
(with an incorrect KEYS link).

I'll fix it by sending another email with a different title to avoid
confusion. Sorry for the multiple emails. Thanks!

On Sun, Nov 28, 2021 at 4:50 PM Mingshen Sun  wrote:
>
> Hi all,
>
> I am pleased to be calling this vote for the second release of
> Apache Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 1).
>
> The Apache Teaclave (incubating) community has voted and approved the
> release, with four +1 votes from IPMC members (Yuan Zhuang, Rong Fan,
> Rundong Zhou, Tongxin Li).
>
> Vote/result threads:
> - https://lists.apache.org/thread/41mpj6r4xo6h49mh5kj0npx6l3o2n2ct
> - https://lists.apache.org/thread/66kbrq8rq8f54pq46g6b1wzlmx70jttt
>
> The release candidate to be voted over is available at:
>   - 
> https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.1/
>
> The release candidate is signed with a GPG key available at:
>   - https://downloads.apache.org/incubator/teaclave/KEYS
>
> The Git commit for this release is:
>   - 
> https://gitbox.apache.org/repos/asf?p=incubator-teaclave-trustzone-sdk.git;a=commit;h=3984789a59fdfe58757a7a60e490a414ca918478
>
> The release note is available in:
>   - 
> https://github.com/apache/incubator-teaclave-trustzone-sdk/releases/tag/v0.2.0-rc.1
>
> Build guide and get started instructions can be found at:
>   - 
> https://github.com/apache/incubator-teaclave-trustzone-sdk/blob/release-v0.2.0/docs/getting-started-with-optee-for-qemu-armv8.md
>
> The short version of building Teaclave from the source tarball:
>
> ```
> $ wget 
> https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.1/apache-teaclave-trustzone-sdk-0.2.0-rc.1-incubating.tar.gz
>
> $ # Instructions to verify the source tar: \
> https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
>
> $ tar zxvf apache-teaclave-trustzone-sdk-0.2.0-rc.1-incubating.tar.gz && cd \
>   apache-teaclave-trustzone-sdk-0.2.0-incubating
>
> $ # Build the SDK and TAs
> $ docker run -v`pwd`:/teaclave -w /teaclave -it
> teaclave/teaclave-trustzone-sdk-build:0.3.0 \
>bash -c "source environment && make"
>
> $ # Test all examples with QEMU
> $ docker run -v`pwd`:/teaclave -w /teaclave -it
> teaclave/teaclave-trustzone-sdk-build:0.3.0 \
>bash -c "cd ci && ./ci.sh"
> ```
>
> The vote will be open for at least 72 hours. Everyone is welcome to
> vote. Please vote by replying to this thread explicitly.
>
>   [ ] +1 approve
>   [ ] +0 no opinion
>   [ ] -1 disapprove with the reason
>
> Anyone can participate in testing and voting, not just committers,
> please feel free to try out the release candidate and provide your
> votes. Please also reply with things you have checked.
>
> A checklist for reference:
>   - 
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> Best,
>
> Mingshen Sun
> Apache Teaclave (incubating) PPMC
> https://mssun.me

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.2.0-rc.1

[Mingshen Sun]

Hi all,

I am pleased to be calling this vote for the second release of
Apache Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 1).

The Apache Teaclave (incubating) community has voted and approved the
release, with four +1 votes from IPMC members (Yuan Zhuang, Rong Fan,
Rundong Zhou, Tongxin Li).

Vote/result threads:
- https://lists.apache.org/thread/41mpj6r4xo6h49mh5kj0npx6l3o2n2ct
- https://lists.apache.org/thread/66kbrq8rq8f54pq46g6b1wzlmx70jttt

The release candidate to be voted over is available at:
  - 
https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.1/

The release candidate is signed with a GPG key available at:
  - https://downloads.apache.org/incubator/teaclave/KEYS

The Git commit for this release is:
  - 
https://gitbox.apache.org/repos/asf?p=incubator-teaclave-trustzone-sdk.git;a=commit;h=3984789a59fdfe58757a7a60e490a414ca918478

The release note is available in:
  - 
https://github.com/apache/incubator-teaclave-trustzone-sdk/releases/tag/v0.2.0-rc.1

Build guide and get started instructions can be found at:
  - 
https://github.com/apache/incubator-teaclave-trustzone-sdk/blob/release-v0.2.0/docs/getting-started-with-optee-for-qemu-armv8.md

The short version of building Teaclave from the source tarball:

```
$ wget 
https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.1/apache-teaclave-trustzone-sdk-0.2.0-rc.1-incubating.tar.gz

$ # Instructions to verify the source tar: \
https://teaclave.apache.org/download/#verify-the-integrity-of-the-files

$ tar zxvf apache-teaclave-trustzone-sdk-0.2.0-rc.1-incubating.tar.gz && cd \
  apache-teaclave-trustzone-sdk-0.2.0-incubating

$ # Build the SDK and TAs
$ docker run -v`pwd`:/teaclave -w /teaclave -it
teaclave/teaclave-trustzone-sdk-build:0.3.0 \
   bash -c "source environment && make"

$ # Test all examples with QEMU
$ docker run -v`pwd`:/teaclave -w /teaclave -it
teaclave/teaclave-trustzone-sdk-build:0.3.0 \
   bash -c "cd ci && ./ci.sh"
```

The vote will be open for at least 72 hours. Everyone is welcome to
vote. Please vote by replying to this thread explicitly.

  [ ] +1 approve
  [ ] +0 no opinion
  [ ] -1 disapprove with the reason

Anyone can participate in testing and voting, not just committers,
please feel free to try out the release candidate and provide your
votes. Please also reply with things you have checked.

A checklist for reference:
  - 
https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist

Best,

Mingshen Sun
Apache Teaclave (incubating) PPMC
https://mssun.me

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.2.0-rc.1

[Mingshen Sun]

Thanks for pointing this out. I'll fix it and send another vote.

Please ignore this voting thread.

On Sun, Nov 28, 2021 at 3:41 AM sebb  wrote:
>
> On Sun, 28 Nov 2021 at 06:08, Mingshen Sun  wrote:
> >
> > Hi all,
> >
> > I am pleased to be calling this vote for the second release of
> > Apache Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 1).
> >
> > The Apache Teaclave (incubating) community has voted and approved the
> > release, with four +1 votes from IPMC members (Yuan Zhuang, Rong Fan,
> > Rundong Zhou, Tongxin Li).
> >
> > Vote/result threads:
> > - https://lists.apache.org/thread/41mpj6r4xo6h49mh5kj0npx6l3o2n2ct
> > - https://lists.apache.org/thread/66kbrq8rq8f54pq46g6b1wzlmx70jttt
> >
> > The release candidate to be voted over is available at:
> >   - 
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.1/
> >
> > The release candidate is signed with a GPG key available at:
> >   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
>
> Please do NOT use dist.apache.org for referencing KEYS.
>
> See
> https://lists.apache.org/thread/g9040zdg0wk5sdl3ovxgnr86wgtr8m04
>
> > The Git commit for this release is:
> >   - 
> > https://gitbox.apache.org/repos/asf?p=incubator-teaclave-trustzone-sdk.git;a=commit;h=3984789a59fdfe58757a7a60e490a414ca918478
> >
> > The release note is available in:
> >   - 
> > https://github.com/apache/incubator-teaclave-trustzone-sdk/releases/tag/v0.2.0-rc.1
> >
> > Build guide and get started instructions can be found at:
> >   - 
> > https://github.com/apache/incubator-teaclave-trustzone-sdk/blob/release-v0.2.0/docs/getting-started-with-optee-for-qemu-armv8.md
> >
> > The short version of building Teaclave from the source tarball:
> >
> > ```
> > $ wget 
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.1/apache-teaclave-trustzone-sdk-0.2.0-rc.1-incubating.tar.gz
> >
> > $ # Instructions to verify the source tar: \
> > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> >
> > $ tar zxvf apache-teaclave-trustzone-sdk-0.2.0-rc.1-incubating.tar.gz && cd 
> > \
> >   apache-teaclave-trustzone-sdk-0.2.0-incubating
> >
> > $ # Build the SDK and TAs
> > $ docker run -v`pwd`:/teaclave -w /teaclave -it
> > teaclave/teaclave-trustzone-sdk-build:0.3.0 \
> >bash -c "source environment && make"
> >
> > $ # Test all examples with QEMU
> > $ docker run -v`pwd`:/teaclave -w /teaclave -it
> > teaclave/teaclave-trustzone-sdk-build:0.3.0 \
> >bash -c "cd ci && ./ci.sh"
> > ```
> >
> > The vote will be open for at least 72 hours. Everyone is welcome to
> > vote. Please vote by replying to this thread explicitly.
> >
> >   [ ] +1 approve
> >   [ ] +0 no opinion
> >   [ ] -1 disapprove with the reason
> >
> > Anyone can participate in testing and voting, not just committers,
> > please feel free to try out the release candidate and provide your
> > votes. Please also reply with things you have checked.
> >
> > A checklist for reference:
> >   - 
> > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
> > Best,
> >
> > Mingshen Sun
> > Apache Teaclave (incubating) PPMC
> > https://mssun.me
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.2.0-rc.1

[Mingshen Sun]

Hi all,

I am pleased to be calling this vote for the second release of
Apache Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 1).

The Apache Teaclave (incubating) community has voted and approved the
release, with four +1 votes from IPMC members (Yuan Zhuang, Rong Fan,
Rundong Zhou, Tongxin Li).

Vote/result threads:
- https://lists.apache.org/thread/41mpj6r4xo6h49mh5kj0npx6l3o2n2ct
- https://lists.apache.org/thread/66kbrq8rq8f54pq46g6b1wzlmx70jttt

The release candidate to be voted over is available at:
  - 
https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.1/

The release candidate is signed with a GPG key available at:
  - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS

The Git commit for this release is:
  - 
https://gitbox.apache.org/repos/asf?p=incubator-teaclave-trustzone-sdk.git;a=commit;h=3984789a59fdfe58757a7a60e490a414ca918478

The release note is available in:
  - 
https://github.com/apache/incubator-teaclave-trustzone-sdk/releases/tag/v0.2.0-rc.1

Build guide and get started instructions can be found at:
  - 
https://github.com/apache/incubator-teaclave-trustzone-sdk/blob/release-v0.2.0/docs/getting-started-with-optee-for-qemu-armv8.md

The short version of building Teaclave from the source tarball:

```
$ wget 
https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.1/apache-teaclave-trustzone-sdk-0.2.0-rc.1-incubating.tar.gz

$ # Instructions to verify the source tar: \
https://teaclave.apache.org/download/#verify-the-integrity-of-the-files

$ tar zxvf apache-teaclave-trustzone-sdk-0.2.0-rc.1-incubating.tar.gz && cd \
  apache-teaclave-trustzone-sdk-0.2.0-incubating

$ # Build the SDK and TAs
$ docker run -v`pwd`:/teaclave -w /teaclave -it
teaclave/teaclave-trustzone-sdk-build:0.3.0 \
   bash -c "source environment && make"

$ # Test all examples with QEMU
$ docker run -v`pwd`:/teaclave -w /teaclave -it
teaclave/teaclave-trustzone-sdk-build:0.3.0 \
   bash -c "cd ci && ./ci.sh"
```

The vote will be open for at least 72 hours. Everyone is welcome to
vote. Please vote by replying to this thread explicitly.

  [ ] +1 approve
  [ ] +0 no opinion
  [ ] -1 disapprove with the reason

Anyone can participate in testing and voting, not just committers,
please feel free to try out the release candidate and provide your
votes. Please also reply with things you have checked.

A checklist for reference:
  - 
https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist

Best,

Mingshen Sun
Apache Teaclave (incubating) PPMC
https://mssun.me

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [MENTORS] Download page issues

[Mingshen Sun]

Teaclave has fixed the issues in the download page [1]. Thanks.

[1] https://teaclave.apache.org/download/

Best,
Mingshen


On Tue, Nov 2, 2021 at 2:09 AM mikexue  wrote:
>
> EventMesh has changed download links to
> www.apache.org/dyn/closer.lua/*, the official address will take effect
> in 24 hours.
>
> Justin Mclean  于2021年11月2日周二 下午2:35写道：
> >
> > HI,
> >
> > As per [1]  mirrors.cgi and closer.cgi scripts have been deprecated and it 
> > states a project's download page "must have at least one link to the 
> > current release. This link must use the closer.lua utility."
> >
> > Kind Regards,
> > Justin
> >
> >
> > 1. https://infra.apache.org/release-download-pages.html#download-page
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave (incubating) v0.3.0-rc.1

[Mingshen Sun]

Thanks, Xun.

Yes, I think this is not a blocking issue (correct me if I'm wrong),
and I will work on this before the next release.


On Mon, Aug 23, 2021 at 7:20 PM Xun Liu  wrote:
>
> Hi mingshen,
>
> Please don't forget to add the `NOTICE` and `DISCLAIMER` in the [1] sub
> repo of incubator-teaclave. Thanks.
> [1] https://github.com/apache/incubator-teaclave-sgx-sdk
>
> Xun Liu
> Best regards
>
> On Tue, Aug 24, 2021 at 1:54 AM Mingshen Sun  wrote:
>
> > Thanks to everyone that participated. The vote to release Apache
> > Teaclave (incubating) version 0.3.0 Release Candidate 1 is now closed.
> >
> > The vote PASSED with 5 binding +1, 0 non binding +1 and 0 -1 votes:
> >
> > Binding votes:
> > - Gordon King
> > - Yulong Zhang
> > - Xun Liu
> > - Hongbo Chen
> > - Rundong Zhou
> >
> > I will release Apache Teaclave (incubating) v0.3.0 and post an
> > announcement. Thanks.
> >
> > Mingshen
> >
> > On Fri, Aug 20, 2021 at 3:41 PM Rundong Zhou 
> > wrote:
> > >
> > > +1
> > >
> > > On 2021/08/20 18:28:53, Hongbo Chen  wrote:
> > > > +1.
> > > > This release works well on my side and I can run examples sucessfully.
> > > >
> > > > Thanks,
> > > > Hongbo
> > > >
> > > > On 2021/08/20 05:15:16, Mingshen Sun  wrote:
> > > > > Hi all,
> > > > >
> > > > > I am pleased to be calling this vote for the third release of
> > > > > Apache Teaclave (incubating) 0.3.0 (release candidate 1).
> > > > >
> > > > > The Apache Teaclave (incubating) community has voted and approved the
> > > > > release, with five +1 votes from IPMC members (Pei Wang, Yulong
> > Zhang,
> > > > > Rundong Zhou, Tongxin Li, Hongbo Chen).
> > > > >
> > > > > Vote/result threads:
> > > > > -
> > https://lists.apache.org/thread.html/r12fda1ea84bff22a62c60a7e6e2988fd40b897c6e998d01b9e0b00ca%40%3Cdev.teaclave.apache.org%3E
> > > > > -
> > https://lists.apache.org/thread.html/r1feb15a35ff03933c794fe18d957c2a312ceeb6662deb4e22153f559%40%3Cdev.teaclave.apache.org%3E
> > > > >
> > > > > The release candidate to be voted over is available at:
> > > > >   -
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.3.0-rc.1/
> > > > >
> > > > > The release candidate is signed with a GPG key available at:
> > > > >   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> > > > >
> > > > > The Git commit for this release is:
> > > > >   -
> > https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=f2be66e025f9323512b2e8fec5d99e04908b552a
> > > > >
> > > > > The release note is available in:
> > > > >   -
> > https://github.com/apache/incubator-teaclave/releases/tag/v0.3.0-rc.1
> > > > >
> > > > > Build guide and get started instructions can be found at:
> > > > >   -
> > https://github.com/apache/incubator-teaclave/blob/v0.3.0-rc.1/docs/my-first-function.md
> > > > >
> > > > > The short version of building Teaclave from the source tarball:
> > > > >
> > > > > ```
> > > > > $ wget
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.3.0-rc.1/apache-teaclave-0.3.0-rc.1-incubating.tar.gz
> > > > > $ tar zxvf apache-teaclave-0.3.0-rc.1-incubating.tar.gz && cd \
> > > > >   apache-teaclave-0.3.0-incubating
> > > > > $ # Instructions to verify the source tar:
> > > > >
> > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> > > > >
> > > > > $ docker run --rm -v $(pwd):/teaclave -w /teaclave \
> > > > >   -it teaclave/teaclave-build-ubuntu-1804-sgx-2.14:latest \
> > > > >bash -c ". /root/.cargo/env && \
> > > > >  . /opt/sgxsdk/environment && \
> > > > >  mkdir -p build && cd build && \
> > > > >  cmake -DTEST_MODE=ON -DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF ..
> > && \
> > > > >  make"
> > > > > ```
> > > > >
> > > > > The vote will be open for at least 72 hours. Everyone is welcome to
> > > > > vote. Please vote by replying to this thread explicitly.
> > > > >
> > > >

[RESULT][VOTE] Release Apache Teaclave (incubating) v0.3.0-rc.1

[Mingshen Sun]

Hi all,

Thanks to everyone that participated. The vote to release Apache
Teaclave (incubating) version 0.3.0 Release Candidate 1 in general@incuabator
is now closed.

Vote thread: 
https://lists.apache.org/thread.html/r018fb18270819082d15b106a9261144c8b27144cef992b68db537597%40%3Cgeneral.incubator.apache.org%3E

The vote PASSED with 5 binding +1, 0 non binding +1 and 0 -1 votes:

Binding votes:
- Gordon King
- Yulong Zhang
- Xun Liu
- Hongbo Chen
- Rundong Zhou

I will be working on publishing the artifacts of Apache Teaclave
(incubating) v0.3.0 and post an announcement. Thanks.

Mingshen

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave (incubating) v0.3.0-rc.1

[Mingshen Sun]

Thanks to everyone that participated. The vote to release Apache
Teaclave (incubating) version 0.3.0 Release Candidate 1 is now closed.

The vote PASSED with 5 binding +1, 0 non binding +1 and 0 -1 votes:

Binding votes:
- Gordon King
- Yulong Zhang
- Xun Liu
- Hongbo Chen
- Rundong Zhou

I will release Apache Teaclave (incubating) v0.3.0 and post an
announcement. Thanks.

Mingshen

On Fri, Aug 20, 2021 at 3:41 PM Rundong Zhou  wrote:
>
> +1
>
> On 2021/08/20 18:28:53, Hongbo Chen  wrote:
> > +1.
> > This release works well on my side and I can run examples sucessfully.
> >
> > Thanks,
> > Hongbo
> >
> > On 2021/08/20 05:15:16, Mingshen Sun  wrote:
> > > Hi all,
> > >
> > > I am pleased to be calling this vote for the third release of
> > > Apache Teaclave (incubating) 0.3.0 (release candidate 1).
> > >
> > > The Apache Teaclave (incubating) community has voted and approved the
> > > release, with five +1 votes from IPMC members (Pei Wang, Yulong Zhang,
> > > Rundong Zhou, Tongxin Li, Hongbo Chen).
> > >
> > > Vote/result threads:
> > > - 
> > > https://lists.apache.org/thread.html/r12fda1ea84bff22a62c60a7e6e2988fd40b897c6e998d01b9e0b00ca%40%3Cdev.teaclave.apache.org%3E
> > > - 
> > > https://lists.apache.org/thread.html/r1feb15a35ff03933c794fe18d957c2a312ceeb6662deb4e22153f559%40%3Cdev.teaclave.apache.org%3E
> > >
> > > The release candidate to be voted over is available at:
> > >   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.3.0-rc.1/
> > >
> > > The release candidate is signed with a GPG key available at:
> > >   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> > >
> > > The Git commit for this release is:
> > >   - 
> > > https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=f2be66e025f9323512b2e8fec5d99e04908b552a
> > >
> > > The release note is available in:
> > >   - https://github.com/apache/incubator-teaclave/releases/tag/v0.3.0-rc.1
> > >
> > > Build guide and get started instructions can be found at:
> > >   - 
> > > https://github.com/apache/incubator-teaclave/blob/v0.3.0-rc.1/docs/my-first-function.md
> > >
> > > The short version of building Teaclave from the source tarball:
> > >
> > > ```
> > > $ wget 
> > > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.3.0-rc.1/apache-teaclave-0.3.0-rc.1-incubating.tar.gz
> > > $ tar zxvf apache-teaclave-0.3.0-rc.1-incubating.tar.gz && cd \
> > >   apache-teaclave-0.3.0-incubating
> > > $ # Instructions to verify the source tar:
> > > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> > >
> > > $ docker run --rm -v $(pwd):/teaclave -w /teaclave \
> > >   -it teaclave/teaclave-build-ubuntu-1804-sgx-2.14:latest \
> > >bash -c ". /root/.cargo/env && \
> > >  . /opt/sgxsdk/environment && \
> > >  mkdir -p build && cd build && \
> > >  cmake -DTEST_MODE=ON -DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \
> > >  make"
> > > ```
> > >
> > > The vote will be open for at least 72 hours. Everyone is welcome to
> > > vote. Please vote by replying to this thread explicitly.
> > >
> > >   [ ] +1 approve
> > >   [ ] +0 no opinion
> > >   [ ] -1 disapprove with the reason
> > >
> > > Best,
> > >
> > > Mingshen Sun
> > > Apache Teaclave (incubating) PPMC
> > > https://mssun.me
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Apache Teaclave (incubating) v0.3.0-rc.1

[Mingshen Sun]

Hi all,

I am pleased to be calling this vote for the third release of
Apache Teaclave (incubating) 0.3.0 (release candidate 1).

The Apache Teaclave (incubating) community has voted and approved the
release, with five +1 votes from IPMC members (Pei Wang, Yulong Zhang,
Rundong Zhou, Tongxin Li, Hongbo Chen).

Vote/result threads:
- 
https://lists.apache.org/thread.html/r12fda1ea84bff22a62c60a7e6e2988fd40b897c6e998d01b9e0b00ca%40%3Cdev.teaclave.apache.org%3E
- 
https://lists.apache.org/thread.html/r1feb15a35ff03933c794fe18d957c2a312ceeb6662deb4e22153f559%40%3Cdev.teaclave.apache.org%3E

The release candidate to be voted over is available at:
  - https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.3.0-rc.1/

The release candidate is signed with a GPG key available at:
  - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS

The Git commit for this release is:
  - 
https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=f2be66e025f9323512b2e8fec5d99e04908b552a

The release note is available in:
  - https://github.com/apache/incubator-teaclave/releases/tag/v0.3.0-rc.1

Build guide and get started instructions can be found at:
  - 
https://github.com/apache/incubator-teaclave/blob/v0.3.0-rc.1/docs/my-first-function.md

The short version of building Teaclave from the source tarball:

```
$ wget 
https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.3.0-rc.1/apache-teaclave-0.3.0-rc.1-incubating.tar.gz
$ tar zxvf apache-teaclave-0.3.0-rc.1-incubating.tar.gz && cd \
  apache-teaclave-0.3.0-incubating
$ # Instructions to verify the source tar:
https://teaclave.apache.org/download/#verify-the-integrity-of-the-files

$ docker run --rm -v $(pwd):/teaclave -w /teaclave \
  -it teaclave/teaclave-build-ubuntu-1804-sgx-2.14:latest \
   bash -c ". /root/.cargo/env && \
 . /opt/sgxsdk/environment && \
 mkdir -p build && cd build && \
 cmake -DTEST_MODE=ON -DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \
 make"
```

The vote will be open for at least 72 hours. Everyone is welcome to
vote. Please vote by replying to this thread explicitly.

  [ ] +1 approve
  [ ] +0 no opinion
  [ ] -1 disapprove with the reason

Best,

Mingshen Sun
Apache Teaclave (incubating) PPMC
https://mssun.me

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Video conferencing platforms for virtual meetups

[Mingshen Sun]

> Apache OpenMeeting?

Thanks. Does Apache OpenMeeting provide any public service? Or, is it
possible to only use Apache's infrastructure for the deployment.

On Wed, Aug 11, 2021 at 10:47 AM Geertjan Wielenga
 wrote:
>
> Apache OpenMeeting?
>
> Gj
>
> On Wed, 11 Aug 2021 at 19:46, Mingshen Sun  wrote:
>
> > > The foundation also has a donated license of Google workspace
> > > and can give you an account on it.
> >
> > Thanks, Kevin. Google Workspace may be helpful, but I'm worried that
> > Google Meet may not be accessible by some places.
> >
> > > For the several projects I am involved in, we use the Zoom sponsored
> > > by my employer. Since my employer has paid subscription, we don't have
> > the limit.
> >
> > I'm also using Zoom sponsored by my employer. I'm thinking it would be
> > great to have a dedicated account (or infra) for ASF projects to
> > collaborate across organizations.
> >
> >
> > Mingshen
> >
> > On Tue, Aug 10, 2021 at 8:27 PM Kevin A. McGrail 
> > wrote:
> > >
> > > The foundation also has a donated license of Google workspace and can
> > give
> > > you an account on it. With that you can use it for longer meetings. Let
> > me
> > > know if you'd like me to set up an account.
> > >
> > > On Tue, Aug 10, 2021, 23:21 Wei-Chiu Chuang  wrote:
> > >
> > > > A while back ago during one of the Apache board meetings, it was
> > discussed
> > > > that they wanted to open up the streaming platform used by ApacheCon
> > for
> > > > Apache projects to organize virtual events, because they pay for a
> > whole
> > > > year's subscription only to use for the few events (ApacheCon).
> > > >
> > > > Not sure what's the status now.
> > > >
> > > > For the several projects I am involved in, we use the Zoom sponsored
> > by my
> > > > employer. Since my employer has paid subscription, we don't have the
> > limit.
> > > >
> > > > On Wed, Aug 11, 2021 at 6:30 AM Mingshen Sun  wrote:
> > > >
> > > > > Dear community,
> > > > >
> > > > > I'm from the Apache Teacalve (incubating) project. We are organizing
> > > > > online virtual meetups every month. Currently, we are using Zoom for
> > > > > the meetups. Seems that Zoom's free plan only supports 40 minutes for
> > > > > group meetings. I'm wondering if there're any recommended video
> > > > > conferencing platforms or infrastructures for the Apache projects.
> > > > > Thanks.
> > > > >
> > > > > Mingshen
> > > > >
> > > > > -
> > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > > >
> > > > >
> > > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Video conferencing platforms for virtual meetups

[Mingshen Sun]

> The foundation also has a donated license of Google workspace
> and can give you an account on it.

Thanks, Kevin. Google Workspace may be helpful, but I'm worried that
Google Meet may not be accessible by some places.

> For the several projects I am involved in, we use the Zoom sponsored
> by my employer. Since my employer has paid subscription, we don't have the 
> limit.

I'm also using Zoom sponsored by my employer. I'm thinking it would be
great to have a dedicated account (or infra) for ASF projects to
collaborate across organizations.


Mingshen

On Tue, Aug 10, 2021 at 8:27 PM Kevin A. McGrail  wrote:
>
> The foundation also has a donated license of Google workspace and can give
> you an account on it. With that you can use it for longer meetings. Let me
> know if you'd like me to set up an account.
>
> On Tue, Aug 10, 2021, 23:21 Wei-Chiu Chuang  wrote:
>
> > A while back ago during one of the Apache board meetings, it was discussed
> > that they wanted to open up the streaming platform used by ApacheCon for
> > Apache projects to organize virtual events, because they pay for a whole
> > year's subscription only to use for the few events (ApacheCon).
> >
> > Not sure what's the status now.
> >
> > For the several projects I am involved in, we use the Zoom sponsored by my
> > employer. Since my employer has paid subscription, we don't have the limit.
> >
> > On Wed, Aug 11, 2021 at 6:30 AM Mingshen Sun  wrote:
> >
> > > Dear community,
> > >
> > > I'm from the Apache Teacalve (incubating) project. We are organizing
> > > online virtual meetups every month. Currently, we are using Zoom for
> > > the meetups. Seems that Zoom's free plan only supports 40 minutes for
> > > group meetings. I'm wondering if there're any recommended video
> > > conferencing platforms or infrastructures for the Apache projects.
> > > Thanks.
> > >
> > > Mingshen
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Video conferencing platforms for virtual meetups

[Mingshen Sun]

Dear community,

I'm from the Apache Teacalve (incubating) project. We are organizing
online virtual meetups every month. Currently, we are using Zoom for
the meetups. Seems that Zoom's free plan only supports 40 minutes for
group meetings. I'm wondering if there're any recommended video
conferencing platforms or infrastructures for the Apache projects.
Thanks.

Mingshen

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT] [VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.1.0-rc1

[Mingshen Sun]

Dear all,

The vote to release Apache Teaclave TrustZone SDK (incubating)
v0.1.0-rc1 is now closed.

The release has PASSED with 9 +1  votes (9 binding), no 0 vote, and 0 -1 vote.

+1 votes
- Yu Ding (binding)
- Yulong Zhang (binding)
- Pei Wang (binding)
- Tongxin Li (binding)
- Rundong Zhou (binding)
- Justin Mclean (binding)
- Zhaofeng Chen (binding)
- Gang(Gary) Wang (binding)
- Furkan Kamaci (binding)

0 votes
- No votes

-1 votes
- No votes

Vote thread: 
https://lists.apache.org/thread.html/rac113d0052984d77e4bb481f7876abef6c3db895c7e4888019d2aca4%40%3Cgeneral.incubator.apache.org%3E

We will follow up with an announcement email soon!

Action items to be fixed before the next release:
- Files without ASF headers should be fixed
- Cleanup unexpected binary files
- Review licenses of third-party sources

Best,
Mingshen Sun
Apache Teaclave (incubating) PPMC

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.1.0-rc1

[Mingshen Sun]

Dear community,

This is a call for a vote to release Apache Teaclave TrustZone SDK
(incubating) 0.1.0.

The Apache Teaclave (incubating) community has voted and approved the
release, with four +1 votes from IPMC members (Rundong Zhou, Matt
Sicker, Tongxin Li, Yu Ding).

Vote/result thread:
  - 
https://lists.apache.org/thread.html/r441addf283f6c8780326f372e39a9d723164f6d910184ea3686a5c4a%40%3Cdev.teaclave.apache.org%3E

The release candidate to be voted over is available at:
  - 
https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.1.0-rc.1

The release candidate is signed with a GPG key available at:
  - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS

The Git commit for this release is:
  - 
https://gitbox.apache.org/repos/asf?p=incubator-teaclave-trustzone-sdk.git;a=commit;h=8587ffca8d3dbed15d2a36ed7cd6a33b6efd8965

The release note is available in:
  - 
https://github.com/apache/incubator-teaclave-trustzone-sdk/releases/tag/v0.1.0-rc.1

Build guide and get started instructions can be found at:
  - 
https://github.com/apache/incubator-teaclave-trustzone-sdk/blob/v0.1.0-rc.1/README.md

The short version of building and testing Teaclave TrustZone SDK from
the source tarball:

```
$ wget 
https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.1.0-rc.1/apache-teaclave-trustzone-sdk-0.1.0-rc.1-incubating.tar.gz
$ tar zxvf apache-teaclave-trustzone-sdk-0.1.0-rc.1-incubating.tar.gz && cd
apache-teaclave-trustzone-sdk-0.1.0-incubating

$ # Instructions to verify the source tar:
https://teaclave.apache.org/download/#verify-the-integrity-of-the-files

$ # Building
$ docker run --rm -it -v$(pwd):/teaclave-trustzone-sdk -w \
/teaclave-trustzone-sdk teaclave/teaclave-trustzone-sdk-build:0.1.1 \
bash -c "source environment && make"

$ # Testing
$ docker run --rm -it -v$(pwd):/teaclave-trustzone-sdk -w \
/teaclave-trustzone-sdk teaclave/teaclave-trustzone-sdk-build:0.1.1 \
bash -c "source environment && cd ci && ./ci.sh"
```

The vote will be open for at least 72 hours.

  [ ] +1 approve
  [ ] +0 no opinion
  [ ] -1 disapprove with the reason

Best,

Mingshen Sun
http://mssun.me

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave (incubating) v0.2.0-rc.1

[Mingshen Sun]

Thanks to everyone that participated. The vote to release Apache
Teaclave (incubating) version 0.2.0 Release Candidate 1 is now closed.

The vote PASSED with 7 binding +1, 0 non binding +1 and 0 -1 votes:

Binding votes:
- Yu Ding
- Furkan Kamaci
- Rundong Zhou
- Pei Wang
- Tongxin Li
- Yiming Jing
- Matt Sicker

I will release Apache Teaclave (incubating) v0.2.0 and post an
announcement. Thanks.

Best,
Mingshen Sun

On Sun, Feb 28, 2021 at 11:45 PM Furkan KAMACI  wrote:
>
> Hi,
>
> I’ll try to compile it again. For the incorrect year in NOTICE, fixing it
> at next release is fine as Justin mentioned.
>
> Kind Regards,
> Furkan KAMACI
>
> On 1 Mar 2021 Mon at 10:42 Justin Mclean  wrote:
>
> > HI,
> >
> > > Also, for the incorrect year in NOTICE. Should I fix it in this
> > > release (and vote for another candidate) or fix it before the next
> > > release version? Thanks.
> >
> > Fix it in the next release is fine IMO.
> >
> > Thanks,
> > Justin
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave (incubating) v0.2.0-rc.1

[Mingshen Sun]

Thanks to everyone that participated. The vote to release Apache
Teaclave (incubating) version 0.2.0 Release Candidate 1 is now closed.

The vote PASSED with 7 binding +1, 0 non binding +1 and 0 -1 votes:

Binding votes:
- Yu Ding
- Furkan Kamaci
- Rundong Zhou
- Pei Wang
- Tongxin Li
- Yiming Jing
- Matt Sicker

I will release Apache Teaclave (incubating) v0.2.0 and post an
announcement. Thanks.

Best,
Mingshen Sun

On Sun, Feb 28, 2021 at 11:45 PM Furkan KAMACI  wrote:
>
> Hi,
>
> I’ll try to compile it again. For the incorrect year in NOTICE, fixing it
> at next release is fine as Justin mentioned.
>
> Kind Regards,
> Furkan KAMACI
>
> On 1 Mar 2021 Mon at 10:42 Justin Mclean  wrote:
>
> > HI,
> >
> > > Also, for the incorrect year in NOTICE. Should I fix it in this
> > > release (and vote for another candidate) or fix it before the next
> > > release version? Thanks.
> >
> > Fix it in the next release is fine IMO.
> >
> > Thanks,
> > Justin
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave (incubating) v0.2.0-rc.1

[Mingshen Sun]

Hi Furkan,

I tried to compile it in Docker for macOS with 8 GB memory and can
compile it successfully (but pretty slow).

Can you verify that the `apache-teaclave-0.2.0-rc.1-incubating/keys`
directory exists? If possible, it's recommended to compile with docker
on Linux.

Also, for the incorrect year in NOTICE. Should I fix it in this
release (and vote for another candidate) or fix it before the next
release version? Thanks.

Best,
Mingshen Sun



On Sun, Feb 28, 2021 at 3:19 PM Matt Sicker  wrote:
>
> Alright, finally finished building and running tests. All passed after
> upping the memory limits to 8 GB, thought that might be overkill.
>
> +1
>
> On Sun, 28 Feb 2021 at 16:43, Yiming Jing  wrote:
> >
> > +1 approve
> >
> > On 2021/02/26 18:26:28, Mingshen Sun  wrote:
> > > Dear community,
> > >
> > > This is a call for a vote to release Apache Teaclave (incubating)
> > > version 0.2.0. This is the second Apache release since Teaclave
> > > entered the incubator.
> > >
> > > The Apache Teaclave (incubating) community has voted and approved the
> > > release, with four +1 votes from IPMC members (Pei Wang, Yulong Zhang,
> > > Rundong Zhou, Tongxin Li).
> > >
> > > Vote/result thread:
> > >   - 
> > > https://lists.apache.org/thread.html/rd0ca1591578bcc60d73ce8722908d5001bd81dffe7a33e205bd28184%40%3Cdev.teaclave.apache.org%3E
> > >
> > > The release candidate to be voted over is available at:
> > >   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.2.0-rc.1/
> > >
> > > The release candidate is signed with a GPG key available at:
> > >   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> > >
> > > The Git commit for this release is:
> > >   - 
> > > https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=0d1a001bb4741e3c652d121d2dfafa5d9361f84c
> > >
> > > The release note is available in:
> > >   - https://github.com/apache/incubator-teaclave/releases/tag/v0.2.0-rc.1
> > >
> > > Build guide and get started instructions can be found at:
> > >   - 
> > > https://github.com/apache/incubator-teaclave/blob/v0.2.0-rc.1/docs/my-first-function.md
> > >
> > > The short version of building Teaclave from the source tarball:
> > >
> > > ```
> > > $ wget 
> > > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.2.0-rc.1/apache-teaclave-0.2.0-rc.1-incubating.tar.gz
> > > $ tar zxvf apache-teaclave-0.2.0-rc.1-incubating.tar.gz && cd
> > > apache-teaclave-0.2.0-rc.1-incubating
> > > $ # Instructions to verify the source tar:
> > > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> > >
> > > $ docker run --rm -v $(pwd):/teaclave -w /teaclave \
> > >   -it teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest \
> > >bash -c ". /root/.cargo/env && \
> > >  . /opt/sgxsdk/environment && \
> > >  mkdir -p build && cd build && \
> > >  cmake -DTEST_MODE=ON DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \
> > >  make"
> > > ```
> > >
> > > The vote will be open for at least 72 hours.
> > >
> > >   [ ] +1 approve
> > >   [ ] +0 no opinion
> > >   [ ] -1 disapprove with the reason
> > >
> > >
> > > Best,
> > >
> > > Mingshen Sun
> > > http://mssun.me
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Teaclave (incubating) v0.2.0-rc.1

[Mingshen Sun]

Hi Matt,

For your case, I believe it is because of the memory limit
(out-of-memory) of Docker for macOS. The Rust compiler needs more
memory than others.

Best,
Mingshen


On Sun, Feb 28, 2021 at 11:57 AM Matt Sicker  wrote:
>
> I tried building on macOS as well, and it got fairly far and ended up
> failing at this point:
>
> Scanning dependencies of target sgxlib-teaclave_authentication_service
> [ 37%] Building sgxlib-teaclave_authentication_service, enclave info
> to 
> /teaclave/build/intermediate/teaclave_authentication_service_enclave_info.toml
>Compiling crc v2.0.0 
> (https://github.com/mesalock-linux/crc-rs-sgx#86696be0)
>Compiling teaclave_proto v0.2.0
> (/teaclave/build/cmake_tomls/sgx_trusted_lib/services/proto)
>Compiling integer-encoding v1.0.7
>Compiling snap v0.2.5
>Compiling jsonwebtoken v6.0.1
> error: could not compile `crc`.
>
> Caused by:
>   process didn't exit successfully:
> `/teaclave/cmake/scripts/rustc_wrapper.sh --crate-name crc
> --edition=2018 
> /teaclave/build/cmake_tomls/sgx_trusted_lib/third_party/crates-sgx/vendor/crc/src/lib.rs
> --error-format=json --json=diagnostic-rendered-ansi,artifacts
> --crate-type lib --emit=dep-info,metadata,link -C debuginfo=2 -C
> metadata=39ca99cb54d77a3c -C extra-filename=-39ca99cb54d77a3c
> --out-dir /teaclave/build/target/trusted/debug/deps -L
> dependency=/teaclave/build/target/trusted/debug/deps --cap-lints allow
> --cfg test_mode` (signal: 9, SIGKILL: kill)
> /usr/bin/ld: cannot find -lteaclave_authentication_service_enclave
> collect2: error: ld returned 1 exit status
> CMakeFiles/sgxlib-teaclave_authentication_service.dir/build.make:57:
> recipe for target 'CMakeFiles/sgxlib-teaclave_authentication_service'
> failed
> make[2]: *** [CMakeFiles/sgxlib-teaclave_authentication_service] Error 1
> CMakeFiles/Makefile2:301: recipe for target
> 'CMakeFiles/sgxlib-teaclave_authentication_service.dir/all' failed
> make[1]: *** [CMakeFiles/sgxlib-teaclave_authentication_service.dir/all] 
> Error 2
> Makefile:83: recipe for target 'all' failed
> make: *** [all] Error 2
>
> Full build log output here:
> https://gist.github.com/jvz/b214f28b788f6459b8e511149781e52a
>
> Signatures, notice, license, disclaimer all good.
>
> On Sun, 28 Feb 2021 at 13:37, Mingshen Sun  wrote:
> >
> > Thanks Furkan,
> >
> > I just tried to download and compile it in a clean Linux environment,
> > and can successfully compile the code.
> >
> > Are you working on macOS? Because of the case-insensitive file system
> > of macOS, Git cannot distinguish the KEYS file and keys directory.
> > That may cause the keys directory is not checkout.
> >
> > I'll fix this in the next release.
> >
> > Best,
> > Mingshen
> >
> > On Sat, Feb 27, 2021 at 12:30 AM Furkan KAMACI  
> > wrote:
> > >
> > > Hi,
> > >
> > > +1 from me (I have notes below).
> > >
> > > I checked:
> > >
> > > - Incubating in name
> > > - DISCLAIMER-WIP exists
> > > - LICENSE is fine
> > > - NOTICE has *incorrect* *year* which should be fixed
> > > - No unexpected binary files
> > > - Checked PGP signatures
> > > - Checked checksums
> > >
> > > I got that error while compiling the project:
> > >
> > > Digest:
> > > sha256:cb80cb3da4ddb15713ecd7ea8b6f4eab144c402644ece8116e762a19886d7ada
> > > Status: Downloaded newer image for
> > > teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest
> > > -- The C compiler identification is GNU 7.5.0
> > > -- Check for working C compiler: /usr/bin/cc
> > > -- Check for working C compiler: /usr/bin/cc -- works
> > > -- Detecting C compiler ABI info
> > > -- Detecting C compiler ABI info - done
> > > -- Detecting C compile features
> > > -- Detecting C compile features - done
> > > -- Found Git: /usr/bin/git (found version "2.27.0")
> > > -- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.so (found version
> > > "1.1.1")
> > > SGX_SDK=/opt/sgxsdk
> > > SGX_MODE=HW
> > > RUSTUP_TOOLCHAIN=nightly-2020-04-07
> > > DCAP=OFF
> > > BUILD_TYPE=debug
> > > TEACLAVE_SYMLINKS=/tmp/teaclave_symlinks.Dvayr2ejnVKi
> > > -- == /teaclave/build/environment GENERATED ==
> > > -- Configuring done
> > > -- Generating done
> > > -- Build files have been written to: /teaclave/build
> > > Scanning dependencies of target prep
> > > cp: cannot stat '/teaclave/keys/dcap_server_cert.pem': Not a directory
> > > CMakeFiles/prep.dir/b

Re: [VOTE] Release Apache Teaclave (incubating) v0.2.0-rc.1

[Mingshen Sun]

Thanks Furkan,

I just tried to download and compile it in a clean Linux environment,
and can successfully compile the code.

Are you working on macOS? Because of the case-insensitive file system
of macOS, Git cannot distinguish the KEYS file and keys directory.
That may cause the keys directory is not checkout.

I'll fix this in the next release.

Best,
Mingshen

On Sat, Feb 27, 2021 at 12:30 AM Furkan KAMACI  wrote:
>
> Hi,
>
> +1 from me (I have notes below).
>
> I checked:
>
> - Incubating in name
> - DISCLAIMER-WIP exists
> - LICENSE is fine
> - NOTICE has *incorrect* *year* which should be fixed
> - No unexpected binary files
> - Checked PGP signatures
> - Checked checksums
>
> I got that error while compiling the project:
>
> Digest:
> sha256:cb80cb3da4ddb15713ecd7ea8b6f4eab144c402644ece8116e762a19886d7ada
> Status: Downloaded newer image for
> teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest
> -- The C compiler identification is GNU 7.5.0
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Found Git: /usr/bin/git (found version "2.27.0")
> -- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.so (found version
> "1.1.1")
> SGX_SDK=/opt/sgxsdk
> SGX_MODE=HW
> RUSTUP_TOOLCHAIN=nightly-2020-04-07
> DCAP=OFF
> BUILD_TYPE=debug
> TEACLAVE_SYMLINKS=/tmp/teaclave_symlinks.Dvayr2ejnVKi
> -- == /teaclave/build/environment GENERATED ==
> -- Configuring done
> -- Generating done
> -- Build files have been written to: /teaclave/build
> Scanning dependencies of target prep
> cp: cannot stat '/teaclave/keys/dcap_server_cert.pem': Not a directory
> CMakeFiles/prep.dir/build.make:57: recipe for target 'CMakeFiles/prep'
> failed
> make[2]: *** [CMakeFiles/prep] Error 1
> CMakeFiles/Makefile2:819: recipe for target 'CMakeFiles/prep.dir/all' failed
> make[1]: *** [CMakeFiles/prep.dir/all] Error 2
> Makefile:83: recipe for target 'all' failed
> make: *** [all] Error 2
>
> Kind Regards,
> Furkan KAMACI
>
> On Fri, Feb 26, 2021 at 10:42 PM Yu Ding  wrote:
>
> > +1 approve
> >
> > On 2021/02/26 18:26:28, Mingshen Sun  wrote:
> > > Dear community,
> > >
> > > This is a call for a vote to release Apache Teaclave (incubating)
> > > version 0.2.0. This is the second Apache release since Teaclave
> > > entered the incubator.
> > >
> > > The Apache Teaclave (incubating) community has voted and approved the
> > > release, with four +1 votes from IPMC members (Pei Wang, Yulong Zhang,
> > > Rundong Zhou, Tongxin Li).
> > >
> > > Vote/result thread:
> > >   -
> > https://lists.apache.org/thread.html/rd0ca1591578bcc60d73ce8722908d5001bd81dffe7a33e205bd28184%40%3Cdev.teaclave.apache.org%3E
> > >
> > > The release candidate to be voted over is available at:
> > >   -
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.2.0-rc.1/
> > >
> > > The release candidate is signed with a GPG key available at:
> > >   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> > >
> > > The Git commit for this release is:
> > >   -
> > https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=0d1a001bb4741e3c652d121d2dfafa5d9361f84c
> > >
> > > The release note is available in:
> > >   -
> > https://github.com/apache/incubator-teaclave/releases/tag/v0.2.0-rc.1
> > >
> > > Build guide and get started instructions can be found at:
> > >   -
> > https://github.com/apache/incubator-teaclave/blob/v0.2.0-rc.1/docs/my-first-function.md
> > >
> > > The short version of building Teaclave from the source tarball:
> > >
> > > ```
> > > $ wget
> > https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.2.0-rc.1/apache-teaclave-0.2.0-rc.1-incubating.tar.gz
> > > $ tar zxvf apache-teaclave-0.2.0-rc.1-incubating.tar.gz && cd
> > > apache-teaclave-0.2.0-rc.1-incubating
> > > $ # Instructions to verify the source tar:
> > > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> > >
> > > $ docker run --rm -v $(pwd):/teaclave -w /teaclave \
> > >   -it teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest \
> > >bash -c ". /root/.cargo/env && \
> > >  . /opt/sgxsdk/environment && \
> > >  mkdir -p build && cd build && \
> &

[VOTE] Release Apache Teaclave (incubating) v0.2.0-rc.1

[Mingshen Sun]

Dear community,

This is a call for a vote to release Apache Teaclave (incubating)
version 0.2.0. This is the second Apache release since Teaclave
entered the incubator.

The Apache Teaclave (incubating) community has voted and approved the
release, with four +1 votes from IPMC members (Pei Wang, Yulong Zhang,
Rundong Zhou, Tongxin Li).

Vote/result thread:
  - 
https://lists.apache.org/thread.html/rd0ca1591578bcc60d73ce8722908d5001bd81dffe7a33e205bd28184%40%3Cdev.teaclave.apache.org%3E

The release candidate to be voted over is available at:
  - https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.2.0-rc.1/

The release candidate is signed with a GPG key available at:
  - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS

The Git commit for this release is:
  - 
https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=0d1a001bb4741e3c652d121d2dfafa5d9361f84c

The release note is available in:
  - https://github.com/apache/incubator-teaclave/releases/tag/v0.2.0-rc.1

Build guide and get started instructions can be found at:
  - 
https://github.com/apache/incubator-teaclave/blob/v0.2.0-rc.1/docs/my-first-function.md

The short version of building Teaclave from the source tarball:

```
$ wget 
https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.2.0-rc.1/apache-teaclave-0.2.0-rc.1-incubating.tar.gz
$ tar zxvf apache-teaclave-0.2.0-rc.1-incubating.tar.gz && cd
apache-teaclave-0.2.0-rc.1-incubating
$ # Instructions to verify the source tar:
https://teaclave.apache.org/download/#verify-the-integrity-of-the-files

$ docker run --rm -v $(pwd):/teaclave -w /teaclave \
  -it teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest \
   bash -c ". /root/.cargo/env && \
 . /opt/sgxsdk/environment && \
 mkdir -p build && cd build && \
 cmake -DTEST_MODE=ON DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \
 make"
```

The vote will be open for at least 72 hours.

  [ ] +1 approve
  [ ] +0 no opinion
  [ ] -1 disapprove with the reason


Best,

Mingshen Sun
http://mssun.me

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Re: [VOTE] Graduate Apache DolphinScheduler (incubating) as a TLP

[Mingshen Sun]

Hi,

+1 (non-binding). Good luck!

Best,
Mingshen Sun

On Sun, Feb 14, 2021 at 8:16 AM Furkan KAMACI  wrote:
>
> Hi,
>
> +1 (binding).
>
> Glad to be a mentor of Apache DolphinScheduler. Good luck!
>
> Kind Regards,
> Furkan KAMACI
>
> On Sun, Feb 14, 2021 at 5:15 PM Goson zhang  wrote:
>
> > +1 non-binding. Congrats!
> >
> > Xiangdong Huang  于2021年2月14日周日 下午9:20写道：
> >
> > > +1 non-binding. Congrats!
> > >
> > > ---
> > > Xiangdong Huang
> > > School of Software, Tsinghua University
> > >
> > >  黄向东
> > > 清华大学 软件学院
> > >
> > >
> > > Liu Ted  于2021年2月14日周日 下午7:59写道：
> > >
> > > > +1 (binding)
> > > > It's good to see a diversified and vibrant incubating project going
> > > > graduation.
> > > >
> > > > Ted Liu
> > > >
> > > >
> > > >
> > > >在 2021 年 2月 月 14 日週日，時間：19:50 ， Ming Wen  寫道：
> > >  +1
> > > > binding
> > > >
> > > > Sheng Wu 于2021年2月14日 周日下午7:21写道：
> > > >
> > > > > +1 binding
> > > > >
> > > > >
> > > > > Sheng Wu 吴晟
> > > > > Twitter, wusheng1108
> > > > >
> > > > >
> > > > > Liang Chen  于2021年2月14日周日 下午7:16写道：
> > > > >
> > > > > > +1(binding)
> > > > > >
> > > > > > Regards
> > > > > > Liang
> > > > > >
> > > > > > 在 2021年2月14日星期日，Kevin Ratnasekera  写道：
> > > > > >
> > > > > > > +1 ( binding )
> > > > > > >
> > > > > > > On Sun, Feb 14, 2021 at 4:19 PM lidong dai <
> > dailidon...@gmail.com>
> > > > > > wrote:
> > > > > > >
> > > > > > > > Hello all,
> > > > > > > >
> > > > > > > > We've got positive feedback on the DISCUSS thread [1], I'd like
> > > to
> > > > > > start
> > > > > > > an
> > > > > > > > official VOTE thread now.
> > > > > > > >
> > > > > > > > Please vote on the resolution pasted below to graduate Apache
> > > > > > > > DolphinScheduler from the incubator to the Top Level Project.
> > > > > > > >
> > > > > > > > [ ] +1 Graduate Apache DolphinScheduler from the Incubator.
> > > > > > > > [ ] +0 Don't care.
> > > > > > > > [ ] -1 Don't graduate Apache DolphinScheduler from the
> > Incubator
> > > > > > because
> > > > > > > > ...
> > > > > > > >
> > > > > > > > This vote will open for at least 72 hours.
> > > > > > > >
> > > > > > > > Many thanks to our mentors and everyone else for their support.
> > > > > > > >
> > > > > > > > [1]
> > > > > > > >
> > > > > > > >
> > > > https://lists.apache.org/thread.html/r1d5f4e122c914b39a49a9ae5c3960
> > > > > > > 5e17c0b82b20de3966e989a9f21%40%3Cgeneral.incubator.apache.org%3E
> > > > > > > >
> > > > > > > >
> > > > > > > > 
> > > > > > > -
> > > > > > > >
> > > > > > > > Establish the Apache DolphinScheduler Project
> > > > > > > >
> > > > > > > > WHEREAS, the Board of Directors deems it to be in the best
> > > > interests
> > > > > of
> > > > > > > > the Foundation and consistent with the Foundation's purpose to
> > > > > > establish
> > > > > > > > a Project Management Committee charged with the creation and
> > > > > > maintenance
> > > > > > > > of open-source software, for distribution at no charge to the
> > > > public,
> > > > > > > > related to a distributed and extensible workflow scheduler
> > > platform
> > > > > > with
> > > > > > > > powerful DAG visual interfaces.
> > > > > > > >
> > > > > > > >

Re: [VOTE] Graduate Apache DolphinScheduler (incubating) as a TLP

[Mingshen Sun]

+1 (non-binding).

Good luck.

On Sat, Feb 13, 2021 at 7:46 PM Xiangdong Huang  wrote:
>
> +1 (non-binding). Congrats!
>
>
> On 2021/02/12 14:18:45, Gang Li  wrote:
> > Hello all,
> >
> > We've got positive feedback on the DISCUSS thread [1], I'd like to start an
> > official VOTE thread now.
> >
> > Please vote on the resolution pasted below to graduate Apache
> > DolphinScheduler from the incubator to the Top Level Project.
> >
> > [ ] +1 Graduate Apache DolphinScheduler from the Incubator.
> > [ ] +0 Don't care.
> > [ ] -1 Don't graduate Apache DolphinScheduler from the Incubator because ...
> >
> > This vote will open for at least 72 hours.
> >
> > Many thanks to our mentors and everyone else for their support.
> >
> > [1] 
> > https://lists.apache.org/thread.html/r1d5f4e122c914b39a49a9ae5c39605e17c0b82b20de3966e989a9f21%40%3Cgeneral.incubator.apache.org%3E
> >
> >
> > -
> >
> > Establish the Apache DolphinScheduler Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to establish
> > a Project Management Committee charged with the creation and maintenance
> > of open-source software, for distribution at no charge to the public,
> > related to a distributed and extensible workflow scheduler platform with
> > powerful DAG visual interfaces.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache DolphinScheduler Project", be and
> > hereby is established pursuant to Bylaws of the Foundation; and be it
> > further
> >
> > RESOLVED, that the Apache DolphinScheduler Project be and hereby is
> > responsible for the creation and maintenance of software related to a
> > distributed and extensible workflow scheduler platform with powerful DAG
> > visual interfaces.; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache DolphinScheduler"
> > be and hereby is created, the person holding such office to serve at the
> > direction of the Board of Directors as the chair of the Apache
> > DolphinScheduler Project, and to have primary responsibility for
> > management of the projects within the scope of responsibility of the
> > Apache DolphinScheduler Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> > appointed to serve as the initial members of the Apache DolphinScheduler
> > Project:
> >
> > * Furkan Kamaci 
> > * Gang Li   
> > * Guo Jiwei 
> > * Guo William   
> > * Jun Gao   
> > * Kevin Ratnasekera 
> > * Leon Bao  
> > * Liang Chen
> > * Lidong Dai
> > * Qiao Zhanwei  
> > * Shao Feng Shi 
> > * Sheng Wu  
> > * Wu Baoqi  
> > * Xiaochun Liu  
> > * ZijJian Gong  
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lidong Dai be appointed to
> > the office of Vice President, Apache DolphinScheduler, to serve in
> > accordance with and subject to the direction of the Board of Directors
> > and the Bylaws of the Foundation until death, resignation, retirement,
> > removal or disqualification, or until a successor is appointed; and be
> > it further
> >
> > RESOLVED, that the Apache DolphinScheduler Project be and hereby is
> > tasked with the migration and rationalization of the Apache Incubator
> > DolphinScheduler podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > DolphinScheduler podling encumbered upon the Apache Incubator PMC are
> > hereafter discharged.
> >
> > 
> >
> >
> > Best Regards
> >
> > --
> > DolphinScheduler(Incubator) PPMC
> > Gang Li 李岗
> >
> > lgcar...@apache.org
> >
> >
> >
> >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache ECharts as TLP (round 2)

[Mingshen Sun]

+1 (non-binding)

Good luck!

On Mon, Nov 23, 2020 at 8:23 AM Dave Fisher  wrote:
>
> +1 (binding)
>
> Sent from my iPhone
>
> > On Nov 23, 2020, at 12:38 AM, Ovilia  wrote:
> >
> > Hi everyone,
> >
> > After discussion with the community [1], and a positive vote result [2] and
> > the
> > discussion under general mailing list [6], we believe
> > ECharts is ready for graduation to a TLP, and we'd like to call on the vote
> > to
> > graduate Apache ECharts as TPL.
> >
> > This is a formal voting thread about Apache ECharts's graduation, please
> > Vote:
> > [ ] +1 - Recommend graduation of Apache ECharts as a TLP
> > [ ]  0 - I don't feel strongly about it, but don't object
> > [ ] -1 - Do not recommend graduation of Apache ECharts because...
> >
> > The VOTE will open for at least 72 hours.
> > 
> > https://www.timeanddate.com/countdown/vote?iso=20201126T1635=237=Graduate+Apache+ECharts+as+TLP=serif=1
> >
> > -
> >
> > X. Establish the Apache ECharts Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best
> > interests of the Foundation and consistent with the
> > Foundation's purpose to establish a Project Management
> > Committee charged with the creation and maintenance of
> > open-source software, for distribution at no charge to
> > the public, related to a charting and data visualization
> > library written in JavaScript.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > Committee (PMC), to be known as the "Apache ECharts Project",
> > be and hereby is established pursuant to Bylaws of the
> > Foundation; and be it further
> >
> > RESOLVED, that the Apache ECharts Project be and hereby is
> > responsible for the creation and maintenance of software
> > related to a charting and data visualization
> > library written in JavaScript; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache ECharts" be
> > and hereby is created, the person holding such office to
> > serve at the direction of the Board of Directors as the chair
> > of the Apache ECharts Project, and to have primary responsibility
> > for management of the projects within the scope of
> > responsibility of the Apache ECharts Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and
> > hereby are appointed to serve as the initial members of the
> > Apache ECharts Project:
> >
> >* Houjin Huang  
> >* Deqing Li 
> >* Dong Rui  
> >* Kener Linfeng 
> >* Kevin A. McGrail  
> >* Wenli Zhang   
> >* Shen Yi   
> >* Shuang Su 
> >* Siwen Su  
> >* Junting Wang  
> >* Zhongxiang Wang   
> >* Dave Fisher   
> >* Sheng Wu  
> >* Zak Wu
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Wenli Zhang
> > be appointed to the office of Vice President, Apache ECharts, to
> > serve in accordance with and subject to the direction of the
> > Board of Directors and the Bylaws of the Foundation until
> > death, resignation, retirement, removal or disqualification,
> > or until a successor is appointed; and be it further
> >
> > RESOLVED, that the initial Apache ECharts PMC be and hereby is
> > tasked with the creation of a set of bylaws intended to
> > encourage open development and increased participation in the
> > Apache ECharts Project; and be it further
> >
> > RESOLVED, that the Apache ECharts Project be and hereby
> > is tasked with the migration and rationalization of the Apache
> > Incubator ECharts podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache
> > Incubator ECharts podling encumbered upon the Apache Incubator
> > Project are hereafter discharged.
> >
> > --
> >
> > A few points to assist in the discussion:
> >
> > - Released 9 official Apache releases by 3 release managers [3]
> > - Voted in 9 committers including 3 PPMC members
> > - Achieved 43556 stars (and counting) on GitHub
> > - Apache suitable name search has been approved [4]
> > - Completed the Podling Maturity Assessment, all items are passed [5]
> > - Our PPMC is diverse and consists of members from 9 organizations
> > - There have been 143 contributors to the codebase, 82 of whom contributed
> > during incubation
> > - Closed 11033+ issues
> > - Merged 603+ pull requests
> >
> > We've resolved all branding issues which include Logo, GitHub repo,
> > documentation, website, and others.
> >
> > Thank you!
> >
> > *Ovilia*
> >
> > [1]
> > https://lists.apache.org/thread.html/rf05e9dfa1aec1ac072c71c9cba882a59c9c57f4f89723da68e96de01%40%3Cdev.echarts.apache.org%3E
> > [2]
> > https://lists.apache.org/thread.html/r1179386814f4f99ccb3809527bc9436fe702e0e7573fb5de2c99151f%40%3Cdev.echarts.apache.org%3E
> > [3] 

[ANNOUNCE] Apache Teaclave (incubating) 0.1.0 Release

[Mingshen Sun]

Hi all,

The Apache Teaclave (incubating) community is happy to announce Apache
Teaclave (incubating) version 0.1.0!

This is the first Apache Incubator release of Teaclave. Apache Teaclave
(incubating) is an open source universal secure computing platform, making
computation on privacy-sensitive data safe and simple.

Apache Teaclave (incubating) has following highlights:

  - Security: Teaclave adopts multiple security technologies to enable
secure computing, in  particular, Teaclave uses Intel SGX to serve the most
security-sensitive tasks  with *hardware-based isolation*, *memory
encryption* and *attestation*.  Also, Teaclave is written in Rust to
prevent *memory-safety* issues.
  - Functionality: Teaclave is provided as a *function-as-a-service
platform*. With many built-in  functions, it supports tasks like machine
learning, private set intersection,  crypto computation, etc. In addition,
developers can also deploy and execute  Python scripts in Teaclave. More
importantly, unlike traditional FaaS,  Teaclave supports both general
secure computing tasks and *flexible single- and multi-party secure
computation*.
- Usability: Teaclave builds its components in containers, therefore,
it supports deployment both locally and within cloud infrastructures.
Teaclave also provides convenient endpoint APIs, client SDKs and command
line tools.
- Modularity: Components in Teaclave are designed in modular, and some like
remote attestation can be easily embedded in other projects. In addition,
Teaclave SGX SDK can also be used separately to write standalone SGX
enclaves for other purposes.

Release notes can be found here:
https://github.com/apache/incubator-teaclave/releases/tag/v0.1.0

A link to the download can be found here:
https://dist.apache.org/repos/dist/release/incubator/teaclave/0.1.0/

The release tag: https://github.com/apache/incubator-teaclave/tree/v0.1.0

Teaclave resources:
  - Teaclave dev mailing list (
https://lists.apache.org/list.html?d...@teaclave.apache.org)
  - Teaclave website (https://teaclave.apache.org/)
  - Github issues (https://github.com/apache/incubator-teaclave/issues)
  - Twitter (https://twitter.com/ApacheTeaclave)

Best regards,
Apache Teaclave (incubating) Team

--
Mingshen Sun

Re: [VOTE] Release Apache Teaclave (incubating) v0.1.0-rc2

[Mingshen Sun]

Thanks to everyone that participated. The vote to release Apache Teaclave
(incubating) version 0.1.0 is now closed.

The vote PASSED with 4 binding +1, 0 non binding +1 and 0 -1 votes:

Binding votes:
- Yu Ding
- Yulong Zhang
- Zhaofeng Chen
- Tongxin Li

We will work to complete the release process.

On Tue, Oct 6, 2020 at 10:57 PM Tongxin Li  wrote:

> +1 approve
>
> On 2020/10/06 21:57:47, Mingshen Sun  wrote:
> > Dear community,
> >
> > This is a call for a vote to release Apache Teaclave (incubating) version
> > 0.1.0. This is the first Apache release since Teaclave entered the
> > incubator.
> >
> > The Apache Teaclave (incubating) community has voted and approved the
> > release, with four +1 votes from IPMC members (Tongxin Li, Yu Ding,
> Furkan
> > Kamaci, and Pei Wang).
> >
> > Vote/result thread:
> >   -
> >
> https://lists.apache.org/thread.html/r78add66efd8eb43be2f7e4548ea516528112bdd1d00a4626f095ca94%40%3Cdev.teaclave.apache.org%3E
> >
> > The release candidate to be voted over is available at:
> >   -
> https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.1.0-rc.2/
> >
> > The release candidate is signed with a GPG key available at:
> >   - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> >
> > The Git commit for this release is:
> >   -
> >
> https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=05769c80fd15612003d629603cadd2ecddbfca46
> >
> > The Release Note is available in:
> >   -
> https://github.com/apache/incubator-teaclave/releases/tag/v0.1.0-rc.2
> >
> > Build guide and get started instructions can be found at:
> >   -
> >
> https://github.com/apache/incubator-teaclave/blob/v0.1.0-rc.2/docs/my-first-function.md
> >
> > The short version of building Teaclave from the source tarball:
> >
> > ```
> > $ wget
> >
> https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.1.0-rc.2/apache-teaclave-0.1.0-rc.2-incubating.tar.gz
> > $ tar zxvf apache-teaclave-0.1.0-rc.2-incubating.tar.gz && cd
> > apache-teaclave-0.1.0-rc.2-incubating
> > $ docker run --rm -v $(pwd):/teaclave -w /teaclave \
> >   -it teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest \
> >bash -c ". /root/.cargo/env && \
> >  . /opt/sgxsdk/environment && \
> >  mkdir -p build && cd build && \
> >  cmake -DTEST_MODE=ON -DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \
> >  make"
> > ```
> >
> > The vote will be open for at least 72 hours.
> >
> >   [ ] +1 approve
> >   [ ] +0 no opinion
> >   [ ] -1 disapprove with the reason
> >
> > Thanks,
> > Mingshen Sun
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[VOTE] Release Apache Teaclave (incubating) v0.1.0-rc2

[Mingshen Sun]

Dear community,

This is a call for a vote to release Apache Teaclave (incubating) version
0.1.0. This is the first Apache release since Teaclave entered the
incubator.

The Apache Teaclave (incubating) community has voted and approved the
release, with four +1 votes from IPMC members (Tongxin Li, Yu Ding, Furkan
Kamaci, and Pei Wang).

Vote/result thread:
  -
https://lists.apache.org/thread.html/r78add66efd8eb43be2f7e4548ea516528112bdd1d00a4626f095ca94%40%3Cdev.teaclave.apache.org%3E

The release candidate to be voted over is available at:
  - https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.1.0-rc.2/

The release candidate is signed with a GPG key available at:
  - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS

The Git commit for this release is:
  -
https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=commit;h=05769c80fd15612003d629603cadd2ecddbfca46

The Release Note is available in:
  - https://github.com/apache/incubator-teaclave/releases/tag/v0.1.0-rc.2

Build guide and get started instructions can be found at:
  -
https://github.com/apache/incubator-teaclave/blob/v0.1.0-rc.2/docs/my-first-function.md

The short version of building Teaclave from the source tarball:

```
$ wget
https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.1.0-rc.2/apache-teaclave-0.1.0-rc.2-incubating.tar.gz
$ tar zxvf apache-teaclave-0.1.0-rc.2-incubating.tar.gz && cd
apache-teaclave-0.1.0-rc.2-incubating
$ docker run --rm -v $(pwd):/teaclave -w /teaclave \
  -it teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest \
   bash -c ". /root/.cargo/env && \
 . /opt/sgxsdk/environment && \
 mkdir -p build && cd build && \
 cmake -DTEST_MODE=ON -DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \
 make"
```

The vote will be open for at least 72 hours.

  [ ] +1 approve
  [ ] +0 no opinion
  [ ] -1 disapprove with the reason

Thanks,
Mingshen Sun

Re: [DISCUSS] Incubation Proposal of MesaTEE

[Mingshen Sun]

Thanks, Stian. Welcome!

-
Mingshen

On Wed, Aug 14, 2019 at 2:16 AM Stian Soiland-Reyes 
wrote:

> On Sat, 10 Aug 2019 10:12:59 -0500, Matt Sicker  wrote:
> > I’d most likely be interested in mentoring this project, but I’m not that
> > experienced in incubator mentorship. If we have another more experienced
> > mentor to work with us, I’d be happy to mentor as well.
>
> I can also join as mentor.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Incubation Proposal of MesaTEE

[Mingshen Sun]

Hi Matt, thanks. We’re glad to have you as a mentor.

--
Mingshen

On Sat, Aug 10, 2019 at 8:13 AM Matt Sicker  wrote:

> I’d most likely be interested in mentoring this project, but I’m not that
> experienced in incubator mentorship. If we have another more experienced
> mentor to work with us, I’d be happy to mentor as well.
>
> On Sat, Aug 10, 2019 at 04:13, Mingshen Sun  wrote:
>
> > Thanks Justin, regarding to your questions:
> >
> > On Thu, Aug 8, 2019 at 2:46 AM Justin Mclean 
> > wrote:
> > >
> > > Hi,
> > >
> > > Thanks for the proposal, it sound like a really interesting project.
> > >
> > > > == Core Developers ==
> > > >
> > > > Current core developers work at Baidu. We are confident that
> > incubation will
> > > > help us grow a diverse community in an open and collaborative way.
> > > >
> > > > The risk of abandonment of MesaTEE is low. MesaTEE has been incubated
> > at Baidu
> > > > for over two years. Baidu is committed to the further development of
> > the project
> > > > and will keep investing resources towards the Apache processes and
> > community
> > > > building, during the incubation period.
> > >
> > > Incubation can sometimes take 2 years or more. Given few people with
> > experience at Apache are involved with this project and the core
> developers
> > are from one company, it may take longer that indicated in this proposal.
> >
> > We understand the incubation could take 2 years or more. Recently, we
> > have already received some pull requests from third-parties.
> > Therefore, during the incubation period, we will try to
> > attract/involved engineers from other companies as constant
> > committers.
> >
> > >
> > > > == Continuous Integration Service ==
> > > >
> > > > MesaTEE currently uses self-hosted continuous integration (CI)
> service
> > which can
> > > > help developers to automatically test commits. The CI service
> involves
> > several
> > > > nodes which support Intel SGX. We would like to continue doing so.
> > >
> > > This may not be possible, what would the project do if that was the
> > case? Have you discussed this with your proposed mentors or infra?
> >
> > About the CI infrastructure, actually, the "self-hosted CI" is not our
> > internal infra, we are using a open source CI service (Drone CI) with
> > our servers/NUC with SGX supported. To answer your questions, we have
> > several solutions:
> >   - we can use simulation mode for basic CI testing (by using existing
> > infra in Apache for example). And before merging a pull request, full
> > testing on a SGX supported machine is required
> >   - donating our SGX machines for CI services to Apache is another
> > option we may consider, but this should be further discussed
> >
> > > >  * Zhijie Shen 
> > >
> > > Is not currently an IPMC member, only IPMC members can officially be
> > mentors.
> > >
> > > Of the three mentors listed 2 have never been mentors to my knowledge,
> > have they been involved with any other projects going through the
> > incubating process at Apache? The third mentor may be a little
> overextended
> > given the number of podlings they mentors. Having only one experienced
> > mentor may be a risk to the project. What will you do if your mentors go
> > missing or unable to help?
> >
> > I have talked with Zhijie Shen. He is very interested in helping us.
> > Currently, he is a member of incubator and can apply for IPMC. In
> > addition to Zhijie Shen, Jianyong Dai, and Luciano Resende, Furkan
> > Kamaci also volunteered to become one of our mentors after posting
> > this proposal in the mailing list. We understand this is a large
> > project and need experienced mentors. We are very open to include more
> > mentors who are interested in the project.
> >
> > -
> > Mingshen
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> > --
> Matt Sicker 
>

Re: [DISCUSS] Incubation Proposal of MesaTEE

[Mingshen Sun]

Thanks Justin, regarding to your questions:

On Thu, Aug 8, 2019 at 2:46 AM Justin Mclean  wrote:
>
> Hi,
>
> Thanks for the proposal, it sound like a really interesting project.
>
> > == Core Developers ==
> >
> > Current core developers work at Baidu. We are confident that incubation will
> > help us grow a diverse community in an open and collaborative way.
> >
> > The risk of abandonment of MesaTEE is low. MesaTEE has been incubated at 
> > Baidu
> > for over two years. Baidu is committed to the further development of the 
> > project
> > and will keep investing resources towards the Apache processes and community
> > building, during the incubation period.
>
> Incubation can sometimes take 2 years or more. Given few people with 
> experience at Apache are involved with this project and the core developers 
> are from one company, it may take longer that indicated in this proposal.

We understand the incubation could take 2 years or more. Recently, we
have already received some pull requests from third-parties.
Therefore, during the incubation period, we will try to
attract/involved engineers from other companies as constant
committers.

>
> > == Continuous Integration Service ==
> >
> > MesaTEE currently uses self-hosted continuous integration (CI) service 
> > which can
> > help developers to automatically test commits. The CI service involves 
> > several
> > nodes which support Intel SGX. We would like to continue doing so.
>
> This may not be possible, what would the project do if that was the case? 
> Have you discussed this with your proposed mentors or infra?

About the CI infrastructure, actually, the "self-hosted CI" is not our
internal infra, we are using a open source CI service (Drone CI) with
our servers/NUC with SGX supported. To answer your questions, we have
several solutions:
  - we can use simulation mode for basic CI testing (by using existing
infra in Apache for example). And before merging a pull request, full
testing on a SGX supported machine is required
  - donating our SGX machines for CI services to Apache is another
option we may consider, but this should be further discussed

> >  * Zhijie Shen 
>
> Is not currently an IPMC member, only IPMC members can officially be mentors.
>
> Of the three mentors listed 2 have never been mentors to my knowledge, have 
> they been involved with any other projects going through the incubating 
> process at Apache? The third mentor may be a little overextended given the 
> number of podlings they mentors. Having only one experienced mentor may be a 
> risk to the project. What will you do if your mentors go missing or unable to 
> help?

I have talked with Zhijie Shen. He is very interested in helping us.
Currently, he is a member of incubator and can apply for IPMC. In
addition to Zhijie Shen, Jianyong Dai, and Luciano Resende, Furkan
Kamaci also volunteered to become one of our mentors after posting
this proposal in the mailing list. We understand this is a large
project and need experienced mentors. We are very open to include more
mentors who are interested in the project.

-
Mingshen

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Incubation Proposal of MesaTEE

[Mingshen Sun]

Thanks Antoine.

Feel free to discuss anything about the MesaTEE project.
I’m glad to answer all questions and concerns.

-
Mingshen

> On Aug 5, 2019, at 11:48 AM, Antoine Toulme  wrote:
> 
> I support this proposal and would like to be listed in the interested parties.
> 
> Cheers,
> 
> Antoine Toulme
> 
>> On Aug 5, 2019, at 8:14 PM, Zhijie Shen  wrote:
>> 
>> BTW, I saw MSR has an interesting research work to integrate MapReduce with
>> SGX to analyze big data in an privacy-preserved way:
>> https://www.microsoft.com/en-us/research/wp-content/uploads/2016/02/vc3-oakland2015.pdf.
>> I'm looking forward to the potential integration between this project with
>> a few big data project under ASF.
>> 
>> On Sun, Aug 4, 2019 at 10:07 AM Mingshen Sun  wrote:
>> 
>>> Thanks for your interests.
>>> 
>>> Regarding to you question, no, you cannot use it to sandbox arbitrary code.
>>> Trusted computing/confidential computing is not just about isolation and
>>> sandbox.
>>> For the SGX setup, because lots of sources (e.g., system calls, IO
>>> functions, etc.)
>>> are not trusted, which will break the treat model of trusted computing.
>>> Normally, you should design a code with “trusted” part and “untrusted”
>>> part.
>>> For legacy code, it needs to be carefully tailored or separated. But
>>> sometimes,
>>> untrusted sources are still needed (e.g., a web service needs network
>>> capabilities),
>>> they should be as minimal as possible and easy to audit.
>>> 
>>> Yesterday, ted gave a very good use case (
>>> https://signal.org/blog/private-contact-discovery/).
>>> But there are others listed in the doc:
>>> https://github.com/mesalock-linux/mesatee/blob/master/docs/case_study.md
>>> 
>>> 
>>>> On Aug 4, 2019, at 8:37 AM, Matt Sicker  wrote:
>>>> 
>>>> I’ve read through a bit of the site and blog posts. I’m pretty interested
>>>> in the project, especially any efforts to support more programming
>>>> languages.
>>>> 
>>>> Is it possible to use this to sandbox arbitrary code?
>>>> 
>>>> On Sat, Aug 3, 2019 at 17:22, Mingshen Sun 
>>> wrote:
>>>> 
>>>>> Yes, this project can be used for securing general computations.
>>>>> You can simply use the `mesatee_core` library to write an SGX encalve.
>>>>> In addition, MesaTEE provides others features like function as a
>>> service.
>>>>> That’s why we call it a universal securing computing framework.
>>>>> 
>>>>> Best,
>>>>> Mingshen Sun
>>>>> 
>>>>> On 2019/08/03 15:27:41, Matt Sicker  wrote:
>>>>>> Would this project be useful in securing general computations? You
>>>>> mention>
>>>>>> big data and AI a lot, though I’m wondering if this is also usable for>
>>>>>> things like, say, general multi tenant applications?>
>>>>>> 
>>>>>> On Sat, Aug 3, 2019 at 03:27, Mingshen Sun 
>>>>> wrote:>
>>>>>> 
>>>>>>> Hi,>
>>>>>>>> 
>>>>>>> This is Mingshen Sun from Baidu X-Lab. Recently, we have open-sourced>
>>>>>>> a universal secure computing framework called MesaTEE (>
>>>>>>> https://mesatee.org/).>
>>>>>>> The MesaTEE project enables general computing service for>
>>>>>>> security-critical scenarios,>
>>>>>>> which attracts many attentions from academia and industry.>
>>>>>>>> 
>>>>>>> To better build up the whole ecosystem, we decide to donate the
>>>>> MesaTEE>
>>>>>>> project to>
>>>>>>> Apache Foundation. Therefore, we’d like to propose our project to go>
>>>>>>> through>
>>>>>>> the incubation process.>
>>>>>>>> 
>>>>>>> Attached is our incubation proposal for open discussion. Thank you so
>>>>> much.>
>>>>>>>> 
>>>>>>> Best,>
>>>>>>> Mingshen Sun>
>>>>>>> Baidu X-Lab>
>>>>>>>> 
>>>>>>>> 
>>>>>>> Here is the proposal details:>
>>>>>>>> 
>>>>>>> ==>
>>>

Re: [DISCUSS] Incubation Proposal of MesaTEE

[Mingshen Sun]

Thanks for your interests.

Regarding to you question, no, you cannot use it to sandbox arbitrary code.
Trusted computing/confidential computing is not just about isolation and 
sandbox.
For the SGX setup, because lots of sources (e.g., system calls, IO functions, 
etc.)
are not trusted, which will break the treat model of trusted computing.
Normally, you should design a code with “trusted” part and “untrusted” part.
For legacy code, it needs to be carefully tailored or separated. But sometimes,
untrusted sources are still needed (e.g., a web service needs network 
capabilities),
they should be as minimal as possible and easy to audit.

Yesterday, ted gave a very good use case 
(https://signal.org/blog/private-contact-discovery/).
But there are others listed in the doc: 
https://github.com/mesalock-linux/mesatee/blob/master/docs/case_study.md


> On Aug 4, 2019, at 8:37 AM, Matt Sicker  wrote:
> 
> I’ve read through a bit of the site and blog posts. I’m pretty interested
> in the project, especially any efforts to support more programming
> languages.
> 
> Is it possible to use this to sandbox arbitrary code?
> 
> On Sat, Aug 3, 2019 at 17:22, Mingshen Sun  wrote:
> 
>> Yes, this project can be used for securing general computations.
>> You can simply use the `mesatee_core` library to write an SGX encalve.
>> In addition, MesaTEE provides others features like function as a service.
>> That’s why we call it a universal securing computing framework.
>> 
>> Best,
>> Mingshen Sun
>> 
>> On 2019/08/03 15:27:41, Matt Sicker  wrote:
>>> Would this project be useful in securing general computations? You
>> mention>
>>> big data and AI a lot, though I’m wondering if this is also usable for>
>>> things like, say, general multi tenant applications?>
>>> 
>>> On Sat, Aug 3, 2019 at 03:27, Mingshen Sun 
>> wrote:>
>>> 
>>>> Hi,>
>>>>> 
>>>> This is Mingshen Sun from Baidu X-Lab. Recently, we have open-sourced>
>>>> a universal secure computing framework called MesaTEE (>
>>>> https://mesatee.org/).>
>>>> The MesaTEE project enables general computing service for>
>>>> security-critical scenarios,>
>>>> which attracts many attentions from academia and industry.>
>>>>> 
>>>> To better build up the whole ecosystem, we decide to donate the
>> MesaTEE>
>>>> project to>
>>>> Apache Foundation. Therefore, we’d like to propose our project to go>
>>>> through>
>>>> the incubation process.>
>>>>> 
>>>> Attached is our incubation proposal for open discussion. Thank you so
>> much.>
>>>>> 
>>>> Best,>
>>>> Mingshen Sun>
>>>> Baidu X-Lab>
>>>>> 
>>>>> 
>>>> Here is the proposal details:>
>>>>> 
>>>> ==>
>>>>> 
>>>> MesaTEE Apache Incubation Proposal>
>>>>> 
>>>> = Abstract =>
>>>>> 
>>>> MesaTEE is a framework for universal secure computing.>
>>>>> 
>>>> = Proposal =>
>>>>> 
>>>> MesaTEE is the next-gen solution to enable general computing service
>> for>
>>>> security-critical scenarios. It will allow even the most sensitive
>> data to>
>>>> be>
>>>> securely processed to enable offshore businesses without leakage.>
>>>>> 
>>>> The solution combines the advanced Hybrid Memory Safety (HMS) model
>> and the>
>>>> power of the Trusted Computing technologies (e.g., TPM) as well as
>> the>
>>>> Confidential Computing technologies (e.g., Intel SGX).>
>>>>> 
>>>>  * Code base:>
>>>>* https://github.com/mesalock-linux/mesatee>
>>>>* https://github.com/baidu/rust-sgx-sdk>
>>>>  * Website: https://mesatee.org>
>>>>  * Documentation: https://mesatee.org/doc/mesatee_sdk/>
>>>>> 
>>>> = Background =>
>>>>> 
>>>> The emerging technologies of big data analytics, machine learning,>
>>>> cloud/edge>
>>>> computing, and blockchain are significantly boosting our productivity,
>> but>
>>>> at>
>>>> the same time they are bringing new confidentiality and integrity>
>>>> concerns. On>
>>>> public cloud and blockchain, sensitive data like health and financial>
>>>> records>

Re: [DISCUSS] Incubation Proposal of MesaTEE

[Mingshen Sun]

Yes, this project can be used for securing general computations.
You can simply use the `mesatee_core` library to write an SGX encalve.
In addition, MesaTEE provides others features like function as a service.
That’s why we call it a universal securing computing framework.

Best,
Mingshen Sun

On 2019/08/03 15:27:41, Matt Sicker  wrote: 
> Would this project be useful in securing general computations? You mention> 
> big data and AI a lot, though I’m wondering if this is also usable for> 
> things like, say, general multi tenant applications?> 
> 
> On Sat, Aug 3, 2019 at 03:27, Mingshen Sun  wrote:> 
> 
> > Hi,> 
> >> 
> > This is Mingshen Sun from Baidu X-Lab. Recently, we have open-sourced> 
> > a universal secure computing framework called MesaTEE (> 
> > https://mesatee.org/).> 
> > The MesaTEE project enables general computing service for> 
> > security-critical scenarios,> 
> > which attracts many attentions from academia and industry.> 
> >> 
> > To better build up the whole ecosystem, we decide to donate the MesaTEE> 
> > project to> 
> > Apache Foundation. Therefore, we’d like to propose our project to go> 
> > through> 
> > the incubation process.> 
> >> 
> > Attached is our incubation proposal for open discussion. Thank you so 
> > much.> 
> >> 
> > Best,> 
> > Mingshen Sun> 
> > Baidu X-Lab> 
> >> 
> >> 
> > Here is the proposal details:> 
> >> 
> > ==> 
> >> 
> > MesaTEE Apache Incubation Proposal> 
> >> 
> > = Abstract => 
> >> 
> > MesaTEE is a framework for universal secure computing.> 
> >> 
> > = Proposal => 
> >> 
> > MesaTEE is the next-gen solution to enable general computing service for> 
> > security-critical scenarios. It will allow even the most sensitive data to> 
> > be> 
> > securely processed to enable offshore businesses without leakage.> 
> >> 
> > The solution combines the advanced Hybrid Memory Safety (HMS) model and 
> > the> 
> > power of the Trusted Computing technologies (e.g., TPM) as well as the> 
> > Confidential Computing technologies (e.g., Intel SGX).> 
> >> 
> >   * Code base:> 
> > * https://github.com/mesalock-linux/mesatee> 
> > * https://github.com/baidu/rust-sgx-sdk> 
> >   * Website: https://mesatee.org> 
> >   * Documentation: https://mesatee.org/doc/mesatee_sdk/> 
> >> 
> > = Background => 
> >> 
> > The emerging technologies of big data analytics, machine learning,> 
> > cloud/edge> 
> > computing, and blockchain are significantly boosting our productivity, but> 
> > at> 
> > the same time they are bringing new confidentiality and integrity> 
> > concerns. On> 
> > public cloud and blockchain, sensitive data like health and financial> 
> > records> 
> > may be consumed at runtime by untrusted computing processes running on> 
> > compromised platforms; during in-house data exchange, confidential> 
> > information> 
> > may cross different clearance boundaries and possibly fall into the wrong> 
> > hands;> 
> > also not to mention the privacy issue arises in offshore data supply> 
> > chains.> 
> >> 
> > Although the consequences of data breaching have been extensively> 
> > elaborated, we> 
> > should also note that proprietary computing algorithms themselves, such as> 
> > AI> 
> > models, also need to be well protected. Once leaked, attackers can steal> 
> > the> 
> > intellectual properties, or launch whitebox attacks and easily exploit the> 
> > weaknesses of the models.> 
> >> 
> > Facing all these risky scenarios, we are in desperate need of a trusted 
> > and> 
> > secure mechanism, enabling us to protect both private data and proprietary> 
> > computing models during a migratable execution in potentially unsafe> 
> > environments, yet preserving functionalities, performance, compatibility,> 
> > and> 
> > flexibility. MesaTEE is targeting to be, as we call it, the full 
> > "Universal> 
> > Secure Computing" stack, so it can help users resolve these runtime> 
> > security> 
> > risks.> 
> >> 
> > MesaTEE aims to promote the development of universal secure computing> 
> > ecosystem> 
> > through open source and openness, to provide basic support for trust> 
> > pro

[DISCUSS] Incubation Proposal of MesaTEE

[Mingshen Sun]

Hi,

This is Mingshen Sun from Baidu X-Lab. Recently, we have open-sourced
a universal secure computing framework called MesaTEE (https://mesatee.org/).
The MesaTEE project enables general computing service for security-critical 
scenarios,
which attracts many attentions from academia and industry.

To better build up the whole ecosystem, we decide to donate the MesaTEE project 
to
Apache Foundation. Therefore, we’d like to propose our project to go through
the incubation process.

Attached is our incubation proposal for open discussion. Thank you so much.

Best,
Mingshen Sun
Baidu X-Lab


Here is the proposal details:

==

MesaTEE Apache Incubation Proposal

= Abstract =

MesaTEE is a framework for universal secure computing.

= Proposal =

MesaTEE is the next-gen solution to enable general computing service for
security-critical scenarios. It will allow even the most sensitive data to be
securely processed to enable offshore businesses without leakage.

The solution combines the advanced Hybrid Memory Safety (HMS) model and the
power of the Trusted Computing technologies (e.g., TPM) as well as the
Confidential Computing technologies (e.g., Intel SGX).

  * Code base:
* https://github.com/mesalock-linux/mesatee
* https://github.com/baidu/rust-sgx-sdk
  * Website: https://mesatee.org
  * Documentation: https://mesatee.org/doc/mesatee_sdk/

= Background =

The emerging technologies of big data analytics, machine learning, cloud/edge
computing, and blockchain are significantly boosting our productivity, but at
the same time they are bringing new confidentiality and integrity concerns. On
public cloud and blockchain, sensitive data like health and financial records
may be consumed at runtime by untrusted computing processes running on
compromised platforms; during in-house data exchange, confidential information
may cross different clearance boundaries and possibly fall into the wrong hands;
also not to mention the privacy issue arises in offshore data supply chains.

Although the consequences of data breaching have been extensively elaborated, we
should also note that proprietary computing algorithms themselves, such as AI
models, also need to be well protected. Once leaked, attackers can steal the
intellectual properties, or launch whitebox attacks and easily exploit the
weaknesses of the models.

Facing all these risky scenarios, we are in desperate need of a trusted and
secure mechanism, enabling us to protect both private data and proprietary
computing models during a migratable execution in potentially unsafe
environments, yet preserving functionalities, performance, compatibility, and
flexibility. MesaTEE is targeting to be, as we call it, the full "Universal
Secure Computing" stack, so it can help users resolve these runtime security
risks.

MesaTEE aims to promote the development of universal secure computing ecosystem
through open source and openness, to provide basic support for trust protection
for the productivity revolution brought by big data and AI, to completely solve
the data exchange or multi-party computing between departments/companies, to
enable privacy-crucial services such as financial and medical care using
blockchain/cloud services, and to convoy businesses that are closely related to
life and safety such as autonomous driving. MesaTEE has been working closely
with mainstream cloud computing/blockchain/chip vendors and
universities/research institutions to promote hardware TEE, software memory
safety, and versatile computing services to create an internationally protected
and flexible secure computing framework. MesaTEE’s open-source release will
greatly accelerate the development of the next generation of big data business
applications, and it is also of great importance to promoting AI ​​in all 
business
areas.

= Rationale =

MesaTEE stack redefines future AI and big data analytics by providing a trusted
and secure offshore computing environment. The confidentiality and privacy of
data and models can be well protected with MesaTEE, even if data and model
originate from different parties with no mutual trust. Moreover, the computing
platform itself is not necessarily trusted either. The Trusted Computing Base
(TCB) can thus be largely reduced to MesaTEE framework alone. A detailed
description of target use-cases can be found at
https://github.com/mesalock-linux/mesatee/blob/master/docs/case_study.md.

We believe that Apache way of open source community empowers MesaTEE to attract
a diverse set of contributors who can bring new ideas into the project.

= Initial Goals =

  * Move the existing codebase, website, documentation, and mailing lists to an
Apache-hosted infrastructure.
  * Integrate with the Apache development process.
  * Ensure all dependencies are compliant with Apache License version 2.0.
  * Incrementally develop and release per Apache guidelines.

= Current Status =

The MesaTEE project (and its sub-project Rust SGX SDK) has bee