llvm-iwg
llvm-iwg copied to clipboard
llvm
The LLVM Infrastructure Working Group
As outlined in the [mailing list archive issue](https://github.com/llvm/llvm-iwg/issues/94), the *-commits and *-bugs email lists are the highest traffic Mailman lists still running on lists.llvm.org. These services still represent a maintenance...
converting the discussion on the mailing list into an issue: >I would like to propose that we start publishing biweekly status reports > for the community on all the outstanding...
based on the discussion in #66: Is there an audit trail for actions on Github triggered via a stolen Github runner token? Can we somehow figure out what an attacker...
From the discussion on 2022-02-01: Original question: Can we have this meeting later in the PST timezone? * Current time slot is hard for folks from ASIA and PST time...
Hi! Every now and then I got bothered with a question if it's OK to process user data available from Phabricator. I didn't manage to find any "terms" or "privacy"...
From IWG meeting on 2022-02-01: Do we want to offer office hours get community input and listen to their concerns? The idea would be to offer a communication channel beyond...
I saw on the mailing list, that a new project "BOLT" shall be added to the LLVM monorepo: https://lists.llvm.org/pipermail/llvm-dev/2021-November/153551.html Some things to do: 1. Update pre-merge checks https://github.com/google/llvm-premerge-checks/issues/364 2. I...
Right now the landscape is fragmented by repository and it's not clear where to do the code reviews. So it would be nice if this is documented somewhere. Migrated from...
From the discussing in the IWG meeting on 2022-02-01: What is the long-term roadmap for the mailing lists and the archive? * Do we want to create static snapshot of...