-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Update Repository Tagline #1714
Comments
Also, the IRC topic: |
Isn't that still technically correct? (If you're an admin you should be able to change it though?)
haha yeah, same-ish as above, but we can change that to anything. :) I'm also going to re-structure the motd a bit and remove the node-forward links once we get suitable replacements on the site. |
the fun thing about the tagline on github is that a bunch of people have access to edit it and I'm not sure it's logged anywhere who changes it to what, it just appears changed - so if you have access and you don't like it, then change it and we'll just have a fun and friendly edit war that will keep us all amused |
Maybe "The future (of) Node.js —"? (Since it effectively is now?) |
Been updated to 'Node.js Next', I think thats fine. |
That's fine except it's boring like hell. Maybe write something like "The Future of the Node.js". |
Maybe @rvagg can change that (I think everyone with 'Owner' can do). |
@mikeal could probably make something even more suiting. :) |
Reopening until consensus is reached. I'm neutral :) |
fixed |
👍 @rvagg |
Casting my vote for "input/output jerry seinfeld." |
I feel very proud to have kicked off such a vibrant bike shedding exercise!
|
"Mostly Harmless Spork of Node.js(tm)" -- and we've gone full circle! this is like the logo thread all over again! |
"Node.js fork™". simplicity does it (but don't forget the ™!!!) |
do we need to like tc-agenda this or something |
I don't think this needs to be tc-agenda, if someone comes up with something great then we'll all recognise it and it'll happen. The main problem is that it's unclear what the future of this repo is so it's not obvious how to label it now. But that's OK. |
"The America of node.js"? ... I'll see myself out. |
It should be messaged that this will end up becoming nodejs/node's master branch, aka it's future, or something like that. |
How about: "JavaScript I/O" Thats what the iojs.org currently starts with. |
"Turtles all the way down" |
@bugs181 Actually io.js might just be "The turtle on top of V8" |
Why not go back to its roots: "libuv javascript bindings" |
Something along the lines of "Node.js leveled up" would fit, considering io.js's implementation of ES6 |
"Over 9000 in no time"? The way V8 is driving the version numbers... |
@bnoordhuis best one so far. |
The tagline looks updated. Could this be closed now? |
So be it. "Node.js, but with bigger and faster version numbers" is amusingly accurate. |
We're not actually going with this are we? I feel it doesn't do the project justice. |
since we don't know what the future of the io.js brand & project is beyond convergence then I suggest we leave it until we have something we want to actually message |
Expanding off of @rlidwka's idea, something like "Node.js' true destiny" would be fitting.
edit: Alternatively, there's always "Harder, better, faster, stronger" |
The light side of Node |
«Node.js, but with bigger and faster version numbers and more fun». |
Guess I'll reopen this once more, keep the suggestions coming. |
I think the real win here is focusing on the first sentence of README.md. Taglines are fun but not really where people spend most of their eye-time (insert research here). |
I think this should probably just be handled by the evangelism/marketing team eventually. For now I'd really like to message that io.js is what nodejs/node will be based off of. (Including in the readme)
|
Seems like folks are starting to take the tagline seriously – we might want to rein it in a bit, at least until nodejs/node becomes the official repository. |
The io.js repository tagline currently says, "A friendly fork of Node.js with an open governance model", this should be updated to more accurately reflect the current state of the foundation. It's minor, yes, but these things tend to be important.
/cc @mikeal @nodejs/tsc
The text was updated successfully, but these errors were encountered: