Hi all,

here are the meeting minutes from today's meeting (in rendered form): https://md.archlinux.org/s/nqqUhLHQ6

Below the plain markdown version:

``` # 2022-10-26 repod meeting

Date: 2022-10-26T17:00:00Z - 18:00:00Z Location: Jitsi Scribe: dvzrv

## Attendees

* dvzrv * prawn * polyzen * wCPO

## Agenda

### Community outreach

We sent [a mail](https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.or...) about the internal Arch Linux projects and got one contributor in return! \o/

### Fixing flaky tests that are flaky

Took only three(!) merge requests to finally fix a flaky test...

### Write empty sync databases for empty repositories

We are now able to also write empty sync databases for empty repositories [!125](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/125) and [!127](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/127).

### Refactor CLI module

The CLI now does not use Tasks and Checks directly anymore, but instead relies upon functions from the `repod.action.workflow` module [!126](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/126).

### Import in bulk in integration tests

Circumvent an issue with "newer/ already existing" packages in integration tests, by importing in bulk instead [!128](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/128).

### Use schema_version throughout the codebase

We now use `schema_version` for the versioning of objects everywhere [!129](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/129) (thanks Isaac!).

### Track source URL per pkgbase in management repository

We are now able to track source URLs (the location where package sources live) per pkgbase. This allows for configuration of a specific set of allowed URLs against which a new package's URL must match [!130](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/130). Existing URLs in the management repository are reused if none are provided.

In the future we want to also allow updating/ changing the URL separately from a package addition.

### Use debug repositories per stability layer

We can now define debug repositories per stability layer (stable, staging, testing) for each repository [!133](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/133). This allows to have a correct handling of debug packages per repository and the moving of packages between repositories.

### Check filename against contained metadata

Work has started to check whether the filename of a given consumed file matches the metadata retrieved from it (e.g. `foo-1:1.0.0-1-any.pkg.tar.zst`) [!132](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/132).

### Outstanding milestone 0.3.0 work

* The communication with e.g. forges (with or without APIs), providing package sources ([#120](https://gitlab.archlinux.org/archlinux/repod/-/issues/120) and [#118](https://gitlab.archlinux.org/archlinux/repod/-/issues/118)) needs investigation. Help is much appreciated! * Workflows for further actions need to be defined (e.g. remove [140](https://gitlab.archlinux.org/archlinux/repod/-/issues/140) and move [#141](https://gitlab.archlinux.org/archlinux/repod/-/issues/141)) and implemented. Investigating good approaches and the required checks when moving/removing is much appreciated! * Ensure that a repository is self-contained [#142](https://gitlab.archlinux.org/archlinux/repod/-/issues/142) and make this configurable (can already be hooked into existing "add packages" workflow and is a fairly easy topic). * The workflows need to be extended/ adapted to support bulk actions across repositories (e.g. "move 10 packages from testing to core and 20 packages from community-testing to community in one action") [#145](https://gitlab.archlinux.org/archlinux/repod/-/issues/145), but we currently only support bulk actions per-repository (e.g. "add these 20 packages to that repository"). To deal with this in a sane manner, we need someone to investigate how to do this via the CLI (maybe even define a separate plaintext file input format, defining sources and targets - e.g. what was discussed in https://md.archlinux.org/s/mH-Nb_oOD). * Documentation documentation documentation [#144](https://gitlab.archlinux.org/archlinux/repod/-/issues/144) ```

Best, David