-
Notifications
You must be signed in to change notification settings - Fork 132
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 to roots-dev #198
Comments
I'm not sure that I'm totally down with the roots-dev team name... something about it doesn't seem right. Any other thoughts on a good organization name we could use to house roots projects? |
eh... not really sure what's wrong with it, but I'd be happy to rename it to whatever you want. |
What does the .cx extension stand for? You could go with something like that. But to be honest I'm really okay with roots staying under the /jenius/ name, I don't really think we're missing out on anything by having it here. |
can we name it a emojicon? if so I vote for 💇 |
👍 I approve |
@yoshuawuyts - it's the ccTLD for the Christmas Islands ... not much meaning for our project. Also, it's not really the name that matters (jenus would actually be a fine team name), it's just easier to manage projects with the GitHub team setup. |
🎄 |
Yeah that was the same reason I was thinking - it would just be easier to manage as a team. |
hmm... maybe we could just move the repos into a team and then deal with thinking of a better name later? |
related to your problem with obtaining the @roots username, any google search for roots gives results for something to do with wordpress (ugh). Perhaps use the word "Roots" in another language as the username ? |
Yeah, the "googleability" of roots is pretty poor, but changing the name now would be a huge pain... I guess we're just gonna have to become more popular than that wordpress theme. As for the idea of using another language: very creative! The Yiddish translation looks pretty cool too: |
👍 |
Now that we've split roots up into like 5 different projects, and a ton of helper utils, it might be worth revisiting this. Also, in the time since this issue was last updated, GitHub added repo redirects, which will make this sooo much easier: https://github.com/blog/1508-repository-redirects-are-here. The name "roots-dev" still kinda sucks... Moving into the carrot org would sorta make sense since they're funding most of the development of the project, but then it would be harder to add people who aren't a part of carrot because we'd need to deal with GitHub teams and we'd need to be very careful not to project a sense of exclusion that might prevent people outside of carrot from contributing (idk if company-name orgs actually do that, it's just something to be careful of). Also, there might be a little difficulty with keeping client-work separated from roots repos (because they're conceptually different, so it seems a little odd to put them in the same org). Maybe we could make an org with a name like "carrot-labs"? It would still maintain that nod to carrot, without mixing roots together with client-projects. Thoughts? |
Would be interested to hear @kylemac's thoughts here as well |
Closing due to inactivity. If this is moved, it will probably be to carrot |
Well, as we found out in #190, we're not getting the @roots username :(
But I did make an account called @roots-dev which kinda makes sense because we're making a development tool... Yes, I know it isn't as cool as @roots, but it's pretty damn close.
Soooo... lets make a list of the stuff that we need switch in order to move this repo over to @roots-dev, and then do it... GH will provide some redirects, but we should make sure that all the links are changed directly after moving.
Stuff that's already been moved over:
The text was updated successfully, but these errors were encountered: