@7c6f434c do you want to be a member of that team?

For some reason my local eval check is failing, but I don't see what is wrong. Other teams are used in the same way. Checking if ofBorg also gives an error.

But could join with a hope of providing a fallback when fixing some of the dependencies.

More eyes are always better. I'll probably also take on more of an advisory role, at least for the near future. The biggest risk I see with teams is dilution of responsibility, but it should be manageable.

Does b7319d2 look good do you @7c6f434c?

@omasanori please also explicitly approve the PR if you are fine with it. I don't want to add anybody against their will ;)

@timokau I am definitely OK with not being maintainer on those things. I am also OK as being listed in the team; I guess for now it has the benefit of me automatically being notified of changes approved by @omasanori so I can merge them (I read what I merge, but I always trust other people's claim of testing, and mostly trust some people's claims of impact evaluation). If both of us have spotty availability I guess it's better to flip the coin twice?

Sorry for my late response.

I'd say that was quite fast :)

I read what I merge, but I always trust other people's claim of testing, and mostly trust some people's claims of impact evaluation.

Similar for me.

I am also OK as being listed in the team

Alright, let's go ahead with this then!

I think you ended up not adding me, at least judging from GitHub diff; I am fine with it if it was your intent; otherwise I guess I wonder if it is mixing up what you committed and what you did not, or GitHub failing at diffs, because the latter case would be… something to know, but no longer unimaginable

Right, I didn't stage my changes to team-list.nix when making the second commit! Thanks for noticing, I'll fix that up.