#meeting:fedoraproject.org log

<@humaton:fedora.im>

14:00:14

!startmeeting Git Forge Meeting

<@meetbot:fedora.im>

14:00:15

Meeting started at 2025-01-29 14:00:14 UTC

<@meetbot:fedora.im>

14:00:15

The Meeting name is 'Git Forge Meeting'

<@smilner:fedora.im>

14:00:16

🥱👋

<@smilner:fedora.im>

14:00:27

!hi

<@zodbot:fedora.im>

14:00:28

None (smilner)

<@Zlopez:matrix.org>

14:00:36

!hi

<@zodbot:fedora.im>

14:00:39

Michal Konecny (zlopez)

<@blc:fedora.im>

14:00:45

!hi

<@ekidney:matrix.org>

14:00:45

!hi

<@zodbot:fedora.im>

14:00:46

Brendan Conoboy (blc)

<@zodbot:fedora.im>

14:00:48

emma kidney (ekidney) - she / her / hers

<@humaton:fedora.im>

14:00:49

!info this is meeting about the Fedora git forge replacement

<@humaton:fedora.im>

14:00:56

!topic init

<@amoloney:fedora.im>

14:01:29

!hi

<@zodbot:fedora.im>

14:01:32

Aoife Moloney (amoloney)

<@james:fedora.im>

14:03:19

!hi

<@zodbot:fedora.im>

14:03:20

James Antill (james)

<@humaton:fedora.im>

14:05:54

hello and welcome everybody

<@humaton:fedora.im>

14:06:11

!topic Meeting structure

<@humaton:fedora.im>

14:06:26

!link https://codeberg.org/fedora/gitforge-migration/src/branch/main/meeting.md

<@humaton:fedora.im>

14:06:48

I have updated the structure and included feedback from the last week

<@lenkaseg:fedora.im>

14:07:32

!hi

<@zodbot:fedora.im>

14:07:34

Lenka Segura (lenkaseg)

<@nphilipp:fedora.im>

14:07:40

!hi

<@zodbot:fedora.im>

14:07:41

Nils Philippsen (nphilipp) - he / him / his

<@humaton:fedora.im>

14:09:18

if there is any additional sections or other feedback for the meeting structure. Speak now or open ticket in in associated tracker.

<@humaton:fedora.im>

14:10:09

!topic Tickets and Updates

<@humaton:fedora.im>

14:10:12

!info go over tickets and updates

<@humaton:fedora.im>

14:10:20

!link https://pagure.io/fedora-infra/forgejo-deployment/issues

<@humaton:fedora.im>

14:11:05

!link https://pagure.io/fedora-infra/forgejo-deployment/issue/1

<@humaton:fedora.im>

14:11:29

So I have updated the pipeline and it no longer fails and it builds upstream development branch

<@smilner:fedora.im>

14:11:35

<3 we have "Definition of Done" listed!

<@humaton:fedora.im>

14:12:38

I am not goingo to make anything "done" that is a demo for other people o pickup and build upon.

<@humaton:fedora.im>

14:12:56

I am not going to make anything "done" that is a demo for other people o pickup and build upon.

<@humaton:fedora.im>

14:13:49

this is how new pipeline is created

<@humaton:fedora.im>

14:13:51

!link https://github.com/fedora-infra/forgejo-deployment-images/pull/3

<@humaton:fedora.im>

14:15:42

anyway info is in the ticket if anybody want to play with konflux and building forgejo fell free to do so.

<@humaton:fedora.im>

14:16:15

!topic forgejo-deployment/issue/7

<@humaton:fedora.im>

14:16:18

!link https://pagure.io/fedora-infra/forgejo-deployment/issue/7

<@humaton:fedora.im>

14:16:49

so we need a voulenteer that will generate the spec file and start package review process

<@humaton:fedora.im>

14:17:25

once the review is started we will have a place to point go community from around the project to help us out.

<@nphilipp:fedora.im>

14:17:33

I volunteer either for that, or doing the review

<@Zlopez:matrix.org>

14:17:35

I can probably start working on that, do we want to have that officially in Fedora of just fedora infra SIG?

<@humaton:fedora.im>

14:17:53

It should be in Fedora proper

<@nphilipp:fedora.im>

14:18:08

Just for infra we wouldn’t need a formal review

<@Zlopez:matrix.org>

14:18:28

Do we want it for EPEL as well?

<@humaton:fedora.im>

14:18:48

Probably

<@nphilipp:fedora.im>

14:18:55

The goland deps would be vendored, no idea if this would fly in EPEL

<@nphilipp:fedora.im>

14:19:08

Without vendored deps, it’s going to be much more work potentially

<@humaton:fedora.im>

14:19:08

but if I understand the bundling correctly it will be the same thing

<@smilner:fedora.im>

14:19:15

Carl George Diego Herrera thoughts?

<@nphilipp:fedora.im>

14:19:32

The golang deps would be vendored, no idea if this would fly in EPEL

<@humaton:fedora.im>

14:19:59

People from GO SiG also mentioned they will help

<@dherrera:fedora.im>

14:20:11

As far as i remember, if it works for Fedora there shouldnt be a problem

<@humaton:fedora.im>

14:20:18

so maybe we should provide spec and the package and they can provide feedback

<@carlwgeorge:fedora.im>

14:20:27

i definitely recommending vendoring go apps in epel

<@nphilipp:fedora.im>

14:20:30

AIUI, it’s only legit from F43 on

<@humaton:fedora.im>

14:20:41

nope its gefault from 43+

<@nphilipp:fedora.im>

14:20:55

Aaaaah

<@nphilipp:fedora.im>

14:20:59

TIL

<@humaton:fedora.im>

14:21:05

nope its default from 43+

<@humaton:fedora.im>

14:21:27

The ticket is your nils

<@nphilipp:fedora.im>

14:21:40

That will make so many things so much easier. I remember giving up packaging something goland-based in desperation because of deps hell 😅

<@carlwgeorge:fedora.im>

14:22:14

if you need an example to work off, take a look at fzf, which i recently vendored to build in epel8/epel10

<@nphilipp:fedora.im>

14:22:34

Thanks jednorozec Carl George

<@humaton:fedora.im>

14:23:32

!topic forgejo-deployment/issue/5

<@humaton:fedora.im>

14:23:34

!link https://pagure.io/fedora-infra/forgejo-deployment/issue/5

<@dkirwan:fedora.im>

14:24:04

o/ helm is now available on the os-control machines

<@dkirwan:fedora.im>

14:24:34

i've got a playbook/role in the fedora-infra ansible that can successfully call to the machines and call helm..

<@dkirwan:fedora.im>

14:24:47

so good to go with a staging deploy using the usptream oci images maybe ?

<@lenkaseg:fedora.im>

14:24:48

https://pagure.io/fedora-infra/ansible/c/0ba5409a9f2ca557d26af1e76433610a17ad4b2b?branch=main

<@lenkaseg:fedora.im>

14:25:05

I was just having a look at David's PR :)

<@nphilipp:fedora.im>

14:25:07

David Kirwan: so much for my question in the ticket 😁

<@dkirwan:fedora.im>

14:25:35

the systems run rhel, and hmm the helm package is not in epel i dont think

<@humaton:fedora.im>

14:26:39

does openshift cluster need something special to be ablu to run helm deplouyments? David Kirwan

<@humaton:fedora.im>

14:26:50

other than the binary

<@dkirwan:fedora.im>

14:26:55

nope not as far as i know

<@dkirwan:fedora.im>

14:28:00

the config to auth with the cluster is on those machines and helm seems to be working so ready to try actually install forgejo in staging using the upstream images id day

<@dkirwan:fedora.im>

14:28:03

id say*

<@humaton:fedora.im>

14:28:22

which brings us to the next ticket

<@humaton:fedora.im>

14:28:34

!topic forgejo-deployment/issue/2

<@humaton:fedora.im>

14:28:38

!link https://pagure.io/fedora-infra/forgejo-deployment/issue/2

<@humaton:fedora.im>

14:29:01

So I think running the helm requires one to be in sysadmin-opneshift

<@humaton:fedora.im>

14:29:12

who wants to try this?

<@dkirwan:fedora.im>

14:29:56

it will involve having helm call the following: helm install forgejo oci://code.forgejo.org/forgejo-helm/forgejo

<@humaton:fedora.im>

14:30:10

or https://codeberg.org/fedora/forgejo-helm

<@humaton:fedora.im>

14:30:59

but yeah running it its straight forward, It will also require bunch of reasonable changes

<@humaton:fedora.im>

14:31:06

like disbale registration by default

<@dkirwan:fedora.im>

14:32:16

Think to use the fedora-forgejo-helm we need the oci images available already but maybe there is a way to call it after a git checkout locally with helm

<@dkirwan:fedora.im>

14:32:52

I can do it if no one else wants to try

<@humaton:fedora.im>

14:33:02

well we can always enable the actions that are in the repo they will build the image that is used for the deployment.

<@lenkaseg:fedora.im>

14:33:29

Can I be around to learn?

<@humaton:fedora.im>

14:33:44

But using Konflux will hit another target we have on the project roadmap

<@lenkaseg:fedora.im>

14:34:13

Thanks!David Kirwan David Kirwan

<@humaton:fedora.im>

14:34:16

I am giving you the ticket David Kirwan once you are sure help works can you please also close the previous one?

<@humaton:fedora.im>

14:36:33

!topic Open floor

<@humaton:fedora.im>

14:37:00

Thats all i had, all other work is blocked on us having staging deployment.

<@humaton:fedora.im>

14:37:20

Any topics for open floor?

<@dkirwan:fedora.im>

14:39:01

Do we have a list of modifications that we know we need to make immediately to the staging install ?

<@dkirwan:fedora.im>

14:39:34

Might be good to spend some time figuring out what they are, and researching how to make the configuration changes? Maybe producing a configuration that can be passed into helm via variables or whatever

<@smilner:fedora.im>

14:41:48

That sounds like a good idea to me David Kirwan!

<@humaton:fedora.im>

14:42:22

Its actually part of the helm documentation

<@humaton:fedora.im>

14:42:37

it includes links to forgejo templating modding how to

<@humaton:fedora.im>

14:43:20

in the root of the forgejo-helm there is a templates dir

<@humaton:fedora.im>

14:45:25

As it goes for what changes there is a list of them. I will put it into a ticket. But as it goes about how to do it there is nothing like reading the docs :D

<@dkirwan:fedora.im>

14:45:49

Ok so for someone wanting to disasble logins for example by default on a fresh install, could clone that repo, make the ch anges locally, and try install forgejo locally via helm on maybe a code ready containers or minishift openshift install

<@humaton:fedora.im>

14:46:37

Yeah.

<@smilner:fedora.im>

14:49:15

Do we have a self formed sub team of people who are going to be focusing on these tickets? Or are we doing things more adhoc?

<@dkirwan:fedora.im>

14:49:52

Should maybe look at a subteam if we want this done timely ! ;D

<@humaton:fedora.im>

14:50:47

What do you meant by sub team?

<@dkirwan:fedora.im>

14:51:04

but once helm was called... forgejo appeared pretty quick.. like minutes from memory when looking over jednorozec 's shoulders one day

<@humaton:fedora.im>

14:51:14

why? We should track all the work in that tracker so everyone willing to work on something should have one assigned

<@smilner:fedora.im>

14:53:12

There isn't a right or wrong answer, just curious :-)

<@smilner:fedora.im>

14:53:12

The subteam idea just means people who are responsible and accountable to move the Gitforge work forward from the technical standpoint, together. Others can absolutely join or pick up tickets, but there would be a group of people who are focusing on this.

<@smilner:fedora.im>

14:53:12

<@nphilipp:fedora.im>

14:54:00

It helps if someone is around with a license to nag 😉

<@nphilipp:fedora.im>

14:54:29

Speaking as someone on the receiving end of being nagged

<@humaton:fedora.im>

14:55:36

I may be missing something but the people who are present are those responsible for implementation.

<@smilner:fedora.im>

14:55:37

We don't need an answer to this right this moment, just something to think about!

<@humaton:fedora.im>

14:56:15

I am trying to understand the question because in my mind it does not make sense.

<@smilner:fedora.im>

14:56:16

If that's the expectation, that works too!

<@humaton:fedora.im>

14:56:20

But my mind is blind...

<@smilner:fedora.im>

14:56:30

"If everyone owns it, no one owns it"

<@smilner:fedora.im>

14:56:39

That's where my question stems from

<@humaton:fedora.im>

14:56:48

Ok I own it ;D

<@humaton:fedora.im>

14:57:04

I will be pinging YOU guys present here and demanding answers!

<@humaton:fedora.im>

14:57:05

<@smilner:fedora.im>

14:57:14

That works!

<@humaton:fedora.im>

14:57:42

!endmeeting