2025-01-13 19:00:46 <@alexsaezm:fedora.im> !startmeeting Go SIG meeting 2025-01-13 19:00:46 <@meetbot:fedora.im> Meeting started at 2025-01-13 19:00:46 UTC 2025-01-13 19:00:46 <@meetbot:fedora.im> The Meeting name is 'Go SIG meeting' 2025-01-13 19:00:55 <@alexsaezm:fedora.im> !topic Roll Call 2025-01-13 19:01:16 <@alexsaezm:fedora.im> Hi everyone! (like always, we can wait a few minutes for everyone). First time in a different room outside our normal one! 2025-01-13 19:01:52 <@mikelolasagasti:matrix.org> !hello 2025-01-13 19:01:54 <@zodbot:fedora.im> Mikel Olasagasti Uranga (mikelo2) 2025-01-13 19:02:24 <@mikelolasagasti:matrix.org> we're aligning with the rest of the sigs, it's always a good thing to do ;) 2025-01-13 19:02:35 <@buckaroogeek:fedora.im> !hello 2025-01-13 19:02:35 <@zodbot:fedora.im> Brad Smith (buckaroogeek) 2025-01-13 19:04:34 <@xbt573:fedora.im> !hi 2025-01-13 19:04:36 <@zodbot:fedora.im> Alexey Lunev (xbt573) - he / him / his 2025-01-13 19:06:04 <@alexsaezm:fedora.im> I think we can start. We have 3 items labeled as "meeting" -> https://pagure.io/GoSIG/go-sig/issues?status=Open&tags=meeting&close_status= 2025-01-13 19:06:40 <@alexsaezm:fedora.im> Any preference or can we start from the older one? 2025-01-13 19:07:22 <@buckaroogeek:fedora.im> Random, queue or stack? :) 2025-01-13 19:07:44 <@mikelolasagasti:matrix.org> Ticket #57 is quite easy. I announced as suggested on the ticket the retirement of the packages next week if someone doesn't step up earlier. Nothing else to discuss about it I guess. 2025-01-13 19:07:44 <@alexsaezm:fedora.im> I have a dice on my desk, we can do random 2025-01-13 19:08:13 <@alexsaezm:fedora.im> Then we can skip that one 2025-01-13 19:08:34 <@alexsaezm:fedora.im> for the oldest one, https://pagure.io/GoSIG/go-sig/issue/43, is there any update? not that I can see 2025-01-13 19:09:06 <@buckaroogeek:fedora.im> I suspect mostly resolved 2025-01-13 19:09:09 <@mikelolasagasti:matrix.org> it's related to the discussions we had in the matrix channel this week 2025-01-13 19:09:59 <@buckaroogeek:fedora.im> several major docker packages are now vendored and much more easily updated 2025-01-13 19:10:56 <@buckaroogeek:fedora.im> moby-engine, docker-compose, docker-compse-switch, containerd, docker-buildx 2025-01-13 19:11:48 <@buckaroogeek:fedora.im> a few more need work (e.g. buildkit) 2025-01-13 19:12:03 <@alexsaezm:fedora.im> that's awesome! 2025-01-13 19:12:30 <@mikelolasagasti:matrix.org> downside is that that created many leave packages and now some are orphaned 2025-01-13 19:12:57 <@buckaroogeek:fedora.im> yes 2025-01-13 19:13:02 <@mikelolasagasti:matrix.org> cadvisor 2025-01-13 19:13:02 <@mikelolasagasti:matrix.org> ``` 2025-01-13 19:13:02 <@mikelolasagasti:matrix.org> 2025-01-13 19:13:02 <@mikelolasagasti:matrix.org> reg 2025-01-13 19:13:02 <@mikelolasagasti:matrix.org> migrate 2025-01-13 19:13:02 <@mikelolasagasti:matrix.org> golang-github-tonistiigi-fsutil 2025-01-13 19:13:02 <@mikelolasagasti:matrix.org> golang-github-prometheus 2025-01-13 19:13:02 <@mikelolasagasti:matrix.org> golang-github-moby-swarmkit-2 2025-01-13 19:13:02 <@mikelolasagasti:matrix.org> golang-github-moby-buildkit 2025-01-13 19:13:02 <@mikelolasagasti:matrix.org> golang-github-fsouza-dockerclient 2025-01-13 19:13:02 <@mikelolasagasti:matrix.org> golang-github-docker-cli 2025-01-13 19:13:02 <@mikelolasagasti:matrix.org> golang-github-docker 2025-01-13 19:13:02 <@mikelolasagasti:matrix.org> ``` 2025-01-13 19:13:02 <@mikelolasagasti:matrix.org> # fedrq whatrequires golang-github-docker-devel -F source 2025-01-13 19:13:02 <@mikelolasagasti:matrix.org> doctl 2025-01-13 19:14:19 <@alexsaezm:fedora.im> is there a goal where we can say that the issue can be close? 2025-01-13 19:15:17 <@mikelolasagasti:matrix.org> I guess the issue can be closed, but a ticket should be opened to discuss what to about vendoring or not packages by default 2025-01-13 19:15:45 <@mikelolasagasti:matrix.org> and I guess that was one of the items to work on the original ticket 2025-01-13 19:16:10 <@mikelolasagasti:matrix.org> the last comment has this one: #action mikelo to create a separate ticket to discuss creating guidelines for bundled packages 2025-01-13 19:16:14 <@mikelolasagasti:matrix.org> but I guess it was never created 2025-01-13 19:16:45 <@buckaroogeek:fedora.im> `#info We'll resume the docker discussion after the release of F37` :) 2025-01-13 19:16:55 <@mikelolasagasti:matrix.org> and current status goes beyond that discussion 2025-01-13 19:17:09 <@mikelolasagasti:matrix.org> that never happened 😅 2025-01-13 19:18:00 <@mikelolasagasti:matrix.org> I think in F38 cycle or F39 we had big issues with eclipseo dropping all the packages he owned due to unresponsiveness and since then everything has been about pushing the ball ahead 2025-01-13 19:18:56 <@mikelolasagasti:matrix.org> I've been workign to keep several complex stacks updated (otel, grpc, ...), but now that we've some orphans around containerd, we need to rethink what to do 2025-01-13 19:20:02 <@alexsaezm:fedora.im> We should make FESCo aware of this and ask them I guess 2025-01-13 19:20:20 <@mikelolasagasti:matrix.org> gotmax23: is working on go-vendor-tools, but it's not the official tool yet. People, myself included, have been proposing vendored packages as it's nearly impossible to get reviews on time in some cases or simply don't want to work on dependencies. EPEL gang is adding vendored packages (`tailscale`, `glow`, ...) without using go-vendor-tools. 2025-01-13 19:20:33 <@mikelolasagasti:matrix.org> we all know gotmax23: is working on go-vendor-tools, but it's not the official tool yet. People, myself included, have been proposing vendored packages as it's nearly impossible to get reviews on time in some cases or simply don't want to work on dependencies. EPEL gang is adding vendored packages (`tailscale`, `glow`, ...) without using go-vendor-tools. 2025-01-13 19:22:03 <@mikelolasagasti:matrix.org> 2025-01-13 19:22:03 <@mikelolasagasti:matrix.org> 2025-01-13 19:22:03 <@mikelolasagasti:matrix.org> our documentation in https://docs.fedoraproject.org/en-US/packaging-guidelines/Golang/#_bundled_or_unbundled states: 2025-01-13 19:22:03 <@mikelolasagasti:matrix.org> but this is not the reality anymore. 2025-01-13 19:22:03 <@mikelolasagasti:matrix.org> 2025-01-13 19:22:03 <@mikelolasagasti:matrix.org> At the moment golang projects packaged in Fedora SHOULD be unbundled by default. It means projects are built from dependencies packaged in Fedora. 2025-01-13 19:22:58 <@mikelolasagasti:matrix.org> if we decided to go bundled/vendored by default, I'll move all my packages to that system and orphan many leave dependencies. And I guess more people would do the same. 2025-01-13 19:23:37 <@mikelolasagasti:matrix.org> would you mind to start the conversation with FESCo alexsaezm ? 2025-01-13 19:24:02 <@mikelolasagasti:matrix.org> I think a ticket must be opened for that, right? I can add info and context after 2025-01-13 19:24:29 <@alexsaezm:fedora.im> Sure 2025-01-13 19:24:32 <@alexsaezm:fedora.im> !action: Make FESCo aware of the Go dependency situation 2025-01-13 19:24:54 <@alexsaezm:fedora.im> hmmmm I think I wrote the command wrong... 2025-01-13 19:25:12 <@alexsaezm:fedora.im> !action @alexsaezm to make FESCo aware of the Go dependency situation 2025-01-13 19:25:19 <@alexsaezm:fedora.im> now 2025-01-13 19:26:45 <@mikelolasagasti:matrix.org> F42 branching is in 3 weeks 2025-01-13 19:27:20 <@mikelolasagasti:matrix.org> I think worst case I can take ownership of the orphaned packages if FESCO's discussion takes longer 2025-01-13 19:28:05 <@mikelolasagasti:matrix.org> there is time until Feb 22nd when orphan packages would cause issues 2025-01-13 19:28:32 <@mikelolasagasti:matrix.org> so we wouldn't be affected by the orphans for F42, but would for F43 2025-01-13 19:28:56 <@mikelolasagasti:matrix.org> F42 would have current status, some packages are outdated, but most of the binaries build just fine 2025-01-13 19:29:27 <@mikelolasagasti:matrix.org> F43 would devel cycle would be the affected one 2025-01-13 19:29:56 <@mikelolasagasti:matrix.org> so no need to take ownership for now, but discussion and decisions should come before Feb22 2025-01-13 19:30:19 <@alexsaezm:fedora.im> understood 2025-01-13 19:30:29 <@alexsaezm:fedora.im> I will create the ticket right away so we can have this sorted as soon as possible 2025-01-13 19:31:16 <@mikelolasagasti:matrix.org> thanks 2025-01-13 19:31:17 <@buckaroogeek:fedora.im> I have some time available to work on packages 2025-01-13 19:31:43 <@buckaroogeek:fedora.im> a list perhaps in priority order would help 2025-01-13 19:32:16 <@mikelolasagasti:matrix.org> I'm not sure what would be the lsit of the packages to work on 2025-01-13 19:32:38 <@mikelolasagasti:matrix.org> if bundling becomes the default, then the picture is much more simpler 2025-01-13 19:32:45 <@buckaroogeek:fedora.im> yes 2025-01-13 19:32:46 <@mikelolasagasti:matrix.org> if not, we would need to think what to do 2025-01-13 19:33:24 <@mikelolasagasti:matrix.org> but let's face it, if there is no enough bandwidth to keep current packages, then it may not make sense to work on those stacks 2025-01-13 19:33:56 <@mikelolasagasti:matrix.org> some simpler packages that just requrie a few non k8s/moby/docker/otel packages might be fine, but bigger ones related to devops/cloud stuff will be impossible to be built 2025-01-13 19:34:26 <@mikelolasagasti:matrix.org> we've all these packages https://gitlab.com/fedora/sigs/go/package-data/-/blob/main/all_packages?ref_type=heads for all these binaries https://gitlab.com/fedora/sigs/go/package-data/-/blob/main/binaries?ref_type=heads 2025-01-13 19:35:08 <@buckaroogeek:fedora.im> Will take a look 2025-01-13 19:35:35 <@mikelolasagasti:matrix.org> packages like `rclone` or `golang-github-acme-lego` have many unique dependencies 2025-01-13 19:36:56 <@mikelolasagasti:matrix.org> packages like `golang-github-pkg-errors`, `golang-gopkg-yaml-3` or `golang-github-spf13-cobra` are shared by many packages 2025-01-13 19:38:22 <@mikelolasagasti:matrix.org> packages like `golang-github-pkg-errors` (73), `golang-gopkg-yaml-2` (72) `golang-gopkg-yaml-3` (43) or `golang-github-spf13-cobra` (63) are shared by many packagese 2025-01-13 19:38:32 <@alexsaezm:fedora.im> anything else from the topic apart from the action? should we move to the next item? 2025-01-13 19:38:54 <@mikelolasagasti:matrix.org> next one, sorry 😅 2025-01-13 19:39:13 <@alexsaezm:fedora.im> nothing to be sorry about :D 2025-01-13 19:39:15 <@alexsaezm:fedora.im> The other issue we have is the membership clean up (https://pagure.io/GoSIG/go-sig/issue/59) 2025-01-13 19:39:25 <@alexsaezm:fedora.im> I only notified the list, nothing else 2025-01-13 19:39:31 <@alexsaezm:fedora.im> it didn't get that much attention 2025-01-13 19:40:00 <@buckaroogeek:fedora.im> I read it :) 2025-01-13 19:40:03 <@mikelolasagasti:matrix.org> I took it as a positive sign 2025-01-13 19:40:12 <@alexsaezm:fedora.im> no news good news? 2025-01-13 19:40:17 <@mikelolasagasti:matrix.org> yep 2025-01-13 19:40:49 <@alexsaezm:fedora.im> In that case, I'll check all the accounts and send the email 2025-01-13 19:41:12 <@mikelolasagasti:matrix.org> Zbigniew, part of FESCo IIRC, gave positive feedback 2025-01-13 19:41:23 <@mikelolasagasti:matrix.org> so "little feedback, good news" in this case 😅 2025-01-13 19:41:28 <@alexsaezm:fedora.im> ha 2025-01-13 19:41:29 <@alexsaezm:fedora.im> correct 2025-01-13 19:41:54 <@alexsaezm:fedora.im> !action @alexsaezm will reach not active Go SIG members 2025-01-13 19:42:11 <@alexsaezm:fedora.im> And I guess with this we can move to the open floor 2025-01-13 19:42:17 <@alexsaezm:fedora.im> !topic: Open floor 2025-01-13 19:42:30 <@alexsaezm:fedora.im> ... : again 2025-01-13 19:42:34 <@alexsaezm:fedora.im> !topic Open floor 2025-01-13 19:42:40 <@alexsaezm:fedora.im> (I didn't use the topics in the whole conversation) 2025-01-13 19:43:58 <@buckaroogeek:fedora.im> nothing from me 2025-01-13 19:44:16 <@alexsaezm:fedora.im> FYI: recently I realized that packit has the fast forward feature already available -> https://packit.dev/docs/fedora-releases-guide/non-divergent-dist-git-branches 2025-01-13 19:44:32 <@mikelolasagasti:matrix.org> 2025-01-13 19:44:32 <@mikelolasagasti:matrix.org> I've a couple of new reviews if someone has time: 2025-01-13 19:44:32 <@mikelolasagasti:matrix.org> - `gosec` https://bugzilla.redhat.com/show_bug.cgi?id=2337048 2025-01-13 19:44:32 <@mikelolasagasti:matrix.org> - `kustomize` https://bugzilla.redhat.com/show_bug.cgi?id=2336849 2025-01-13 19:44:49 <@mikelolasagasti:matrix.org> both are bundled with go-vendor-tools 2025-01-13 19:45:14 <@alexsaezm:fedora.im> I'll check them 2025-01-13 19:45:51 <@buckaroogeek:fedora.im> alexsaezm: - did you see my note on govulncheck? 2025-01-13 19:46:10 <@alexsaezm:fedora.im> damn... I saw a notification but I think I messed up something 2025-01-13 19:46:14 <@alexsaezm:fedora.im> sorry 2025-01-13 19:46:20 <@buckaroogeek:fedora.im> :) 2025-01-13 19:46:21 <@alexsaezm:fedora.im> let me try to find it 2025-01-13 19:46:22 <@mikelolasagasti:matrix.org> is it broken again? 2025-01-13 19:46:45 <@buckaroogeek:fedora.im> govulncheck -version returns v0.0.0 2025-01-13 19:46:58 <@alexsaezm:fedora.im> I will check that 2025-01-13 19:47:10 <@alexsaezm:fedora.im> !action @alexsaezm to check govulncheck version issue 2025-01-13 19:48:14 <@alexsaezm:fedora.im> Sorry for missing it Brad Smith 2025-01-13 19:48:26 <@buckaroogeek:fedora.im> Not too worry 2025-01-13 19:48:29 <@alexsaezm:fedora.im> Anything else? or we can call it? 2025-01-13 19:48:39 <@buckaroogeek:fedora.im> Nothing more from me 2025-01-13 19:49:44 <@mikelolasagasti:matrix.org> neither 2025-01-13 19:50:07 <@alexsaezm:fedora.im> In that case... I think our first meeting outside the classic room has been a good one :D 2025-01-13 19:50:18 <@alexsaezm:fedora.im> thanks everyone! 2025-01-13 19:50:28 <@alexsaezm:fedora.im> !endmeeting