We are targeting having our final Pantheon release on our September 10th repo, and we then need the new Besu repo set up prior to the 1.3 Release Candidate scheduled for September 25th.
|RocketChat / Mailing list best practices|
Mailing list; Distribute Release updates/notes, send schedule/invite for maintainer meeting and notes
Community Calendar - Post our Maintainer meeting invite there
One maintainer meeting and one application developer meeting
Send welcome email to community once repo is up
|What other tools/actions am I missing to make sure we're onboarded on appropriately and can quickly move to Active status||Grace Hartley|
Members for Security list David Huseby
Documentation - > Overview page on wiki
|GitHub team management||Ry Jones|
- Grace HartleyI need two volunteer email addresses to add to the firstname.lastname@example.org team. It's a very light traffic list but each team is expected to contribute a primary and secondary volunteer who can handle helping triage incoming security issues with all projects and can also help resolve any incoming security issues on Besu.
- Grace Hartley If Besu is looking at going to active status ASAP, then we need to kick off a security audit of the code base. I am in the process of refreshing our vendors for security audits and would like somebody on the Besu team to help me write a proposal to send out to a few vendors for bids.