Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

(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)

  • 8 am Monday Los Angeles
  • 11 am Monday New York

Agenda

  •  Housekeeping
  • 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. The validators are up and running for now.  Here is the final documentation from the Hyperledger side:  
      View file
      namemain.pdf
      height250
      • Thanks to Sally and Danno for their suggestions!  
      • Ask: start for community lead initiative for nominations
        • timeline: 6 months after the Merge
        • discussion on wiki or GitHub for the contributions: both for now
          • no design for duplication for now 
  • Release updates
    • Tracking who is doing each release Release Rotations 2022
      • 22.4.0-RC2 complete. 
      • 22.4.0 complete
      • 22.4.1 scheduled for May 18th - Jason Frame (Australia) is down to execute this one 
    • discussion on merge and version sync

Work Updates

    • Merge Update:
      • Ongoing UX and other bugs being raised and fixed quickly. Testnet was launched last week. Besu had some syncing challenges. 
      • Mainnet shadow fork on this Th
    • Snap Sync: Goerli and Mainnet sync has been tested. Adding benchmarks to identify any other issues. Next call: Karim Taamto share broader update. Don't want to have usable snapsync on main branch yet. If it is ready to be tested, will share in besu-contributors once ready. 
      • working on a blog on results
  • 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).  The feature set is very low at the moment, but they are actively soliciting feature requests.  What would Besu want to see?
      • No high priority requests.
    • Debug Issue with Besu: (brought up by Justin Florentine: Having some challenges with Docker. Need to do more research to understand options/issue further. (no need to add in the next agendas)
    • Separate lists for code maintainers and non-code maintainers https://github.com/hyperledger/besu/pull/3790
      • Should the approval process be different? Non-code maintainers can change status of tickets but can't approve PRs
      • PR to add 2 new non-code maintainers https://github.com/hyperledger/besu/pull/3811
      • discussion if triage is working or not and looks like it is working: permissions are working for Execution Client triage
    • Security Audit Update? Timeline?
    • Validator Experience with Besu
  • Metrics Review - https://insights.lfx.linuxfoundation.org/projects/hyperledger%2Fbesu/dashboard;quicktime=time_filter_3Y
  • Roadmap Review - Roadmap
    • Note from Matt on 22.7 
    • optimistic support, rollup client diversity question 
      • Matt Nelson  will engage more with those devs re changes rollups product requirement 
        • example on providing more APIs
  • Open Forum
    • Proposal - "Off Week" Discord voice chat meetup. When?
    • Deprecating log42j - from Diego see Contributor channel
  • Future Topics


Attachments