-
Notifications
You must be signed in to change notification settings - Fork 124
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
Is this repository still maintained ? #93
Comments
@paliari can the ownership be transferred to someone else who is active? |
@paliari
Willing people could flag their interest in this issue. Thank you for your great plugin and the time you have spent on it so far! I have a few open source projects myself and I know how it can be hard to find time to maintain properly. Maybe you are not even using the plugin yourself anymore, or even vue. But at least it would be great if you could open up for someone else to help out. Many might be using this in production and without maintenance, people will sooner or later consider switching to another plugin. |
As @paliari is not answering, I suppose he's not active on this project/github. |
Making the fork and moving activity there is easy enough, but we can't publish under the same npm name without given permission from @paliari . |
Actually I see there are 5 collaborators on the npm package. So I think any of those can publish. But probably not add another publisher. |
We may change the name if nobody pops up. I add people I found from npm package page : @dflourusso @neves |
I see many open issues with no answer from maintainer @paliari
We are using the component for a new developement and we started by fixing an issue when the field is empty (the list was not emptied).
The code is here : https://github.com/LaRoueVerte/v-autocomplete. We can still merge upstream :)
The text was updated successfully, but these errors were encountered: