-
Notifications
You must be signed in to change notification settings - Fork 6
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
Forking and renaming? #39
Comments
Hey, I have nothing against you taking full contol and becoming main maintainer of it. ;) |
For now I've added you as a contributor, hope that will give you proper rights immediately. Other option is just transfer the ownership which I'm totally fine with. Let me know what options works best for you. |
Hey Sergei, thanks for your nice answer. Have now tried to push stuff onto new feature branches on your repo but that failed as I obviously don't have enough rights - I am afraid the "contributor" karma is not enough for that. So, here is what would be desireable;
I am afraid the only way to accomplish all of this is to transfer ownership of the repo; see https://help.github.com/articles/about-repository-transfers/ |
Turns out that renaming a repo is no issue at all. Github will maintain all known names - so scratch the last point :) |
Hi, is there any update on this? I also have some contributions I would like to share, regarding settings related to connecting to remote machines and accessing files via SFTP. |
Dear @rampage644 - I would like to reiterate on my proposal. I will now try to update the package-manager metadata with a PR. Chances are however that the maintainers will not let me do that, given that I am not the original author. Will keep you posted. |
Dear @rampage644,
What do you think about me taking over a forked (and renamed?) version of this plugin?
In my current fork I have now added a bunch of new features which I would love to get published and given to more users as soon as possible.
As you have stated before, you don't use this plugin anymore while I am using it every single day for my work. Creating PRs against your repo is certainly still an option I do not want to dismiss too hastily. However I feel bothering you with issues and PR merging which you won't be quality checking is not the most efficient thing to do at this point. On that thought, please note that I posted some new issues a bunch of days ago.
Please let me know if I was stepping on your toes here - that is something I definitely do not want to do. If you would prefer keeping full control of community support and new developments on this plugin, then I would be more than happy to keep contributing.
cheers!
Till
The text was updated successfully, but these errors were encountered: