llvm-iwg
llvm-iwg copied to clipboard
llvm
The LLVM Infrastructure Working Group
Once we have the basic documentation in https://github.com/ChristianKuehnel/iwg-workspace/issues/37, scan through the list of workers to make sure that each of them really has an owner that can be contacted. Where...
Some possible solutions: - Discourse tags? - Additional Categories? To get an idea of how cross-posting is used with mailman, I went through and found all threads that were sent...
The [Phabricator Github page](https://github.com/phacility/phabricator) says: > Effective June 1, 2021: Phabricator is no longer actively maintained. What should we do about that?
We have two topics on the table where we should take a formal decision: Here's a proposal for taking such decisions: 1. One member of the IWG creates a pull...
Once we start owning some machines/services, we somehow need to agree on how we manage access to these. #32 will probably be the first case where we need some agreement...
This is part of #22 Document our working mode: * GitHub repo for documents & meeting minutes, notes taken in markdown * GitHub issues for planning/coordinating work items * GitHub...
When creating a proposal for the LLVM board in #32 I noticed that we will need a place to store sensitive information (e.g. pricing). **Requirements:** * not publicly visible *...
Request from the Foundation: We need to formalise the working group * elect chair * single point of contact for the board * point of contact for community * organise...
We have collected surveys on infrastructure components #10 and development workflows #40 . The next step is to define the scope of our working group. The outcome should be an...