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

Move Typhoon to its own org in GitHub #71

Closed
jasperblues opened this issue Sep 8, 2013 · 11 comments
Closed

Move Typhoon to its own org in GitHub #71

jasperblues opened this issue Sep 8, 2013 · 11 comments

Comments

@jasperblues
Copy link
Member

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.

@jasperblues
Copy link
Member Author

  • AFAIK these are the steps that will need to happen:
  1. Create an organization account called Typhoon. Reassign the repositories: Typhoon, Typhoon-example, OCLogTemplate to the Typhoon repository.
  2. Update links in the website. . . perhaps also check in the code on the website.

@jasperblues
Copy link
Member Author

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.

@jasperblues
Copy link
Member Author

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.

@jasperblues
Copy link
Member Author

We also need to change the links in the podspecs in the main spec repo. . RubyMine's 'Replace In Path' should do this quickly.

@jasperblues
Copy link
Member Author

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

@jasperblues
Copy link
Member Author

Done:

Created the new organisation
Forked the old repos, left a message saying we’ve moved. This will prevent broken links for now.

Need to Do:

Edit all the StackOverflow questions to change the links
Update the CI build to publish to the new page
Update typhoonframework.org to pull updates to gh-pages from the new repo
Update all the links in the PodSpecs
Register an info@typhoonframework.org email address, and create a gravatar

@jasperblues
Copy link
Member Author

Done:

  • Created the new organisation
  • Forked the old repos, left a message saying we’ve moved. This will prevent broken links for now.
  • Update the CI build to publish to the new page (needs testing)
  • Update typhoonframework.org to pull updates to gh-pages from the new repo
  • Register an info@typhoonframework.org email address, and create a gravatar (need better logo)
  • Update all the links in the PodSpecs

Need to Do:

  • Edit all the StackOverflow questions to change the links (some down)
    *What else?

@jasperblues
Copy link
Member Author

Also need to stick Daniel and Erik on the website. . . will try to get that done tonight. . have to do some real work now.

@jasperblues
Copy link
Member Author

Site update done. . .

All the wiki links in the README need updating.

@drodriguez
Copy link
Contributor

README done at dbb8ab3. I’m going to edit those questions on SO.

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?

@jasperblues
Copy link
Member Author

Thanks folks! Let's close this and tackle any remaining issues one by one.

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

2 participants