|
| 1 | +# working group meeting on 2021-03-3ß |
| 2 | + |
| 3 | +## Participants |
| 4 | + |
| 5 | +* Christian Kühnel |
| 6 | +* Zhiqian Xia |
| 7 | +* anja gerbes |
| 8 | +* Azhar |
| 9 | +* Tom Stellard |
| 10 | +* Wei Wu - PLCT Lab |
| 11 | +* Anton Korobeynikov |
| 12 | +* Philip |
| 13 | +* mishal_shah |
| 14 | +* Mike Edwards |
| 15 | + |
| 16 | +## Hiring for infrastructure role #27 |
| 17 | + |
| 18 | +* tasks/goals for this role: |
| 19 | + * System Admin type of work, keep infrastructure up and running |
| 20 | + * Have SLAs to respond to issues, e.g. 24/7 |
| 21 | + * Help community set up infrastructure, perform migrations, ... |
| 22 | +* Contract work, hiring a company |
| 23 | + * company is probably more flexible, foundation is not hiring individuals (at |
| 24 | + the moment) |
| 25 | + * probably we want a group of professionals able to guarantee SLAs |
| 26 | + * Can we hire non-USA / non-California? Yes, company needs to have experience |
| 27 | + with contracts in the US though. |
| 28 | + * for any contracts: we need to go through an official RFP process across |
| 29 | + multiple companies. |
| 30 | + * initial work items: |
| 31 | + * keep websites up and running |
| 32 | +* Option: Extend Access Softek contract to cover this? |
| 33 | + * In any case, we should contact them first. |
| 34 | +* Hours per week: maybe start with part time and ramp up as needed |
| 35 | +* work split: |
| 36 | + * IWG to create the RFPs for the work |
| 37 | + * sysadmin/company to do the work |
| 38 | +* required skills: |
| 39 | + * IWG to prioritize the list of services to be taken over |
| 40 | + * system administration |
| 41 | + * Amazon AWS |
| 42 | + * customizing off-the-shelf services (e.g. Phabricator) |
| 43 | + * fix the source code in case of outages/upgrades |
| 44 | +* Tom to create a draft, Philip, Christian to help |
| 45 | + * start with problem description |
| 46 | + * maybe ruse the [infrastructuresurvey](https://github.com/llvm/llvm-iwg/blob/main/infrastructure_survey.md) |
| 47 | + we collected. |
| 48 | + |
| 49 | +## Set up a permanent Zoom videoconference for our meetings #12 |
| 50 | + |
| 51 | +Christian received new Zoom conference from Tanya, will send out the details |
| 52 | +with the meeting minutes. |
| 53 | + |
| 54 | +## Epic: improve infrastructure documentation #14 |
| 55 | + |
| 56 | +* Issue is a collection of open/ongoing documentation work. |
| 57 | +* Please self-assign the tasks you're (planning to be) working on. |
| 58 | + |
| 59 | +## Mailman to Discourse migration |
| 60 | + |
| 61 | +* related to issue [#6](https://github.com/llvm/llvm-iwg/issues/6) |
| 62 | +* The LLVM Foundation is investigating a potential migration from mailman to |
| 63 | + discourse |
| 64 | +* The mailing list archive would be migrated by [discourse.org](https://www.discourse.org/)} |
| 65 | + (the company behind the tool) |
| 66 | +* The Foundation would like the IWG to manage the migration and investigate |
| 67 | + how to migrate the related workflows. |
| 68 | +* we need to understand the workflows on the mailing list and figure out |
| 69 | + how that could be migrated |
| 70 | +* use cases we're aware of |
| 71 | + * discussions of community members |
| 72 | + * interaction via email |
| 73 | + * integrations with all the tools sending to the mailing list |
| 74 | +* This would be a **major** effort and require significant time investment from |
| 75 | + the working group members. For this we need explicit buy-in from enough |
| 76 | + members so we can actually manage the work load. Christian will open the |
| 77 | + discussion on the mailing list. |
0 commit comments