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

Complete the Learn Teach Code name change #26

Open
LearningNerd opened this issue Dec 20, 2016 · 9 comments
Open

Complete the Learn Teach Code name change #26

LearningNerd opened this issue Dec 20, 2016 · 9 comments

Comments

@LearningNerd
Copy link
Member

LearningNerd commented Dec 20, 2016

Remaining to-dos for this:

  • Change the name and URL on Twitter (more details on the process here), send a tweet notifying people.

    • Since "LearnTeachCode" is taken on Twitter and we haven't had luck yet hearing back from the guy who claimed it, suggestions for our new Twitter handle include: LTCorg, LearnTeachCode_, _LearnTeachCode, or just leave it as LearnToCodeLA a while longer.
  • Work on plan for merging GitHub and website with Learn Teach Code Seoul (coordinating with @TheBeege)

After some discussion (see #19) and a vote, we're all set to change our organization's name to Learn Teach Code!

In this issue I'll list the tasks for making the name change as I think of them, so feel free to add your thoughts here on how to make the transition go as smoothly as possible. Thanks!

Tasks for name change, for LA group and general stuff:

  • I will send two mass email and Slack announcements: one before the name change as a heads up, and one immediately after to give people all our new links and remind everyone to update their bookmarks.
  • Change the name and URL on Meetup (according to this, they will redirect from the old URL, yay!)
  • Remember to change the name/URL in our Meetup description/settings/welcome email too
  • Change our organization name and URL on GitHub (see details on how GitHub handles this)
  • Archive Facebook group (since nobody's using it). We can always revive it later.
  • Set up a redirect from LearnToCodeLA.org/.com to LearnTeachCode.org
    - Change our Slack team name and URL
  • Update links in any upcoming meetup event pages for our Slack, Twitter, website etc
  • Create new company page on LinkedIn (now at https://www.linkedin.com/company/learn-teach-code)
  • Set up a redirect for our Slack signup page
@TheBeege
Copy link
Member

We have a site, but no one is yet using it. The Seoul site should be easy to port. I imagine we can setup a post-commit hook to auto-update things as needed.

Can we add a unified Github org to this, too? Or do you think they would be better separate?

If we do the Gitter thing, I have suggestions, based on my last company's move to Slack. They identified people likely to be early adopters and got them in on it as kind of a closed beta. They helped flesh out the channels, figure out a channel taxonomy, setup custom emotes, and all that sort of stuff. Once the dust settled from all the customizations they'd done, they started communicating out a date to move everyone to Slack and allowed teams to move over early. I think that strategy would be helpful here, too.

So are we not communicating out the name change yet?

@LearningNerd
Copy link
Member Author

@TheBeege On the site -- cool :)

Not announcing the name change just yet, I want to make sure I have a roadmap for the change first so I can make sure the announcement is clear! I plan to announce it this week though, as a heads up for everyone, and maybe we do that actual name change in January? What do you think?

On GitHub - Yup we could definitely make a unified GitHub now, I'm all for that -- I think! I haven't really considered the challenges of combining them yet. I'd like to chat with you more on that via private message or a call sometime soon! Feel free to post thoughts on that here in the meantime though.

On Gitter -- I made a new issue for it, #27 Try Gitter...

@TheBeege
Copy link
Member

@LearningNerd

Name change - Sounds good to me. I've been hinting at it among the Seoul group, but I've been mostly committal about it.

Github - I believe we'd just need to create the new org and migrate all the repos. IIRC, GitHub maintains redirects for transferred repos and provides a message when you push to a deprecated repo. It should make things relatively painless.

Gitter - Cool

I'm in Florida until the 29th, so I'm more easily available

@TheBeege
Copy link
Member

Seoul links:

@ghost
Copy link

ghost commented Feb 11, 2017

I'll get on building a new LinkedIn page.

@LearningNerd Hook me up with an email address you'd like to link to the new (or old) LinkedIn account.

@LearningNerd
Copy link
Member Author

I'll be taking care of this very soon. BTW @easyspirit who are you? lol I don't see a name on your profile and I'm terrible at names and especially names + various usernames. 😆

@ghost
Copy link

ghost commented Feb 15, 2017

var easyspirit = Ray;

@LearningNerd
Copy link
Member Author

@easyspirit oh hai! :D hahaha. I'm gonna do the linkedin thing now, since I already have the old org page there. Thanks though!! I wanna link it to the domain email which for now only I have access to. Gotta figure out the whole email thing eventually... any experience there or research is appreciated. (that of course will belong in a separate issue, don't wanna hijack this thread too much)

@ykcab
Copy link

ykcab commented May 22, 2021

@LearningNerd what else do we need support for on completing the brand legalization?

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