-
Notifications
You must be signed in to change notification settings - Fork 21
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
Migrate to dlang-community #75
Comments
Actually, all you need to do to transfer is to give me (or any other dlang-community admin) Owner / Admin access to this repository for me to do the transfer. |
You're both added as what GitHub is calling "collaborators". I don't see anything in GitHub's current UI about "Owner" or "Admin" so I don't know if that's sufficient or not. |
I think collaborators don't have the permissions to do a package transfer, at least I cannot initiate it. I think everyone in the dlang-community group can create repositories, so inviting you to the group should work instead. I invited you to dlang-community, so if you would like to join and migrate the repository there that would be appreciated. |
@Abscissa : Did you have any chance to look at transferring the repository ? |
It wouldn't let me transfer to dlang-community (not a member) or WebFreak001 (repo named SDLang-D already exists) so I transfered to Geod24. |
@Abscissa last time you didn't accept the invitation in time, so it expired - I sent you a new one now and you should see it in your github notifications inbox as well as your emails. |
And I don't think the repo has been transferred to me, I can't see anything to that effect. |
Would you like to transfer this repository to dlang-community so there are more contributors that can merge pull requests?
Since this project is (vendored) inside dub and has a lot of stars I think it'd be good to move it there.
If you agree to this, feel free to just comment here, we will invite you to the organization, then you can transfer the repository in the repo settings and some dlang-community members (I guess dub maintainers primarily) can then work on it more.
The text was updated successfully, but these errors were encountered: