-
Notifications
You must be signed in to change notification settings - Fork 265
Feature: Dynamic badge #171
Comments
I think |
I agree with @shurcooL that projects shouldn't be penalized for not including a That being said I do recognize the need to label Go projects based on their license. In most cases it should be possible to determine the license of a project without requiring a dedicated An example of such wording is given in the |
I'm not sure exactly what the intention is around the license:
Considering packages in I think the main criteria should be that their is reference documentation and package descriptions that GoDoc can use. |
Sounds good. I think placing a badge in the README is in itself an indication that a developer wants to share a package and wants to provide easy access to the documentation. |
What's the status here? |
I'm not sure if this is something we still want. I came at this from the angle of being able to make the badge dynamic, so what could we make it do. That doesn't seem like the best way to design features. |
Agree. Let's shelve it for now. |
Pass/fail #107 (comment)
![BSD](http://img.shields.io/badge/license-BSD-green.svg)
Another possibility is a sort of "documentation coverage" score. See #107 (comment).
The text was updated successfully, but these errors were encountered: