-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Which status of this project? #221
Comments
I am using it myself for tests with Neomake (using the branch from #107). |
Sad to hear that. It's a very useful tool with pretty good concepts to write tests for vim plugins. Nevertheless, thank you for your advice about your improvements, I'll try it. |
I still find this quite useful, and I see lots of projects using it still. I'd like to see it say alive. Would you consider migrating it to the @preservim org namespace? I would keep you as the listed owner, but I would facilitate some maintenance on it — specifically reviewing PR requests, triaging issues, and monitoring contributions for people who are consistently high quality and offering them some elevated permissions to help with the same (triage, pr review). You can see I've done this for several other well known plugins with pretty decent success. Nerdcommenter was the first in 2016 and it is still doing well today. Others joined along the way and several have active maintainers again besides myself (see for example tagbar contributions). |
As a completion, https://github.com/thinca/vim-themis is a good alternative for similar usage. |
Hi @junegunn ! I can see that you've merged in a PR 5 months ago, so it would seem that the vader.vim project is not entirely dead as some here mentioned (it may have been the case back then that there was no movement happening for a while). This plugin is doing something super useful and I'm happy to be using it for the vim-puppet plugin. There are alternative testing frameworks for vim/nvim but if this project is still alive and maintained, I'd rather keep on using it. Can you give us a status update for this project? Do you intend to keep on merging PRs, or did you mostly stop using / lost interest in it? If the latter, would you consider adding some folks to the repository as maintainers so that the project can stay alive? I personally don't know too much about the plugin's codebase so I don't feel comfortable proposing myself, but maybe other ppl that were active in PRs and issues in the past might be interested in taking on this role? let us hear your thoughts |
Both @blueyed and I are not actively developing vader.vim. But that doesn't mean it's broken, it works as expected and it's still used to test the existing plugins. You can certainly use it if the existing feature set covers your needs.
Simple ones, yes. But a feature that requires a lot of effort in reviewing and maintaining it is unlikely to be merged in the near future. On the flip side, because the upstream is essentially frozen, you can use a fork without worrying too much about not keeping up to date with it.
If there are volunteers, yes. Or we can officially suggest a link to the actively developed fork not to break existing tests that point to the master branch of this repository. |
@junegunn thanks for your feedback! |
Hi! I'm interested in is this project alive or, probably, another active fork exists?
The text was updated successfully, but these errors were encountered: