<@humaton:fedora.im>
14:00:04
!startmeeting Git Forge Meeting
<@meetbot:fedora.im>
14:00:06
Meeting started at 2025-02-05 14:00:04 UTC
<@meetbot:fedora.im>
14:00:06
The Meeting name is 'Git Forge Meeting'
<@humaton:fedora.im>
14:00:11
!info this is meeting about the Fedora git forge replacement
<@humaton:fedora.im>
14:00:16
!topic init
<@Zlopez:matrix.org>
14:00:17
!hi
<@smilner:fedora.im>
14:00:17
!hi
<@zodbot:fedora.im>
14:00:19
None (smilner)
<@zodbot:fedora.im>
14:00:20
Michal Konecny (zlopez)
<@humaton:fedora.im>
14:00:57
Hi None :D
<@dkirwan:fedora.im>
14:01:39
o/
<@abompard:fedora.im>
14:01:57
Hi!
<@lenkaseg:fedora.im>
14:02:59
!hi
<@zodbot:fedora.im>
14:03:00
Lenka Segura (lenkaseg)
<@humaton:fedora.im>
14:04:09
lets start
<@jnsamyak:matrix.org>
14:04:28
!hi
<@nphilipp:fedora.im>
14:04:29
!hi
<@zodbot:fedora.im>
14:04:30
Nils Philippsen (nphilipp) - he / him / his
<@zodbot:fedora.im>
14:04:31
Samyak Jain (jnsamyak) - he / him / his
<@humaton:fedora.im>
14:04:44
!topic Fedora & Forgejo meetup @FOSDEM
<@humaton:fedora.im>
14:05:25
So we met with some of the Forgejo devels on Saturday dinner and Sunday during the day
<@humaton:fedora.im>
14:06:04
they are opened to implement features we as Fedora find important for our use-cases.
<@humaton:fedora.im>
14:06:20
discussions and tracking should happen on upstream forgejo tracker
<@dherrera:fedora.im>
14:06:26
!hi
<@zodbot:fedora.im>
14:06:27
Diego Herrera (dherrera) - he / him / his
<@humaton:fedora.im>
14:08:06
hmm
<@humaton:fedora.im>
14:08:33
I want to make action item in the meeting log but element keeps suggesting weird things
<@Zlopez:matrix.org>
14:08:59
Don't listen to him, it's a trap!
<@jnsamyak:matrix.org>
14:09:11
😂😂
<@humaton:fedora.im>
14:09:44
!action @humaton together with ryanlerch will open upstream tickets with functionality we are missing
<@humaton:fedora.im>
14:10:43
There we as wider community can help them is to use our talented Design team and help with UX experience
<@humaton:fedora.im>
14:11:08
!action I will open ticket with Fedora design team
<@smilner:fedora.im>
14:11:48
jednorozec: Is the design team already aware of the idea? Or will the ticket be the first contact? Just curious.
<@humaton:fedora.im>
14:12:09
One of the things we discussed was accessibility. FOrgejo has some user testing results that they would like to implement.
<@humaton:fedora.im>
14:12:44
They are, I asked them first if they are opened to cooperate with/on Forgejo
<@humaton:fedora.im>
14:14:39
one of the UI/UX things https://codeberg.org/forgejo/forgejo/issues/3
<@humaton:fedora.im>
14:15:02
anyway we discussed bunch of other things. But the main points are ^^
<@humaton:fedora.im>
14:16:05
!info Forgejo is opened to cooperation with Fedora on missing features and enhancements in the upstream.
<@humaton:fedora.im>
14:17:09
!topic Tickets and Updates
<@humaton:fedora.im>
14:17:16
!info go over tickets and updates
<@humaton:fedora.im>
14:17:33
!link https://pagure.io/fedora-infra/forgejo-deployment/issue/2
<@humaton:fedora.im>
14:18:01
David Kirwan you have any updates?
<@dkirwan:fedora.im>
14:18:06
o/ this ones with me, still working on it here
<@dkirwan:fedora.im>
14:18:54
i didnt get much time to work on it, distracted with another fedora infra ticket on communishift, but will hopefully get that finished today, so can get back on this deploy for forgejo
<@humaton:fedora.im>
14:19:24
did you have any chance to look at helm?
<@dkirwan:fedora.im>
14:19:43
yep helm is sitting there installed on the os-control machines
<@dkirwan:fedora.im>
14:19:54
so its ready to be used to deploy
<@dkirwan:fedora.im>
14:20:20
ive got a fedora infra ansible playbook which can call helm too.. so we just need to clone our forked helm charts and call the helm utility against them
<@dkirwan:fedora.im>
14:21:01
hopefully can try this out tomorrow morning
<@humaton:fedora.im>
14:21:37
cool
<@humaton:fedora.im>
14:22:10
We already discussed this with David, but for the record he will be the person calling shots on infrastructure side of things
<@humaton:fedora.im>
14:22:30
I am opening RFR ticket with his name on it.
<@nphilipp:fedora.im>
14:22:46
What’s “RFR”?
<@Zlopez:matrix.org>
14:22:51
Let me know if you need anything
<@humaton:fedora.im>
14:23:14
Request For Resources, its a way infra tracks who runs what
<@nphilipp:fedora.im>
14:23:24
Ahh, thanks!
<@humaton:fedora.im>
14:23:29
well its SOP more than anything else...
<@humaton:fedora.im>
14:24:13
let s move on
<@humaton:fedora.im>
14:24:23
!topic https://pagure.io/fedora-infra/forgejo-deployment/issue/7
<@humaton:fedora.im>
14:24:27
!link https://pagure.io/fedora-infra/forgejo-deployment/issue/7
<@nphilipp:fedora.im>
14:25:38
Meanwhile I’ve found out (I thin) that I probably have to invoke make rather than using the go2srpm defaults
<@nphilipp:fedora.im>
14:26:26
It’s also confusing that the code base is permeated with references to gitea 😅
<@humaton:fedora.im>
14:26:42
does it have something to do with thei building 2 targets? frontend and backend?
<@humaton:fedora.im>
14:26:54
Oh this!
<@nphilipp:fedora.im>
14:27:01
This is an option, by default the Makefile will build both
<@humaton:fedora.im>
14:27:08
So I think they announced it in this release v10
<@humaton:fedora.im>
14:27:26
This was the last gitea <-> forgejo compatible version
<@humaton:fedora.im>
14:27:36
that is why there is a LOT of gitea references
<@nphilipp:fedora.im>
14:27:42
I’m following https://forgejo.org/docs/latest/contributor/from-source/ for the time being 😉
<@nphilipp:fedora.im>
14:28:05
In summary: I’m on it 😉
<@humaton:fedora.im>
14:28:45
should I make it into statemtn?
<@humaton:fedora.im>
14:28:53
!info nils is on it!
<@nphilipp:fedora.im>
14:29:05
Thanks!
<@humaton:fedora.im>
14:29:30
!topic forgejo-deployment/issue/8
<@humaton:fedora.im>
14:29:33
!link https://pagure.io/fedora-infra/forgejo-deployment/issue/8
<@humaton:fedora.im>
14:30:07
I talked to Yash today he is poking around it
<@smilner:fedora.im>
14:30:14
Some good context in that issue!
<@humaton:fedora.im>
14:30:20
not sure if lenkaseg had time to look at it?>
<@lenkaseg:fedora.im>
14:30:46
I was looking at it, figured out that the best way might be to build a theme
<@lenkaseg:fedora.im>
14:31:02
forgejo is using tailwind for the ui
<@lenkaseg:fedora.im>
14:31:28
Yaash was interested in it, so I dropped the links there and I'm ready to assist him
<@humaton:fedora.im>
14:32:21
he has his first contribution to forgejo
<@lenkaseg:fedora.im>
14:32:52
Just for clarification, what's the borderline between what should be done for this issue and what will be the Design team's work?
<@humaton:fedora.im>
14:32:57
https://codeberg.org/forgejo/forgejo/pulls/6769
<@humaton:fedora.im>
14:33:40
Yup, find a way to generate theme and way of placing it in to the app
<@lenkaseg:fedora.im>
14:33:59
Ok then!
<@humaton:fedora.im>
14:34:14
the theme itself should be coordinated with design folks and branding practicies
<@humaton:fedora.im>
14:35:05
lets move on
<@humaton:fedora.im>
14:35:18
!topic forgejo-deployment/issue/4
<@humaton:fedora.im>
14:35:21
!link https://pagure.io/fedora-infra/forgejo-deployment/issue/4
<@humaton:fedora.im>
14:35:42
SO this is one of the missing things in forgejo, they are curently using queues implemented in forgejo
<@humaton:fedora.im>
14:35:59
they like it that way because they aim to be single binary deployment
<@Zlopez:matrix.org>
14:36:35
Do they support webhooks?
<@humaton:fedora.im>
14:36:39
but, they are open to implement the queue system in plugable/configurable form
<@Zlopez:matrix.org>
14:36:46
So we can leverage webhooks2fedmsg?
<@humaton:fedora.im>
14:37:02
yes, but that is probably not sustainable
<@smilner:fedora.im>
14:37:14
Due to the amount of messages?
<@humaton:fedora.im>
14:37:17
if you imagine the volume of msgs produced by pagure or distgit
<@Zlopez:matrix.org>
14:37:31
In that case we will need to listen to events and convert them to fedmsg
<@humaton:fedora.im>
14:37:34
its for sure good enough for now for staging deployment
<@humaton:fedora.im>
14:37:44
maybe even for production general forge
<@Zlopez:matrix.org>
14:37:56
Or if they can add amqp support that would be enough
<@humaton:fedora.im>
14:37:57
but I dont think its ok for distgit
<@Zlopez:matrix.org>
14:38:33
I understand, it was just first idea that came to my mind
<@humaton:fedora.im>
14:38:55
yeah and its valid one and we will use it in near future
<@humaton:fedora.im>
14:39:48
!proposal Staging deployment of forgejo will use webhooks2fedmsg as a primary messaging implementation.
<@humaton:fedora.im>
14:40:15
!propose Staging deployment of forgejo will use webhooks2fedmsg as a primary messaging implementation.
<@humaton:fedora.im>
14:40:24
how is the cmd
<@nphilipp:fedora.im>
14:40:39
Assuming `...fedmsg` doesn’t mean fedmsg 😁
<@Zlopez:matrix.org>
14:40:44
We need to investigate what is missing in webhook2fedmsg for this
<@lenkaseg:fedora.im>
14:40:51
fedora-messaging :)
<@Zlopez:matrix.org>
14:41:05
It's fedora messaging, but it would be really mouthful as an app name
<@humaton:fedora.im>
14:41:11
yup
<@humaton:fedora.im>
14:41:30
old fedmsg is dead, all references point to fedora-messaging
<@humaton:fedora.im>
14:41:41
anyway
<@humaton:fedora.im>
14:41:54
propose does not work so its just info
<@humaton:fedora.im>
14:42:06
!info Staging deployment of forgejo will use webhooks2fedmsg as a primary messaging implementation.
<@Zlopez:matrix.org>
14:42:29
Not yet, but soon
<@humaton:fedora.im>
14:42:36
!action new ticket for upstream discussion on this problem will be opened
<@humaton:fedora.im>
14:43:15
!topic Open floor
<@humaton:fedora.im>
14:44:25
I have one thing, we should start talking pagure.io sunset
<@humaton:fedora.im>
14:44:39
First probably just no new repos
<@nphilipp:fedora.im>
14:44:53
Yup, the `.io` TLD will also go away
<@humaton:fedora.im>
14:45:04
Codeberg people agreed that we can point people at them.
<@Zlopez:matrix.org>
14:45:14
Shouldn't this be a council decision? I thought that we were only talking about dist-git only for now
<@humaton:fedora.im>
14:45:25
I dont know sir .su is still around
<@Zlopez:matrix.org>
14:45:49
That seems like a solid replacement
<@humaton:fedora.im>
14:45:55
General forge was actually the first one Zlopez
<@humaton:fedora.im>
14:46:07
and its going to be the test bed for us to play with forgejo
<@Zlopez:matrix.org>
14:48:00
You are right, but that was some time ago, when the GitLab was announced
<@humaton:fedora.im>
14:48:58
Anyhow I will raise ticket with council regarding dates and sunset timeline
<@lenkaseg:fedora.im>
14:49:02
you mean of the apps we infra team maintains? I guess for wide public it's gonna be open till...always
<@nphilipp:fedora.im>
14:49:47
Looks like IANA has learned from that lesson: https://every.to/p/the-disappearance-of-an-internet-domain (at about the middle of the article)
<@humaton:fedora.im>
14:49:55
I dont think we are going to run pagure.io once we have migrated to forge.fedoraproject.org or what ever the hostname is
<@Zlopez:matrix.org>
14:50:15
We shouldn't
<@lenkaseg:fedora.im>
14:50:43
huh, the sunset is close then!
<@humaton:fedora.im>
14:51:08
ofc there will be some time to migrate for folks
<@nphilipp:fedora.im>
14:51:17
Not that this is the place, but I think we shouldn’t give it a generic name (and cause headaches down the road when our successors want to migrate to yet something else)
<@humaton:fedora.im>
14:51:19
we will not just flip the switch
<@Zlopez:matrix.org>
14:51:25
we will probably still need to keep it read-only for some time
<@humaton:fedora.im>
14:52:35
yup we will keep the light on for a while
<@humaton:fedora.im>
14:52:55
anyhow do we have anyhing else for the open floor?
<@humaton:fedora.im>
14:53:02
should I glue the tiles back?
<@humaton:fedora.im>
14:54:46
Thank you all for your time today and all the work.
<@humaton:fedora.im>
14:54:49
!endmeeting