| 12 Oct 2023 |
 Lily Foster | (i really gotta pretty up some lists and plans and get community feedback going for ofborg soon...) | 15:07:53 |
 @adam:robins.wtf | Yeah it'd be nice to see where you think the priorities are :) | 15:13:25 |
| Lily Foster | it'd be more nice to see what others think they should be tbh, because i usually am not great at prioritization and often have bad ideas.... | 15:17:23 |
| Lily Foster | (i've also been a bit busy the past few weeks since the OC may have come during a, uh, life event.... but i'll have time again this weekend to get some of that going) | 15:20:05 |
 @delroth:delroth.net | small stuff I'd like to see ofborg do better:
- better handle changes to NixOS modules: automatically run tests, notify maintainers
- properly mark errors as errors, not just "skipped" (which is easy to miss) - and yes, that means people will have to fix their broken/flaky tests
- maybe split off the eval to compute number of rebuilds into a separate async step, so that maintainers notification / builds / tests can start while that long eval step gets processed
larger stuff:
- merge queue for nixpkgs when :) or at least a way to auto-merge a PR once eval+builds+tests have completed and are successful
- auto nixpkgs-review-like rebuild of dependents for changes with few dependents, maybe same but with some sampling for changes that impact more derivations (smoke test, basically)
- figuring out a way to have a local testing setup for ofborg so contributions aren't limited to people with access to the infra (maybe via a public tee of webhooks events to handle dynamic public/anonymous subscribers, and a dry run mode that doesn't try to perform actions on github)
| 15:39:55 |
| @delroth:delroth.net | since you're asking... :p | 15:40:05 |
| Lily Foster | The small stuff you listed and ability for mortals to run pieces of or all of ofborg locally are definitely pain points i'm looking at helping short-term. I appreciate you making the list ❤️ | 15:42:31 |
