Automatic retirement of @colemickens

[nixpkgs-committers]

This is an automated PR to retire @colemickens as a Nixpkgs committers due to not using their commit access for 1 year.

Make a comment with your motivation to keep commit access, otherwise this PR will be merged and implemented in 1 month.

[nixpkgs-committers]

One month has passed, to this PR should now be merged and implemented by:

• Adding @colemickens to the Retired Nixpkgs Contributors team

  gh api \
    --method PUT \
    '/orgs/NixOS/teams/retired-nixpkgs-contributors/memberships/colemickens' \
    -f role=member

• Removing @colemickens from the Nixpkgs Committers team

  gh api \
    --method DELETE \
    '/orgs/NixOS/teams/nixpkgs-committers/memberships/colemickens'

[colemickens]

Hm, I don't understand why/how maintainers are being retired when they have packages that they're listed as maintainer on.

I did just do some review and one merge.... I wouldn't mind keeping the bit, but I understand if there's some new policy in place. Cheers!

[MattSturgeon]

I don't understand why/how maintainers are being retired when they have packages that they're listed as maintainer on.

This has nothing to do with retiring maintainers. This is about retiring committers, as per RFC 55. See Semi-automatic retirement in this repo's README.

There is separate guidance for retiring inactive maintainers, either removing them from packages they aren't actively maintaining or removing their maintainers entry entirely if they aren't active at all as a maintainer. See Losing maintainer status in the nixpkgs maintainers README.

I did just do some review and one merge.... I wouldn't mind keeping the bit, but I understand if there's some new policy in place. Cheers!

As I'm not part of the commit bit delegation team, I haven't looked at your personal activity, and I'm not intimately familiar with the policies from RFC55, I won't comment on whether your commit bit should or shouldn't be removed. But I will say that any removal need not be permanent; retired committers (and maintainers, for that matter) are welcome to re-apply.

As an aside: I believe the automation is based on how recently you merged changes into nixpkgs (since, for the most part, that's the only thing you need commit bit to actually do).

[colemickens]

Aha, right, that totally makes sense, thank you @MattSturgeon. I very much understand and appreciate the desires to keep this committer list tight, and I leave it to the team to decide my fate. :) Cheers!

[winterqt]

I did just do some review and one merge....

It looks like the last PR you merged was in [I can't actually find it, GitHub's search sucks]. Just to make sure the automation isn't missing anything, can you clarify what PR you've recently merged, and/or if you're going to review/merge PRs in Nixpkgs going forward? Thanks!

[wolfgangwalther]

can you clarify what PR you've recently merged

That would be NixOS/nixpkgs#441582.

The one before was NixOS/nixpkgs#331628, I think.

So automation is alright.