{"action":"created","issue":{"url":"https://api.github.com/repos/linuxfoundation/cii-best-practices-badge/issues/474","repository_url":"https://api.github.com/repos/linuxfoundation/cii-best-practices-badge","labels_url":"https://api.github.com/repos/linuxfoundation/cii-best-practices-badge/issues/474/labels{/name}","comments_url":"https://api.github.com/repos/linuxfoundation/cii-best-practices-badge/issues/474/comments","events_url":"https://api.github.com/repos/linuxfoundation/cii-best-practices-badge/issues/474/events","html_url":"https://github.com/linuxfoundation/cii-best-practices-badge/issues/474","id":172321663,"number":474,"title":"Add criteria to comply to implemented standards","user":{"login":"david-a-wheeler","id":813150,"avatar_url":"https://avatars.githubusercontent.com/u/813150?v=3","gravatar_id":"","url":"https://api.github.com/users/david-a-wheeler","html_url":"https://github.com/david-a-wheeler","followers_url":"https://api.github.com/users/david-a-wheeler/followers","following_url":"https://api.github.com/users/david-a-wheeler/following{/other_user}","gists_url":"https://api.github.com/users/david-a-wheeler/gists{/gist_id}","starred_url":"https://api.github.com/users/david-a-wheeler/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/david-a-wheeler/subscriptions","organizations_url":"https://api.github.com/users/david-a-wheeler/orgs","repos_url":"https://api.github.com/users/david-a-wheeler/repos","events_url":"https://api.github.com/users/david-a-wheeler/events{/privacy}","received_events_url":"https://api.github.com/users/david-a-wheeler/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/linuxfoundation/cii-best-practices-badge/labels/criteria","name":"criteria","color":"fbca04"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-08-21T13:42:53Z","updated_at":"2016-08-22T21:00:16Z","closed_at":null,"body":"Niels Lohmann (project \"[JSON for Modern C++](https://bestpractices.coreinfrastructure.org/projects/289)\") suggested adding compliance to implemented standards:\r\n\r\n> For the badge, I currently see a strong focus on security-related issues, which is understandable. I think it would also be nice to make some effort to reason about compliance to implemented standards. For instance, my project implements JSON (RFC 7159) which also includes a lot of the Unicode standard. It is easy to miss some edge cases of these standards, so it may be a good idea to ask whether the project uses some known test suite, or at least lists all covered standards to be explicit about such dependencies.\r\n\r\nIn principle this makes sense.  This one may be tricky in detail.  He already noted that this would only apply to \"implemented\" standards (that helps).  However, there are many “standards” with edge cases you should *not* implement, or maybe they shouldn't apply in your case.  But the basic idea seems very good, if we can figure out how to handle the details (maybe this applies to a \"higher level\" badge).\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/linuxfoundation/cii-best-practices-badge/issues/comments/241548747","html_url":"https://github.com/linuxfoundation/cii-best-practices-badge/issues/474#issuecomment-241548747","issue_url":"https://api.github.com/repos/linuxfoundation/cii-best-practices-badge/issues/474","id":241548747,"user":{"login":"bagder","id":177011,"avatar_url":"https://avatars.githubusercontent.com/u/177011?v=3","gravatar_id":"","url":"https://api.github.com/users/bagder","html_url":"https://github.com/bagder","followers_url":"https://api.github.com/users/bagder/followers","following_url":"https://api.github.com/users/bagder/following{/other_user}","gists_url":"https://api.github.com/users/bagder/gists{/gist_id}","starred_url":"https://api.github.com/users/bagder/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bagder/subscriptions","organizations_url":"https://api.github.com/users/bagder/orgs","repos_url":"https://api.github.com/users/bagder/repos","events_url":"https://api.github.com/users/bagder/events{/privacy}","received_events_url":"https://api.github.com/users/bagder/received_events","type":"User","site_admin":false},"created_at":"2016-08-22T21:00:16Z","updated_at":"2016-08-22T21:00:16Z","body":"The more I think about it, the more I think it is *purely* a matter of documentation.\r\n\r\nIf I document that my product clearly breaks a protocol or standard, but everybody likes it and the project follows all our existing best practices. Are we then suddenly saying it isn't following best practices because of that?\r\n\r\nIt is on overreach to try to cover standards and behavior compliance for a project best practices methinks.\r\n\r\nA project can meet \"100% best practices\" and still be a project people don't want to use because of what it does and doesn't do as a program. We can't and shouldn't try to fix what the code actually does."}}
{"actor":{"display_login":"bagder"}}