---
# System prepended metadata

title: 'Community Meeting, September 22, 2022'
tags: [' community', unikraft]

---

---
title: Community Meeting, September 22, 2022
tags: unikraft, community
datetime: 2022-09-22T17:00:00+02:00
location: Online, Discord (https://bit.ly/UnikraftDiscord), the `#monkey-business` voice channel
teams:
- community
participants:
- TODO
---

## :dart: Agenda

- Community updates: GSoC, community leaders, hackathons, release schedule
- Musl update
- Kraftkit update
- Walkthrough of PRs to be ready for release 0.11: https://github.com/unikraft/unikraft/pulls

## :closed_book: Discussions

CC: Maybe people don't have anything to say.

CC: We could mark some important tag to some meetings.

RD: Aim to make meetings more democratic and engaging.

CC: PR walking should happen once a month.

AJ: Add someone to present what they're working on.
This could open up a more open-table discussion.

CC: People doing blog posts.

MS: Meetings seem quite formal.
And with multiple difficult items, it's difficult to have a good grasp of the discussion.

AJ: Community gatherings are open to everyone.

### Kraftkit

AJ: Kraftkit is about to reach parity with kraft.

AJ: It's using the QAPI for QEMU, via a JSON-based protocol.

AJ: Hopefully, next week I will start getting together the PRs.

### Musl

FP: I added a custom rule to the libc-test repository.
I still need to get input from Simon.

AJ: Every new PR is getting on `staging-musl`.
Otherwise, we would have to cherry pick commits from `staging` and from `staging-musl`.

FP: At the moment, the `libc-test` repository is working on Musl.
Then it will be ported to other libc parts as well.

RK: I didn't do anything on Musl.

MS: I have some question to ask Simon about requirements.

## :wrench: TODOs and Decisions

FP: I will look on the Musl PR for threading.

RD: Create GSoC folder to store work products for GSoC participants.