Re: Hyperledger Besu Proposal is Live
|
Arnaud Le Hors
Hi all,
toggle quoted messageShow quoted text
I find myself largely in agreement with the sentiment expressed by Shawn and Chris. I find it rather unfortunate that attempts to understand how Besu will fit in and what its addition means to be interpreted as a vote against it. I think it is the TSC's job to take a serious look at every proposal and understand what the implications are. These shouldn't necessarily be seen as a pushback as much as an interest in looking after the well being of Hyperledger. It has been said that we are making new rules as we go and I think that's a fair point but I for one don't think that's really by choice nor a bad thing. Hyperledger is still a very young organization and it should be expected that it goes through some transformation as it grows. Our charter states that our missing is to "create an enterprise grade, open source distributed ledger framework and code base" [1]. So, as a matter of fact, we've literally been making new rules all along since we accepted developing in parallel more than one dlt. Why should anyone be then surprised we keep doing so? Anyway, I trust that with time we will get our act together. I understand the board is looking into updating our charter, which seems to be a good start. What's important to me, in line with what Chris stated and what I put in my TSC nomination pitch, is that we do a better job at documenting how the different projects compare and relate to one another, so that people in the community out there no longer get utterly confused when they come to our website in search for where to start they journey. Cheers. [1] https://www.hyperledger.org/about/charter -- Arnaud Le Hors - Senior Technical Staff Member, Blockchain & Web Open Technologies - IBM From: "Christopher Ferris" <chris.ferris@...> To: Shawn Amundson <amundson@...> Cc: VIPIN BHARATHAN <vip@...>, "vipinsun@..." <vipinsun@...>, Silas Davis <silas@...>, "jon.geater@..." <jon.geater@...>, "tsc@..." <tsc@...> Date: 08/27/2019 03:14 PM Subject: [EXTERNAL] Re: [Hyperledger TSC] Hyperledger Besu Proposal is Live Sent by: tsc@... comments in-lined, below.
On Tue, Aug 27, 2019 at 2:11 AM Shawn Amundson <amundson@...> wrote: On Mon, Aug 26, 2019 at 7:43 AM VIPIN BHARATHAN <vip@...> wrote: Hi Jon, Thanks for the thoughtful response.
I would agree with Shawn, here. There could be a bit more alignment, across projects but we do have plug-able consensus. However, I will remind people that code doesn't write itself, and no one ever shipped an architecture diagram/paper into production. Hyperledger is, all being said, an open source community. I would really love to see people diving in and working out the "how" and then rolling up sleeves to help drive the implementation of their thinking.
Agree, no one is campaigning against WGs, per se. The discussion of WGs is more about making WGs *more relevant* to the projects so that the project contributors and maintainers might pay them more attention and participate, meaningfully to the benefit of the projects and the broader community.
...
...
Agreed. I've been struggling with this. I think that there's positive benefit to bringing the Hyperledger and Ethereum communities closer together in the hopes that kumbayah. Though, I don't necessarily think that there will ever be one DLT to rule them all, and in the darkness bind them. What I DO think that Hyperledger needs to sort out is how it positions and promotes its projects. Right now, there is a considerable amount of overlap/redundancy, and it can be difficult at best to try to articulate to the general public how the projects are differentiated from one another. Further, during any project's life-cycle there's a great deal of effort expended to raise its voice above the din, to get people to kick the tires and maybe get more interested/invested. I'm fine if Hyperledger is to become the Apache-for-Enterprise-Blockchain-and-DLTs, but note that Apache marketing is about promoting Apache and the Apache Way, not Hadoop, Kafka, Maven, Tomcat, or OpenWhisk. Brian and Jessica have a difficult job, just as any parents with multiple offspring. Each child is special yet loved and nurtured equally. When someone asks a parent which child they love more, the correct response is "all of them". So, what should be the Hyperledger response when asked by press and analysts which of its projects is better, the correct answer needs to be "judge for yourself, we support them all equally". Yet, in this ultra-competitive landscape there is a natural tendency for press and analysts to look for differentiation, conflict and adoption to inform their audiences (and drive clicks). How do we enable the projects to make their case if they are promoted as equals? Where am I going with all of this? I think we need to collectively (with the Board and Marketing) address the question that Shawn posed: "What is Hyperledger?". If Hyperledger is indeed to be a "greenhouse" or "umbrella" organization where open source blockchain/dlt for enterprise is developed - taking its cue from Apache. Then, I think we need to come to terms with two things: 1) what we want to be the "Hyperledger Way", and 2) how projects are marketed I think there's much to be learned from the success of Apache and Eclipse, both of which are home to hundreds of projects, some overlapping/competing, some collaborative integrate-able components that fit a given framework. It could be just about creating a "safe place to innovate", as I like to say. It could be about encouraging growth of community(s) around projects. It could be about defining a single compose-able framework for DLTs shepherded by a collection of WGs that do top-down architecture overseen by the TSC. However, whatever we choose, we then need to sort out how (or whether) we market the projects via Hyperledger or, allow the projects to manage their own messaging. -Shawn
|
|
|