Skip to content

Conversation

@christianh814
Copy link
Member

This PR removes inactive maintainers from the maintainers' file.

Context: #107

Signed-off-by: Christian Hernandez christian@codefresh.io

Signed-off-by: Christian Hernandez <christian@codefresh.io>
@christianh814 christianh814 mentioned this pull request Jun 17, 2022
4 tasks
@christianh814 christianh814 removed the request for review from chris-short July 1, 2022 17:45
@christianh814
Copy link
Member Author

+1 Binding

Copy link
Member

@scottrigby scottrigby left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Its true project governance does say that – among other maintainer responsibilities – maintainers must:

  • Maintain involvement and open collaboration with working group members and committees
  • Ask for help when unsure and step down considerately when appropriate

But a few things before merging this or any PR like it:

  1. personally, I would ideally like to hear from @chrispat and @csand-msft on this PR about their upcoming availability before removing either of them from the maintainers list. If we can not reach any maintainer for a period of time (perhaps a few months?) then I agree at some point it would make sense to remove without hearing back. But I don't think we're there yet
  2. It would make sense to separate these PRs individually, if we hear back from one person and not the other. Because they are not really tied together for any specific reason
  3. When/if a maintainer is removed, let's add them to an alumni section somewhere. We currently have a GitHub team called alumni with previous maintainers on it. I think it would be nice to add that to this or another file just to publicly recognize their service

@todaywasawesome
Copy link
Member

CC #115

I'm unclear on the process to remove maintainers per the governance doc today.

@todaywasawesome
Copy link
Member

This will be resolved in a separate PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants