# Image Builder

This document outlines the current and near-future responsibilities of the Image Builder team. I intentionally tried to represent the de facto, rather than the de jure state of things in order to highlight the things that are not sustainable.

## Maintenance

Each of the upstream projects that we rely on must have a sustainable plan for long-term maintainership. It is easy to start projects and consider them done when they reach their MVP, but maintaining a project is a long-term commitment and we cannot depend on abandonware.

The maintainers listed below has the final say on design decisions in the components they own, and what code is merged into them. And is ultimately responsible for project health.

Where applicable the components need to be regularly released into Fedora, CentOS Stream and RHEL. We must package each bi-weekly release, and triage incoming bug reports. Packaging is currently done by the maintaniers mentioned below, but bug triage is mostly best-effort.

### osbuild

Released into Fedora, CentOS Stream and RHEL.

Maintained by Christian.

### osbuild-composer

Released into Fedora, CentOS Stream and RHEL.

Also contains `osbuild-worker`, which might belong in its own project. Serves three distinct use-cases, with one API each:
- `weldr` --- used on-prem
- `cloud` --- used from cloudDot
- `koji` --- used by Koji/Brew

It might make sense to split responsibility based on use-cases.

Maintained by Ondřej.

### image-types

Currently part of `osbuild-composer`, might want to be split out into a sub-package. Ideally should be possible to develop in lock-step with `osbuild`, and be useable outside of `osbuild-composer`. Ideally (in some cases) the image types should be defined in the distro they belong to, following the life-cycle and policies of the RPMs.

Maintenance needs discussion.

### osbuild-koji

Released into Fedora and an internal brew tag.

Mainatined by Christian.

### cockpit-composer

Released into Fedora, CentOS Stream and RHEL.

Should ideally move closer to `image-builder-frontend`, but both will likely continue to serve their distinct use-cases long-term.

Maintained by Jacob.

### composer-cli

Released into Fedora, CentOS Stream and RHEL.

The project might be replaced by RHEL9, but under the same maintainership.

Maintained by Brian.

### image-builder

Maintained by Sanne.

### image-builder-frontend

Maintained by Sanne.

### schutzbot

Our CI system, used for most of our comopenent, also in part reused for downstream gating.

Maintained by Ondřej, moving to being maintainded by QE?

### rpmrepos

Maintained by David, who is on paternity leave.

### imagebuilder-packer

Needs discussion. Move to `osbuild-composer`, eventually to AppSRE?

### imagebuilder-terraform

Needs discussion. Eventually move to AppSRE?

### osbuild.org

Maintained by David, who is on paternity leave.

### rhel-guest-image-container

Provides the rhel-guste-image in a container for use by CNV. Currently maintained by Tom, need to hand it off.

## Deployment

### image-builder-frontend

Maintained by Sanne.

### image-builder

Maintained by Sanne.

### osbuild-composer

Maintained by Ondřej.

### osbuild-workers-internal

Maintained by Ondřej.

### osbuild-workers-external

Maintained by Ondřej.

## Initiatives

In addition to ongoing maintanenca work, we also have fixed-term projects. These things are more flexible, and will invariable change as

### Edge

Tom agrees on feature priorities with the RHEL BU and works closely with Christian and Achilleas on execution.

### Automotive

Tom agrees on feature priorities with the RHEL BU and works closely with Christian on execution.

### RHEL compose

Tom agrees on feature priorities with EXD / RHEL PO and works closely with Ondřej and Tomas on execution.

### CentOS compose

Tom leading initial discussions with CPE. Ideally their koji instance would have support for speaking with composer in cloud.redhat.com, using our `koji` api.

### Fedora compose

Ditto.

### CoreOS

Needs discussion.

## Engagements

Finally we have ongoing engagements with outside stakeholders.

### RHEL program

Ondřej is the SST lead, and reports to the RHEL program.

### Insights program

Lars reports to the Insights program.

### AppSRE

Lars works with Service Delivery on our on-boarding.

### RHEL BU

Tom works with the RHEL BU to prioritize features for both our service and on-prem offerings.

### QE

Ondřej leads our QE engagement.

### Docs

Lars and Sanne lead our Docs engagement.

### Support

Tom leads our CEE engagement.

### Engineering Leadership

Lars and Tom engage with Stef.