(Meeting Link: https://zoom.us/j/97540031823?pwd=dEJrRW1LakFlWnZPelI3VGxoVjg2dz09)
EMEA Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20201012T150000&p1=224&p2=179&p3=1440&p4=195&p5=47)
- 11 am New York
Agenda
- Housekeeping
- Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/
- This meeting is being recorded
- Please Mute unless speaking
- If you have a question use the raise hand feature
- General Announcements
- Incentive Program Update: [WIP] Proposal #4 is considered the final proposal. EF, HLF, and CSI are currently working with their respective legal teams.
- Action Items Review from prior call
- From Grace - We agreed on Option 2 for how to resolve who are mainnet maintainers in the Incentive program.
- Release updates and Improvements: Generally agreed we need to improve this process. Sajida was going to act as PoC from CSI side.
- Have we scheduled an off week Discord voice chat meeting yet?
- Release updates
- 22.1.0 done
- 22.1.1 done on 24 Feb
- Tracking who is doing each release Release Rotations 2022
- Add your name here to volunteer for release rotation
- Note quarterly release is a larger coordination role
- Team is working toward several Release Process Improvements here
- Work Updates
- trace APIs - ongoing
- Merge Update
- Future Backwards Incompatible Changes (Danno Ferrin)
- Java 17 migration (notice in next quarterly, actual upgrade next after)
- EVM migration from Gas object to long (git branch) (next quarterly)
- Other Business
- Automated Security Bot Requests
LinuxFoundation as a part of the insights process is creating an automated "security bot" that will analyze LF (and hence Hyperledger project). Feature set is very low at the moment, but they are actively soliciting feature requests. What would Besu want to see? (Danno Ferrin) - Documentation Discussion from (Nicolas MASSART) : https://discord.com/channels/905194001349627914/905205502940696607/951487768272465981
- Automated Security Bot Requests
- Metrics Review - https://insights.lfx.linuxfoundation.org/projects/hyperledger%2Fbesu/dashboard;quicktime=time_filter_3Y
- Roadmap Review - Roadmap
- Open Forum
- We are officially on Discord! Should we add maintainer's Discord handle on Maintainer list?
- Proposal - "Off Week" Discord voice chat meetup. When?
- Deprecating log42j - from Diego see Contributor channel
- Future Topics
2 Comments
Nicolas MASSART
I'd like to discuss Besu doc guidelines and specifically how it's perhaps not necessary to have specific guidelines for this project (we already point to
Google and Microsoft writing guidelines, why not more?).
The point is that it requires some maintenance that only a few of us are doing and because only the contribution process is specific to Besu, maybe we could point to Consensys doc writing guidelines directly so we only update them.
The Consensys doc guidelines are public and anyone can contribute (and we are reworking them currently so we would like to prevent having to do the work twice to do that also on Besu wiki).
The main question is how much isolation of Besu meta content (it's not code, it's not doc, it's the guidelines to write doc) do we want vs how easy it is to maintain.
Do you think we could discuss this in this community call?
(see my messages on Discord 1 2)
Francesco Andreoli
https://wiki.hyperledger.org/display/~shemnon/Besu+2022+Vision from Danno