---
# System prepended metadata

title: 'Kraft WG, January 25, 2023'
tags: [' kraft', unikraft]

---

---
title: "Kraft WG, January 25, 2023"
tags: unikraft, kraft
datetime: 2023-01-25T12:30:00+02:00
location: Online, Discord (https://bit.ly/UnikraftDiscord), the `#monkey-business` voice channel
teams:
- kraft
participants:
- TODO
---

## :dart: Agenda

- Status update
- Next steps

## :closed_book: Discussions

AJ: I posted a snippet of what the Kraftfile could look like.
This should be possible to use locally.
This is to be used by people building library locally.

AJ: I did a re-factor PR.

CC: Cezar is looking through the re-factor.

AJ: The re-factor is closely related to the OCI features for packaging.

AJ: The networking support is a complicated topic.
Cezar has been bringing all items in one place.

AJ: Once we have these in place, we can do networking.
Likely end of February.

RD: What about ditching libgit2?

AJ: Cezar is now looking into it, because he also got frustrated with it.

CC: Review the re-factor PR from Alex.

LS: I started looking into what compose-go does for serializing.
Apart from their types having a marshaling method, I'm not sure what to look into.
There's a huge specification of what the YAML files should look for.

AJ: The approach is to have a `marshal_yaml()` method as part of every component.
Maybe a `marshal_maps` structure.

AJ: Do also look into the inside of kraftkit `config` directories.
What if the user has custom line spacing and comments?
There needs to be a way to keep that information.

AJ: A good first step is to use my branch and add a `marshal_yaml()` and `marshal_map()` interface to each component.

## :wrench: TODOs and Decisions

TODO