---
# System prepended metadata

title: 'Community Gathering, January 6, 2023'
tags: [' community', unikraft]

---

---
title: "Community Gathering, January 6, 2023"
tags: unikraft, community
datetime: 2023-01-06T14:00:00+02:00
location: Online, Discord (https://bit.ly/UnikraftDiscord), the `#monkey-business` voice channel
teams:
- community
participants:
- AlexJ
- Cezar
- Gabi
- Maria
- Sairaj
- Luca
- Sergiu
- ȘtefanJ
- Vlad
- Delia
- RăzvanD
- RaduNichita
- RăzvanV
---

## :dart: Agenda

- Community updates: events, meetings, FOSDEM'23, GSoC'23
- 3 month OSS goals
- Higher-level goals (2023), OSS Roadmap
- Keeping track of OSS work
- Planning for the 0.12 release
- Status updates
   - Documentation
   - App Compatibility (including Binary Compatibility, ELF Loader)
   - VMM
   - Bootloaders
   - Rust
   - SMP, synchronization
   - Plat rearchitecting
   - Clang
   - Security
   - Benchmarking, profiling, introspection
   - Kraftkit
   - CI/CD, governance
   - fdtab
   - mmap
   - uksignal
   - Fixing ELF
   - virtio / vsock
   - others
- Demo: Using `gh` CLI interface (for GitHub)

## :closed_book: Discussions

### Community Updates

Hackathon, Saturday, January 14, 2023, full day (online)

FOSDEM'23: February 4-5, 2023, Brussels

GitHub Accelerator

GSoC'23. deadline: February 7, 2023

CloudFest: March 2023, hackathon on Unikraft Security

Athens, March 30-31, 2023

Amsterdam, Vancouver, Haifa, Porto, Aveiro

Tutorial, OSDI, October 2023 (Pramod Bhahotia - Munich, October 2023)

Xen Summit at UPB, June 2023 (workshop)

USoC'23

Focus more on building, high-level aspects of Unikraf / kraft in USoC

### 3 Month OSS Goals

Community feedback form (to be filled yearly)

Constant feedback form

Advance kraftkit as the prime tool for users, testers;
and ideally, for some development work

Re-design community meetings to make them more participative: demos, questions
  - Make it office hours
  - Show & tell (as demo)
  - Distinct meeting times
  - Bi-weekly meeting for office hours (30 minutes)

Organize monthly hackathons (one Saturday per month)

Improve hackathon contents
  - making content work from the start
  - improve the hackathon tasks
  - think of prizes / awards

Start organizing USoC'23

Organize GSoC'23

Document internal libraries

### Higher-level Goals

Constant progress in adding new libraries and applications in the Unikraft ecosystem: native and binary compatibile

New release plan: a release every 3 months, 2 week feature freeze window before hand

Improvements / updates to governance / CI/CD to automate integration, static checking, integration testing, workflows

Integration testing, new branch model (`stable`, `staging`), `uktest` for all internal libraries

Handling of upstream application / libraries version

Increase platform support (Firecracker, Hyper-V, VMware, GCP, CloudVM)

Recruiting track owners, people to ensure technical progress on different areas of the Unikraft ecosystem

### Community Guidelines

Make sure people know what you are working on.
Be verbose about your work.
Others may be doing the same and duplicate the effort.
Create early draft PRs.

Take the initiative: come up with proposals, voice concerns, provide your input, be critical, be assertive, take charge, ask for ownership.

Ask for help: no one knows everything.
Don't be afraid / ashamed / reluctat to ask, even stupid questions.

Provide support: when someone asks for help, if you have the time and knowledge, help them.

You have a great responsibility as a reviewer.
Take good care of items you are a reviewer of.
Be rigurous: test everything, make sure you understand, make sure the solution is sound, make sure the design is sound.
Be considerate: provide constructive feedback, accept that someone may be a beginner and still making the first steps on contributing.
Perfection is achieved through iteration.
It's OK and expected to do do multiple review rounds.

As a reviewer, have a review day per week.

As a contributor, your contributions are valued and appreciated.
Be aware that getting someting in may take a while.
Make that easy by following the contributors guidelines, providing good quality commits and sound design.
Be aware that a good reviewer will ask for even minor updates; it's expected, we value code quality.
Create early draft PRs.

### Keeping Track of OSS Work

People: https://docs.google.com/spreadsheets/d/10DuQCr6c65Lr2Q55LzoKTnadJz8rcs4L2u0CMDR7CvM/edit#gid=0

GitHub projects: https://github.com/orgs/unikraft/projects

Community Roadmap: https://github.com/orgs/unikraft/projects/30/views/10

### 0.12 Release

Scheduled for Monday, January 23, 2023.

0.12 GitHub projects: https://github.com/orgs/unikraft/projects/24/views/33

### Status updates

Postponed for next meeting

### Demo: Using the `gh` CLI Interface

Demo recording on YouTube: https://youtu.be/xqjXbanCTrU

## :wrench: TODOs and Decisions

RD/AJ: Post on social media on Unikraft hackathon happening on Saturday, January 14, 2023.

RD: Arrange unikernel dinner at Brussels.

RD: Create yearly feedback form.

RD: Create constant feedback form.

RD: Organize separate "office hours" meeting.

Community leaders: Fill items in the community roadmap: https://github.com/orgs/unikraft/projects/30/views/10

All: Work towards the 0.12 release.

All: Consider track ownership positions in the community.

TODO: Find place to post community guidelines / pledge.
Probably on the documentation website.