Board Meeting Minutes - April 2024

Community LLVM Foundation
1

The April 2024 board meeting minutes can be found here.

The contents of the PDF are also copied here:

Board Meeting Minutes

Date: Apr 5, 2024
Time: 9AM pacific time
Location: Video conferencing, multiple locations

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

Agenda

  • Approve March 1, 2024 previous meeting minutes
    • Approved by: Tanya, Kristof, Reid, Chris L, Chris B, Anton, Mike, Wei, Kit
  • EuroLLVM 2024 Updates [Tanya]
    • Attendance
      • At 260 registered attendees; contracted with venue for 300
    • Budget
      • Projected budget was $1100/person; actual costs are expected to be around $1300/person
      • We have multi-year contracts for the US dev meeting, but EuroLLVM has traditionally been a “roaming” conference. Discussed the option of having a recurring EuroLLVM venue to reduce cost.
      • Noted that US EuroLLVM attendees will need a visa to travel to the Shengen zone starting in 2025
    • Community.o
      • Workshop will mimic the US-workshop more; community involvement seems to have decreased since pandemic
      • Need support from corporations to encourage people to volunteer for this
      • Also need to have a larger discussion about burn-out within the community, and need to impress the importance of community involvement to the corporate sponsors
  • Budget Update [ Tanya ]
    • Virtual Status
      • We have terminated contract with Virtual
      • In discussion with Beyond Balanced Books to clean up our books and resuming bookkeeping services
      • Still do not have a budget for 2024
  • Dropping requirement for contributions to be covered under legacy license [Kristof]
    • Our IP lawyer answered our questions (about dropping legacy license): no concerns.
    • Go ahead with posting message to Discourse?
      • Yes; post on announcements and ask people to email responses board@llvm
    • The LLVM Foundation, as a binary distributor of LLVM, needs to ensure correct attributions are provided in the distribution.
    • When do we declare success on relicensing?
      • Unlikely to get agreement on 100% of code that is currently in the codebase
      • Declare success when the vast majority of code is under new license and remaining code is under dual license.
  • GSoC update [Anton]
    • Project proposal submission period ended on Tuesday (April 2)
    • Mentors are evaluating proposals
    • Received 33 proposals, compared to 54 last year
    • Feedback from mentors on reduced participation indicates shift in priorities from employers away from GSoC projects
    • Have 3 weeks to review all proposals and select projects
  • Infrastructure hiring [ChrisB]
    • More important to hire a DevOps engineer instead of a Infrastructure Director; motivation is to hire someone to do the work, instead of organizing the work that needs to be done.
      • Is there enough consensus on what needs to be done? There are a lot of pain points that could be addressed immediately to improve things
      • Do we have a decision-making process to guide what should be done? The governance guidelines from Chris B is a step in the right direction.
      • We still have a lot of work that is in progress and has not been completed; this also needs to be included as part of this role.
    • TODO: Chris B and Mike will drive the job posting over the next month.
    • TODO: Chris B and Mike will write proposal for how the infrastructure role will receive work/direction, receive feedback, performance reviews, etc.
  • Supply Chain Security [ChrisB]
    • Recent issues with security in Open Source supply chain.
    • The foundation can help advise the community and develop directions/thoughts on how to approach and deal with these problems.
    • TODO: Should we do a sponsored talk at the US LLVM Dev Meeting to discuss this? What other ways can the foundation help the community get more information or help with this problem?
    • Need to promote and encourage high functioning community members (e.g., code reviews) and the ability to react quickly if something bad happens while balancing contributor burnout.
    • We should be having discussions in alternative open forums (e.g., zoom, online sync-ups) in addition to Discourse, to be more inclusive and ensure a broader community reach.
  • AI Generated Code notice [Tanya]
    • TODO: Chris L and Reid will write a paragraph to add to the developer policy (link) explaining the LLVM’s approach of the use of AI-generated code
  • Review and approve minutes (time permitting) [Everyone]
1 Like