Re: Podling Teaclave Report Reminder - January 2022
Looks good to me! — Matt Sicker > On Jan 12, 2022, at 13:16, Mingshen Sun wrote: > > Hi mentors, > > Sorry for the late reply. I have complete the report and uploaded to > the wiki page: > https://cwiki.apache.org/confluence/display/INCUBATOR/January2022#teaclave > > Also, please kindly help to sign off the report if everything looks > good to you. Thanks! > > Mingshen Sun > > Here is the report: > > ## Teaclave > > ### Three most important unfinished issues to address before graduating: > > - Improve project structure and documentation > - Grow the community (attracting more committers, contributors, users) > - Publish Apache releases (resolving logistics on Apache release) > > ### Are there any issues that the IPMC or ASF Board need to be aware of? > > None. > > ### How has the community developed since the last report? > > Since the last report, we have organized two monthly virtual meetups. > For each meetup, we have write-ups published on the Teaclave blog. > - Teaclave Meetup #8: > <https://teaclave.apache.org/blog/2021-10-14-teaclave-meetup-8/> > - Teaclave Meetup #9: > <https://teaclave.apache.org/blog/2021-11-30-teaclave-meetup-9/> > > We also published a security advisory on a recent vulnerability on > Intel SGX SDK. > - SECURITY ADVISORY OF SMASHEX AND CVE-2021-0186: > <https://teaclave.apache.org/blog/2021-10-25-security-advisory-of-smashex-and-cve-2021-0186/> > > To promote the recent TrustZone SDK in the Chinese community, we > published a blog on getting started with the SDK for newcomers. > - 使用 TEACLAVE TRUSTZONE SDK 开发 TRUSTZONE 应用: > <https://teaclave.apache.org/blog/2021-10-15-developing-teaclave-application-with-teaclave-trustzone-sdk/> > > ### How has the project developed since the last report? > > Here are the summaries of recent progress: > > Teaclave Faas Platform > > - [docker] start Teaclave docker services with auto-detection mechanism > - Support selectively including executors (#574) > - Optimize RPC memory footprint of serde (#577) > - Persistent MockDB in test mode. (#580) > - Flush DB and compact_range after dequeue operation > - API updates (#588): UpdateFunction, ListFunciton, DeleteFunction, > UserUpdate, UserRegister, UserUpdate > - Introduce role-based user management and access control > - Bug fixes and code refactoring > > Teaclave TrustZone SDK > > - Update Rust toolchain to nightly-2021-09-20 an std to 1.56.1 > > Teaclave SGX SDK > > - Support Intel SGX SDK 2.15, DCAP 1.12 > - Update rust toolchain to nightly-2021-11-01 > > Website > > - [blog] Teaclave Meetup #8: > <https://teaclave.apache.org/blog/2021-10-14-teaclave-meetup-8/> > - [blog] Teaclave Meetup #9: > <https://teaclave.apache.org/blog/2021-11-30-teaclave-meetup-9/> > - [blog] SECURITY ADVISORY OF SMASHEX AND CVE-2021-0186: > <https://teaclave.apache.org/blog/2021-10-25-security-advisory-of-smashex-and-cve-2021-0186/> > - [blog] 使用 TEACLAVE TRUSTZONE SDK 开发 TRUSTZONE 应用: > <https://teaclave.apache.org/blog/2021-10-15-developing-teaclave-application-with-teaclave-trustzone-sdk/> > > ### How would you assess the podling's maturity? > Please feel free to add your own commentary. > > - [ ] Initial setup > - [ ] Working towards first release > - [x] Community building > - [ ] Nearing graduation > - [ ] Other: > > ### Date of last release: > > 2021-08-23: Apache Teaclave (incubating) 0.3.0 > > ### When were the last committers or PPMC members elected? > > - 2021-09-20: Yuan Zhuang (Apache ID: yuanz), Committer > - 2021-09-20: Rong Fan (Apache ID: fanrong), Committer > > ### Have your mentors been helpful and responsive? > > Yes, our mentors work responsively to help us with electing new > mentors, developing new features, fixing bugs, and expanding the > community. > > ### Is the PPMC managing the podling's brand / trademarks? > > We don't find any 3rd parties incorrectly using the podling's name and > brand. The VP, Brand has approved the project name. > (PODLINGNAMESEARCH-175) > >> On Tue, Jan 4, 2022 at 1:44 PM Mingshen Sun wrote: >> >> Dear Teaclave community, >> >> I'll work on this today. Sorry for the delay. >> >> Mingshen >> >>> On Thu, Dec 23, 2021 at 10:20 PM wrote: >>> >>> Dear podling, >>> >>> This email was sent by an automated system on behalf of the Apache >>> Incubator PMC. It is an initial reminder to give you plenty of time to >>> prepare your quarterly board report. >>> >>> The board meeting is scheduled f
Re: Welcoming Yuan Zhuang (@yuanz) as Teaclave committer
Welcome to the community! On Mon, Nov 1, 2021 at 10:13 PM Yuan Zhuang wrote: > > Dear Teaclave community, > I am glad to become a committer in the Teaclave project. I will continue to > work on contributing code to Teaclave TrustZone SDK or other repositories. > Thanks to Mingshen and the community! > > > Best, > Yuan Zhuang > > > 在 2021年11月2日 09:44，Mingshen Sun 写道： > > > Dear Teaclave community, Please welcome Yuan Zhuang (@yuanz) to join the > Teaclave community as a committer. Yuan started working on Teaclave TrustZone > SDK for about half year ago and made several major contributions [1] to the > project including: - update for OP-TEE 3.11.0 - support for new TEE API and > update examples/aes/ta - loadable plugins - new documents She also helped > with the recent Teaclave/OP-TEE integration [2]. Right now, Teaclave > TrustZone SDK is the recommended SDK by OP-TEE for developing Rust TAs. [3] > Congratulations to Yuan and thanks! [1] > https://github.com/apache/incubator-teaclave-trustzone-sdk/commits?author=DemesneGH > [2] https://github.com/OP-TEE/optee_docs/pull/140 [3] > https://optee.readthedocs.io/en/latest/building/optee_with_rust.html Mingshen > Sun Apache Teaclave (incubating) PPMC https://mssun.me - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: Welcoming Rong Fan (@fanrong) as Teaclave committer
Welcome to the community! On Mon, Nov 1, 2021 at 9:29 PM 樊荣 wrote: > > Hi Teaclave community, > > I am very honored to join the community. I will continue to work hard to > contribute to the development of the community. Please advise, thanks. > > > > > > > > Best regards, > Rong Fan > > > > > > At 2021-11-02 09:44:32, "Mingshen Sun" wrote: > >Dear Teaclave community, > > > >Please welcome Rong Fan (@fanrong) to join the Teaclave community as a > >committer. > > > >Rong started working on Teaclave TrustZone SDK for about half year ago > >and made several major contributions [1] to the project including: > > > >- keep update with the latest OP-TEE versions > >- use dynamic library in the client library > >- make our building system compatible with that in OP-TEE > > > >He also helped with the recent Teaclave/OP-TEE integration [2, 3], > >which is a huge milestone for the Teaclave TrustZone SDK project. > >Right now, Teaclave TrustZone SDK is the recommended SDK by OP-TEE for > >developing Rust TAs. [4] > > > >Congratulations to Rong and thanks! > > > >[1] > >https://github.com/apache/incubator-teaclave-trustzone-sdk/commits?author=fanrong1992 > >[2] https://github.com/OP-TEE/manifest/pull/200 > >[3] https://github.com/OP-TEE/build/pull/521 > >[4] https://optee.readthedocs.io/en/latest/building/optee_with_rust.html > > > >Mingshen Sun > >Apache Teaclave (incubating) PPMC > >https://mssun.me - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: [apache/incubator-teaclave] Doc: C code can also be compiled using Zig (#550)
Zig supports all of C along with its own Zig programming language. It's a drop in compiler replacement with friendly errors. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/550#issuecomment-904698761
Re: Welcome Gordon as our mentor
Welcome! On Mon, Jul 26, 2021 at 11:22 AM Zhaofeng Chen wrote: > > Hi Gordon, > > Welcome to the community! > > Best, > Zhaofeng > > On Sun, Jul 25, 2021 at 11:20 PM Gordon King wrote: > > > Thank you all for adding me as a mentor to Teaclave community ! > > > > Gordon. > > > > On 2021/07/26 05:46:51, Mingshen Sun wrote: > > > Dear Teaclave community, > > > > > > Let's welcome our new mentor - Gordon [1]. Gordon is from Apache > > > Mnemonic PMC and Intel. > > > > > > Gordon is working closely with the community on the integration of > > > Teaclave and Graphene [2]. As a confidential computing platform, > > > Teaclave is using Intel SGX as our TEE backend. I'm sure that Gordon's > > > involvement can help our community in both technical aspects and > > > diversity. > > > > > > Congratulations to Gordon and welcome! > > > > > > Best, > > > Mingshen > > > > > > - [1] > > https://lists.apache.org/thread.html/rf45f78a21060a62b67efc2573328214ece981a4bcfd089f3c3438624%40%3Cdev.teaclave.apache.org%3E > > > - [2] https://github.com/apache/incubator-teaclave/issues/525 > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: [VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.1.0-rc1
+1 Signatures good, builds and tests good (using Docker), proper disclaimer files, license, notice, and license header info in rust source files (though not all of them; those will need license clarification later). Notes for future releases (not blocking due to DISCLAIMER-WIP): there are some source files that support comments like .toml, Dockerfile, .yml, .sh, and so forth, that will need appropriate Apache License headers. This is detailed at [1]. See [2] for a short form that would be useful for certain files that have limited space for license info. [1]: https://www.apache.org/legal/src-headers.html [2]: https://www.apache.org/legal/src-headers.html#is-a-short-form-of-the-source-header-available On Fri, 4 Jun 2021 at 18:02, Rundong Zhou wrote: > > +1 > > Regards, > Rundong > > On 2021/06/04 22:18:59, Mingshen Sun wrote: > > Dear Teaclave community, > > > > I am pleased to be calling this vote for the first release of Apache > > Teaclave TrustZone SDK (incubating) 0.1.0 (release candidate 1). > > > > 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. 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. > > > > A checklist for reference: > > - > > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > > > Note that you can also reply with things you have checked. > > > > Best, > > > > Mingshen Sun > > http://mssun.me > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > For additional commands, e-mail: dev-h...@teaclave.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: [apache/incubator-teaclave-sgx-sdk] Benchmarking / Profiling Recommendations (#330)
Benchmarking might be complicated here as many use cases should use constant-time algorithms to avoid side channel information leakage. Are you looking for benchmarks of individual operations? I'd be interested in how that could work here as well. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/330#issuecomment-805115007
Re: Teaclave Meetup #1 Minutes
Very cool to see! Thanks for sharing the minutes. I'm looking forward to see where the community takes us. On Thu, 28 Jan 2021 at 23:51, Mingshen Sun wrote: > > Dear Teaclave community, > > We just finished the first public virtual meetup. Around 11 people > from the community show up in the virtual meetup. Thanks for attending > the meetup. For people who were not available at this time, here is a > short summary: > > ## Schedule > > - Recent Update and Roadmap in 2021 by Mingshen Sun (40 minutes) > - Q and free discussion (20 minutes) > > ## Recent Updates of Teaclave > > - Teaclave TrustZone SDK donation > - Rust/C client SDK > - GitHub Actions, GitHub Issue templates > - GSoC call for proposals > - Teaclave meetup call for speakers > > ## 2021 Objectives of Teaclave Projects > > - Teaclave FaaS Platform: The best platform for secure computing > applications. The most influential open source project in the secure > computing community. > - Teaclave SGX SDK: Keep the leading position in SGX SDK. Healthy and > sustainable community. > - Teaclave TrustZone SDK: Become a mature project for developing > TrustZone applications. > - MesaPy for SGX (not in ASF, but related with Teaclave): Mature > Python scripting VM for SGX. More versatile scenarios: data analytics, > machine learning, and smart contract. > > ## Project Release Timeline > > - Release Teaclave SGX SDK's Apache official release (Q1, Q3) > - Regular releases of Teaclave FaaS Platform (Q1, Q2, Q3, Q4) > - Teaclave TrustZone SDK Apache donation (Q1) > - Teaclave TrustZone SDK apache official release (Q2) > - MesaPy for SGX Apache donation (Q2) > - MesaPy for SGX Apache official release (Q3) > > ## Community Activities > > - Regular meetup (monthly) > - Annually Teaclave workshop (H2) > - Blogs (monthly) > > ## To-do List > > - [RFC] Roadmap in 2021: Project Maturity and Community Buildup > (https://github.com/apache/incubator-teaclave/issues/460) > > At last, thanks for attending this meetup. I'll continue to drive this meetup > and make it a monthly activity for the community. If you want to speak in the > next time, please post your proposed topic in the mailing list. I'll help you > to schedule the time. > > * This post is also published on the Teaclave blog > (https://teaclave.apache.org/blog/2021-01-27-teaclave-meetup-1/). > > Best, > Mingshen Sun > > - > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > For additional commands, e-mail: dev-h...@teaclave.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: Podling Teaclave Report Reminder - January 2021
Looks good to me! On Wed, 6 Jan 2021 at 19:23, Mingshen Sun wrote: > > Dear Teaclave community, > > Here is the report for 2020 Q4. Feel free to comment on the report. Thanks. > > To mentors, I have uploaded the report to the wiki page. [1] > > Best, > Mingshen > > [1] https://cwiki.apache.org/confluence/display/INCUBATOR/January2021#teaclave > > ## Teaclave > > Teaclave is a universal secure computing platform. > > Teaclave has been incubating since 2019-08-20. > > ### Three most important unfinished issues to address before graduating: > > 1. Improve project structure and documentation > 2. Grow the community (attracting more committers, contributors, users) > 3. Publish more Apache releases > > ### Are there any issues that the IPMC or ASF Board need to be aware of? > > None. > > ### How has the community developed since the last report? > > - We received contributions from a new external contributor. > - We found a new project using Teaclave SGX SDK called Veracruz, which is a > framework for defining and deploying collaborative, privacy-preserving > computations amongst a group of mutually mistrusting individuals. > - We summarized the community and projects powered by Teaclave and published > a blog on our homepage. > - Rust TrustZone SDK will be accepted in Teaclave as a subproject. The > community > is discussing and voting the acceptance. > - The community has accepted a new committer. > > ### How has the project developed since the last report? > > - Add PCA function in the builtin executor. > - Add exposed password checking function in the builtin executor. > - Add the attestation subcommand to display attestation reports form > the Intel attestation service. > - Add document to support deploying on Azure confidential computing VM. > > > ### How would you assess the podling's maturity? > Please feel free to add your own commentary. > > - [ ] Initial setup > - [ ] Working towards first release > - [x] Community building > - [ ] Nearing graduation > - [ ] Other: > > ### Date of last release: > > 2020-10-09 > > ### When were the last committers or PPMC members elected? > > 2020-10-22 > > ### Have your mentors been helpful and responsive? > > Yes, our mentors are very helpful and responsive on our discussion > about security > reporting and new projects acceptance voting. > > ### Is the PPMC managing the podling's brand / trademarks? > We don't find any 3rd parties incorrectly using the podling's name and brand. > The VP, Brand has approved the project name. (PODLINGNAMESEARCH-175) > > On Wed, Jan 6, 2021 at 10:48 AM Mingshen Sun wrote: > > > > Hi Dave, > > > > Thanks for the reminder. Don't know why I missed this email. > > > > To mentors, I will prepare the report today. > > > > Best, > > Mingshen > > > > On Wed, Jan 6, 2021 at 10:44 AM Dave Fisher wrote: > > > > > > A reminder to discuss and submit a report. > > > > > > Thanks, > > > Dave > > > > > > On 2020/12/24 00:35:06, jmcl...@apache.org wrote: > > > > Dear podling, > > > > > > > > This email was sent by an automated system on behalf of the Apache > > > > Incubator PMC. It is an initial reminder to give you plenty of time to > > > > prepare your quarterly board report. > > > > > > > > The board meeting is scheduled for Wed, 20 January 2021. > > > > The report for your podling will form a part of the Incubator PMC > > > > report. The Incubator PMC requires your report to be submitted 2 weeks > > > > before the board meeting, to allow sufficient time for review and > > > > submission (Wed, January 06). > > > > > > > > Please submit your report with sufficient time to allow the Incubator > > > > PMC, and subsequently board members to review and digest. Again, the > > > > very latest you should submit your report is 2 weeks prior to the board > > > > meeting. > > > > > > > > Candidate names should not be made public before people are actually > > > > elected, so please do not include the names of potential committers or > > > > PPMC members in your report. > > > > > > > > Thanks, > > > > > > > > The Apache Incubator PMC > > > > > > > > Submitting your Report > > > > > > > > -- > > > > > > > > Your report should contain the following: > > > > > > > > * Your project name > > > > * A brief description of your project, which assumes no knowledge of > > > > the project or necessarily of its field > > > > * A list of the three most important issues to address in the move > > > > towards graduation. > > > > * Any issues that the Incubator PMC or ASF Board might wish/need to be > > > > aware of > > > > * How has the community developed since the last report > > > > * How has the project developed since the last report. > > > > * How does the podling rate their own maturity. > > > > > > > > This should be appended to the Incubator Wiki page at: > > > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/January2021 > > > > > > > > Note: This is manually populated.
Re: [VOTE] Accept Rust OP-TEE TrustZone SDK to Apache Teaclave (incubating)
+1 assuming you won't have any problems with getting the software grants for your donation :) On Tue, 5 Jan 2021 at 20:21, Gao,Yingchun(SEC) wrote: > > +1 > > -邮件原件- > 发件人: Mingshen Sun > 发送时间: 2021年1月5日 7:43 > 收件人: dev@teaclave.apache.org; simonsy...@gmail.com > 主题: [VOTE] Accept Rust OP-TEE TrustZone SDK to Apache Teaclave (incubating) > > Hi all, > > Rust OP-TEE TrustZone SDK provides abilities to build safe TrustZone > applications in Rust. The SDK is based on the OP-TEE project which follows > GlobalPlatform TEE specifications and provides ergonomic APIs. > > The SDK was developed by Baidu and open source on Jan 30, 2019. I'm one of > the initial comitters of the project. > > On behalf of the Rust OP-TEE TrustZone SDK project, I would like to call a > VOTE to accept Rust OP-TEE TrustZone SDK into Apache Teaclave > (incubating) as a subproject. I'm using part of the incubator proposal > template, but omit some irrelevant sections. > > Please cast your vote: > > [ ] +1, bring Rust OP-TEE TrustZone SDK into Teaclave > [ ] +0, I don't care either way > [ ] -1, do not bring Rust OP-TEE TrustZone SDK into Teaclave, because... > > The vote will open at least for 72 hours and only votes from the Teaclave > PPMC are binding, but votes from everyone are welcome. > > Proposal === > > ## Abstract > > Rust OP-TEE TrustZone SDK provides abilities to build safe TrustZone > applications in Rust. The SDK is based on the OP-TEE project which follows > GlobalPlatform TEE specifications and provides ergonomic APIs. > More information can be found at the project repository: > https://github.com/sccommunity/rust-optee-trustzone-sdk. > > ## Proposal > > Rust OP-TEE TrustZone SDK provides abilities to build safe TrustZone > applications in Rust. > > ### Background > > The Rust OP-TEE TrustZone project is being actively developed within Baidu. > It was open source on Jan 30, 2019. > > ### Rationale > > ARM TrustZone is another hardware trusted execution environment > implementation. The goal of Teaclave is to provide a universal secure > computing platform which is agnostic with TEE implementation. > Currently, Teaclave has Teaclave SGX SDK and only supports Intel SGX. > With the Rust OP-TEE TrustZone SDK, we can build the Teaclave platform on ARM > TrustZone. > > ### Initial Goals > > - Transfer repository to the Apache Incubator under the Teaclave project > - Code cleanup and more documentation > > Meritocracy: > > The Rust OP-TEE TrustZone SDK project was originally developed by Shengye Wan > and Mingshen Sun within Baidu. The project now has new committers from around > the world. Some open source projects like https://github.com/veracruz-project > are using the SDK to build their systems. We encourage everyone to ask > questions and create pull requests to the project. > > Community: > > We see several open source projects which are using the SDK for development. > Also, we already receive contributions from external comitters. The community > is growing overtime. > > Core Developers: > > The core developers are: > - Shengye Wan (simonsywan at gmail dot com) > - Mingshen Sun (mssun at apache.org) > > Alignment: > > The project is a complimentary of Teaclave's TEE backends. > > ### Known Risks > > An exercise in self-knowledge. Risks don't mean that a project is > unacceptable. If they are recognized and noted, then they can be addressed > during incubation. > > Project Name > > Since the project will be accepted as a subproject in Teaclave, the project > is renamed to Teaclave TrustZone SDK. > > Inexperience with Open Source: > > One of the core developers, Mingshen Sun is from the Teaclave community. He's > familiar with The Apache Way for the open source community. > > Length of Incubation: > > The project will be in incubation with Apache Teaclave (incubating) project. > > ### Documentation > > - > https://github.com/sccommunity/rust-optee-trustzone-sdk/wiki/Getting-started-with-OPTEE-for-QEMU-ARMv8 > > ### Initial Source > > - https://github.com/sccommunity/rust-optee-trustzone-sdk > > ### Source and Intellectual Property Submission Plan > > We will submit a Software Grant for this project later. > > External Dependencies: > > The dependencies have Apache compatible license, which is provided under the > BSD 2-Clause license. > > Cryptography: > > N/A > > ### Required Resources > > Mailing lists: > > The project shares the same mailing list of Teaclave. > > Git Repositories: > > - https://gitbox.apache.org/repos/asf/incubator-teaclave-trustzone-sdk.git > - https://github.com/apache/incubator-teaclave-trustzone-sdk > > Issue Tracking: > > Same with Teaclave. > > Other Resources: > > N/A > > ### Initial Committers > > - Shengye Wan (simonsywan at gmail dot com) > - Mingshen Sun (mssun at apache dot org) > > - > To unsubscribe,
Re: [apache/incubator-teaclave] Add instruction to report security issue in the community page (#441)
Might make sense to copy the links to a `SECURITY.md` file for better GitHub integration. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/pull/441#issuecomment-743459811
Re: Podling Teaclave Report Reminder - October 2020
; >> * How has the community developed since the last report > >> * How has the project developed since the last report. > >> * How does the podling rate their own maturity. > >> > >> This should be appended to the Incubator Wiki page at: > >> > >> https://cwiki.apache.org/confluence/display/INCUBATOR/October2020 > >> > >> Note: This is manually populated. You may need to wait a little before > >> this page is created from a template. > >> > >> Note: The format of the report has changed to use markdown. > >> > >> Mentors > >> --- > >> > >> Mentors should review reports for their project(s) and sign them off on > >> the Incubator wiki page. Signing off reports shows that you are > >> following the project - projects that are not signed may raise alarms > >> for the Incubator PMC. > >> > >> Incubator PMC > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > >> For additional commands, e-mail: dev-h...@teaclave.apache.org > >> > > > -- Matt Sicker
Re: Planning for the first Apache incubator release
Looking forward to it! I’ve got a bit of experience managing releases in other projects, so I can certainly help validate this. On Fri, Aug 21, 2020 at 22:32 Mingshen Sun wrote: > Hi folks, > > > > Since we entered the Apache Incubator, we have made a lot of progress [1]. > > The current codebase is becoming stable. I propose to make the first Apache > > incubator release, i.e., the first release (0.1.0) of Teaclave. I plan to > > work on the logistics of releasing an Apache version in the next week. > > These includes: > > - license checking > > - code packaging and signing > > - composing release notes > > > > Before that, I'd like to ask if there are any building blocks missing or > > any critical bugs still unsolved for the 0.1.0 release. For new features > > and enhancements, we can put them to the next release. Thanks. > > > > Best, > > Mingshen Sun > > > > - [1] https://github.com/apache/incubator-teaclave/issues/121 > > -- Matt Sicker
Re: Implications of SGAxe?
Thanks for the explanations everyone! And a blog post sounds like a great idea. On Wed, 10 Jun 2020 at 17:50, Mingshen Sun wrote: > > BTW, maybe we can write a blog about the implication of recent side > channel attacks in SGX. But we need some time to survey this problem > and collect enough materials. > > On Wed, Jun 10, 2020 at 3:18 PM Mingshen Sun wrote: > > > > Hi Matt, > > > > Thanks for bringing up this issue. Regardless of this specific attack > > itself, let me answer another frequently asked question about > > supporting other hardware enclaves. > > > > Actually, we have investigated other hardware enclaves for a long > > time. The following are commonly mentioned hardware TEE > > implementations: > > > > - Intel SGX > > - AMD SEV > > - ARM TrustZone > > - RISC-V Keystone > > > > From our experience, Intel SGX provides better security guarantees > > memory encryption/integrity. Also it is more mature in terms of > > ecosystem including toolchains, documents, community, etc. Sadly, > > because of various reasons, they all somehow suffer from side channel > > attacks. Luckly, there are mitigation methods for these attacks. > > > > To answer the question, yes, we do want to support other hardware TEE > > implementations and provide different choices for users/developers. I > > believe as the time goes on, other TEE implementations will become > > mature eventually. Before that, we plan to spend more time on > > implementing the platform itself: providing better interfaces, > > improving functionalities of services, defining the work flow, etc. In > > the meantime, we should also design the system with better > > abstraction with layers so that once things are ready, we can support > > other platforms. > > > > Best, > > Mingshen Sun > > > > On Wed, Jun 10, 2020 at 1:50 PM Yu Ding wrote: > > > > > > From what I understand, SGAxe is still utilizing TSX to leak data from > > > LFB. > > > It's not a problem of SGX, but a problem of TSX. TSX breaks the security > > > guarantees provided by SGX, or VMX. > > > > > > The TSX problem is not limited to attacking SGX, but also stealing memory > > > from Dom0 in Xen, or memory from the kernel of Host OS. To solve this > > > problem, TSX needs to be completely removed/disabled. It's a long-existing > > > problem. Intel tried to remove TSX from a couple of commercial SKUs but > > > haven't done it completely. > > > > > > Best, > > > Yu > > > > > > On Wed, Jun 10, 2020 at 7:43 AM Matt Sicker wrote: > > > > > > > https://cacheoutattack.com/ > > > > > > > > With all these practical attacks in place for Intel (and AMD to a > > > > different extent), what do you think the future of SGX and its > > > > competitors will look like? Are there plans on supporting other > > > > hardware enclaves that may be more secure (if they exist)? > > > > > > > > -- > > > > Matt Sicker > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > For additional commands, e-mail: dev-h...@teaclave.apache.org > -- Matt Sicker - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Implications of SGAxe?
https://cacheoutattack.com/ With all these practical attacks in place for Intel (and AMD to a different extent), what do you think the future of SGX and its competitors will look like? Are there plans on supporting other hardware enclaves that may be more secure (if they exist)? -- Matt Sicker - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: [apache/incubator-teaclave] Can I generate key for encrypting output file during computation instead of before registering output file (#328)
Using encryption, anything is possible! Using a single symmetric key, you can feed that into a cipher to form a random number generator. Then you can use keys derived from the key stream. On a more serious note, key management is definitely important. What happened? On Tue, Jun 2, 2020 at 02:09 czzmmc wrote: > Hi, here is problem that is a little bit hard for me. I see u guys kicked > kms service and tdfs service away from the whole system. And if u want to > compute something using teaclave, u have to generate a key for output file > before the computation happens. But when I use teaclave to solve my > preblem, it is usually not a single computation, which means I have to use > several teaclave functions one by one like a chain. So I do not want any > one know the keys of intermediate files but teaclave itself. And after the > last computation finishes, I can get key from teaclave, just like tdfs kms > style. It is possible that I can do that? > > -- > You are receiving this because you are subscribed to this thread. > Reply to this email directly or view it on GitHub: > https://github.com/apache/incubator-teaclave/issues/328 -- Matt Sicker
Re: Teaclave Website
m...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > > > > Hi Mingshen, > > > > > > > > > > > > > > > > > > Sure! Feel free to ask if you have any questions. > > > > > > > > > > > > > > > > > > Kind Regards, > > > > > > > > > Furkan KAMACI > > > > > > > > > > > > > > > > > > On Thu, May 14, 2020 at 1:04 AM Mingshen Sun < > > ms...@apache.org> > > > > > wrote: > > > > > > > > > > > > > > > > > > > Thanks for asking, Furkan. > > > > > > > > > > > > > > > > > > > > I did some research on how to deploy a website under the > > Apache > > > > > > > > > > infrastructure. There are several options > > > > > > > > > > (https://infra.apache.org/project-site.html). Since we are > > > > > mainly > > > > > > > > > > working on GitHub, I think the GitHub pages fit our needs. > > We > > > > > can use > > > > > > > > > > .asf.yml to configure the deployment > > > > > > > > > > ( > > > > > > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories > > > > > > > > > > ). > > > > > > > > > > > > > > > > > > > > Let me try to start with a simple one with essential > > information > > > > > and > > > > > > > > > > later polishing details. > > > > > > > > > > > > > > > > > > > > On Wed, May 13, 2020 at 9:55 AM Furkan KAMACI < > > > > > > > furkankam...@gmail.com> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > Hi All, > > > > > > > > > > > > > > > > > > > > > > As far as I know, there is not a website created for > > Teaclave > > > > > yet. > > > > > > > Is > > > > > > > > > > there > > > > > > > > > > > any progress for it? > > > > > > > > > > > > > > > > > > > > > > Kind Regards, > > > > > > > > > > > Furkan KAMACI > > > > > > > > > > > > > > > > > > > > > > > > > - > > > > > > > > > > To unsubscribe, e-mail: > > dev-unsubscr...@teaclave.apache.org > > > > > > > > > > For additional commands, e-mail: > > dev-h...@teaclave.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > - > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > > > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > > > > > > > > > > > > > > > > > > - > > > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > -- Matt Sicker - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: Podling Teaclave Report Reminder - April 2020
towards graduation. > > * Any issues that the Incubator PMC or ASF Board might wish/need to be > > aware of > > * How has the community developed since the last report > > * How has the project developed since the last report. > > * How does the podling rate their own maturity. > > > > This should be appended to the Incubator Wiki page at: > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/April2020 > > > > Note: This is manually populated. You may need to wait a little before > > this page is created from a template. > > > > Note: The format of the report has changed to use markdown. > > > > Mentors > > --- > > > > Mentors should review reports for their project(s) and sign them off on > > the Incubator wiki page. Signing off reports shows that you are > > following the project - projects that are not signed may raise alarms > > for the Incubator PMC. > > > > Incubator PMC > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > - > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > For additional commands, e-mail: dev-h...@teaclave.apache.org > > -- Matt Sicker
Re: OP-TEE TrustZone
Currently, only two repos have been donated so far: https://github.com/apache?q=teaclave We're still early in incubation, so after we have a release published, that could be a good time to import any other repos, though I'm not sure which ones are planned to be donated. On Tue, 10 Mar 2020 at 19:37, Vijay Chakilam wrote: > > Hi, > > I am trying to find resources to help understand how to build trusted > applications for OP-TEE using Rust. I came across the repository > https://github.com/mesalock-linux/rust-optee-trustzone-sdk. And then, I > discovered MesaTEE, which is now the Teaclave project (please correct me if > I am wrong). It is great to see an apache project being incubated to > provide an open source universal secure computing platform. However, I am a > bit lost under the teaclave project that it's a bit unclear if teaclave > includes the Rust SDK for OP-TEE TrustZone? Is the Rust SDK moved to > Teaclave or is it now a separate project (if yes, is it still being > actively worked on?)? > > Thanks, > Vijay -- Matt Sicker - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Intro guide for Rust development
Hey all, I'm at a Hackathon this weekend at a nearby university, and one of the groups there are mentors from the Rust project. From them, there are these neat slides introducing Rust which could potentially be useful for anyone interested in getting started with Rust. https://intro.rustbridge.com/en/intro/#1 -- Matt Sicker - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: Mailing list setup issues?
I think it's finally working! I haven't seen any new moderation emails in a while. On Thu, 23 Jan 2020 at 09:58, Matt Sicker wrote: > > Also, if you're not already a moderator for the lists, please > volunteer to do so: https://issues.apache.org/jira/browse/INFRA-19758 > > On Thu, 23 Jan 2020 at 09:52, Matt Sicker wrote: > > > > On Wed, 15 Jan 2020 at 12:49, Mingshen Sun wrote: > > > > > > The original GitBox notifications go to the notification@teaclave for > > > archive: > > > http://mail-archives.apache.org/mod_mbox/teaclave-notifications/202001.mbox/browser. > > > > This makes sense. > > > > > Right now, we are trying to setup GitHub notifications forwarding to > > > dev@teaclave. > > > > I already see all those messages going to notifications@ and commits@ > > where applicable. This should not be duplicated on dev@. Development > > discussions should happen on the mailing list which can easily refer > > to a URL to the corresponding issue or pull request (and those > > comments are mirrored to notifications@). I'd suggest taking a look at > > some other Apache dev@ lists to see how mailing list traffic is > > separated into categories like this to make things easier for users > > (we on the PPMC, of course, are subscribed to all the lists, so it > > might not be as obvious how this can be useful). > > > > Unless I'm missing something, I think we can disable this dev@ > > subscription for now. > > > > > > -- > > Matt Sicker > > > > -- > Matt Sicker -- Matt Sicker - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: Mailing list setup issues?
Also, if you're not already a moderator for the lists, please volunteer to do so: https://issues.apache.org/jira/browse/INFRA-19758 On Thu, 23 Jan 2020 at 09:52, Matt Sicker wrote: > > On Wed, 15 Jan 2020 at 12:49, Mingshen Sun wrote: > > > > The original GitBox notifications go to the notification@teaclave for > > archive: > > http://mail-archives.apache.org/mod_mbox/teaclave-notifications/202001.mbox/browser. > > This makes sense. > > > Right now, we are trying to setup GitHub notifications forwarding to > > dev@teaclave. > > I already see all those messages going to notifications@ and commits@ > where applicable. This should not be duplicated on dev@. Development > discussions should happen on the mailing list which can easily refer > to a URL to the corresponding issue or pull request (and those > comments are mirrored to notifications@). I'd suggest taking a look at > some other Apache dev@ lists to see how mailing list traffic is > separated into categories like this to make things easier for users > (we on the PPMC, of course, are subscribed to all the lists, so it > might not be as obvious how this can be useful). > > Unless I'm missing something, I think we can disable this dev@ > subscription for now. > > > -- > Matt Sicker -- Matt Sicker - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: Mailing list setup issues?
On Wed, 15 Jan 2020 at 12:49, Mingshen Sun wrote: > > The original GitBox notifications go to the notification@teaclave for > archive: > http://mail-archives.apache.org/mod_mbox/teaclave-notifications/202001.mbox/browser. This makes sense. > Right now, we are trying to setup GitHub notifications forwarding to > dev@teaclave. I already see all those messages going to notifications@ and commits@ where applicable. This should not be duplicated on dev@. Development discussions should happen on the mailing list which can easily refer to a URL to the corresponding issue or pull request (and those comments are mirrored to notifications@). I'd suggest taking a look at some other Apache dev@ lists to see how mailing list traffic is separated into categories like this to make things easier for users (we on the PPMC, of course, are subscribed to all the lists, so it might not be as obvious how this can be useful). Unless I'm missing something, I think we can disable this dev@ subscription for now. -- Matt Sicker - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: Mailing list setup issues?
Damn, it still didn't work. I wonder if it's because they generate unique reply-to addresses to bridge email to comments? For future reference, the "admin" page for this is here: https://whimsy.apache.org/committers/moderationhelper This is mostly just a web UI to generate the appropriate email addresses to send mail to in order to execute mailing list commands, though it also offers some sort of mail client to send the command for you. I tried adding notificati...@github.com by sending a message to dev-allow-subscribe-notifications=github@teaclave.apache.org though that doesn't seem to have done the trick. On Mon, 20 Jan 2020 at 13:13, Mingshen Sun wrote: > > I just closed an issue on GitHub. There should be a notification sent > to the dev list from notificati...@github.com, but it didn't appear. > > > > On Mon, Jan 20, 2020 at 9:50 AM Matt Sicker wrote: > > > > I found some feature of the mailing list to subscribe the > > notifications github email address. Let's see if the next GitHub > > notification makes it through. > > > > On Thu, 16 Jan 2020 at 23:51, Mingshen Sun wrote: > > > > > > Ok, let me check with the INFRA team to see what's wrong. > > > > > > On Thu, Jan 16, 2020 at 9:49 PM Matt Sicker wrote: > > > > > > > > Still getting moderation mail for notifications. I wonder what’s wrong > > > > with > > > > the config? Do we need to add the email to a whitelist somewhere? I’ve > > > > never tried setting up GH notifications like this before. > > > > > > > > On Thu, Jan 16, 2020 at 20:08 Matt Sicker wrote: > > > > > > > > > I’ll watch for more moderation messages as new GitHub notifications > > > > > come > > > > > through. > > > > > > > > > > On Thu, Jan 16, 2020 at 20:08 Mingshen Sun wrote: > > > > > > > > > >> INFRA said that emails from `notificati...@github.com` are > > > > >> whitelisted > > > > >> 11 hours ago [1]. Do our moderators still need to approve the email > > > > >> from GitHub? If not, I'll ask INFRA for help. > > > > >> > > > > >> [1] > > > > >> https://issues.apache.org/jira/browse/INFRA-19621?focusedCommentId=17017001=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17017001 > > > > >> > > > > >> On Thu, Jan 16, 2020 at 6:04 PM Matt Sicker wrote: > > > > >> > > > > > >> > That works well enough I think. Thanks for the explanation! > > > > >> > > > > > >> > On Thu, Jan 16, 2020 at 19:16 Mingshen Sun > > > > >> > wrote: > > > > >> > > > > > >> > > I just tested whether I can reply the GitHub notification with > > > > >> > > email. > > > > >> > > Yes, you can do that, but the name of the reply displayed on > > > > >> > > GitHub is > > > > >> > > from our archiver (i.e., teaclave.archiver@gmail). > > > > >> > > > > > > >> > > That is, when you reply notification email from GitHub on our dev > > > > >> > > list, the reply will be synced on behalf of the archiver. > > > > >> > > > > > > >> > > > > > > >> > > On Thu, Jan 16, 2020 at 5:03 PM Mingshen Sun > > > > >> wrote: > > > > >> > > > > > > > >> > > > Sorry for the late reply. > > > > >> > > > > > > > >> > > > Let me explain this again. > > > > >> > > > > > > > >> > > > Originally, GitBox will send notifications to dev@teaclave with > > > > >> > > > issues/PRs/comments notifications, "making it seems that there > > > > >> > > > is a > > > > >> > > > lot of spam where the actual discussions get lost on the > > > > >> > > > archives." > > > > >> > > > [1] > > > > >> > > > > > > > >> > > > Then I propose this solution: > > > > >> > > > > > > > >> > > > - dev@: general dev related discussion (by human) > > > > >> > > > - commits@: auto-generated emails of commits for archive > > > > >&g
Re: Mailing list setup issues?
I found some feature of the mailing list to subscribe the notifications github email address. Let's see if the next GitHub notification makes it through. On Thu, 16 Jan 2020 at 23:51, Mingshen Sun wrote: > > Ok, let me check with the INFRA team to see what's wrong. > > On Thu, Jan 16, 2020 at 9:49 PM Matt Sicker wrote: > > > > Still getting moderation mail for notifications. I wonder what’s wrong with > > the config? Do we need to add the email to a whitelist somewhere? I’ve > > never tried setting up GH notifications like this before. > > > > On Thu, Jan 16, 2020 at 20:08 Matt Sicker wrote: > > > > > I’ll watch for more moderation messages as new GitHub notifications come > > > through. > > > > > > On Thu, Jan 16, 2020 at 20:08 Mingshen Sun wrote: > > > > > >> INFRA said that emails from `notificati...@github.com` are whitelisted > > >> 11 hours ago [1]. Do our moderators still need to approve the email > > >> from GitHub? If not, I'll ask INFRA for help. > > >> > > >> [1] > > >> https://issues.apache.org/jira/browse/INFRA-19621?focusedCommentId=17017001=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17017001 > > >> > > >> On Thu, Jan 16, 2020 at 6:04 PM Matt Sicker wrote: > > >> > > > >> > That works well enough I think. Thanks for the explanation! > > >> > > > >> > On Thu, Jan 16, 2020 at 19:16 Mingshen Sun wrote: > > >> > > > >> > > I just tested whether I can reply the GitHub notification with email. > > >> > > Yes, you can do that, but the name of the reply displayed on GitHub > > >> > > is > > >> > > from our archiver (i.e., teaclave.archiver@gmail). > > >> > > > > >> > > That is, when you reply notification email from GitHub on our dev > > >> > > list, the reply will be synced on behalf of the archiver. > > >> > > > > >> > > > > >> > > On Thu, Jan 16, 2020 at 5:03 PM Mingshen Sun > > >> wrote: > > >> > > > > > >> > > > Sorry for the late reply. > > >> > > > > > >> > > > Let me explain this again. > > >> > > > > > >> > > > Originally, GitBox will send notifications to dev@teaclave with > > >> > > > issues/PRs/comments notifications, "making it seems that there is a > > >> > > > lot of spam where the actual discussions get lost on the archives." > > >> > > > [1] > > >> > > > > > >> > > > Then I propose this solution: > > >> > > > > > >> > > > - dev@: general dev related discussion (by human) > > >> > > > - commits@: auto-generated emails of commits for archive > > >> > > > - notifications@: auto-generated emails of GitBox syncs and other > > >> > > > third-party notifications for archive > > >> > > > > > >> > > > However, since we are using GitHub as our main development > > >> > > > platform, > > >> > > > issues, feature requests and RFC will normally be posted on the > > >> > > > "GitHub Issues". People subscribed to the dev list will not see > > >> these > > >> > > > updates on the GitHub. > > >> > > > > > >> > > > Then, I think TVM's dev list [2] may be a good solution - > > >> > > > forwarding > > >> > > > notifications of GitHub to dev list. This will keep the original > > >> > > > discussion in thread, and not look like spam. > > >> > > > > > >> > > > I asked the INFRA team to redirect all GitBox notifications to > > >> > > > notification@teaclave and only accept GitHub's notification in dev > > >> > > > list. That's what you mentioned earlier on double notifications. > > >> > > > > > >> > > > I'm not sure if "responding to the dev@ thread does indeed mirror > > >> your > > >> > > > comment back to GitHub". I'll try myself. > > >> > > > > > >> > > > Overall, here we want to solve is make the dev list looks clean and > > >> > > useful. > > >> > > >
Re: Mailing list setup issues?
Still getting moderation mail for notifications. I wonder what’s wrong with the config? Do we need to add the email to a whitelist somewhere? I’ve never tried setting up GH notifications like this before. On Thu, Jan 16, 2020 at 20:08 Matt Sicker wrote: > I’ll watch for more moderation messages as new GitHub notifications come > through. > > On Thu, Jan 16, 2020 at 20:08 Mingshen Sun wrote: > >> INFRA said that emails from `notificati...@github.com` are whitelisted >> 11 hours ago [1]. Do our moderators still need to approve the email >> from GitHub? If not, I'll ask INFRA for help. >> >> [1] >> https://issues.apache.org/jira/browse/INFRA-19621?focusedCommentId=17017001=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17017001 >> >> On Thu, Jan 16, 2020 at 6:04 PM Matt Sicker wrote: >> > >> > That works well enough I think. Thanks for the explanation! >> > >> > On Thu, Jan 16, 2020 at 19:16 Mingshen Sun wrote: >> > >> > > I just tested whether I can reply the GitHub notification with email. >> > > Yes, you can do that, but the name of the reply displayed on GitHub is >> > > from our archiver (i.e., teaclave.archiver@gmail). >> > > >> > > That is, when you reply notification email from GitHub on our dev >> > > list, the reply will be synced on behalf of the archiver. >> > > >> > > >> > > On Thu, Jan 16, 2020 at 5:03 PM Mingshen Sun >> wrote: >> > > > >> > > > Sorry for the late reply. >> > > > >> > > > Let me explain this again. >> > > > >> > > > Originally, GitBox will send notifications to dev@teaclave with >> > > > issues/PRs/comments notifications, "making it seems that there is a >> > > > lot of spam where the actual discussions get lost on the archives." >> > > > [1] >> > > > >> > > > Then I propose this solution: >> > > > >> > > > - dev@: general dev related discussion (by human) >> > > > - commits@: auto-generated emails of commits for archive >> > > > - notifications@: auto-generated emails of GitBox syncs and other >> > > > third-party notifications for archive >> > > > >> > > > However, since we are using GitHub as our main development platform, >> > > > issues, feature requests and RFC will normally be posted on the >> > > > "GitHub Issues". People subscribed to the dev list will not see >> these >> > > > updates on the GitHub. >> > > > >> > > > Then, I think TVM's dev list [2] may be a good solution - forwarding >> > > > notifications of GitHub to dev list. This will keep the original >> > > > discussion in thread, and not look like spam. >> > > > >> > > > I asked the INFRA team to redirect all GitBox notifications to >> > > > notification@teaclave and only accept GitHub's notification in dev >> > > > list. That's what you mentioned earlier on double notifications. >> > > > >> > > > I'm not sure if "responding to the dev@ thread does indeed mirror >> your >> > > > comment back to GitHub". I'll try myself. >> > > > >> > > > Overall, here we want to solve is make the dev list looks clean and >> > > useful. >> > > > >> > > > [1] >> > > >> http://mail-archives.apache.org/mod_mbox/teaclave-dev/201912.mbox/browser >> > > > [2] https://lists.apache.org/list.html?d...@tvm.apache.org >> > > > >> > > > >> > > > On Thu, Jan 16, 2020 at 9:05 AM Matt Sicker >> wrote: >> > > > > >> > > > > And I'm wondering what the purpose of mirroring notifications of >> any >> > > > > kind to dev@ would do unless responding to the dev@ thread does >> indeed >> > > > > mirror your comment back to GitHub. >> > > > > >> > > > > On Wed, 15 Jan 2020 at 13:09, Matt Sicker >> wrote: >> > > > > > >> > > > > > That would just lead to double notifications still, wouldn't it? >> > > > > > >> > > > > > On Wed, 15 Jan 2020 at 12:49, Mingshen Sun >> wrote: >> > > > > > > >> > > > > > > The original GitBox notifications go to the >> notification@
Re: Mailing list setup issues?
I’ll watch for more moderation messages as new GitHub notifications come through. On Thu, Jan 16, 2020 at 20:08 Mingshen Sun wrote: > INFRA said that emails from `notificati...@github.com` are whitelisted > 11 hours ago [1]. Do our moderators still need to approve the email > from GitHub? If not, I'll ask INFRA for help. > > [1] > https://issues.apache.org/jira/browse/INFRA-19621?focusedCommentId=17017001=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17017001 > > On Thu, Jan 16, 2020 at 6:04 PM Matt Sicker wrote: > > > > That works well enough I think. Thanks for the explanation! > > > > On Thu, Jan 16, 2020 at 19:16 Mingshen Sun wrote: > > > > > I just tested whether I can reply the GitHub notification with email. > > > Yes, you can do that, but the name of the reply displayed on GitHub is > > > from our archiver (i.e., teaclave.archiver@gmail). > > > > > > That is, when you reply notification email from GitHub on our dev > > > list, the reply will be synced on behalf of the archiver. > > > > > > > > > On Thu, Jan 16, 2020 at 5:03 PM Mingshen Sun wrote: > > > > > > > > Sorry for the late reply. > > > > > > > > Let me explain this again. > > > > > > > > Originally, GitBox will send notifications to dev@teaclave with > > > > issues/PRs/comments notifications, "making it seems that there is a > > > > lot of spam where the actual discussions get lost on the archives." > > > > [1] > > > > > > > > Then I propose this solution: > > > > > > > > - dev@: general dev related discussion (by human) > > > > - commits@: auto-generated emails of commits for archive > > > > - notifications@: auto-generated emails of GitBox syncs and other > > > > third-party notifications for archive > > > > > > > > However, since we are using GitHub as our main development platform, > > > > issues, feature requests and RFC will normally be posted on the > > > > "GitHub Issues". People subscribed to the dev list will not see these > > > > updates on the GitHub. > > > > > > > > Then, I think TVM's dev list [2] may be a good solution - forwarding > > > > notifications of GitHub to dev list. This will keep the original > > > > discussion in thread, and not look like spam. > > > > > > > > I asked the INFRA team to redirect all GitBox notifications to > > > > notification@teaclave and only accept GitHub's notification in dev > > > > list. That's what you mentioned earlier on double notifications. > > > > > > > > I'm not sure if "responding to the dev@ thread does indeed mirror > your > > > > comment back to GitHub". I'll try myself. > > > > > > > > Overall, here we want to solve is make the dev list looks clean and > > > useful. > > > > > > > > [1] > > > > http://mail-archives.apache.org/mod_mbox/teaclave-dev/201912.mbox/browser > > > > [2] https://lists.apache.org/list.html?d...@tvm.apache.org > > > > > > > > > > > > On Thu, Jan 16, 2020 at 9:05 AM Matt Sicker > wrote: > > > > > > > > > > And I'm wondering what the purpose of mirroring notifications of > any > > > > > kind to dev@ would do unless responding to the dev@ thread does > indeed > > > > > mirror your comment back to GitHub. > > > > > > > > > > On Wed, 15 Jan 2020 at 13:09, Matt Sicker > wrote: > > > > > > > > > > > > That would just lead to double notifications still, wouldn't it? > > > > > > > > > > > > On Wed, 15 Jan 2020 at 12:49, Mingshen Sun > wrote: > > > > > > > > > > > > > > The original GitBox notifications go to the > notification@teaclave > > > for > > > > > > > archive: > > > > http://mail-archives.apache.org/mod_mbox/teaclave-notifications/202001.mbox/browser > > > . > > > > > > > > > > > > > > Right now, we are trying to setup GitHub notifications > forwarding > > > to > > > > > > > dev@teaclave. The only thing left is to setup the list to > accept > > > > > > > notification from `notificati...@github.com`. I have > submitted the > > > > > > > ticket but no one ta
Re: Mailing list setup issues?
That works well enough I think. Thanks for the explanation! On Thu, Jan 16, 2020 at 19:16 Mingshen Sun wrote: > I just tested whether I can reply the GitHub notification with email. > Yes, you can do that, but the name of the reply displayed on GitHub is > from our archiver (i.e., teaclave.archiver@gmail). > > That is, when you reply notification email from GitHub on our dev > list, the reply will be synced on behalf of the archiver. > > > On Thu, Jan 16, 2020 at 5:03 PM Mingshen Sun wrote: > > > > Sorry for the late reply. > > > > Let me explain this again. > > > > Originally, GitBox will send notifications to dev@teaclave with > > issues/PRs/comments notifications, "making it seems that there is a > > lot of spam where the actual discussions get lost on the archives." > > [1] > > > > Then I propose this solution: > > > > - dev@: general dev related discussion (by human) > > - commits@: auto-generated emails of commits for archive > > - notifications@: auto-generated emails of GitBox syncs and other > > third-party notifications for archive > > > > However, since we are using GitHub as our main development platform, > > issues, feature requests and RFC will normally be posted on the > > "GitHub Issues". People subscribed to the dev list will not see these > > updates on the GitHub. > > > > Then, I think TVM's dev list [2] may be a good solution - forwarding > > notifications of GitHub to dev list. This will keep the original > > discussion in thread, and not look like spam. > > > > I asked the INFRA team to redirect all GitBox notifications to > > notification@teaclave and only accept GitHub's notification in dev > > list. That's what you mentioned earlier on double notifications. > > > > I'm not sure if "responding to the dev@ thread does indeed mirror your > > comment back to GitHub". I'll try myself. > > > > Overall, here we want to solve is make the dev list looks clean and > useful. > > > > [1] > http://mail-archives.apache.org/mod_mbox/teaclave-dev/201912.mbox/browser > > [2] https://lists.apache.org/list.html?d...@tvm.apache.org > > > > > > On Thu, Jan 16, 2020 at 9:05 AM Matt Sicker wrote: > > > > > > And I'm wondering what the purpose of mirroring notifications of any > > > kind to dev@ would do unless responding to the dev@ thread does indeed > > > mirror your comment back to GitHub. > > > > > > On Wed, 15 Jan 2020 at 13:09, Matt Sicker wrote: > > > > > > > > That would just lead to double notifications still, wouldn't it? > > > > > > > > On Wed, 15 Jan 2020 at 12:49, Mingshen Sun wrote: > > > > > > > > > > The original GitBox notifications go to the notification@teaclave > for > > > > > archive: > http://mail-archives.apache.org/mod_mbox/teaclave-notifications/202001.mbox/browser > . > > > > > > > > > > Right now, we are trying to setup GitHub notifications forwarding > to > > > > > dev@teaclave. The only thing left is to setup the list to accept > > > > > notification from `notificati...@github.com`. I have submitted the > > > > > ticket but no one take action yet. Let me ping the ticket again. > > > > > Thanks. > > > > > > > > > > > > > > > On Wed, Jan 15, 2020 at 8:09 AM Matt Sicker > wrote: > > > > > > > > > > > > Ok yeah, I'm definitely seeing duplicate messages. It seems like > Infra > > > > > > enabled the notifications through a different mechanism. > > > > > > > > > > > > On Wed, 15 Jan 2020 at 10:05, Matt Sicker > wrote: > > > > > > > > > > > > > > I'm also noticing that some of the GitHub notifications being > filtered > > > > > > > by the list are already being sent from another address now. > We can > > > > > > > probably remove the first notification setup now. > > > > > > > > > > > > > > On Wed, 15 Jan 2020 at 10:02, Matt Sicker > wrote: > > > > > > > > > > > > > > > > Still getting flooded with moderation messages for filtered > messages. > > > > > > > > > > > > > > > > On Sun, 12 Jan 2020 at 18:53, Mingshen Sun > wrote: > > > > > > > > > > > > > > > > >
Re: Mailing list setup issues?
And I'm wondering what the purpose of mirroring notifications of any kind to dev@ would do unless responding to the dev@ thread does indeed mirror your comment back to GitHub. On Wed, 15 Jan 2020 at 13:09, Matt Sicker wrote: > > That would just lead to double notifications still, wouldn't it? > > On Wed, 15 Jan 2020 at 12:49, Mingshen Sun wrote: > > > > The original GitBox notifications go to the notification@teaclave for > > archive: > > http://mail-archives.apache.org/mod_mbox/teaclave-notifications/202001.mbox/browser. > > > > Right now, we are trying to setup GitHub notifications forwarding to > > dev@teaclave. The only thing left is to setup the list to accept > > notification from `notificati...@github.com`. I have submitted the > > ticket but no one take action yet. Let me ping the ticket again. > > Thanks. > > > > > > On Wed, Jan 15, 2020 at 8:09 AM Matt Sicker wrote: > > > > > > Ok yeah, I'm definitely seeing duplicate messages. It seems like Infra > > > enabled the notifications through a different mechanism. > > > > > > On Wed, 15 Jan 2020 at 10:05, Matt Sicker wrote: > > > > > > > > I'm also noticing that some of the GitHub notifications being filtered > > > > by the list are already being sent from another address now. We can > > > > probably remove the first notification setup now. > > > > > > > > On Wed, 15 Jan 2020 at 10:02, Matt Sicker wrote: > > > > > > > > > > Still getting flooded with moderation messages for filtered messages. > > > > > > > > > > On Sun, 12 Jan 2020 at 18:53, Mingshen Sun wrote: > > > > > > > > > > > > Just give you guys an update on this. I have submitted the ticket > > > > > > but > > > > > > still haven't been setup up. Hopefully, this will resolve this week. > > > > > > Thanks. > > > > > > > > > > > > - https://issues.apache.org/jira/projects/INFRA/issues/INFRA-19621 > > > > > > > > > > > > On Wed, Jan 8, 2020 at 11:43 AM Mingshen Sun > > > > > > wrote: > > > > > > > > > > > > > > Sure, I have submitted ticket to the INFRA team. Will update this > > > > > > > email when it's done. Thanks. > > > > > > > > > > > > > > On Wed, Jan 8, 2020 at 11:04 AM Matt Sicker > > > > > > > wrote: > > > > > > > > > > > > > > > > I'm not really sure how that works, so I'd go the infra route > > > > > > > > for now. > > > > > > > > They might already have a service we can use for this. > > > > > > > > > > > > > > > > On Wed, 8 Jan 2020 at 12:12, Mingshen Sun > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > Thanks. I have notice this issue. One extra step is to put ` > > > > > > > > > notificati...@github.com` into the dev list's whitelist. > > > > > > > > > Should I contact > > > > > > > > > INFRA team or our moderators can get it done? > > > > > > > > > > > > > > > > > > On Wed, Jan 8, 2020 at 10:06 AM Matt Sicker > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Seems that some sort of archival service isn't actually > > > > > > > > > > subscribed to > > > > > > > > > > the mailing list which is causing every notification to be > > > > > > > > > > blocked. An > > > > > > > > > > INFRA ticket could be helpful in configuring notification > > > > > > > > > > lists here. > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > Matt Sicker > > > > > > > > > > > > > > > > > > > > - > > > > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > > > > > > > > For additional commands, e-mail: > > > > > > > > > > dev-h...@teaclave.apache.org > > > >
Re: Mailing list setup issues?
That would just lead to double notifications still, wouldn't it? On Wed, 15 Jan 2020 at 12:49, Mingshen Sun wrote: > > The original GitBox notifications go to the notification@teaclave for > archive: > http://mail-archives.apache.org/mod_mbox/teaclave-notifications/202001.mbox/browser. > > Right now, we are trying to setup GitHub notifications forwarding to > dev@teaclave. The only thing left is to setup the list to accept > notification from `notificati...@github.com`. I have submitted the > ticket but no one take action yet. Let me ping the ticket again. > Thanks. > > > On Wed, Jan 15, 2020 at 8:09 AM Matt Sicker wrote: > > > > Ok yeah, I'm definitely seeing duplicate messages. It seems like Infra > > enabled the notifications through a different mechanism. > > > > On Wed, 15 Jan 2020 at 10:05, Matt Sicker wrote: > > > > > > I'm also noticing that some of the GitHub notifications being filtered > > > by the list are already being sent from another address now. We can > > > probably remove the first notification setup now. > > > > > > On Wed, 15 Jan 2020 at 10:02, Matt Sicker wrote: > > > > > > > > Still getting flooded with moderation messages for filtered messages. > > > > > > > > On Sun, 12 Jan 2020 at 18:53, Mingshen Sun wrote: > > > > > > > > > > Just give you guys an update on this. I have submitted the ticket but > > > > > still haven't been setup up. Hopefully, this will resolve this week. > > > > > Thanks. > > > > > > > > > > - https://issues.apache.org/jira/projects/INFRA/issues/INFRA-19621 > > > > > > > > > > On Wed, Jan 8, 2020 at 11:43 AM Mingshen Sun wrote: > > > > > > > > > > > > Sure, I have submitted ticket to the INFRA team. Will update this > > > > > > email when it's done. Thanks. > > > > > > > > > > > > On Wed, Jan 8, 2020 at 11:04 AM Matt Sicker > > > > > > wrote: > > > > > > > > > > > > > > I'm not really sure how that works, so I'd go the infra route for > > > > > > > now. > > > > > > > They might already have a service we can use for this. > > > > > > > > > > > > > > On Wed, 8 Jan 2020 at 12:12, Mingshen Sun > > > > > > > wrote: > > > > > > > > > > > > > > > > Thanks. I have notice this issue. One extra step is to put ` > > > > > > > > notificati...@github.com` into the dev list's whitelist. Should > > > > > > > > I contact > > > > > > > > INFRA team or our moderators can get it done? > > > > > > > > > > > > > > > > On Wed, Jan 8, 2020 at 10:06 AM Matt Sicker > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Seems that some sort of archival service isn't actually > > > > > > > > > subscribed to > > > > > > > > > the mailing list which is causing every notification to be > > > > > > > > > blocked. An > > > > > > > > > INFRA ticket could be helpful in configuring notification > > > > > > > > > lists here. > > > > > > > > > > > > > > > > > > -- > > > > > > > > > Matt Sicker > > > > > > > > > > > > > > > > > > - > > > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > > > > > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Matt Sicker > > > > > > > > > > > > > > - > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > > > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > > > > - > > > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > > > > > > > > > > > -- > > > > Matt Sicker > > > > > > > > > > > > -- > > > Matt Sicker > > > > > > > > -- > > Matt Sicker > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > - > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > For additional commands, e-mail: dev-h...@teaclave.apache.org > -- Matt Sicker - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: Mailing list setup issues?
Ok yeah, I'm definitely seeing duplicate messages. It seems like Infra enabled the notifications through a different mechanism. On Wed, 15 Jan 2020 at 10:05, Matt Sicker wrote: > > I'm also noticing that some of the GitHub notifications being filtered > by the list are already being sent from another address now. We can > probably remove the first notification setup now. > > On Wed, 15 Jan 2020 at 10:02, Matt Sicker wrote: > > > > Still getting flooded with moderation messages for filtered messages. > > > > On Sun, 12 Jan 2020 at 18:53, Mingshen Sun wrote: > > > > > > Just give you guys an update on this. I have submitted the ticket but > > > still haven't been setup up. Hopefully, this will resolve this week. > > > Thanks. > > > > > > - https://issues.apache.org/jira/projects/INFRA/issues/INFRA-19621 > > > > > > On Wed, Jan 8, 2020 at 11:43 AM Mingshen Sun wrote: > > > > > > > > Sure, I have submitted ticket to the INFRA team. Will update this > > > > email when it's done. Thanks. > > > > > > > > On Wed, Jan 8, 2020 at 11:04 AM Matt Sicker wrote: > > > > > > > > > > I'm not really sure how that works, so I'd go the infra route for now. > > > > > They might already have a service we can use for this. > > > > > > > > > > On Wed, 8 Jan 2020 at 12:12, Mingshen Sun wrote: > > > > > > > > > > > > Thanks. I have notice this issue. One extra step is to put ` > > > > > > notificati...@github.com` into the dev list's whitelist. Should I > > > > > > contact > > > > > > INFRA team or our moderators can get it done? > > > > > > > > > > > > On Wed, Jan 8, 2020 at 10:06 AM Matt Sicker > > > > > > wrote: > > > > > > > > > > > > > Seems that some sort of archival service isn't actually > > > > > > > subscribed to > > > > > > > the mailing list which is causing every notification to be > > > > > > > blocked. An > > > > > > > INFRA ticket could be helpful in configuring notification lists > > > > > > > here. > > > > > > > > > > > > > > -- > > > > > > > Matt Sicker > > > > > > > > > > > > > > - > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > > > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Matt Sicker > > > > > > > > > > - > > > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > > > -- > > Matt Sicker > > > > -- > Matt Sicker -- Matt Sicker - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: Mailing list setup issues?
I'm also noticing that some of the GitHub notifications being filtered by the list are already being sent from another address now. We can probably remove the first notification setup now. On Wed, 15 Jan 2020 at 10:02, Matt Sicker wrote: > > Still getting flooded with moderation messages for filtered messages. > > On Sun, 12 Jan 2020 at 18:53, Mingshen Sun wrote: > > > > Just give you guys an update on this. I have submitted the ticket but > > still haven't been setup up. Hopefully, this will resolve this week. > > Thanks. > > > > - https://issues.apache.org/jira/projects/INFRA/issues/INFRA-19621 > > > > On Wed, Jan 8, 2020 at 11:43 AM Mingshen Sun wrote: > > > > > > Sure, I have submitted ticket to the INFRA team. Will update this > > > email when it's done. Thanks. > > > > > > On Wed, Jan 8, 2020 at 11:04 AM Matt Sicker wrote: > > > > > > > > I'm not really sure how that works, so I'd go the infra route for now. > > > > They might already have a service we can use for this. > > > > > > > > On Wed, 8 Jan 2020 at 12:12, Mingshen Sun wrote: > > > > > > > > > > Thanks. I have notice this issue. One extra step is to put ` > > > > > notificati...@github.com` into the dev list's whitelist. Should I > > > > > contact > > > > > INFRA team or our moderators can get it done? > > > > > > > > > > On Wed, Jan 8, 2020 at 10:06 AM Matt Sicker wrote: > > > > > > > > > > > Seems that some sort of archival service isn't actually subscribed > > > > > > to > > > > > > the mailing list which is causing every notification to be blocked. > > > > > > An > > > > > > INFRA ticket could be helpful in configuring notification lists > > > > > > here. > > > > > > > > > > > > -- > > > > > > Matt Sicker > > > > > > > > > > > > - > > > > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > > > > > > > > > > > > > > > > -- > > > > Matt Sicker > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > -- > Matt Sicker -- Matt Sicker - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: Mailing list setup issues?
Still getting flooded with moderation messages for filtered messages. On Sun, 12 Jan 2020 at 18:53, Mingshen Sun wrote: > > Just give you guys an update on this. I have submitted the ticket but > still haven't been setup up. Hopefully, this will resolve this week. > Thanks. > > - https://issues.apache.org/jira/projects/INFRA/issues/INFRA-19621 > > On Wed, Jan 8, 2020 at 11:43 AM Mingshen Sun wrote: > > > > Sure, I have submitted ticket to the INFRA team. Will update this > > email when it's done. Thanks. > > > > On Wed, Jan 8, 2020 at 11:04 AM Matt Sicker wrote: > > > > > > I'm not really sure how that works, so I'd go the infra route for now. > > > They might already have a service we can use for this. > > > > > > On Wed, 8 Jan 2020 at 12:12, Mingshen Sun wrote: > > > > > > > > Thanks. I have notice this issue. One extra step is to put ` > > > > notificati...@github.com` into the dev list's whitelist. Should I > > > > contact > > > > INFRA team or our moderators can get it done? > > > > > > > > On Wed, Jan 8, 2020 at 10:06 AM Matt Sicker wrote: > > > > > > > > > Seems that some sort of archival service isn't actually subscribed to > > > > > the mailing list which is causing every notification to be blocked. An > > > > > INFRA ticket could be helpful in configuring notification lists here. > > > > > > > > > > -- > > > > > Matt Sicker > > > > > > > > > > - > > > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > > > > > > > > > > > -- > > > Matt Sicker > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > - > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > For additional commands, e-mail: dev-h...@teaclave.apache.org > -- Matt Sicker - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: Mailing list setup issues?
I'm not really sure how that works, so I'd go the infra route for now. They might already have a service we can use for this. On Wed, 8 Jan 2020 at 12:12, Mingshen Sun wrote: > > Thanks. I have notice this issue. One extra step is to put ` > notificati...@github.com` into the dev list's whitelist. Should I contact > INFRA team or our moderators can get it done? > > On Wed, Jan 8, 2020 at 10:06 AM Matt Sicker wrote: > > > Seems that some sort of archival service isn't actually subscribed to > > the mailing list which is causing every notification to be blocked. An > > INFRA ticket could be helpful in configuring notification lists here. > > > > -- > > Matt Sicker > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > -- Matt Sicker - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Mailing list setup issues?
Seems that some sort of archival service isn't actually subscribed to the mailing list which is causing every notification to be blocked. An INFRA ticket could be helpful in configuring notification lists here. -- Matt Sicker - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: Test Teaclave Archiver
Confirmed. On Tue, Jan 7, 2020 at 19:52 Teaclave Archiver wrote: > I just made a forwarding request in Gmail. There should be an email > from Gmail about setup code, can you approve this email so that I can > continue the setup. Thanks. > > On Tue, Jan 7, 2020 at 5:48 PM Teaclave Archiver > wrote: > > > > Typo fixed. Thank you so much! > > > > On Tue, Jan 7, 2020 at 5:44 PM Matt Sicker wrote: > > > > > > The From header has a typo it looks like. > > > > > > On Tue, Jan 7, 2020 at 19:29 Teachave Archiver < > teaclave.archi...@gmail.com> > > > wrote: > > > > > > > As mentioned in this thread [1], we can use a archiver to make the > dev > > > > list more readable. This email is to test the email subscription. No > > > > action needed. Thanks. > > > > > > > > [1] > > > > > https://lists.apache.org/thread.html/065a9c6b85cd73cfb0b5188a48e0815a44ed834c47e5648e09cbe4f2%40%3Cdev.teaclave.apache.org%3E > > > > > > > > ----- > > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > > -- > > > Matt Sicker > > - > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > For additional commands, e-mail: dev-h...@teaclave.apache.org > > -- Matt Sicker
Re: Test Teaclave Archiver
The From header has a typo it looks like. On Tue, Jan 7, 2020 at 19:29 Teachave Archiver wrote: > As mentioned in this thread [1], we can use a archiver to make the dev > list more readable. This email is to test the email subscription. No > action needed. Thanks. > > [1] > https://lists.apache.org/thread.html/065a9c6b85cd73cfb0b5188a48e0815a44ed834c47e5648e09cbe4f2%40%3Cdev.teaclave.apache.org%3E > > - > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > For additional commands, e-mail: dev-h...@teaclave.apache.org > > -- Matt Sicker
Re: Podling Teaclave Report Reminder - January 2020
Signed off. Thanks! On Tue, 31 Dec 2019 at 02:02, Mingshen Sun wrote: > > Added: > https://cwiki.apache.org/confluence/display/INCUBATOR/January2020#teaclave > > To mentors, please sign off if it looks good to you. Thank you! > > > On Mon, Dec 30, 2019 at 11:55 PM Mingshen Sun wrote: > > > > Thanks, Matt. > > > > Let me copy the draft to the wiki. Feel free to tell me if there are > > any missing parts. > > > > On Mon, Dec 30, 2019 at 10:34 AM Matt Sicker wrote: > > > > > > Looks good to me! The level of detail about what components were > > > refactored > > > might be too much, but I don’t think it’s a problem. > > > > > > On Mon, Dec 30, 2019 at 01:08 Mingshen Sun wrote: > > > > > > > Hi all, > > > > > > > > I drafted a report for this month. Feel free to reply if I miss > > > > something. Thanks. > > > > > > > > Mingshen > > > > > > > > > > > > ## Teaclave > > > > > > > > Teaclave is a universal secure computing platform. > > > > > > > > Teaclave has been incubating since 2019-08-20. > > > > > > > > ### Three most important unfinished issues to address before graduating: > > > > > > > > 1. Improving project structure and documentation > > > > 2. Grow the community (committers, contributors, users) > > > > 3. Publish Apache release > > > > > > > > ### Are there any issues that the IPMC or ASF Board need to be aware of? > > > > > > > > No. > > > > > > > > ### How has the community developed since the last report? > > > > > > > > - Since last report, we planned to schedule an online meetup recently. > > > > - We have also received contributions of two new contributors. > > > > - We draft a roadmap RFC for discussion. > > > > - We use GitHub issues to track bugs, features, enhancements. Issues > > > > labeled with "good first issues" is more approachable for newcomers. > > > > > > > > ### How has the project developed since the last report? > > > > > > > > - Resolve all renaming issues of INFRA (INFRA-19532) > > > > - Refactor components: `teaclave_utils`, `teaclave_config`, > > > > `teaclave_cli`, `teaclave_binder` > > > > - Rewrite README.md to clearly explain the project's highlights in > > > > security, functionality, and usability. > > > > - Start to use protobuf for RPC definition > > > > - SGX SDK starts to use Intel SGX SDK v2.7.1 > > > > > > > > ### How would you assess the podling's maturity? > > > > > > > > - [ ] Initial setup > > > > - [x] Working towards first release > > > > - [ ] Community building > > > > - [ ] Nearing graduation > > > > - [ ] Other: > > > > > > > > ### Date of last release: > > > > > > > > N/A > > > > > > > > ### When were the last committers or PPMC members elected? > > > > > > > > We haven't started new committers or PPMC members elections yet. > > > > Currently, our work focus on improving the design and documents to > > > > make the project more approachable for newcomers. > > > > > > > > ### Have your mentors been helpful and responsive? > > > > > > > > Yes. Last month, we changed name from MesaTEE to Teaclave. There are a > > > > lot of changes need to be done. The mentors and infra teams help us a > > > > lot on the transfer. > > > > > > > > ### Is the PPMC managing the podling's brand / trademarks? > > > > > > > > We don't find any 3rd parties incorrectly using the podling's name and > > > > brand. The VP, Brand has approve the project name. > > > > (PODLINGNAMESEARCH-175) > > > > > > > > > > > > On Sun, Dec 29, 2019 at 10:30 AM Mingshen Sun wrote: > > > > > > > > > > Hi Furkan, thanks for asking. I'll work on the report today. > > > > > > > > > > On Sun, Dec 29, 2019 at 10:29 AM Furkan KAMACI > > > > > > > > > wrote: > > > > > > > > > > > > Hi All, > > > > > > > > > > > > Is there anybody working on report? Let me know if you need help. > > > >
Re: Podling Teaclave Report Reminder - January 2020
s no knowledge > of > > > > the project or necessarily of its field > > > > * A list of the three most important issues to address in the move > > > > towards graduation. > > > > * Any issues that the Incubator PMC or ASF Board might wish/need > to be > > > > aware of > > > > * How has the community developed since the last report > > > > * How has the project developed since the last report. > > > > * How does the podling rate their own maturity. > > > > > > > > This should be appended to the Incubator Wiki page at: > > > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/January2020 > > > > > > > > Note: This is manually populated. You may need to wait a little > before > > > > this page is created from a template. > > > > > > > > Note: The format of the report has changed to use markdown. > > > > > > > > Mentors > > > > --- > > > > > > > > Mentors should review reports for their project(s) and sign them off > on > > > > the Incubator wiki page. Signing off reports shows that you are > > > > following the project - projects that are not signed may raise alarms > > > > for the Incubator PMC. > > > > > > > > Incubator PMC > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > For additional commands, e-mail: dev-h...@teaclave.apache.org > > -- Matt Sicker
Re: Changes subject to brand name change
Looks good to me! On Fri, Dec 13, 2019 at 13:05 Mingshen Sun wrote: > Hi Matt, > > I compose another diff for the `incubator-public` SVN truck to replace > all occurrences: > > Here is a summary: > ``` > M content/clutch/_includes/clutchm.ad > M content/clutch/_includes/clutchr.ad > M content/clutch/clutch.json > M content/clutch/clutch.txt > M content/clutch/report_due_1.txt > D content/podlings/mesatee.yml > A content/podlings/teaclave.yml > M content/podlings.xml > D content/projects/mesatee.xml > A content/projects/teaclave.xml > M content/shepherd_assignments.json > ``` > > Here is the diff: > > ``` > Index: content/clutch/_includes/clutchm.ad > === > --- content/clutch/_includes/clutchm.ad(revision 1871349) > +++ content/clutch/_includes/clutchm.ad(working copy) > @@ -15,8 +15,8 @@ > . David Meikle (dmeikle): Flagon > . Devaraj Das (ddas): Ratis > . Evans Ye (evansye): DataSketches > -. Felix Cheung (felixcheung): Crail, MesaTEE, Pinot > -. Furkan Kamaci (kamaci): DataSketches, DLab, DolphinScheduler, > Flagon, MesaTEE, Tuweni, TVM > +. Felix Cheung (felixcheung): Crail, Teaclave, Pinot > +. Furkan Kamaci (kamaci): DataSketches, DLab, DolphinScheduler, > Flagon, Teaclave, Tuweni, TVM > . Henri Yandell (bayard): MXNet > . Henry Saputra (hsaputra): DLab, TVM > . Hyunsik Choi (hyunsik): Nemo > @@ -27,7 +27,7 @@ > . Jason Dai (jasondai): MXNet > . Jean-Baptiste Onofré (jbonofre): BatchEE, brpc, Gobblin, Livy, > Nemo, StreamPipes, Tuweni > . Jean-Frederic Clere (jfclere): Milagro > -. Jianyong Dai (daijy): Hivemall, MesaTEE > +. Jianyong Dai (daijy): Hivemall, Teaclave > . Jim Jagielski (jim): Gobblin, Pinot, Tuweni > . John D. Ament (johndament): Pony Mail, Tamaya > . Jukka Zitting (jukka): PageSpeed > @@ -48,10 +48,10 @@ > . Leif Hedstrom (zwoop): PageSpeed > . Lewis John McGibbney (lewismc): Flagon > . Liang Chen (chenliang613): DataSketches, DolphinScheduler > -. Luciano Resende (lresende): Crail, Hudi, Livy, Marvin-AI, MesaTEE, Toree > +. Luciano Resende (lresende): Crail, Hudi, Livy, Marvin-AI, Teaclave, > Toree > . Mark Struberg (struberg): BatchEE > . Markus Weimer (weimer): MXNet, Nemo > -. Matt Sicker (mattsicker): MesaTEE > +. Matt Sicker (mattsicker): Teaclave > . Michael Wall (mjwall): MXNet, Tuweni > . Myrle Krantz (myrle): Weex > . Nick Kew (niq): Annotator, Milagro, PageSpeed > @@ -83,4 +83,4 @@ > . William Colen (colen): Marvin-AI > . Woonsan Ko (woonsan): S2Graph > . Xiangrui Meng (meng): Hivemall > -. Zhijie Shen (zjshen): MesaTEE > +. Zhijie Shen (zjshen): Teaclave > Index: content/clutch/_includes/clutchr.ad > === > --- content/clutch/_includes/clutchr.ad(revision 1871349) > +++ content/clutch/_includes/clutchr.ad(working copy) > @@ -461,22 +461,22 @@ > |[.care]#False# > > > -|link:mesatee.html[MesaTEE] > +|link:teaclave.html[Teaclave] > |Incubator > |2019-08-20 > -|link:/projects/mesatee.html">[[.cool2]#93#] > +|link:/projects/teaclave.html">[[.cool2]#93#] > |False > |1 > -|link:/projects/mesatee.html">[[.cool1]#True#] > +|link:/projects/teaclave.html">[[.cool1]#True#] > |2019-09-23 > -|link:/projects/mesatee.html">[[.cool1]#59#] > +|link:/projects/teaclave.html">[[.cool1]#59#] > |3,3,- > -|https://people.apache.org/phonebook.html?podling=mesatee[[.cool1]#15#] > +|https://people.apache.org/phonebook.html?podling=teaclave[[.cool1]#15#] > |[.care]#0# > -| > https://gitbox.apache.org/repos/asf?p=incubator-mesatee.git;a=tree;hb=HEAD[[.cool1]#True#] > +| > https://gitbox.apache.org/repos/asf?p=incubator-teaclave.git;a=tree;hb=HEAD[[.cool1]#True#] > |https://issues.apache.org/jira/browse/XXX[[.cool1]#True#] > -|http://mail-archives.apache.org/mod_mbox/mesatee-dev[[.cool1]#True#] > -|http://mail-archives.apache.org/mod_mbox/mesatee-commits[[.cool1]#True#] > <http://mail-archives.apache.org/mod_mbox/mesatee-dev%5B%5B.cool1%5D#True%23]-%7Chttp://mail-archives.apache.org/mod_mbox/mesatee-commits[[.cool1]%23True%23]> > +|http://mail-archives.apache.org/mod_mbox/teaclave-dev[[.cool1]#True#] > +| > http://mail-archives.apache.org/mod_mbox/teaclave-commits[[.cool1]#True#] > |[.care]#False# > |[.care]#False# > |[.care]#False# > Index: content/clutch/clutch.json > === > --- content/clutch/clutch.json(revision 1871349) > +++ content/clutch/clutch.json(working copy) > @@ -3366,11 +3366,11 @@ &
Re: Changes subject to brand name change
> - These items are not to be signed as done during > incubation, as they > - may change during incubation. > - They are to be looked into and described in the status > reports and > - completed in the request for incubation signoff. > - > - > - Collaborative Development > - > -Have all of the active long-term volunteers been identified > and > -acknowledged as committers on the project? > - > -Are there three or more independent committers? (The > legal definition > -of independent is long and boring, but basically it > means that there > -is no binding relationship between the individuals, > such as a shared > -employer, that is capable of overriding their free will as > -individuals, directly or indirectly.) > -Are project decisions being made in public by the > committers? > -Are the decision-making guidelines published and > agreed to by all of > -the committers? > - > - > - > - Licensing awareness > - > -Are all licensing, trademark, credit issues being > taken care of and > -acknowleged by all committers? > - > - > - > - Project Specific > - > -Add project specific tasks here. > - > - > - > - > -Exit > - > - Things to check for before voting the project out. > - > - id="Organizational+acceptance+of+responsibility+for+the+project"> > - Organizational acceptance of responsibility for the > project > - > -If graduating to an existing PMC, has the PMC voted > to accept it? > -If graduating to a new PMC, has the board voted to > accept it? > - > - > - > - Incubator sign-off > - > -Has the Incubator decided that the project has > accomplished all of > -the above tasks? > - > - > - > - > - > - > Index: content/projects/teaclave.xml > === > --- content/projects/teaclave.xml(nonexistent) > +++ content/projects/teaclave.xml(working copy) > @@ -0,0 +1,422 @@ > + > + > + > +Teaclave Incubation Status > +http://purl.org/DC/elements/1.0/; rel="schema.DC"/> > + > + > + > + Teaclave Project Incubation Status > + This page tracks the project status, incubator-wise. For more > general > + project status, look on the project website. > + > + > + Description > + Teaclave 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). > + > + > + > + News > + > +2019-08-19 Project enters incubation. > + > + > + > + Project info > + > +link to the main website > + > + > +link to the page(s) that tell how to participate (Website,Mailing > +lists,Bug tracking,Source code) > + > + > +link to the project status file (Committers,non-incubation action > +items,project resources, etc) > + > + If the project website and code repository are not yet setup, use > the > + following table: > + > + > + item > + type > + reference > + > + > + Website > + www > + > + href="http://teaclave.incubator.apache.org/;>http://teaclave.incubator.apache.org/ > + > + > + > + Mailing list > + dev > + id="mail-dev">dev@teaclave.incubator.apache.org > + > + > + . > + issues > + id="mail-issues">issues@teaclave.incubator.apache.org > + > + > + . > +
