neovim-lib
neovim-lib copied to clipboard
daa84
Mainstream this repo
What about moving the repo under the neovim namespace?
It is an organization, so you will retain the same access, while increasing the repository visibility.
They host libraries/clients for another languages as well: https://github.com/neovim/
It will help to improve testing as well.
Pro: Might increase visibility.
Contra: I could imagine that people consider repos within the neovim organization to be "official" and expect core members to work at it. So, when daa84 should ever stop contributing, we're left with a dead repo.
Then again, we're already the home of other providers that don't see much activity, so... yeah, I'm mostly in favor of it.
Certainly we're in favor of this if @daa84 , @vhakulinen and any others using the library want to work together on it. @daa84 would have "admin" access and then manage it as needed.
how can i do this?
Using GitHub "transfer" feature to transfer to the "neovim" organization. https://help.github.com/en/articles/transferring-a-repository
Is it too late to change the library name? It is better for users if Nvim clients don't have the name "neovim" or "neovim lib" because this is too generic and makes documentation and discussions more verbose. E.g. an unambiguous identifier like nvimrust is better than "neovim-lib, the Nvim rust client". It also makes searching for documentation and discussions easier. See also :help dev-api-client.
we're already the home of other providers that don't see much activity,
We want to avoid that, and will retire anything that gets abandoned.
Ok, I can transfer it to neovim organization. Lately i don't have much time on develop this library, only some basic support. Is it ok? Currently neovim-lib also registered on creates.io with same name, so not sure about renaming.
Are you ok with others taking the lead on it then? @vhakulinen do you have interest in maintaining this ?
@vhakulinen do you have interest in maintaining this ?
I would, as part of gnvim development. My time is limited but I'll do what I can.
What would happen to the neovim-lib crates package? I guess that should move under neovim's (the organization) ownership then?
@daa84 I noticed there was some activity recently, could you please check this issue again?
I mean this is Open Source so as @daa84 expressed interest but for some reason wasn't able to transfer this library it would be possible to create a fork, right? As long as there are people willing to administrate that.
