maintainers: create sage team

[timokau]

Motivation for this change

Maintaining all the packages whose updates might break some aspect of
sage.

For reference:
#103810 (comment)

Things done

• Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Determined the impact on package closure size (by running nix path-info -S before and after)
• Ensured that relevant documentation is up to date
• Fits CONTRIBUTING.md.

[timokau]

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

[timokau]

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.

[7c6f434c]

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

Right now I will not be a good one… I have forgotten all the Sage stuff from my failures, and I am usually a bit behind on reacting to things… But could join with a hope of providing a fallback when fixing some of the dependencies.

[timokau]

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 ;)

[omasanori]

@timokau Sorry for my late response.

I am glad to join the team to help the sustainability of nixpkgs mathematical and scientific computing stack.

[7c6f434c]

@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?

[timokau]

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!

[7c6f434c]

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

[timokau]

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