(Meeting Link: https://consensys.zoom.us/j/94665568300)
APAC/AMER Friendly Time - 0100UTC (https://www.timeanddate.com/worldclock/converter.html?iso=20210913T010000&p1=224&p2=179&p3=1440&p4=195&p5=47)
- 6 pm Monday Los Angeles
- 9 pm Monday New York
- 1 am Tuesday UTC
- 3 am Tuesday Paris/Berlin
- 11 am Tuesday Brisbane
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
- outreach from finance re versioning info - Danno Ferrin has some info, and will share confidentially so we can address
- Release updates
- Release process in general, plan for diversifying who can make a release.(Justin Florentine )
- How many maintainers required to sign off on a release?
- GAR-E - what does it still need to reduce friction? - currently GAR-E is proprietary. Outside maintainers currently need to use a checklist and do it manually.
- What role (if any) does CircleCI have in releasing?
- Objections to tag-based release
- doesn't have immutable metadata - tags can be moved
- one person can run a release - this should be prevented currently by branch protection
- Release process in general, plan for diversifying who can make a release.(Justin Florentine )
- Work Updates
- Static code analysis (Justin Florentine)
- Example output here: https://sonarcloud.io/dashboard?id=hyperledger-cicd_besu
- Can we get it to run for non-maintainers (uses a restricted context)
- Can we get the coverage output combined across reference tests, acceptance tests, unit tests
- Chat platform - Matrix/Rocketchat discussion
- discussions are happening (Grace Hartley)
- Vert.x upgrade - complete
- Static code analysis (Justin Florentine)
- Other Business
- Discussion re having community zoom used to ensure that meetings can be recorded
- Open Forum
- Recap of conversations from prior two Besu contributor calls re EF incentive program
- Inactivity clause for moving maintainers to emeritus status - the current guide says a quarter of inactivity. Do we want to extend that? 6 months? Longer?
> A general measure of inactivity will be no commits or code review comments for one reporting quarter, although this will not be strictly enforced if the maintainer expresses a reasonable intent to continue contributing.
- Future direction of Besu
- some thoughts from Danno Ferrin - Besu 2022 Vision
View recording:
TBA