2025-04-23 08:59:29 <@t0xic0der:fedora.im> !startmeeting Git Forge Meeting
2025-04-23 08:59:31 <@meetbot:fedora.im> Meeting started at 2025-04-23 08:59:29 UTC
2025-04-23 08:59:31 <@meetbot:fedora.im> The Meeting name is 'Git Forge Meeting'
2025-04-23 08:59:52 <@t0xic0der:fedora.im> !info this is meeting about the Fedora git forge replacement this meeting template can be found at https://codeberg.org/fedora/gitforge-migration
2025-04-23 09:00:03 <@t0xic0der:fedora.im> !topic Hellos and hallos
2025-04-23 09:00:38 <@t0xic0der:fedora.im> !hi
2025-04-23 09:00:39 <@zodbot:fedora.im> Akashdeep Dhar (t0xic0der) - he / him / his
2025-04-23 09:00:49 <@t0xic0der:fedora.im> Hoi Kamil Páral ! 👋
2025-04-23 09:02:00 <@t0xic0der:fedora.im> !info this meeting marks the end of our two week sprint and the start of a new one 
2025-04-23 09:02:13 <@humaton:fedora.im> o/
2025-04-23 09:02:24 <@t0xic0der:fedora.im> !info please mark the tickets that are supposed to be reported as completed here 
2025-04-23 09:02:27 <@t0xic0der:fedora.im> !link https://codeberg.org/fedora/forgejo-deployment/projects/13486
2025-04-23 09:03:08 <@t0xic0der:fedora.im> !info https://codeberg.org/fedora/forgejo-deployment/issues/35 completed by @t0xic0der
2025-04-23 09:03:21 <@t0xic0der:fedora.im> !info https://codeberg.org/fedora/forgejo-deployment/issues/18 completed by ryanlerch 
2025-04-23 09:03:33 <@t0xic0der:fedora.im> !info https://codeberg.org/fedora/forgejo-deployment/issues/40 completed by @t0xic0der
2025-04-23 09:03:45 <@t0xic0der:fedora.im> !info https://codeberg.org/fedora/forgejo-deployment/issues/21 completed by ryanlerch 
2025-04-23 09:03:59 <@t0xic0der:fedora.im> !info https://codeberg.org/fedora/forgejo-deployment/issues/36 completed by @t0xic0der
2025-04-23 09:04:15 <@t0xic0der:fedora.im> !info https://codeberg.org/fedora/forgejo-deployment/issues/39 completed by Yaash 
2025-04-23 09:04:27 <@t0xic0der:fedora.im> !info https://codeberg.org/fedora/forgejo-deployment/issues/38 completed by @t0xic0der
2025-04-23 09:04:56 <@t0xic0der:fedora.im> That is all that was done in this sprint - Clearing up the board for more excitement to come in the next couple of weeks
2025-04-23 09:05:57 <@t0xic0der:fedora.im> !topic rebasing atop the newly released v11.0/forgejo
2025-04-23 09:06:06 <@t0xic0der:fedora.im> !info lenkaseg created https://codeberg.org/fedora/oci-image-definitions/pulls/10
2025-04-23 09:08:00 <@t0xic0der:fedora.im> !topic decide between redis operator vs. valkey operator
2025-04-23 09:08:30 <@t0xic0der:fedora.im> David Kirwan states that there is a Redis operator that exists at the moment but the Valkey operator needs to be looked into 
2025-04-23 09:09:07 <@t0xic0der:fedora.im> nils wonders if the Redis licensing problem (source available vs. open source) is resolved before looking into exploring that area
2025-04-23 09:09:43 <@t0xic0der:fedora.im> 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
2025-04-23 09:12:46 <@t0xic0der:fedora.im> 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(
2025-04-23 09:13:01 <@t0xic0der:fedora.im> !link https://github.com/hyperspike/valkey-operator
2025-04-23 09:13:25 <@t0xic0der:fedora.im> !link https://codeberg.org/fedora/forgejo-deployment/issues/30
2025-04-23 09:14:34 <@t0xic0der:fedora.im> !agreed Start with experimenting with the valkey operator and then if needed pivot over to maintaining one by ourselves 
2025-04-23 09:15:51 <@t0xic0der:fedora.im> !action David Kirwan assigned to investigate the Valkey operator 
2025-04-23 09:16:22 <@t0xic0der:fedora.im> !topic RPM packaging of Forgejo
2025-04-23 09:16:52 <@t0xic0der:fedora.im> 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
2025-04-23 09:17:28 <@t0xic0der:fedora.im> Resorting to running commands manually using the Go2RPM Macros and that would potentially need looking into should hte build stages change down the road
2025-04-23 09:19:09 <@t0xic0der:fedora.im> nils would be willing to look into the private issue tickets feature once the RPM packaging thing is resolved 
2025-04-23 09:19:53 <@t0xic0der:fedora.im> !link https://codeberg.org/fedora/forgejo-deployment/issues/24
2025-04-23 09:20:16 <@t0xic0der:fedora.im> !link https://codeberg.org/fedora/forgejo-deployment/issues/16
2025-04-23 09:21:35 <@t0xic0der:fedora.im> !action nils to add EPIC as a label/tag and assign the existing epics and potential new ones with the EPIC label triaging
2025-04-23 09:23:42 <@t0xic0der:fedora.im> !action nils to break the RPM packaging epic down into small issue tickets and list the existing items as comments under the epic
2025-04-23 09:25:44 <@t0xic0der:fedora.im> !topic actions and synchronization
2025-04-23 09:27:29 <@t0xic0der:fedora.im> !link https://codeberg.org/fedora/forgejo-deployment/issues/25
2025-04-23 09:27:38 <@t0xic0der:fedora.im> !link https://codeberg.org/fedora/forgejo-deployment/issues/34
2025-04-23 09:28:10 <@t0xic0der:fedora.im> !action lenkaseg to work on fedora/forgejo-deployment#25 and fedora/forgejo-deployment#34
2025-04-23 09:32:01 <@t0xic0der:fedora.im> !agreed TASK label to be renamed to STORY label so that they can block EPICS
2025-04-23 09:33:49 <@t0xic0der:fedora.im> !topic migration, webhook integration and upstream features
2025-04-23 09:33:56 <@t0xic0der:fedora.im> !link https://codeberg.org/fedora/forgejo-deployment/issues/37
2025-04-23 09:34:26 <@t0xic0der:fedora.im> It was suggested by gotmax23 that we have a native Forgejo support for the exports done from Pagure to preserve more metadata
2025-04-23 09:34:52 <@t0xic0der:fedora.im> While it won't serve any purpose beyond the major deployment of Pagure that is in Fedora Project, it is a more elegant appraoch
2025-04-23 09:35:59 <@t0xic0der:fedora.im> 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
2025-04-23 09:37:40 <@t0xic0der:fedora.im> Zlopez states that we are better off using something that is more tightly bound to the Git Forge system to avoid custom rollouts
2025-04-23 09:39:07 <@t0xic0der:fedora.im> nils states More intimate support can help with avoiding the abstraction layer that cannot cover all the conditions and scenarios of exporting process
2025-04-23 09:40:06 <@t0xic0der:fedora.im> !info import / export samples
2025-04-23 09:40:09 <@t0xic0der:fedora.im> !link https://forgejo.apps.ocp.stg.fedoraproject.org/infrastructure/fedora-team-community-logos/issues
2025-04-23 09:40:16 <@t0xic0der:fedora.im> !link https://forgejo.apps.ocp.stg.fedoraproject.org/infrastructure/fedora-team-community-logos/pulls
2025-04-23 09:41:09 <@t0xic0der:fedora.im> These have been exported from GitLab by ryanlerch using the internal Forgejo exporting tooling so this might be worth looking into
2025-04-23 09:42:24 <@t0xic0der:fedora.im> 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.
2025-04-23 09:43:16 <@t0xic0der:fedora.im> !link https://codeberg.org/fedora/forgejo-deployment/issues/41
2025-04-23 09:43:31 <@t0xic0der:fedora.im> !link https://codeberg.org/fedora/forgejo-deployment/issues/31
2025-04-23 09:43:46 <@t0xic0der:fedora.im> !link https://codeberg.org/fedora/forgejo-deployment/issues/19
2025-04-23 09:43:57 <@t0xic0der:fedora.im> !link https://codeberg.org/fedora/forgejo-deployment/issues/14
2025-04-23 09:44:32 <@t0xic0der:fedora.im> !action @t0xic0der to work on the issues listed above
2025-04-23 09:45:00 <@t0xic0der:fedora.im> !topic repositories that would want to move over 
2025-04-23 09:48:18 <@t0xic0der:fedora.im> !link https://discussion.fedoraproject.org/t/migrating-repositories-to-forgejo/149892/
2025-04-23 09:48:25 <@t0xic0der:fedora.im> !link https://codeberg.org/fedora/forgejo-deployment/issues/21
2025-04-23 09:48:40 <@t0xic0der:fedora.im> ryanlerch has opened up the list of repos to move over for the community feedback
2025-04-23 09:51:12 <@t0xic0der:fedora.im> !endmeeting