toc@lists.hyperledger.org | [Hyperledger Project TSC] [technical-discuss] Ethereum Everywhere (C++ re-licensing)

Home Messages Hashtags Subgroups Calendar

Date Date 1 - 2 of 2

[Hyperledger Project TSC] [technical-discuss] Ethereum Everywhere (C++ re-licensing)

Joseph Lubin #230 Bob, Sizable effort. Diligently and skillfully orchestrated. Large potential payoff. Thank you. On Tue, Jul 12, 2016 at 5:15 PM Andrew Keys via hyperledger-technical-discuss <hyperledger-technical-discuss@...> wrote: toggle quoted message Show quoted text Strong work, Bob. -- Please excuse spelling/grammatical errors in an attempt to respond as quickly as possible from my mobile. On Jul 13, 2016, at 5:10 AM, Bob Summerwill via hyperledger-technical-discuss <hyperledger-technical-discuss@...> wrote: https://bobsummerwill.com/2016/07/12/ethereum-everywhere/ TL;DR – What are you proposing? I am proposing to the contributors that the C++ Ethereum client runtime cpp-ethereum be re-licensed from the copyleft GPLv3 license to the more permissive Apache 2.0 license, to enable Ethereum software to be used as broadly as possible - a long-standing plan. This proposal only addresses the client runtime and does not include Solidity or Mix (the C++ tools). There is another blog post detailing the likely operational steps in that process. This document seeks to explain why I am making that proposal. https://bobsummerwill.com/2016/07/12/c-re-licensing-plan/ I would personally love to see Ethereum as part of the Hyperledger story, and I know that many others feel the same way. Hopefully this re-licensing can be the first step in the journey leading to that outcome. See also https://bobsummerwill.com/2016/06/12/cats-and-dogs-can-be-friends/. Best wishes to you all! Bob Summerwill Ethereum Foundation -- bob@... _______________________________________________ hyperledger-technical-discuss mailing list hyperledger-technical-discuss@... https://lists.hyperledger.org/mailman/listinfo/hyperledger-technical-discuss _______________________________________________ hyperledger-technical-discuss mailing list hyperledger-technical-discuss@... https://lists.hyperledger.org/mailman/listinfo/hyperledger-technical-discuss
More All Messages By This Member
Andrew Keys <andrew.keys@...> #229 Strong work, Bob. -- Please excuse spelling/grammatical errors in an attempt to respond as quickly as possible from my mobile. On Jul 13, 2016, at 5:10 AM, Bob Summerwill via hyperledger-technical-discuss <hyperledger-technical-discuss@...> wrote: toggle quoted message Show quoted text https://bobsummerwill.com/2016/07/12/ethereum-everywhere/ TL;DR – What are you proposing? I am proposing to the contributors that the C++ Ethereum client runtime cpp-ethereum be re-licensed from the copyleft GPLv3 license to the more permissive Apache 2.0 license, to enable Ethereum software to be used as broadly as possible - a long-standing plan. This proposal only addresses the client runtime and does not include Solidity or Mix (the C++ tools). There is another blog post detailing the likely operational steps in that process. This document seeks to explain why I am making that proposal. https://bobsummerwill.com/2016/07/12/c-re-licensing-plan/ I would personally love to see Ethereum as part of the Hyperledger story, and I know that many others feel the same way. Hopefully this re-licensing can be the first step in the journey leading to that outcome. See also https://bobsummerwill.com/2016/06/12/cats-and-dogs-can-be-friends/. Best wishes to you all! Bob Summerwill Ethereum Foundation -- bob@... _______________________________________________ hyperledger-technical-discuss mailing list hyperledger-technical-discuss@... https://lists.hyperledger.org/mailman/listinfo/hyperledger-technical-discuss
More All Messages By This Member

1 - 2 of 2

1

Previous Topic Next Topic

Home Hashtags Subgroups Calendar Terms