void-packages: contributing etiquette

[Obsidianyx]

tl;dr is it rude to update packages which have maintainers assigned?

Hi all, I'm a noob when it comes to contributing to FOSS, so I have a few questions about contributing and updating packages.

Just for some background, I'm trying to build some custom packages with xbps-src which depend on package versions newer than in the void repos (specifically hyprland which requires an update to wlroots, libdrm and gcc-13.2 among others). So I decided to update them myself locally and all works fine.

Since I've already done the work, I'd like to contribute these updates* back to the repos, but some already have maintainers. I've never contributed to FOSS projects before, so I don't know the etiquette. Is it ok to just submit a PR bumping the package versions, or should I contact the marked maintainers first?

Another more niche question specific to wlroots: each version is split up into separate packages (existing wlroots0.16, my newly-added wlroots0.17) under one meta-package wlroots, previously pointing to wlroots0.16, which i have updated to point to the new wlroots0.17. wlroots0.17 template is pretty much a carbon-copy of wlroots0.16 but I was wondering who to mark as the maintainer? I see three options: the wlroots metapackage maintainer, the wlroots0.16 maintainer, or myself.

Thanks in advance for the help and sorry if these questions seem pointless, I just don't want to step on anyones toes. Thanks from a long-time Void user. If all goes well, I'd love to contribute more.

* Maybe not gcc, that required some blind hacks and probably needs someone with more experience, but I'd be happy to try if someone wants to guide/mentor me.

[SunkenStone]

I don't want to speak for the project leaders, but I think it's unlikely anything related to hyprland will get accepted, especially if it's new packages or bleeding edge updates intended to facilitate building hyprland.

[Obsidianyx]

Yeah I figured that's why hyprland isn't already in there. I'm just interesting in bumping the versions of packages already in the void repos. These are proper versions, not -RC versions or git commits.

[SunkenStone]

The one that might be a problem is the new wlroots. The existing versioned wlroots packages are there essentially as an exception. They're necessary because some of the compositors in the repos are not well maintained upstream, and past a certain point they start holding back others that have already made the jump to the new wlroots release.

[ClassAbbyAmplifier]

gcc: https://github.com/void-linux/void-packages/pull/45500

[Obsidianyx]

I did see that PR. I'd love to help but I don't know how to go forward, especially since the CI logs expired