User Tools

Site Tools


groups:tsc:project-updates:burrow-2018-may

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
groups:tsc:project-updates:burrow-2018-may [2018/05/23 17:26]
Silas Davis created
groups:tsc:project-updates:burrow-2018-may [2018/11/26 17:14] (current)
Silas Davis [Hyperledger Burrow Project Update Q3 2018]
Line 1: Line 1:
-====== Hyperledger Burrow Project Update ​Q3 2018 ======+====== Hyperledger Burrow Project Update ​Q2 2018 ======
  
  
Line 7: Line 7:
  
 ===== Issues ===== ===== Issues =====
 +   * We need a flexible fee structure compatible with new Tendermint (ability to charge for gas, on value transferred,​ on contract, based on volumes, etc)
    * We need to build governance primitives around our validator bonding/​unbonding flow    * We need to build governance primitives around our validator bonding/​unbonding flow
    * We need the ability to escrow between chains    * We need the ability to escrow between chains
Line 12: Line 13:
  
 ===== Releases ===== ===== Releases =====
-//​**Required** Regular software product releases are a sign of a healthy projectReports should list the releases made since your last report, along with the release date of each. NOTEIf no releases were made, list the date of the most recent prior release.//+Burrow v0.18.0 released 9th May 2018 with a large number ​of improvements[[https://​github.com/hyperledger/burrow/​blob/​develop/​CHANGELOG.md]]
  
  
 ===== Overall Activity in the Past Quarter ===== ===== Overall Activity in the Past Quarter =====
-//​**Required** Discuss briefly how active the project mailing lists and chat channels are. Are emails or user questions regularly read and responded to?  What technical changes ​is the project working on? Is there new development ​happening, or just bug fixes? NOTE: If activity ​is minimal, verify whether or not there are at least three active maintainers who can step in when needed, and include this information in the report.// +Hyperledger ​chat channels are increasingly busy, particularly #​burrow-contributors which is generating useful ​development ​discussion. Burrow mailing list is quietbut I will provide an update with recent information ​and see if that generates any interest.
  
 ===== Current Plans ===== ===== Current Plans =====
-//**Required** A healthy project will often be working towards a common goal, or have shared understanding ​of what is being done next even if individual contributors have their own "​itches"​. What are the main features planned? What releases are planned? Are there any specific efforts or branches of development under way? This does not need to be described in technical detail. Conversely, if activity is minimal, discuss how the project plans to address that - whether through seeking out new contributors,​ maintaining in a dormant but available state, or planning towards a move to a Deprecated (and ultimately End of Life) state.//+Our big ticket items are: 
 +   * Pulling out key management and crypto into Burrow (from monax-keys). Updating libraries, stripping away intermediate layers (go-crypto),​ and making Burrow more 'self hosted'​ for validators. See: [[https://github.com/​hyperledger/​burrow/​pull/​776]] 
 +   Implementing GovTx the base mechanism for changing validator sets according to bonding rules and other '​governance fork' events 
 +   Adding an event firehose from which consumers can stream all events occurring within ​range of blocks ​- to be used to drive Kafka and other integrations
  
 +The major theme for Burrow this quarter is operability in the sense of running a production validator pool which includes ideas/work around:
 +   * Network formation - starting networks from a single genesis validator and provisioning an initial secret to bond validators within a pool on
 +   * Introducing hierarchical identity to validator pools to differentiate from the key matter on individual nodes (that can be generated on those nodes and never leave) and the human/​organisational authority that runs those nodes
 +   * Improvements to config generation
 +   * Kubernetes helm charts
 +   * State snapshotting backup and recovery ​
  
 ===== Maintainer Diversity ===== ===== Maintainer Diversity =====
-//​**Required** Please include the maintainers that were added since your last reportThis information will allow us to track the diversity and growth of the maintainers of the project. NOTEIf no maintainers were added since your last report, provide the list of existing maintainers.//​+We have added Sean Young (sean@monax.io) as a maintainer, joining:
  
 +   * Silas Davis (silas@monax.io)
 +   * Casey Kuhlman (casey@monax.io)
 +   * Tyler Jackson (tyler@monax.io)
  
 +We have a health pipeline of intended maintainers coming through, with two developers joining us from Finterra who have already done good work and I hope to have onboarded by next update:
  
-===== Contributor Diversity ===== +   * Ahmad Pouladzade (pouladzade@gmail.com - Finterra) 
-//**Required** A healthy project should survive the departure of any single contributor or employer of contributorsHealthy projects also serve needs of many partiesInclude information on the number of unique organizations currently contributing to the projectNOTE: The contributions do not need to be source code.//+   ​Mostafa Sedaghat (mostafa.sedaghat@gmail.com - Finterra) 
 +   * Sean Blucker (sean.blucker@tcs.com - TCS)
  
  
-===== Additional Information ​===== +===== Contributor Diversity ​===== 
-//**Optional** Please provide any additional information that you feel would be useful for TSC to be aware.//+We have added 3 new contributors and 1 entirely new satellite project [[https://github.com/pouladzade/snack]] (providing package management).
  
- +A few contributions are around our documentation hitting the Bosmarmot repo and we have had some significant contributions from Sean Blucker on the EVM bringing us into compatibility.
  
 +
 +===== Additional Information =====
 +Burrow is known in Hyperledger as being the project with an EVM. As we deploy our own public network and work more closely with Tendermint/​Cosmos I think there is scope for Burrow to become the project for building permissioned public chains as part of the Tendermint/​Cosmos ecosystem or 'The Hyperledger App for Tendermint'​. Burrow will increasingly have means for: constructing dynamic fee/gas schemes, running BPMN process models on across an ABCI (not necessarily limited to Tendermint) interface, and sending messages across Tendermint zones with IBC. It might warrant a brief discussion in the TSC. 
groups/tsc/project-updates/burrow-2018-may.1527096370.txt.gz · Last modified: 2018/05/23 17:26 (external edit)