Looking to add maintainers to this project. MAINTAINERS.md goes into some detail of what is required. Make sure the addition/update passes tests, and is a valid plugin.
Will only require a few co-maintainers but if you are interested you can add yourself to this issue.
This issue is to keep communication transparent.
Originally created by @rockerBOO on GitHub (Jul 27, 2025).
Original GitHub issue: https://github.com/rockerBOO/awesome-neovim/issues/1612
Originally assigned to: @rockerBOO on GitHub.
Looking to add maintainers to this project. [MAINTAINERS.md](https://github.com/rockerBOO/awesome-neovim/blob/main/MAINTAINERS.md) goes into some detail of what is required. Make sure the addition/update passes tests, and is a valid plugin.
Will only require a few co-maintainers but if you are interested you can add yourself to this issue.
This issue is to keep communication transparent.
@mcauley-penney commented on GitHub (Jul 27, 2025):
I am interested in throwing my hat into the ring for a co-maintainer position!
<!-- gh-comment-id:3124692792 -->
@mcauley-penney commented on GitHub (Jul 27, 2025):
I am interested in throwing my hat into the ring for a co-maintainer position!
Hopefully my behaviour of "commenting on pull requests without taking action" is not too much of a bother.
I prefer taking a "maintainer in training" approach and compare my comments with what @rockerBOO (sorry for the mention!) would do before starting to merge things (and possibily doing damage).
I will start acting more independently as soon as I get the okay from the repo owner.
<!-- gh-comment-id:3133688652 -->
@Penaz91 commented on GitHub (Jul 29, 2025):
Hopefully my behaviour of "commenting on pull requests without taking action" is not too much of a bother.
I prefer taking a "maintainer in training" approach and compare my comments with what @rockerBOO (sorry for the mention!) would do before starting to merge things (and possibily doing damage).
I will start acting more independently as soon as I get the okay from the repo owner.
@Penaz91 Your approach is good, to understand the flow and possible blocking points. In most cases we can fix issues but look to keep things aligned to the checklist.
So you can look to Squash merge when you see the chance. Squash merge because we do not need the individual commits for this repo. Approving can still be a good approach if not clear if the PR should be accepted.
<!-- gh-comment-id:3144887608 -->
@rockerBOO commented on GitHub (Aug 1, 2025):
@Penaz91 Your approach is good, to understand the flow and possible blocking points. In most cases we can fix issues but look to keep things aligned to the checklist.
So you can look to Squash merge when you see the chance. Squash merge because we do not need the individual commits for this repo. Approving can still be a good approach if not clear if the PR should be accepted.
@rockerBOO Hello there. I'm interested in co-maintaining this repository. I've followed the steps laid out in CONTRIBUTING.md.
My approach may be rough around the edges still, but I am more than happy to follow any advice. Obviously, I'd wait for a second opinion in case I'm not sure.
I'm regularly available in this period of my life, so I trust with my capabilities to help out.
I'll keep my eyes open for your response!
<!-- gh-comment-id:3342730662 -->
@DrKJeff16 commented on GitHub (Sep 28, 2025):
@rockerBOO Hello there. I'm interested in co-maintaining this repository. I've followed the steps laid out in `CONTRIBUTING.md`.
My approach may be rough around the edges still, but I am more than happy to follow any advice. Obviously, I'd wait for a second opinion in case I'm not sure.
I'm regularly available in this period of my life, so I trust with my capabilities to help out.
I'll keep my eyes open for your response!
@DrKJeff16 Hey, sorry for the late response, a bit going on. I've added you. We worked through some issues already so I'm sure you're do great. Let me know if you have any questions.
<!-- gh-comment-id:3413418368 -->
@rockerBOO commented on GitHub (Oct 17, 2025):
@DrKJeff16 Hey, sorry for the late response, a bit going on. I've added you. We worked through some issues already so I'm sure you're do great. Let me know if you have any questions.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @rockerBOO on GitHub (Jul 27, 2025).
Original GitHub issue: https://github.com/rockerBOO/awesome-neovim/issues/1612
Originally assigned to: @rockerBOO on GitHub.
Looking to add maintainers to this project. MAINTAINERS.md goes into some detail of what is required. Make sure the addition/update passes tests, and is a valid plugin.
Will only require a few co-maintainers but if you are interested you can add yourself to this issue.
This issue is to keep communication transparent.
@mcauley-penney commented on GitHub (Jul 27, 2025):
I am interested in throwing my hat into the ring for a co-maintainer position!
@Penaz91 commented on GitHub (Jul 28, 2025):
Thanks for the invitation, I'm more than glad to accept and help out!
@Penaz91 commented on GitHub (Jul 29, 2025):
Hopefully my behaviour of "commenting on pull requests without taking action" is not too much of a bother.
I prefer taking a "maintainer in training" approach and compare my comments with what @rockerBOO (sorry for the mention!) would do before starting to merge things (and possibily doing damage).
I will start acting more independently as soon as I get the okay from the repo owner.
@rockerBOO commented on GitHub (Aug 1, 2025):
@Penaz91 Your approach is good, to understand the flow and possible blocking points. In most cases we can fix issues but look to keep things aligned to the checklist.
So you can look to Squash merge when you see the chance. Squash merge because we do not need the individual commits for this repo. Approving can still be a good approach if not clear if the PR should be accepted.
@DrKJeff16 commented on GitHub (Sep 28, 2025):
@rockerBOO Hello there. I'm interested in co-maintaining this repository. I've followed the steps laid out in
CONTRIBUTING.md.My approach may be rough around the edges still, but I am more than happy to follow any advice. Obviously, I'd wait for a second opinion in case I'm not sure.
I'm regularly available in this period of my life, so I trust with my capabilities to help out.
I'll keep my eyes open for your response!
@rockerBOO commented on GitHub (Oct 17, 2025):
@DrKJeff16 Hey, sorry for the late response, a bit going on. I've added you. We worked through some issues already so I'm sure you're do great. Let me know if you have any questions.
@DrKJeff16 commented on GitHub (Oct 17, 2025):
No worries! I'll get myself familiar for now. Thanks btw!