| 26 Feb 2024 |
 infinisil | In reply to @raitobezarius:matrix.org
It can, but I guess it can be rename to hydra-for-nixosorg and people can have nix-community/hydra if they want a community maintained Hydra I like that idea | 20:31:15 |
 K900 | It would help some, but ehhhh | 20:31:20 |
 @delroth:delroth.net | hydra without the Perl and with a better scheduler would be significantly better and would probably suffice for the nixos.org use case for 5+ years | 20:31:53 |
| infinisil | In reply to @raitobezarius:matrix.org
It can, but I guess it can be rename to hydra-for-nixosorg and people can have nix-community/hydra if they want a community maintained Hydra So the idea would be that hydra-for-nixosorg can remove all code not needed for hydra.nixos.org? | 20:32:02 |
| K900 | Well yes, but the scheduler is very much backend | 20:32:04 |
 @janik0:matrix.org | In reply to @k900:0upti.me
tbh I don't know if rewriting just the frontend would help much some what unrelated but is there some db query result cache, that would probably go a long way for making the ui more usable? | 20:32:16 |
| @delroth:delroth.net | In reply to @janik0:matrix.org
some what unrelated but is there some db query result cache, that would probably go a long way for making the ui more usable? do you want to go implement that in Perl? | 20:32:28 |
 raitobezarius | In reply to @infinisil:matrix.org
So the idea would be that hydra-for-nixosorg can remove all code not needed for hydra.nixos.org? hydra-for-nixosorg is maintained by people working on hydra.nixos.org (code & infra) and they do what they see fit with it | 20:32:33 |
| raitobezarius | They don't have to care about breaking Hydra usecases of other people | 20:32:47 |
| raitobezarius | nix-community/hydra can host the GP Hydra if someone comes and say "I will do that" | 20:32:59 |
| raitobezarius | * nix-community/hydra can host the general purpose Hydra if someone comes and say "I will do that" | 20:33:05 |
| infinisil | Sounds good to me! | 20:33:12 |
| raitobezarius | But NixOS officially does not communicate anymore the following fact: "Hydra is the CI we advise you to use for Nix(OS)" | 20:33:27 |
| raitobezarius | which also enable people who want to see a blessed solution to jump and make whatever better and reinstate a blessed solution later on | 20:33:54 |
| raitobezarius | Like, if someone makes nix-community/hydra without Perl, fast, better scheduler and infra people says "mmm looks good, we want it", hydra-for-nixosorg can be manipulated to be thrown away (I suppose?) | 20:34:23 |
| @janik0:matrix.org | In reply to @delroth:delroth.net
do you want to go implement that in Perl? rather not to be honest:( | 20:34:49 |
| @delroth:delroth.net | I don't see any reason for the two forks to ever be far apart | 20:34:50 |
| @janik0:matrix.org | In reply to @delroth:delroth.net
do you want to go implement that in Perl? * rather not to be honest :( | 20:34:52 |
| @janik0:matrix.org | * rather not to be honest :(
(so I did some perl mojolicious legacy maintenance at dayjob 🙈) | 20:35:32 |
| @janik0:matrix.org | * rather not to be honest :(
(but I did some perl mojolicious legacy maintenance at dayjob, so.. 🙈) | 20:35:42 |
| infinisil | I guess we don't actually need a fork. It can just be an increase in version number along with setting a new expectation that new versions won't be backwards compatible anymore | 20:36:07 |
| infinisil | If somebody wants to fork a version they can just grab an older commit | 20:36:20 |
| infinisil | In reply to @infinisil:matrix.org
I guess we don't actually need a fork. It can just be an increase in version number along with setting a new expectation that new versions won't be backwards compatible anymore Or even not doing any releases anymore, also changing the attribute/name or something | 20:36:42 |
| raitobezarius | The problem with the idea of not needing a fork is that I don't know how to go see to do this | 20:36:58 |
| raitobezarius | But if you all agree with that and that infra people can be unblocked to do their changes, I guess that's fine as well | 20:37:09 |
 ma27 | In reply to @raitobezarius:matrix.org
I know that ma27 also does maintenance for his own needs ....and a backlog of UI improvements somewhere :D
but, the only Hydra I'm really using is my personal one, so I don't really have the resources on my own to debug issues that only come up with large instances.
But generally, I'd be open to help with Hydra (or whatever fork) - in the time constraints I have of course | 20:37:26 |
| raitobezarius | But if this means they have to go see an unknown non-existent committee of maintainers to bless this, it might be a bit frustrating (understandably) | 20:37:27 |
| ma27 | In reply to @infinisil:matrix.org
I guess we don't actually need a fork. It can just be an increase in version number along with setting a new expectation that new versions won't be backwards compatible anymore which version number btw? :D | 20:37:45 |
| infinisil | Hah | 20:37:57 |
| raitobezarius | I guess the question boils down a bit to you John Ericson who was the latest committer on Hydra | 20:37:59 |
