#meeting:fedoraproject.org log

<@humaton:fedora.im>

14:00:06

!startmeeting Git Forge Meeting

<@meetbot:fedora.im>

14:00:08

Meeting started at 2025-03-26 14:00:06 UTC

<@meetbot:fedora.im>

14:00:08

The Meeting name is 'Git Forge Meeting'

<@humaton:fedora.im>

14:00:11

!topic init

<@humaton:fedora.im>

14:00:11

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

<@nphilipp:fedora.im>

14:00:36

!hi

<@zodbot:fedora.im>

14:00:38

Nils Philippsen (nphilipp) - he / him / his

<@dkirwan:fedora.im>

14:00:47

<@Zlopez:matrix.org>

14:02:26

!hi

<@zodbot:fedora.im>

14:02:27

Michal Konecny (zlopez)

<@jflory7:fedora.im>

14:02:50

!hi

<@zodbot:fedora.im>

14:02:51

Justin W. Wheeler (jflory7) - he / him / his

<@jflory7:fedora.im>

14:02:53

Just lurking 😛

<@humaton:fedora.im>

14:03:52

!topic Meetings and such

<@humaton:fedora.im>

14:04:33

So we have currently 3 meetings relevant to this effort. there is 2xweek video call there is APAC call earlier today.

<@humaton:fedora.im>

14:04:51

So what should be the purpose of this meeting?

<@humaton:fedora.im>

14:06:42

Any ides or suggestions? Should we just replicate the effort and talk about the same things in multiple places?

<@humaton:fedora.im>

14:07:06

should we use this just to update wider audience? Should we sync in this meeting?

<@pboy:fedora.im>

14:12:03

!hi

<@zodbot:fedora.im>

14:12:04

Peter Boy (pboy)

<@dkirwan:fedora.im>

14:12:27

was thinking just to gather anything from apac team eg ryanlerch we can then repeat anything relevant in the later meetings

<@humaton:fedora.im>

14:13:42

was any of you on the APAC meeting? Its not in my powers to attend

<@dkirwan:fedora.im>

14:14:45

just myself and ryan,

<@dkirwan:fedora.im>

14:14:52

let me remember what updates he had..

<@dkirwan:fedora.im>

14:15:36

just that hes figured out how to block users creating organisations

<@dkirwan:fedora.im>

14:15:54

but theres a few other issues we need to lock down, suach as users creating issue trackers on forks etc

<@dkirwan:fedora.im>

14:16:28

guess will be better prepared next week, with links to the tickets he mentioned..

<@jflory7:fedora.im>

14:16:58

Have you considered running office hours? Using this as an as-needed time to solicit questions from the community?

<@jflory7:fedora.im>

14:17:13

If nobody shows up or participates for one hour, then the meeting can end. But then, it leaves an open invitation for folks to come by

<@jflory7:fedora.im>

14:17:21

I think it is wise to offer both A/V and text meeting options

<@jflory7:fedora.im>

14:17:30

I am always more likely to show up to a text meeting than an A/V meeting 😛

<@humaton:fedora.im>

14:17:57

i am not leading the initiative. So no I didnt consider office hours....

<@jflory7:fedora.im>

14:18:29

OK, I was answering the question, just an idea 🙂 I like office hours more than meetings because organizing them is less work 😄

<@humaton:fedora.im>

14:18:40

A/V meetings in NA timezones are mostly no go for me my calendar is full and I am double booked for most text meetings already...

<@jflory7:fedora.im>

14:18:45

And seems like the existing A/V calls have good coverage?

<@humaton:fedora.im>

14:19:14

But I will bring the office hours question up with Ryan tmrw

<@humaton:fedora.im>

14:20:21

!info go over tickets and updates

<@humaton:fedora.im>

14:20:21

!topic Tickets and Updates

<@humaton:fedora.im>

14:20:21

<@humaton:fedora.im>

14:20:59

I have one update here, just started to look at the package Nils has created https://codeberg.org/fedora/forgejo-deployment/issues/16

<@humaton:fedora.im>

14:21:24

not much to update just that I started today.

<@humaton:fedora.im>

14:22:03

hmm and the review already has some comments

<@jflory7:fedora.im>

14:23:50

nils++

<@humaton:fedora.im>

14:23:52

Any updates for any of the attendees?

<@zodbot:fedora.im>

14:23:53

jflory7 gave a cookie to nphilipp. They now have 63 cookies, 1 of which were obtained in the Fedora 41 release cycle

<@nphilipp:fedora.im>

14:25:39

Heh, I made the package ready for review and submitted it 😉 nothing else since

<@humaton:fedora.im>

14:26:37

I have updated the meeting template so we will go over the APAC updates https://codeberg.org/fedora/forgejo-deployment/src/branch/main/meeting.md

<@humaton:fedora.im>

14:27:11

!topic Open floor

<@humaton:fedora.im>

14:27:28

I will leave the open floor for a while if people have any questions

<@dkirwan:fedora.im>

14:28:07

One quick one https://codeberg.org/fedora/forgejo-deployment/issues/12 just looking at this CrunchyData Postgresql operator, have it installed, and now looking at configuring and wireing it up into the forgejo deploy to replace the database being deployed by default.

<@zodbot:fedora.im>

14:28:34

zlopez gave a cookie to nphilipp. They now have 64 cookies, 2 of which were obtained in the Fedora 41 release cycle

<@pboy:fedora.im>

14:28:57

I'm going to check installlation on Fedora Server and write a Doku

<@pboy:fedora.im>

14:29:39

Maybe, I've more questions / issues later

<@dkirwan:fedora.im>

14:30:44

Another topic we might need to figure out, possibly not here, but rather can figure it out in our forgejo deployment channel..

<@dkirwan:fedora.im>

14:31:08

but how we plan to handle updates from upstream, and minimising merge conflicts with our modifications..

<@dkirwan:fedora.im>

14:31:16

on https://codeberg.org/fedora/forgejo

<@dkirwan:fedora.im>

14:31:56

Upstream follows forgejo branch, we should aim to keep that in sync on our fork.. maybe stick to main branch with our modifications, but then need to make sure we are rebasing on top of forgejo branch?

<@dkirwan:fedora.im>

14:32:28

This image then gets built in konflux from the main branch which we then deploy on openshift

<@dkirwan:fedora.im>

14:33:33

I think I have that right anyway

<@humaton:fedora.im>

14:36:44

So I would suggest to keep latest stable branch synced in our main and build the images from there

<@humaton:fedora.im>

14:38:09

And yes rebasing on the top. But the way we are doing changes. We should only add new files ie templates, css, images

<@dkirwan:fedora.im>

14:38:12

so upstream forgejo -> main on our fork?

<@humaton:fedora.im>

14:38:38

so the re-bases should be smooth most of the time...

<@humaton:fedora.im>

14:38:50

no upstream forgejo branch is there main

<@humaton:fedora.im>

14:38:53

v10 is latest stable

<@humaton:fedora.im>

14:39:14

will be v11 once it gets released

<@humaton:fedora.im>

14:53:57

ok I am closing the meeting see you all next time!

<@humaton:fedora.im>

14:54:01

!nedmeeting

<@humaton:fedora.im>

14:54:07

!endmeeting