-
Notifications
You must be signed in to change notification settings - Fork 268
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
Move Typhoon to its own org in GitHub #71
Comments
|
tentative date for the move is December 8th GMT+8. . . (as long as I can get my client workload cleared). Please avoid commits to the Typhoon website on this day. |
Also need to set up an "info@typhoonframework.org" email address, so that I can use it as a Gravatar picture for the logo on the GH org. |
We also need to change the links in the podspecs in the main spec repo. . RubyMine's 'Replace In Path' should do this quickly. |
Tentative plan was for Dec 9th. This didn't happen as I was working on the new Typhoon docs. . . . this week I'm busy with a client project. . we have a change-over plan here. . . let's execute before Dec 29th |
Done: Created the new organisation Need to Do: Edit all the StackOverflow questions to change the links |
Done:
Need to Do:
|
Also need to stick Daniel and Erik on the website. . . will try to get that done tonight. . have to do some real work now. |
Site update done. . . All the wiki links in the README need updating. |
README done at dbb8ab3. And SO done (everything I could find). Should we remove the wiki pages from the old repo? Or maybe include a warning at the top? |
Thanks folks! Let's close this and tackle any remaining issues one by one. |
I started Typhoon on my own, but we have some fantastic contributors now. . .
. . to recognize shared ownership, when it reaches 400 stars in GitHub, we'll move it to its own organization page.
The text was updated successfully, but these errors were encountered: