Hi all, I won't be maintaining this repository anymore. There are multiple reasons for that.
The first reason being that I'm migrating away from GitHub to Codeberg due to my lack of faith in Microsoft and other political reasons.
The second reason being that I've personally switched to using Helix as my code editor a while now already, since 2021.
If someone wants to be the maintainer, please leave a comment. @rockerBOO can then decide whether to appoint you as my successor, since it's their repository.
I will probably still be merging some PRs for a while until a successor is found, but not on a regular schedule.
Originally created by @tversteeg on GitHub (Mar 23, 2025).
Original GitHub issue: https://github.com/rockerBOO/awesome-neovim/issues/1488
Hi all, I won't be maintaining this repository anymore. There are multiple reasons for that.
The first reason being that I'm migrating away from GitHub to Codeberg due to my lack of faith in Microsoft and other political reasons.
The second reason being that I've personally switched to using Helix as my code editor a while now already, since 2021.
If someone wants to be the maintainer, please leave a comment. @rockerBOO can then decide whether to appoint you as my successor, since it's their repository.
I will probably still be merging some PRs for a while until a successor is found, but not on a regular schedule.
Thank you Thomas for your work in helping this project beyond your own usage of Neovim and lifting this list to it's current heights. It wouldn't be possible without you. I appreciate your help over these years.
I can fully appreciate you moving off Github. I don't think this list should be exclusive to Github but I think it has the most impact here still. A few tools use this list to allow people to not have to use Github but maybe limits people's contributions if they do not use it.
As for merging PR's I can try my best to keep up the merging as we find some other co-maintainers. I would like to keep the same regularity you have been able to do it. So feel free to do what you feel you need to do.
Thank you so much :)
<!-- gh-comment-id:2763076824 -->
@rockerBOO commented on GitHub (Mar 29, 2025):
Thank you Thomas for your work in helping this project beyond your own usage of Neovim and lifting this list to it's current heights. It wouldn't be possible without you. I appreciate your help over these years.
I can fully appreciate you moving off Github. I don't think this list should be exclusive to Github but I think it has the most impact here still. A few tools use this list to allow people to not have to use Github but maybe limits people's contributions if they do not use it.
As for merging PR's I can try my best to keep up the merging as we find some other co-maintainers. I would like to keep the same regularity you have been able to do it. So feel free to do what you feel you need to do.
Thank you so much :)
As an active Nvim user, I might be able to occasionally give a hand, provided some guidance at the beginning.
I've been referencing this list for a while to keep an eye on how the ecosystem is evolving, and would love to see it continue.
<!-- gh-comment-id:2867655406 -->
@Penaz91 commented on GitHub (May 9, 2025):
As an active Nvim user, I might be able to occasionally give a hand, provided some guidance at the beginning.
I've been referencing this list for a while to keep an eye on how the ecosystem is evolving, and would love to see it continue.
I can participate in the maintenance of the repositories
I have experience in plugin development myself and have participated in the contribution of some other plugins
Thank you for all the hard work!
But in my opinion, you don’t have to worry too much about Microsoft. Since Microsoft acquired github, github has achieved very rapid development and progress
<!-- gh-comment-id:2869659378 -->
@jinzhongjia commented on GitHub (May 11, 2025):
I can participate in the maintenance of the repositories
I have experience in plugin development myself and have participated in the contribution of some other plugins
Thank you for all the hard work!
But in my opinion, you don’t have to worry too much about Microsoft. Since Microsoft acquired github, github has achieved very rapid development and progress
@mcauley-penney commented on GitHub (Jul 24, 2025):
I'd be willing to take a role. I'm a plugin author who has submitted here a couple times and who plans to submit more in the future. I've been involved in the plugin ecosystem for quite a while and will be around for the foreseeable future
<!-- gh-comment-id:3114523286 -->
@mcauley-penney commented on GitHub (Jul 24, 2025):
I'd be willing to take a role. I'm a plugin author who has submitted here a couple times and who plans to submit more in the future. I've been involved in the plugin ecosystem for quite a while and will be around for the foreseeable future
<!-- gh-comment-id:3124691837 -->
@rockerBOO commented on GitHub (Jul 27, 2025):
@Penaz91 @jinzhongjia @mcauley-penney
Sorry I have been a little busy. I added some documentation for [maintainers](https://github.com/rockerBOO/awesome-neovim/blob/main/MAINTAINERS.md), and some scripts to try and automate some things.
Let's chat further in #1612
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 @tversteeg on GitHub (Mar 23, 2025).
Original GitHub issue: https://github.com/rockerBOO/awesome-neovim/issues/1488
Hi all, I won't be maintaining this repository anymore. There are multiple reasons for that.
The first reason being that I'm migrating away from GitHub to Codeberg due to my lack of faith in Microsoft and other political reasons.
The second reason being that I've personally switched to using Helix as my code editor a while now already, since 2021.
If someone wants to be the maintainer, please leave a comment. @rockerBOO can then decide whether to appoint you as my successor, since it's their repository.
I will probably still be merging some PRs for a while until a successor is found, but not on a regular schedule.
@wimstefan commented on GitHub (Mar 23, 2025):
Thank you for all the hard work!
You did an amazing job 🤩
@mosheavni commented on GitHub (Mar 23, 2025):
thanks for your work here!
@rockerBOO commented on GitHub (Mar 29, 2025):
Thank you Thomas for your work in helping this project beyond your own usage of Neovim and lifting this list to it's current heights. It wouldn't be possible without you. I appreciate your help over these years.
I can fully appreciate you moving off Github. I don't think this list should be exclusive to Github but I think it has the most impact here still. A few tools use this list to allow people to not have to use Github but maybe limits people's contributions if they do not use it.
As for merging PR's I can try my best to keep up the merging as we find some other co-maintainers. I would like to keep the same regularity you have been able to do it. So feel free to do what you feel you need to do.
Thank you so much :)
@Penaz91 commented on GitHub (May 9, 2025):
As an active Nvim user, I might be able to occasionally give a hand, provided some guidance at the beginning.
I've been referencing this list for a while to keep an eye on how the ecosystem is evolving, and would love to see it continue.
@cxwx commented on GitHub (May 10, 2025):
蹲一个后续
Thank you for all the hard work!
@jinzhongjia commented on GitHub (May 11, 2025):
I can participate in the maintenance of the repositories
I have experience in plugin development myself and have participated in the contribution of some other plugins
Thank you for all the hard work!
But in my opinion, you don’t have to worry too much about Microsoft. Since Microsoft acquired github, github has achieved very rapid development and progress
@mcauley-penney commented on GitHub (Jul 24, 2025):
I'd be willing to take a role. I'm a plugin author who has submitted here a couple times and who plans to submit more in the future. I've been involved in the plugin ecosystem for quite a while and will be around for the foreseeable future
@rockerBOO commented on GitHub (Jul 27, 2025):
@Penaz91 @jinzhongjia @mcauley-penney
Sorry I have been a little busy. I added some documentation for maintainers, and some scripts to try and automate some things.
Let's chat further in #1612