Looking for maintainers #507
Comments
|
Hello, First of all thank you for maintaining this overlay over the years. I would like to help, as I really value the existence of an audio dedicated overlay for music production and music related packages. I would be available to jump in a couple times a week. I have a fair command of english, casually tweak my own ebuilds and my gentoo systems, and have some experience with github, though not much with the automated build and validation. I'm interested in learning whatever is relevant, and usually do so quickly. If you think I could be of some help please let me know. |
|
Hi @sangibeaud! Thanks for reaching out and for the offer! We mostly follow upstream/gentoo's way of working, so if you're already familiar with how to write an ebuild you're pretty much all set :) If you want you could have a look a the open issues and/or see if any packages need fixing or could use rev-bump and maybe start with that? Would that work for you? I at the moment pretty much only have some spare time during the weekends, so it might take a bit of time for me to reply. |
|
Hey there, I am using a few packages in the overlay as well and already have experience in maintaining a few packages in ::gentoo, ::guru and ::fem-overlay. I'd mainly like to take care of the packages I am using (at the moment pyliblo, cadence, carla, ladish, new-session-manager and ntk), but I can also take care of minor verbumps and bugfixes for other packages. |
|
I use Bitwig consistently and can help maintain that. I think @NexAdn sounds like a good person to take over :) |
|
You can always count me in to help out. |
|
Hi @NexAdn! Thanks for reaching out (and for the PRs!), very much appreciated. Regarding the CI, I'm afraid we'll have to drop the emerge tests. They are very nice to have and I'd prefer to keep them, but the short version of it is that without a external binary package cache it just takes too long to compile the packages and all their dependencies, even with CircleCI's pretty generous timeouts and resources. I also don't want to rely on a package cache hosted from my (or someone else's) home, since that will inevitable break/go down at some point. I guess we can keep the scripts so one can still run the emerge checks locally but just dont' run the emerge test from CI. @kaythomas0 and @audiodef Thanks for the offer (and PRs) as well. I'll make sure to add both of you to the team as well. FYI the org requires 2FA, so make sure that you have that enabled :) |
|
Best of luck with the construction! Sounds exciting.
I have a hosted server I'm happy to volunteer as a resource for a binary
package cache. I've had one for years and it's not going anywhere, since I
run a few web sites, including Gentoo Studio. I've found the host to have
reliable uptime. Just let me know.
Damien (audiodef)
…On Tue, Dec 13, 2022, 16:38 Simon van der Veldt ***@***.***> wrote:
Hi @NexAdn <https://github.com/NexAdn>! Thanks for reaching out (and for
the PRs!), very much appreciated.
First of all apologies for the delay. I'm currently demolishing (the
majority of) my house for new construction to begin in January, so pretty
busy with all of that. I'll to get to your PRs though. Hope it's OK if it
takes a bit of time.
Regarding the CI, I'm afraid we'll have to drop the emerge tests. They are
very nice to have and I'd prefer to keep them, but the short version of it
is that without a external binary package cache it just takes to long to
compile the packages and all their dependencies, even with CircleCI's
pretty generous timeouts and resources. I also don't want to rely on a
package cache hosted from my (or someone else's) home, since that will
inevitable break/go down at some point. I guess we can keep the scripts so
one can still run the emerge checks locally but just dont' run the emerge
test from CI.
Switching from repoman to pkgcheck makes sense, although I have to admit I
haven't used pkgcheck yet since I've not really done much packaging related
the last 12 months or so, so not entirely sure if it covers the same things.
@kaythomas0 <https://github.com/kaythomas0> and @audiodef
<https://github.com/audiodef> Thanks for the offer (and PRs) as well.
I'll make sure to add both of you to the team as well.
FYI the org requires 2FA, so make sure that you have that enabled :)
—
Reply to this email directly, view it on GitHub
<#507 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AG7CO5GNBSHXCX5HXTE7VKTWNDUHFANCNFSM6AAAAAARBII4NY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I'd be happy to take care of pure-data for a while, I've already been bumping my own ebuild to the newer versions. |
|
I'd like to try one more time to offer my help. My project, Gentoo Studio, is probably the longest-surviving audio project/overlay for Gentoo, having been around since 2007, and I have no plans to stop. This overlay has a very nice setup, and if you'll let me be blunt - please, please, please make me an admin or something before archiving it! |
|
I've made both @audiodef and @NexAdn members per pings on IRC and to unblock this. @simonvanderveldt, if you agree, I'd like to formally hand off my owner role to someone (I'm happy to stay on as a backup to unblock things if we run into another stall in the future, but don't expect to make contributions myself; I can also give up my role entirely. Up to everyone else here.) |
|
@marcan Thanks a lot for taking care of this! It's been incredibly busy for IRL the last month and half with the (de)construction, plus I'm also still working full time, so I haven't had time to take a look at anything here at all. Apologies for that. I'm going to have to hand off my owner role as well. Would be happy to stay on as backup as well, same as @marcan :) @NexAdn you should have an invite to join the org so you can move your (and other people's) PRs forward. @kennypm Feel free to create a PR for bumps, it might take bit of time, but assuming no large changes/issues we should be able to merge them :) |
|
@simonvanderveldt and @marcan: first of all thank you very much for inviting us to the org and for the trust. I am still struggling with merging my own PRs, but maybe there are some problems due to the failing CI pipeline triggering some merge rules. Hopefully this can be resolved with an approval for #512. |
|
@NexAdn Welcome to the club! :) |
The team that used to maintain this overlay is no longer able to work on it.
So we're looking for people that want to help out and maintain this overlay. We'll still be there to help out of course :)
Please comment on this issue if you're interested.
If we can't find any new maintainers we'll archive this repo per 2023.01.01.@NexAdn and @audiodef have now joined the org, so we should be fine for the foreseeable future :)
The text was updated successfully, but these errors were encountered: