---
# System prepended metadata

title: Untitled

---

            # Meeting #3 for Fedora Source-git SIG

## Intro

malmond: the context for Matthew to join the SIG is for maintenance of Facebook's "forks" of mostly CentOS packages and those could be early adopters

Justin: Rebasing on top of upstream history regularly makes it hard to contribute for outsiders. Rebase invalidates merge requests because history is rewritten.
Justin: kernel-ark solves this to use Linus' tree in rawhide
 * there is an os-build branch for daily development which is being merged daily
 * the spec file is being generated via a make file
 * stable kernels are being branched from Greg's tree, with a fedora-5.x tree for fedora changes. Greg's branch is merged on releases.
 * Upstream tarballs are generated from the upstream git tree in clean and verifiable ways
 * Due to merge, fedora specific patches are a single patchball diff, but we generate a patch list with git commit hashes so that people can see what we carry and why.
 * https://cki-project.gitlab.io/kernel-ark/

Workflow proposal from Hunor: https://pagure.io/fedora-source-git/docs/pull-request/2

What would be the timeline to implement git-hooks in pagure so we could gate changes to be merged.

Direct pushes can still trigger CI, but we cannot abort the push on GitLab.

Restrict pushing vs. pulls only.

We still need to do force-pushes for sake of rebasing against upstream.

Our long-term plan is to build in koji directly from source-git and "bypass" dist-git for production builds.

Action item: we can try create source-git repos for "rpm" ( https://git.centos.org/rpms/rpm/tree/c8s-sig-hyperscale-experimental )
 * docs: https://packit.dev/docs/cli/init/
Action item: assess if pagure.io is really a feasible place to host the repos: catch up with Neal