|
| 1 | +# working group meeting on 2021-04-27 |
| 2 | + |
| 3 | +## Participants |
| 4 | + |
| 5 | +* Zhiqian Xia |
| 6 | +* Tom Stellard |
| 7 | +* Wei Wu - PLCT Lab |
| 8 | +* Anton Korobeynikov |
| 9 | +* Mike Edwards |
| 10 | +* Azhar |
| 11 | +* Zhiqian Xia |
| 12 | + |
| 13 | +## Agenda |
| 14 | + |
| 15 | +Agenda items taken from the [backlog](https://github.com/llvm/llvm-iwg/projects/1) |
| 16 | + |
| 17 | +### Epic: improve infrastructure documentation [#14](https://github.com/llvm/llvm-iwg/issues/14) |
| 18 | + |
| 19 | +* 2 issues resolved |
| 20 | +* a few more in progress |
| 21 | + |
| 22 | +### Hiring for infrastructure role #27 |
| 23 | + |
| 24 | +see comment on issue #27 |
| 25 | + |
| 26 | +### Formalize the working group #22 |
| 27 | + |
| 28 | +* see comment on issue #22 |
| 29 | +* created new issue #34 to document our current learnings |
| 30 | + |
| 31 | +### Decide on incoming requests |
| 32 | + |
| 33 | +There were some requests for our involvement recently. We should decide which of |
| 34 | +these we want to work on: |
| 35 | + |
| 36 | +* how do we decide on requests? |
| 37 | + * If we can't handle it right away and if a meaningful request: try to find a |
| 38 | + vendor with the right expertise to do it. |
| 39 | + * Major question: Can we find enough volunteers to take on the topic? |
| 40 | + * Until we have a better solution: discuss on a case by case basis. |
| 41 | +* Mac-Hardware for pre-merge testing #32 |
| 42 | + * details are on the mailing list |
| 43 | + * Christian and Mike are requesting quotes for the hardware |
| 44 | + * Mike will then propose this to the foundation |
| 45 | +* Mailman - investigate long term solutions #6 |
| 46 | + * volunteers so far: Christian Kühnel, Mike Edwards, Chris Lattner, Kit Barton |
| 47 | + * [initial |
| 48 | + research](https://github.com/ChristianKuehnel/llvm-iwg/blob/Discourse/Discourse_research.md) |
| 49 | + on the migration |
| 50 | + * proposal: have this sub-group of 4 work on the issue |
| 51 | + * ask for objections on mailing list |
| 52 | + |
| 53 | +* Discontinue code reviews on the mailing list #31 |
| 54 | + * out of time, postponed to next meeting |
| 55 | + |
| 56 | +### other topics |
| 57 | + |
| 58 | +* Screen sharing is not working in the Zoom meeting. Christian to talk to Tanya. |
| 59 | +* #32 sparked a longer discussion around our build systems |
| 60 | + * We all agree that we should be working to reducing the number of different |
| 61 | + CI systems in place. Users and maintainers should only have to deal with |
| 62 | + one platform. |
| 63 | + * This would be a major migration project, it's unclear today how we can |
| 64 | + gather a large enough group to work on this. |
| 65 | + * We should decide on where we want to proceed with pre-merge testing. Today |
| 66 | + we do not really have an agreed roadmap for it. |
| 67 | + * Maybe: Create a dashboard to show contributors how their commit progresses |
| 68 | + through the different CI pipelines. |
| 69 | + * Maybe change the way Buildbot is set up today to speed up config changes: |
| 70 | + Only configure some parts on the server, take the rest of the configuration |
| 71 | + from the repo. |
| 72 | +* For prototyping new features: We should help the community members pick the |
| 73 | + right technology stack to implement/demonstrate new ideas to reduce the amount |
| 74 | + of different solutions in place. |
0 commit comments