Date
1 - 7 of 7
PR for adding deprecation notice to the Avalon repo
|
Jim Zhang
As discussed in the last TSC meeting, we want to add a deprecation notice to the Avalon github repo. I went ahead and proposed a notice at the top of the README. Here's the PR: https://github.com/hyperledger/avalon/pull/777. It can use your input for details of the CCC project as well as what other Hyperledger projects might be the right catcher for the various aspects of project Avalon. thanks, -- |
|
|
|
Hart Montgomery <hmontgomery@...>
Hi Jim,
Thanks for doing this.
I'm fine with what is currently written. Does anyone want to add anything else?
Thanks,
Hart
From: tsc@... <tsc@...> on behalf of Jim Zhang via lists.hyperledger.org <jim.zhang=kaleido.io@...>
Sent: Sunday, January 23, 2022 11:55 AM To: Technical Steering Committee (TSC) <tsc@...>; Yarmosh, Yevgeniy Y <yevgeniy.y.yarmosh@...> Subject: [Hyperledger TSC] PR for adding deprecation notice to the Avalon repo As discussed in the last TSC meeting, we want to add a deprecation notice to the Avalon github repo. I went ahead and proposed a notice at the top of the README. Here's the PR: https://github.com/hyperledger/avalon/pull/777.
It can use your input for details of the CCC project as well as what other Hyperledger projects might be the right catcher for the various aspects of project Avalon.
thanks,
-- |
|
|
|
I think we can add " fabric private chaincode lab details, it offers samething. "Hyperledger Fabric Private Chaincode (FPC) enables the execution of chaincodes using Intel SGX for Hyperledger Fabric. The transparency and resilience gained from blockchain protocols ensure the integrity of blockchain applications and yet contradicts the goal to keep application state confidential and to maintain privacy for its users. To remedy this problem, this project uses Trusted Execution Environments (TEEs), in particular Intel Software Guard Extensions (SGX), to protect the privacy of chaincode data and computation from potentially untrusted peers." On Mon, Jan 24, 2022 at 7:28 AM Hart Montgomery <hmontgomery@...> wrote:
|
|
|
|
Jim Zhang
Thanks Kamlesh, that makes sense. Do you mind adding a new commit to the PR with this? Regards, Jim On Mon, Jan 24, 2022 at 12:12 AM kamlesh nagware <kamlesh.nagware@...> wrote:
--
|
|
|
|
I'm also fine with it as it is. I did +1 on the nit for the unnecessary style changes, but I also recognize that it doesn't matter that much given that project is being deprecated anyway and the diff is not too big with or without the style changes. In short:
LGTM.
Peter Somogyvari
Technology Architect Accenture Products & Platforms (APP) Office: +1 (415) 537-5541 Mobile: +1 (650) 488-1741 From: tsc@... <tsc@...> on behalf of Hart Montgomery <hmontgomery@...>
Sent: Sunday, January 23, 2022 5:58 PM To: Technical Steering Committee (TSC) <tsc@...>; Yarmosh, Yevgeniy Y <yevgeniy.y.yarmosh@...>; jim.zhang@... <jim.zhang@...> Subject: [External] Re: [Hyperledger TSC] PR for adding deprecation notice to the Avalon repo
This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.
Hi Jim,
Thanks for doing this.
I'm fine with what is currently written. Does anyone want to add anything else?
Thanks,
Hart
From: tsc@... <tsc@...> on behalf of Jim Zhang via lists.hyperledger.org <jim.zhang=kaleido.io@...>
Sent: Sunday, January 23, 2022 11:55 AM To: Technical Steering Committee (TSC) <tsc@...>; Yarmosh, Yevgeniy Y <yevgeniy.y.yarmosh@...> Subject: [Hyperledger TSC] PR for adding deprecation notice to the Avalon repo As discussed in the last TSC meeting, we want to add a deprecation notice to the Avalon github repo. I went ahead and proposed a notice at the top of the README. Here's the PR: https://github.com/hyperledger/avalon/pull/777.
It can use your input for details of the CCC project as well as what other Hyperledger projects might be the right catcher for the various aspects of project Avalon.
thanks,
-- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy. ______________________________________________________________________________________ www.accenture.com |
|
|
|
I've updated the PR. On Mon, Jan 24, 2022 at 12:07 PM Somogyvari, Peter via lists.hyperledger.org <peter.somogyvari=accenture.com@...> wrote:
|
|
|
|
Jim, that PR is already merged. On Mon, Jan 24, 2022 at 11:06 PM Jim Zhang <jim.zhang@...> wrote:
|
|
|