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

node.js version badges #45

Closed
dougwilson opened this issue Aug 16, 2014 · 18 comments
Closed

node.js version badges #45

dougwilson opened this issue Aug 16, 2014 · 18 comments
Labels

Comments

@dougwilson
Copy link
Contributor

since the version badges are not an official service (perhaps someone might get shields.io to add it, ehh?), i thought i would put down the different ones with there colors here:

Node.js 0.8
Node.js 0.10
Node.js 0.11

with 0.8 or lower being bright green, 0.10 being green and 0.11 being orange for not the greatest support, haha. the numbers would all go up one with 0.12 comes out, so 0.10 would then be green, etc.

@rlidwka
Copy link
Contributor

rlidwka commented Aug 16, 2014

... or matching traffic lights...

Node.js 0.8 // oldstable
Node.js 0.10 // stable
Node.js 0.11 // dev

PS: orange and red are too similar imho

@jonathanong
Copy link
Member

i think @rlidwka 's colors make more sense. my only issue is that 0.10 is so old it should be considered two versions. 0.10 should be green and 0.8 should be really really green. hahaha

@dougwilson
Copy link
Contributor Author

this is what it looks like:

filtered

@jonathanong
Copy link
Member

is your computer colorblind?

@jonathanong
Copy link
Member

or are we considering people with colorblindness? or am i just confused...

@dougwilson
Copy link
Contributor Author

oops, i mean to type "... to colorblind people" ;) i usually try to avoid the whole green/red duality for them haha

@dougwilson
Copy link
Contributor Author

really, it doesn't matter :) my idea was just to try and be like the badge to the left (npm version badge), but i guess eh

@yoshuawuyts
Copy link

I find these colors to be a little confusing. As a user I'd expect:

  • Green means it's stable / good to use
  • Red means I shouldn't use it.

e.g. Maybe it's a good idea to indicate unstable releases with red and stable releases with green? Orange, purple and fifty shades of yellow aren't intuitively clear.

@jonathanong
Copy link
Member

make any stable version green and any unstable version red? make 0.8 greener?

@rlidwka
Copy link
Contributor

rlidwka commented Aug 16, 2014

Green means it's stable / good to use
Red means I shouldn't use it.

By your definition we should make anything green. No point publishing something if you don't want people to use it, right?

So I'd suggest to redefine colors this way:

  • Green means "feel free to use it and report bugs if you see them"
  • Red means "feel free to use it and report bugs when you see them"

@jonathanong
Copy link
Member

yeah, it's not like we're goign to have >= 0.11 modules ever. let's just make everything green lol

@Fishrock123
Copy link
Member

So I'd suggest to redefine colors this way:

  • Green means "feel free to use it and report bugs if you see them"
  • Red means "feel free to use it and report bugs when you see them"

I feel no one will understand that. Dx

Also, no one might actually care.

@dougwilson
Copy link
Contributor Author

OK everyone, I updated the original post. How does that look to everyone?

@Fishrock123
Copy link
Member

Seems good to me.

@jonathanong
Copy link
Member

what about 0.6? can we make it even greeeener for mime-db? hahaha

@Fishrock123
Copy link
Member

meh

@dougwilson
Copy link
Contributor Author

lol. You just want to feel special, don't you :)? Because of your dev dependencies we can't actually run it in 0.6 on Travis, haha

@jonathanong
Copy link
Member

i'm liking the different shades of green we have now. close?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants