<worldofpeace>
ah right infinisil the maintainers list could just have an attribute `teams.desktop` with your attribute in it. that wouldn't help with the fact that you still have to manually add everyone to the particular expressions though.
<worldofpeace>
and guess somehow that could map to the teams on github automatic
<infinisil>
I mean, you can then do `meta.maintainers = lib.maintainers.teams.desktop ++ [ lib.maintainers.paul ];`
<infinisil>
Ah you mean that the list still needs to be appended to manually
<worldofpeace>
ooh I was thinking that `teams.desktop` could be a github team, but whoever is a member of it, through some magic tool, updates the maintainers list automatic
<infinisil>
worldofpeace: I think having it in code only might be easier, people can make PR's to add themselves, which can get reviewed and seen by maintainers
<worldofpeace>
infinisil: Ah I'm seeing that now
<worldofpeace>
We probably need some sort of social process for the teams to take root defined, and then a technical implementation so they can be recognized
<clever>
ivan: if you dont do that, then preInstall/postInstall just never work
<worldofpeace>
I do this with more complex expressions where someone would expect the pre post things to exist. but it's a pretty minor detail, not much block anything on.
<infinisil>
mkDerivation desperately needs a redesign
<clever>
id say its a good idea to have them, so confusion doesnt hit the next guy to .overrideAttrs (old: { postInstall, and nothing happens
<ivan>
OK, if you think those are a good idea then please merge so that PR author doesn't have to write some silly comment to "make clear [the] usage of runHook preInstall and runHook postInstall"
<infinisil>
I wouldn't want to have to mention that in all reviews..
<infinisil>
It's a minor detail imo, one which hopefully gets fixed with an eventual mkDerivation redesign