-
Notifications
You must be signed in to change notification settings - Fork 92
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
Transfer repository ownership to GitHub organization #306
Comments
@JoeLametta - I got the invitation for the orga, but it required me to set up 2fa, which I didn't do yet. JFYI. |
I just joined. |
👍 I've sent an invitation to @RecursiveForest and @Freso too. |
I've already migrated the plugins repositories to the organization: only whipper is left. |
Since GCI is starting Tuesday next week and we'll hopefully have some whipper tasks as part of that, it would be great if the repository could be transferred already on Monday so we won't have to scramble and update URLs in the tasks after they've been published. 🙏 😅 |
Also, I'm pretty sure GitHub will redirect HTTP requests after the transfer, so things should still continue to be downloadable from the current/old URLs, but repo maintainers won't be able to updated their packages until the move has actually been done, so the sooner it's moved, the sooner packages will be able to actually be updated. |
I confirm this.
All right, I've just sent an email to all known whipper's package maintainers stating that on 2018/10/21 (YYYY/MM/DD) I'm going to transfer this repository to the whipper-team organization. 😉 |
Done! 😉 |
Given the nature of this project, I'd like to transfer all whipper's related repositories (whipper, morituri-eaclogger, morituri-yamllogger) to a dedicated organization on GitHub.
I've created this issue to notify, in advance, users and package maintainers of this planned change.
The text was updated successfully, but these errors were encountered: