Change Details

Right, tracking this for the week, to make sure it actually gets done.. @DataDrake has kindly reworked the foobarred job handling in ferryd so I can restart work on that. - [x] Finish ferryd in a test-deployable form this week. - [x] Get it deployed (For realsies!!!!111) for the weekend (not on, not after, **FOR**) (Edit 2: THIS WEEKEND.) - [x] Onboard community maintainers - [x] Sort out the god-awful fuckery that is our current repo network speed. New host, CDN, something. Throw money at someone. For the love of cheese sandwiches, make network speeds to the repo great again. - [ ] Discuss and establish formal sync cadence. I'm inclined to say 2 days but for stuff like a GNOME update it's not enough time. Input requested here. Long and short of it is, make downloads from repo faster, make syncs faster, make stuff go from dev portal **to** repos faster. This blocks {T4235} because without the fastly bits done, we can't move quick enough to make it all happen. Plus other high-p items need to wait for this to be done. Re: onboarding: We'd really love to make some of you guys actual full blown maintainers if you're up for it. We need to also help you in transitioning to that ... "trusted "(?) role, but we also need to make sure that we're all in sync with one another (i.e. `#Solus-Dev` IRC channel) and that all stuff hitting the repos is valid. Maybe we need to put together a very simple `ypkg-check-cranky` script to ensure we're not making common mistakes, we can hit a great cadence.

Right, tracking this for the week, to make sure it actually gets done.. @DataDrake has kindly reworked the foobarred job handling in ferryd so I can restart work on that. - [x] Finish ferryd in a test-deployable form this week. - [x] Get it deployed (For realsies!!!!111) for the weekend (not on, not after, **FOR**) (Edit 2: THIS WEEKEND.) - [x] Onboard community maintainers - [x] Sort out the god-awful fuckery that is our current repo network speed. New host, CDN, something. Throw money at someone. For the love of cheese sandwiches, make network speeds to the repo great again. - [x] Discuss and establish formal sync cadence. I'm inclined to say 2 days but for stuff like a GNOME update it's not enough time. Input requested here. Long and short of it is, make downloads from repo faster, make syncs faster, make stuff go from dev portal **to** repos faster. This blocks {T4235} because without the fastly bits done, we can't move quick enough to make it all happen. Plus other high-p items need to wait for this to be done. Re: onboarding: We'd really love to make some of you guys actual full blown maintainers if you're up for it. We need to also help you in transitioning to that ... "trusted "(?) role, but we also need to make sure that we're all in sync with one another (i.e. `#Solus-Dev` IRC channel) and that all stuff hitting the repos is valid. Maybe we need to put together a very simple `ypkg-check-cranky` script to ensure we're not making common mistakes, we can hit a great cadence.

Right, tracking this for the week, to make sure it actually gets done.. @DataDrake has kindly reworked the foobarred job handling in ferryd so I can restart work on that. - [x] Finish ferryd in a test-deployable form this week. - [x] Get it deployed (For realsies!!!!111) for the weekend (not on, not after, **FOR**) (Edit 2: THIS WEEKEND.) - [x] Onboard community maintainers - [x] Sort out the god-awful fuckery that is our current repo network speed. New host, CDN, something. Throw money at someone. For the love of cheese sandwiches, make network speeds to the repo great again. - [ - [x] Discuss and establish formal sync cadence. I'm inclined to say 2 days but for stuff like a GNOME update it's not enough time. Input requested here. Long and short of it is, make downloads from repo faster, make syncs faster, make stuff go from dev portal **to** repos faster. This blocks {T4235} because without the fastly bits done, we can't move quick enough to make it all happen. Plus other high-p items need to wait for this to be done. Re: onboarding: We'd really love to make some of you guys actual full blown maintainers if you're up for it. We need to also help you in transitioning to that ... "trusted "(?) role, but we also need to make sure that we're all in sync with one another (i.e. `#Solus-Dev` IRC channel) and that all stuff hitting the repos is valid. Maybe we need to put together a very simple `ypkg-check-cranky` script to ensure we're not making common mistakes, we can hit a great cadence.