Skip to content

helvum: update to 0.6.2, adopt.#60823

Closed
gnpaone wants to merge 1 commit into
void-linux:masterfrom
gnpaone:master
Closed

helvum: update to 0.6.2, adopt.#60823
gnpaone wants to merge 1 commit into
void-linux:masterfrom
gnpaone:master

Conversation

@gnpaone
Copy link
Copy Markdown
Contributor

@gnpaone gnpaone commented May 30, 2026

Testing the changes

  • I tested the changes in this PR: YES

Local build testing

  • I built this PR locally for my native architecture, x86_64-libc

@tranzystorekk
Copy link
Copy Markdown
Contributor

please do not reopen PRs just to make small adjustments, amend and squash git commits properly instead

also, do not adopt already owned packages without discussing it with current maintainer, besides we require a proof of good stewardship before contributors are allowed to adopt packages

Comment thread srcpkgs/helvum/template
depends="pipewire"
short_desc="GTK patchbay for pipewire"
maintainer="0x5c <dev@0x5c.io>"
maintainer="Naveen Prashanth <gnpaone@gmail.com>"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Revert this change. We expect contributors to establish a history of package maintenance before putting their name on templates.

Furthermore, as this package already has a maintainer, you should ping that maintainer when you submit an update. Even after establishing a history with this project, it would be inappropriate to replace an existing maintainer without prior approval.

@gnpaone
Copy link
Copy Markdown
Contributor Author

gnpaone commented May 30, 2026

I'm the maintainer of this actual source, and its not been updated for quite a while, that's the reason, I will ping the maintainer and wait for response

@gnpaone gnpaone closed this May 30, 2026
@ahesford
Copy link
Copy Markdown
Member

You don't have to close the PR. It is ok to submit updates, just don't add your name to the maintainer field and make sure to loop in the existing maintainer.

@0x5c 0x5c mentioned this pull request Jun 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants