#meeting:fedoraproject.org log

<@t0xic0der:fedora.im>

08:59:29

!startmeeting Git Forge Meeting

<@meetbot:fedora.im>

08:59:31

Meeting started at 2025-04-23 08:59:29 UTC

<@meetbot:fedora.im>

08:59:31

The Meeting name is 'Git Forge Meeting'

<@t0xic0der:fedora.im>

08:59:52

!info this is meeting about the Fedora git forge replacement this meeting template can be found at https://codeberg.org/fedora/gitforge-migration

<@t0xic0der:fedora.im>

09:00:03

!topic Hellos and hallos

<@t0xic0der:fedora.im>

09:00:38

!hi

<@zodbot:fedora.im>

09:00:39

Akashdeep Dhar (t0xic0der) - he / him / his

<@t0xic0der:fedora.im>

09:00:49

Hoi Kamil Páral ! 👋

<@t0xic0der:fedora.im>

09:02:00

!info this meeting marks the end of our two week sprint and the start of a new one

<@humaton:fedora.im>

09:02:13

<@t0xic0der:fedora.im>

09:02:24

!info please mark the tickets that are supposed to be reported as completed here

<@t0xic0der:fedora.im>

09:02:27

!link https://codeberg.org/fedora/forgejo-deployment/projects/13486

<@t0xic0der:fedora.im>

09:03:08

!info https://codeberg.org/fedora/forgejo-deployment/issues/35 completed by @t0xic0der

<@t0xic0der:fedora.im>

09:03:21

!info https://codeberg.org/fedora/forgejo-deployment/issues/18 completed by ryanlerch

<@t0xic0der:fedora.im>

09:03:33

!info https://codeberg.org/fedora/forgejo-deployment/issues/40 completed by @t0xic0der

<@t0xic0der:fedora.im>

09:03:45

!info https://codeberg.org/fedora/forgejo-deployment/issues/21 completed by ryanlerch

<@t0xic0der:fedora.im>

09:03:59

!info https://codeberg.org/fedora/forgejo-deployment/issues/36 completed by @t0xic0der

<@t0xic0der:fedora.im>

09:04:15

!info https://codeberg.org/fedora/forgejo-deployment/issues/39 completed by Yaash

<@t0xic0der:fedora.im>

09:04:27

!info https://codeberg.org/fedora/forgejo-deployment/issues/38 completed by @t0xic0der

<@t0xic0der:fedora.im>

09:04:56

That is all that was done in this sprint - Clearing up the board for more excitement to come in the next couple of weeks

<@t0xic0der:fedora.im>

09:05:57

!topic rebasing atop the newly released v11.0/forgejo

<@t0xic0der:fedora.im>

09:06:06

!info lenkaseg created https://codeberg.org/fedora/oci-image-definitions/pulls/10

<@t0xic0der:fedora.im>

09:08:00

!topic decide between redis operator vs. valkey operator

<@t0xic0der:fedora.im>

09:08:30

David Kirwan states that there is a Redis operator that exists at the moment but the Valkey operator needs to be looked into

<@t0xic0der:fedora.im>

09:09:07

nils wonders if the Redis licensing problem (source available vs. open source) is resolved before looking into exploring that area

<@t0xic0der:fedora.im>

09:09:43

As Valkey is nearly a drop-in replacement to Redis, we can start experimenting with the more readily available Redis operator before switching over to Valkey

<@t0xic0der:fedora.im>

09:12:46

David Kirwan: states that if Valkey operator does not exist then we'd have to work on maintaining the operator in the long run (if it does not exist(

<@t0xic0der:fedora.im>

09:13:01

!link https://github.com/hyperspike/valkey-operator

<@t0xic0der:fedora.im>

09:13:25

!link https://codeberg.org/fedora/forgejo-deployment/issues/30

<@t0xic0der:fedora.im>

09:14:34

!agreed Start with experimenting with the valkey operator and then if needed pivot over to maintaining one by ourselves

<@t0xic0der:fedora.im>

09:15:51

!action David Kirwan assigned to investigate the Valkey operator

<@t0xic0der:fedora.im>

09:16:22

!topic RPM packaging of Forgejo

<@t0xic0der:fedora.im>

09:16:52

Macro defined build flags cannot be injected into the Makefiles because of the quoting issues and hence, that has introduced some complications in the building

<@t0xic0der:fedora.im>

09:17:28

Resorting to running commands manually using the Go2RPM Macros and that would potentially need looking into should hte build stages change down the road

<@t0xic0der:fedora.im>

09:19:09

nils would be willing to look into the private issue tickets feature once the RPM packaging thing is resolved

<@t0xic0der:fedora.im>

09:19:53

!link https://codeberg.org/fedora/forgejo-deployment/issues/24

<@t0xic0der:fedora.im>

09:20:16

!link https://codeberg.org/fedora/forgejo-deployment/issues/16

<@t0xic0der:fedora.im>

09:21:35

!action nils to add EPIC as a label/tag and assign the existing epics and potential new ones with the EPIC label triaging

<@t0xic0der:fedora.im>

09:23:42

!action nils to break the RPM packaging epic down into small issue tickets and list the existing items as comments under the epic

<@t0xic0der:fedora.im>

09:25:44

!topic actions and synchronization

<@t0xic0der:fedora.im>

09:27:29

!link https://codeberg.org/fedora/forgejo-deployment/issues/25

<@t0xic0der:fedora.im>

09:27:38

!link https://codeberg.org/fedora/forgejo-deployment/issues/34

<@t0xic0der:fedora.im>

09:28:10

!action lenkaseg to work on fedora/forgejo-deployment#25 and fedora/forgejo-deployment#34

<@t0xic0der:fedora.im>

09:32:01

!agreed TASK label to be renamed to STORY label so that they can block EPICS

<@t0xic0der:fedora.im>

09:33:49

!topic migration, webhook integration and upstream features

<@t0xic0der:fedora.im>

09:33:56

!link https://codeberg.org/fedora/forgejo-deployment/issues/37

<@t0xic0der:fedora.im>

09:34:26

It was suggested by gotmax23 that we have a native Forgejo support for the exports done from Pagure to preserve more metadata

<@t0xic0der:fedora.im>

09:34:52

While it won't serve any purpose beyond the major deployment of Pagure that is in Fedora Project, it is a more elegant appraoch

<@t0xic0der:fedora.im>

09:35:59

Pagure Exporter is forge agnostic in nature and hence, a lot of information can be lost (or kept in a different form) as a result

<@t0xic0der:fedora.im>

09:37:40

Zlopez states that we are better off using something that is more tightly bound to the Git Forge system to avoid custom rollouts

<@t0xic0der:fedora.im>

09:39:07

nils states More intimate support can help with avoiding the abstraction layer that cannot cover all the conditions and scenarios of exporting process

<@t0xic0der:fedora.im>

09:40:06

!info import / export samples

<@t0xic0der:fedora.im>

09:40:09

!link https://forgejo.apps.ocp.stg.fedoraproject.org/infrastructure/fedora-team-community-logos/issues

<@t0xic0der:fedora.im>

09:40:16

!link https://forgejo.apps.ocp.stg.fedoraproject.org/infrastructure/fedora-team-community-logos/pulls

<@t0xic0der:fedora.im>

09:41:09

These have been exported from GitLab by ryanlerch using the internal Forgejo exporting tooling so this might be worth looking into

<@t0xic0der:fedora.im>

09:42:24

nils states that we do not stand to lose much metadata if we were to use a Forge Agnostic Pagure Exporter, it just changes form and not creates ghost users etc.

<@t0xic0der:fedora.im>

09:43:16

!link https://codeberg.org/fedora/forgejo-deployment/issues/41

<@t0xic0der:fedora.im>

09:43:31

!link https://codeberg.org/fedora/forgejo-deployment/issues/31

<@t0xic0der:fedora.im>

09:43:46

!link https://codeberg.org/fedora/forgejo-deployment/issues/19

<@t0xic0der:fedora.im>

09:43:57

!link https://codeberg.org/fedora/forgejo-deployment/issues/14

<@t0xic0der:fedora.im>

09:44:32

!action @t0xic0der to work on the issues listed above

<@t0xic0der:fedora.im>

09:45:00

!topic repositories that would want to move over

<@t0xic0der:fedora.im>

09:48:18

!link https://discussion.fedoraproject.org/t/migrating-repositories-to-forgejo/149892/

<@t0xic0der:fedora.im>

09:48:25

!link https://codeberg.org/fedora/forgejo-deployment/issues/21

<@t0xic0der:fedora.im>

09:48:40

ryanlerch has opened up the list of repos to move over for the community feedback

<@t0xic0der:fedora.im>

09:51:12

!endmeeting