Skip to content
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

Mainstream this repo #35

Open
XVilka opened this issue Aug 27, 2019 · 15 comments
Open

Mainstream this repo #35

XVilka opened this issue Aug 27, 2019 · 15 comments

Comments

@XVilka
Copy link

XVilka commented Aug 27, 2019

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.

@daa84
Copy link
Owner

daa84 commented Aug 28, 2019

Ok
how can i do this?

@XVilka
Copy link
Author

XVilka commented Aug 29, 2019

FYI @justinmk @blueyed @mhinz @bfredl @vhakulinen

@mhinz
Copy link

mhinz commented Aug 29, 2019

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.

@justinmk
Copy link

justinmk commented Aug 29, 2019

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.

@XVilka
Copy link
Author

XVilka commented Sep 13, 2019

@daa84 so, what have you decided?

@daa84
Copy link
Owner

daa84 commented Sep 16, 2019

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.

@justinmk
Copy link

Are you ok with others taking the lead on it then? @vhakulinen do you have interest in maintaining this ?

@vhakulinen
Copy link
Contributor

vhakulinen commented Sep 17, 2019

@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?

@h-michael
Copy link
Contributor

I can help maintaining too. ;)

@KillTheMule
Copy link

I'd be interested in working on this as well.

@XVilka
Copy link
Author

XVilka commented Oct 14, 2019

So, what was decided? @daa84

@justinmk
Copy link

I haven't seen a transfer request.

@XVilka
Copy link
Author

XVilka commented Dec 9, 2019

@daa84 I noticed there was some activity recently, could you please check this issue again?

@XVilka
Copy link
Author

XVilka commented Jan 13, 2020

@daa84 so what you have decided?

@ModProg
Copy link

ModProg commented May 14, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants