Skip to content
This repository has been archived by the owner on Dec 16, 2022. It is now read-only.

Badges badges badges #465

Merged
merged 4 commits into from
Jan 10, 2016
Merged

Badges badges badges #465

merged 4 commits into from
Jan 10, 2016

Conversation

astorije
Copy link
Collaborator

Pretty pretty badges, because red looks nicer in SVG!

@floogulinc
Copy link
Collaborator

Your LICENSE link is broken because there is no LICENSE file.

@astorije
Copy link
Collaborator Author

Ah, well spotted! Adding one right now!

@floogulinc
Copy link
Collaborator

You might want to change the name on the copyright to Mattias Erming before it is merged.

@astorije
Copy link
Collaborator Author

-__-'
Sorry, another paste hastily done...
Amended my last commit, thanks for your thorough eyes!

This was referenced Sep 14, 2015
@astorije
Copy link
Collaborator Author

@JocelynDelalande, @erming, may I have your respective 👍 on this?

@@ -0,0 +1,21 @@
The MIT License (MIT)

Copyright (c) 2015 Mattias Erming
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add « and contributors », since there is no CLA as far as I know.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh boy, that moment at the end of a talk when you hope no one would raise their hands when you ask "Any questions?"

I don't know. This is a tricky question. At first I was like, sure why not, then after reading this, I'm like, heck, that's why not. Honestly, we do not want a CLA, that would just get in the way of enhancing that project (I know of one project I contribute to that requires to sign a CLA, and boy it's tedious for everyone).

This seems like we would need a keen eye on this. I'm sure she is very busy, but if @wseltzer happens to receive notifications, and would be okay to help us a bit, that would be great :-)
@wseltzer, essentially, this is an Free and Open Source Software project under the MIT license and we get a lot of contributions. What would be the best thing to type here? Of course it's always nice when we give the right credit to the right people, but on the other hand if that forces us to get agreement from all contributors if we decide to change license), that would be hard to organize.

@JocelynDelalande, what I am sure about though, is that I want this PR to make it into master quickly :-) Can I get your +1 and continue the discussion to reach to a solution even if it has to be done post-merged, in another PR?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JocelynDelalande, what I am sure about though, is that I want this PR to make it into master quickly :-) Can I get your +1 and continue the discussion to reach to a solution even if it has to be done post-merged, in another PR?

Sure :) so please reflect current project state : copyright holder is "Mathias Erming and contributors", I was not discussing if we wanted a CLA or not, that's outside the scope of this PR.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aaah yeah, sure, whatever, done in 92d2466.

@erming
Copy link
Owner

erming commented Sep 27, 2015

-1 for me. Sure, you can add the license if you want (even though I don't think it's needed). But I don't know about the badges. I just think they're ugly and unnecessary.

@astorije
Copy link
Collaborator Author

@erming, badges are a nice display of seriousness accessible on a first glance.
Almost all open source projects out there provide a Travis CI badge for example, among other things to assess overall stability, and dependency badges are also very useful when assessing security concerns (deps flagged as insecure).

Let's follow well accepted/de facto open source conventions here please. Some world class examples:

Also, dude, it's SVG badges, how can you find them ugly! :D (PNG badge on the current README weeps my eyes on Retina ^^)

@astorije
Copy link
Collaborator Author

Also, it adds transparency (if our project is broken, we don't hide it), which is always a good thing.

@williamboman
Copy link
Contributor

+1 For badges, definitely a good addition.

@JocelynDelalande
Copy link
Collaborator

That's a 👍 for me also.

@erming those badges are not a matter of being « flashy & shiny », (yes, visual aspect is debatable but it's bikeshedding IMHO).

The matter is : it allows some visitor to evaluate quickly your project : is it active ? are dependencies up-to-date ? are tests passing ?

I'm evaluating OSS projects on a daily basis, the information carried by badges is valuable as hints about software quality.

It's not about having a badges collection, it's about being transparent on software quality.

Another point in favor of those badges is: if they are turning red, it will give us a reminder to take action in order to get them green.

@JocelynDelalande
Copy link
Collaborator

@astorije is PR title in link with http://www.badgerbadgerbadger.com/ ?

@astorije
Copy link
Collaborator Author

@astorije is PR title in link with http://www.badgerbadgerbadger.com/ ?

What else? ^^

Also thanks @JocelynDelalande for putting better words on my exact thoughts. Hope that @erming will change his mind :-)

@astorije
Copy link
Collaborator Author

Ah, another pro-badges argument: I froze for a moment where trying to get to our Travis CI builds. "Wait, where do I click already? Right, I need to manually type the URL..." :-)

@Calinou
Copy link
Contributor

Calinou commented Oct 4, 2015

👍

@astorije astorije force-pushed the astorije/badges branch 2 times, most recently from b028303 to a67a77d Compare October 7, 2015 02:33
@astorije
Copy link
Collaborator Author

astorije commented Oct 7, 2015

Rebased on master to comply with changes added by #508.

@erming
Copy link
Owner

erming commented Jan 10, 2016

Remove License and devDependencies and it's all good!

@astorije
Copy link
Collaborator Author

Whyyyyyy, please nooooo! What's wrong with clearly expressing what free license we are using and easily linking to it?!

@astorije
Copy link
Collaborator Author

I live to fight another day. Removed, merging now.

astorije added a commit that referenced this pull request Jan 10, 2016
@astorije astorije merged commit 2f5b166 into erming:master Jan 10, 2016
@astorije astorije deleted the astorije/badges branch January 10, 2016 23:47
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants