Call for maintainers!

[trstringer]

This project started out of a need I had, and a gap in the existing tooling. Adoption was constantly increasing. Years later, this GitHub Action has been downloaded 2.4 million times.

At the time of writing this post, there are 13 contributors already on the project! With that being said, as the sole maintainer of this repo I no longer have the necessary time to contribute to this project: Responding to issues, reviewing pull requests, adding features, and fixing bugs.

While it would be possible to archive this project, I'm not sure that it is the right thing to do: Current and future users would continue to use this product, archived or not.

Why not fork? When a project reaches this state, it's not unusual to archive and then just expect interested developers to fork it and maintain their fork. But GitHub Actions is tightly coupled to trstringer/manual-approval, so that would have its own share of issues.

With that introduction out of the way, I think it is in the best interest of this product, its users, and open source software to onboard project maintainers. It would be ideal to have 2-4 active maintainers.

Who should be a maintainer? Somebody with GitHub Actions experience, or the desire to obtain that experience. Also a maintainer should be a modern code craftsperson that is passionate about shipping production-quality software. This GitHub Action can be part of important build and deployment pipelines. Not to mention, it is likely running inside many existing users' environments in their runners. It is important that changes are well-tested, and are the right thing for our users.

What will be my role? While I will likely not be part of daily operations, I would be part of new maintainer selection, design discussions, and periodic code reviews.

If you are interested in being a maintainer please respond to this issue. A requirement of being a maintainer is also that you have had an approved and merged PR that is not documentation only. Thanks!

[lizziemac]

I would be interested in becoming a maintainer! I have a PR merged and use the manual-approval action in my company's actions. I have a good understanding of GitHub actions, and would like to apply that knowledge here as able to introduce new features and improve older ones.

[snskArora]

Hi Thomas

I am interested in maintaining this action. I have an open PR, #142. I extensively use this action and losing support for this project would be a major setback for dozens of workflows I employed this in. Looking forward to possibly working with the community and helping this project continue to grow

[beverts312]

I would be interested in being a maintainer, I have #137 open and #138 queued up behind it (I kept them separate to keep the changes small and more consumable).

This plugin is great and definitely will be used at my company for the foreseeable future (currently using a fork but once/if my pr's get merged we will move back to the main project)

[trstringer]

@lizziemac @sunny-1651 @beverts312: Thanks so much for your interest and contributions! I have sent an invite to all three of you to become collaborators on this project! I'd love to start some group communication. I think email would be my preference. Could you all email me at thomas@trstringer.com? Once I have all of your emails, I'll start a group email thread so we can move forward in the same direction. Thanks!

[lizziemac]

Thanks @trstringer !

[alexivanov-danone]

Hi Thomas,
I have been working with GitHub actions for around 2 years as a DevOps engineer. We heavily work with actions, custom and marketplace alike, and i think i could help here. Let me know if you still need help.