Board Meeting Minutes - February 2024

Community LLVM Foundation
1

The February 2024 board meeting minutes can be found here: https://foundation.llvm.org/documents/minutes/2024-02-02-Meeting-Minutes.pdf

The contents of the PDF are also copied here:

Board Meeting Minutes
Date: February 2, 2024
Time: 9AM pacific time
Location: Video conferencing, multiple locations

Attendees: Tanya, Reid, Chris B, Kristof, Chris L, Wei, Mike, Anton, Kit

Agenda

  • Approve December 8, 2023 meeting minutes
    • Approved by Tanya, Reid, Chris B, Kristof, Chris L, Wei, Mike, Anton, and Kit
  • Follow-up from previous meeting
    • Budget
      • Waiting for budget report from Virtual; have received some reports, but not complete
      • Mike and Tanya will have a discussion with Virtual to level-set our expectations from them and determine if they will be able to satisfy our requirements. If not, then we will need to find a replacement for Virtual moving forward.
    • Discourse Traffic Limits
      • Traffic rates are lower, but still high
      • Discourse still does not have any proactive rate-limiting; all rate limiting is done reactively
  • [ChrisB] Code Review Tools
    • Reviewable.io - Code Review Process Update - #127 by AaronBallman
    • Graphite.dev
    • Privacy Policy Draft
    • Some people in the community would like to have some tools enabled.
    • Board needs to approve privacy policy around 3rd party extensions so we can enable reviewable.io
      • Tools used to be available for our repo at the beginning, but they were explicitly disabled shortly afterwards
    • Will multiple review tools cause fragmentation within the community?
      • Both of these tools are optional to use; they just provide a different interface to viewing a pull request, adding comments, etc.
      • There may be some additional metadata that are added by different tools that would only be visible from within the tool.
      • The community needs to evaluate and experiment with the different tools first to collect more information and experience.
    • For Graphite.dev, we can explicitly specify which repositories it is enabled for (e.g., llvm-project).
      • We should investigate whether the same can be done for reviewable.io (specific repositories instead of entire organization)
    • Reviewable is specifically asking for:
      • Read-only access to organizations and teams
      • Read-only access to public repositories
      • Access to user email addresses (if it is publicly in repository or request from user if it is not publicly in repository)
    • Graphite.dev is specifically asking for:
      • Read-only access to administration, commit statuses, issues, members, and metadata
      • Read and write access to actions, checks, code, and pull requests
    • For Privacy Policy, we should ensure it has some sort of checklist that includes what people should look for when requesting access for an application
    • Vote: Approve access to the github LLVM Organization for reviewable.io and graphite.dev, assuming that they will access only publicly available information or explicitly request consent from individuals whose information is not publicly available. Once a privacy policy is in place, we will retroactively review these two apps and ensure they adhere with the privacy policy.
      • Approved by Tanya, Reid, Chris B, Kristof, Chris L, Wei, Mike, Anton, and Kit
      • Chris B will follow-up on Discourse thread and Anton will enable the apps.
  • GSoC 2024
    • Anton has blog post ready outlining GSOC 2023 and requesting project proposals for 2024 (will post shortly)
    • Open projects page requires updating:
      • Need to clean up old projects and add new ones
      • Need to contact former mentors and request volunteers for new mentors
    • Considering ideas of how to improve process to ensure more successful projects
      • mid/final project presentation/reviews to present to larger audience and collect feedback
  • DMARC and emails
    • Major email distributors are going to begin enforcing DMARC policies for large distribution lists
    • LLVM does fall into the bulk-email category
      • Email traffic through gmail can exceed 10GB/day
    • Need to implement:
      1. Revise email sending policy
      2. DMARC policy in place
        a. Delegate back-channel to receive report from future receivers
    • There are providers that provide a DMARC service that will take the DMARC emails and create a dashboard summary
    • Anton will work with Tom to try and reduce the amount of email traffic we are generating from Github
    • Vote: Create budget expense for a DMARC service ($2500/year).
      • Approved: Anton, Mike, Reid, Kristof, Kit, Wei Wei, Chris B.
      • Does not Approve: Chris L. (thinks we should fix the infra instead)

Mike dropped part-way through this discussion

  • Relicensing next step: only require submission under the Apache-2.0 WITH LLVM-exception license, no longer under legacy licenses.
    • Expected not an issue for contributors. One contributor started asking.
    • Would any users/consumers of LLVM be affected?
  • Public documents: what could be improved so they will be published in timed manner (last financial report published back in 2022)
  • Review and approve minutes (time permitting) [Everyone]
2 Likes