#meeting:fedoraproject.org: Git Forge Meeting

Meeting started by @t0xic0der:fedora.im at 08:59:29 UTC

Meeting summary

  1. 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, 08:59:52)
  2. TOPIC:Hellos and hallos (@t0xic0der:fedora.im, 09:00:03)
    1. INFO: this meeting marks the end of our two week sprint and the start of a new one (@t0xic0der:fedora.im, 09:02:00)
    2. INFO: please mark the tickets that are supposed to be reported as completed here (@t0xic0der:fedora.im, 09:02:24)
    3. LINK: https://codeberg.org/fedora/forgejo-deployment/projects/13486 (@t0xic0der:fedora.im, 09:02:27)
    4. INFO: https://codeberg.org/fedora/forgejo-deployment/issues/35 completed by @t0xic0der (@t0xic0der:fedora.im, 09:03:08)
    5. INFO: https://codeberg.org/fedora/forgejo-deployment/issues/18 completed by ryanlerch (@t0xic0der:fedora.im, 09:03:21)
    6. INFO: https://codeberg.org/fedora/forgejo-deployment/issues/40 completed by @t0xic0der (@t0xic0der:fedora.im, 09:03:33)
    7. INFO: https://codeberg.org/fedora/forgejo-deployment/issues/21 completed by ryanlerch (@t0xic0der:fedora.im, 09:03:45)
    8. INFO: https://codeberg.org/fedora/forgejo-deployment/issues/36 completed by @t0xic0der (@t0xic0der:fedora.im, 09:03:59)
    9. INFO: https://codeberg.org/fedora/forgejo-deployment/issues/39 completed by Yaash (@t0xic0der:fedora.im, 09:04:15)
    10. INFO: https://codeberg.org/fedora/forgejo-deployment/issues/38 completed by @t0xic0der (@t0xic0der:fedora.im, 09:04:27)
  3. TOPIC:rebasing atop the newly released v11.0/forgejo (@t0xic0der:fedora.im, 09:05:57)
    1. INFO: lenkaseg created https://codeberg.org/fedora/oci-image-definitions/pulls/10 (@t0xic0der:fedora.im, 09:06:06)
  4. TOPIC:decide between redis operator vs. valkey operator (@t0xic0der:fedora.im, 09:08:00)
    1. LINK: https://github.com/hyperspike/valkey-operator (@t0xic0der:fedora.im, 09:13:01)
    2. LINK: https://codeberg.org/fedora/forgejo-deployment/issues/30 (@t0xic0der:fedora.im, 09:13:25)
    3. AGREED: Start with experimenting with the valkey operator and then if needed pivot over to maintaining one by ourselves (@t0xic0der:fedora.im, 09:14:34)
    4. ACTION: David Kirwan assigned to investigate the Valkey operator (@t0xic0der:fedora.im, 09:15:51)
  5. TOPIC:RPM packaging of Forgejo (@t0xic0der:fedora.im, 09:16:22)
    1. LINK: https://codeberg.org/fedora/forgejo-deployment/issues/24 (@t0xic0der:fedora.im, 09:19:53)
    2. LINK: https://codeberg.org/fedora/forgejo-deployment/issues/16 (@t0xic0der:fedora.im, 09:20:16)
    3. 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:21:35)
    4. 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:23:42)
  6. TOPIC:actions and synchronization (@t0xic0der:fedora.im, 09:25:44)
    1. LINK: https://codeberg.org/fedora/forgejo-deployment/issues/25 (@t0xic0der:fedora.im, 09:27:29)
    2. LINK: https://codeberg.org/fedora/forgejo-deployment/issues/34 (@t0xic0der:fedora.im, 09:27:38)
    3. ACTION: lenkaseg to work on fedora/forgejo-deployment#25 and fedora/forgejo-deployment#34 (@t0xic0der:fedora.im, 09:28:10)
    4. AGREED: TASK label to be renamed to STORY label so that they can block EPICS (@t0xic0der:fedora.im, 09:32:01)
  7. TOPIC:migration, webhook integration and upstream features (@t0xic0der:fedora.im, 09:33:49)
    1. LINK: https://codeberg.org/fedora/forgejo-deployment/issues/37 (@t0xic0der:fedora.im, 09:33:56)
    2. INFO: import / export samples (@t0xic0der:fedora.im, 09:40:06)
    3. LINK: https://forgejo.apps.ocp.stg.fedoraproject.org/infrastructure/fedora-team-community-logos/issues (@t0xic0der:fedora.im, 09:40:09)
    4. LINK: https://forgejo.apps.ocp.stg.fedoraproject.org/infrastructure/fedora-team-community-logos/pulls (@t0xic0der:fedora.im, 09:40:16)
    5. LINK: https://codeberg.org/fedora/forgejo-deployment/issues/41 (@t0xic0der:fedora.im, 09:43:16)
    6. LINK: https://codeberg.org/fedora/forgejo-deployment/issues/31 (@t0xic0der:fedora.im, 09:43:31)
    7. LINK: https://codeberg.org/fedora/forgejo-deployment/issues/19 (@t0xic0der:fedora.im, 09:43:46)
    8. LINK: https://codeberg.org/fedora/forgejo-deployment/issues/14 (@t0xic0der:fedora.im, 09:43:57)
    9. ACTION: @t0xic0der to work on the issues listed above (@t0xic0der:fedora.im, 09:44:32)
  8. TOPIC:repositories that would want to move over (@t0xic0der:fedora.im, 09:45:00)
    1. LINK: https://discussion.fedoraproject.org/t/migrating-repositories-to-forgejo/149892/ (@t0xic0der:fedora.im, 09:48:18)
    2. LINK: https://codeberg.org/fedora/forgejo-deployment/issues/21 (@t0xic0der:fedora.im, 09:48:25)


Meeting ended at 09:51:12 UTC

Action items

  1. David Kirwan assigned to investigate the Valkey operator
  2. nils to add EPIC as a label/tag and assign the existing epics and potential new ones with the EPIC label triaging
  3. nils to break the RPM packaging epic down into small issue tickets and list the existing items as comments under the epic
  4. lenkaseg to work on fedora/forgejo-deployment#25 and fedora/forgejo-deployment#34
  5. @t0xic0der to work on the issues listed above


People present (lines said)

  1. @t0xic0der:fedora.im (62)
  2. @meetbot:fedora.im (2)
  3. @humaton:fedora.im (1)
  4. @zodbot:fedora.im (1)