Burrow is being deployed to an ever-widening group through the (https://agreements.network/) now on its T3 test networks. This is producing a lot of feedback (and issues). Code-wise Burrow is in best shape of its life and we are moving away from paying down technical debt to working now new features such as our ETL and governance systems. Community engagement is good from users - though it has been frustrating for some as we have consolidated our tooling (which now overwhelming resides in the single burrow binary). Now would be the right time to put effort into documenting the detail of Burrow since anything produced is likely to be durable now the shape of the project is in less flux. We had disappointment with maintainer diversity - in that one developer on a maintainer track has been relocated by his employer and two other who could have done useful advanced work have decided, regrettably, to fork Burrow. They have said they would like to contribute but there action makes this harder given they could have depended on us as a library. Still Burrow has four full-time developers and receives useful contributions from the community on a regular basis - but not on a maintainer level. Any assistance from Hyperledger would be useful in this respect.
Post-refactor our release cadence has increased significantly and we have automated cross-compilation and release to github:
We have received several pull requests and issue that demonstrate actual bugs and are actionable beyond requests for help. Our mailing list remains fairly inactive, but Hyperledger chat generates a steady stream of questions which we respond to within a day or so at most.
In terms of features we have added:
We have three buckets of functionality we are working on:
We had hoped to be able to say we had added three new maintainers outside Monax, but one has ceased contributing to the project because he has been reallocated, and two have decided to work on a fork of Burrow having initially begun by copy and pasting the code.
Many of our developer users are working on prototypes and often do not have the project security such that they feel able to get more involved. The amount of movement in all aspects of the code base over the last quarter (whilst much needed) also made it more difficult for contributions to be accepted (or indeed mergeable). We would appreciate help and advice on improving our maintainer diversity.
Over the last quarter we have received contributions for 3-5 contributors unrelated to Monax.
We continue to work with Tendermint/Cosmos and have been collaborating over some of there efforts in building EVM state, and their authenticated data structure IAVL.