|
| 1 | +# working group meeting on 2021-05-11 |
| 2 | + |
| 3 | +The agenda is in the [Kanban board](https://github.com/llvm/llvm-iwg/projects/1) |
| 4 | + |
| 5 | +## Participants |
| 6 | + |
| 7 | +* Christian Kühnel |
| 8 | +* ZhiqianXia |
| 9 | +* Mikhail Goncharov |
| 10 | +* DeclanHuang |
| 11 | +* qzhong |
| 12 | +* Mike Edwards |
| 13 | +* Philip |
| 14 | +* Anton Korobeynikov |
| 15 | +* Tanya Lattner |
| 16 | + |
| 17 | +## Epic: improve infrastructure documentation #14 |
| 18 | + |
| 19 | +## Decision 1: Working on a Mailman to Discourse migration #37 |
| 20 | + |
| 21 | +* The LLVM board will take the decision on the migration itself. The working |
| 22 | + group should figure out the best way perform the migration. |
| 23 | +* Philip has serious concerns in the migration itself and the way it is decided. |
| 24 | +* Christian will contact Philip to understand his concerns around Discourse. |
| 25 | +* We had a general discussion on how LLVM as a community decides such things. |
| 26 | + * Is Discourse really the right decision? |
| 27 | + * Why not keep the mailing list? |
| 28 | + * Who shall take such decisions? |
| 29 | +* For future decisions: The IWG should be involved in the decision process and |
| 30 | + understand the rationale, not just execute something someone else decided. |
| 31 | +* At the moment no objections to forming the sub-group. |
| 32 | +* We will leave this open for a couple of days to give people a chance to review |
| 33 | + and respond. |
| 34 | + |
| 35 | +## Decision 2: MacOS hardware for libc++ pre-merge testing #39 |
| 36 | + |
| 37 | +* It's good to get something moving, it's unclear if this is the most important |
| 38 | + topic. |
| 39 | +* Add to the proposal document: |
| 40 | + * This is an experiment where the LLVM foundation spends budget for a CI |
| 41 | + system. |
| 42 | + * We need to measure the impact/benefits for the community to understand if |
| 43 | + this effort was successful. |
| 44 | +* We do not have an assigned budget at the moment. This will probably change |
| 45 | + for 2022. This project will be less than 5% of the annual infrastructure |
| 46 | + budget. |
| 47 | +* The proposal should be a public document and ends up in the board's meeting |
| 48 | + minutes. However we need to find a way to keep the pricing information |
| 49 | + confidential. |
| 50 | + * For future RFPs: Tell bidders their pricing information will be released |
| 51 | + publicly after 30 days. |
| 52 | +* Do not wait for the board meeting and take the decision via email. |
| 53 | +* Mike will update the document, wait a day for feedback and then send to the |
| 54 | + board. |
| 55 | + |
| 56 | +## Add Infrastructure Admin description #41 |
| 57 | + |
| 58 | +See comment in issue. |
| 59 | + |
| 60 | +## other |
| 61 | + |
| 62 | +* Christian is OOO during the next meeting 2021-05-11. Mike will host the next |
| 63 | + meeting. |
0 commit comments