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

Forking and renaming? #39

Open
tillt opened this issue Oct 3, 2017 · 6 comments
Open

Forking and renaming? #39

tillt opened this issue Oct 3, 2017 · 6 comments

Comments

@tillt
Copy link
Contributor

tillt commented Oct 3, 2017

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

@rampage644
Copy link
Owner

rampage644 commented Oct 4, 2017

Hey,

I have nothing against you taking full contol and becoming main maintainer of it. ;)

@rampage644
Copy link
Owner

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.

@tillt
Copy link
Contributor Author

tillt commented Oct 15, 2017

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;

  • rename the plugin to RTagsComplete as sublime-rtags is not so welcome in package control
  • allow me to push feature branches to the repo
  • allow me to merge feature branches
  • allow me to merge PRs
  • at some point in the future, allow me to rename the repo towards RTagsComplete
    • this I would only do after having contacted sites that link to your original version

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/

@tillt
Copy link
Contributor Author

tillt commented Oct 15, 2017

Turns out that renaming a repo is no issue at all. Github will maintain all known names - so scratch the last point :)

@wastedepository
Copy link

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.

@tillt
Copy link
Contributor Author

tillt commented Jul 15, 2018

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.

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

3 participants