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

what happened the repo's url ? #655

Closed
Shane-XB-Qian opened this issue Sep 14, 2020 · 9 comments
Closed

what happened the repo's url ? #655

Shane-XB-Qian opened this issue Sep 14, 2020 · 9 comments
Labels

Comments

@Shane-XB-Qian
Copy link
Contributor

maybe silly, but want to confirm tagbar 's repo had been transfer-ed or mirror-ed
from : remote.origin.url=https://github.com/majutsushi/tagbar.git to here ?
though the url still under 'majutsushi' at my local, (so need confirm if needed to update) but redirect to here automaticly now ..
the ori owner transfer-ed the repo ?

@alerque
Copy link
Member

alerque commented Sep 14, 2020

Yes. See #651.

@Shane-XB-Qian
Copy link
Contributor Author

Shane-XB-Qian commented Sep 14, 2020

ok, thanks your confirm, and i am reading #651 .
just may/would be a little confusion/mess, since looks (script) no way to detect the ownership change from the git config or sth at local, except the url redirection.

@alerque
Copy link
Member

alerque commented Sep 14, 2020

except the url redirection

This is exactly what redirection is for. The status code & redirect is literally a way of saying "This thing you were looking for on this URL has now moved, the canonical location is now some other place, I'm forwarding you over there." — it makes things continue to work seamlessly (not actually breaking the old URLs) while making sure as often as possible people end up on the new URLs. I don't know what else you expect to have happen.

@Shane-XB-Qian
Copy link
Contributor Author

well, sometime unless the ori owner confirmed, otherwise user maybe concerned the redirection was a security risk fake.
at least to me .. :) since looks no way to detect the change from git config or sth at local ..
at least, user maybe confused or hesitated if really need to update the url (e.g at plugin mgr) or had to ..

@alerque
Copy link
Member

alerque commented Sep 14, 2020

In the case of Github transferring repositories can only be initiated by repository owners. If the original owner didn't confirm the migration there wouldn't be redirects in the first place! That or the original owner's account is completely compromised, in which case you wouldn't be able to get trustworthy confirmation anyway—and the repository could be compromised in other ways without you noticing.

@Shane-XB-Qian
Copy link
Contributor Author

i see, but redirection did not always mean repo owner 's password had been hacked, but just the url ..
anyway, that just a concern or confusion (to me at least or only, perhaps), or a strange feeling.
but since this had been confirmed, and had done, then let it be. thanks your answer.

@Shane-XB-Qian
Copy link
Contributor Author

btw: you are doing a great job - i am a little worry some classic wonderful vim plugin lost update too :)
but moved all those repo into one account not sure if was a good idea, since/looks there was a vim-scripts account too - lots classic plugins from vim.org, but looks no update anymore.
another hand even though, not sure if git or github side later can feedback a redirection confirmation msg after clone/pull cmd, that maybe a little convinced/helpful to user.
fyi.

@alerque
Copy link
Member

alerque commented Sep 14, 2020

The @vim-scripts org was just scraping plugin sources from other sites (notably vim.org), there was no effort at maintaining them there. Everything in there should be considered a fork (or ignored).

Note that this effort is not pulling everything under one account. This is an organization namespace and has multiple people listed an owners and many more members with permissions on the projects they contribute to. Every one of the projects here has multiple admins and contributors. The idea is to diversify and spread out the responsibility, not to put it under one person.

I'd be happy to talk to other great classic plugins that are struggling but there are some qualifications. I'm not interested in loading up on a bunch of plugins that nobody is interested in maintaining, only in freeing up projects that are no longer primarily maintained by their original authors. There needs to be at least one active maintainer who is also willing to work with other collaborators, and the plugin has to be reasonable successful (say 1k stars or something). There are undoubtedly some other good ones out there that have lots of open PRs from active users, the original author is not actively working on, and somebody would be interested maintaining that we could consider—but this is a limited subset of all the classic plugins that have fallen by the wayside.

@Shane-XB-Qian
Copy link
Contributor Author

um.. looks like a biz mode - a some kind foundation.
whatever, i just wish some plugin e.g dbext would not dead ..

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

No branches or pull requests

2 participants