{"action":"created","issue":{"url":"https://api.github.com/repos/TestAnything/Specification/issues/17","labels_url":"https://api.github.com/repos/TestAnything/Specification/issues/17/labels{/name}","comments_url":"https://api.github.com/repos/TestAnything/Specification/issues/17/comments","events_url":"https://api.github.com/repos/TestAnything/Specification/issues/17/events","html_url":"https://github.com/TestAnything/Specification/issues/17","id":63605231,"number":17,"title":"Ownership of specification?","user":{"login":"isaacs","id":9287,"avatar_url":"https://avatars.githubusercontent.com/u/9287?v=3","gravatar_id":"","url":"https://api.github.com/users/isaacs","html_url":"https://github.com/isaacs","followers_url":"https://api.github.com/users/isaacs/followers","following_url":"https://api.github.com/users/isaacs/following{/other_user}","gists_url":"https://api.github.com/users/isaacs/gists{/gist_id}","starred_url":"https://api.github.com/users/isaacs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/isaacs/subscriptions","organizations_url":"https://api.github.com/users/isaacs/orgs","repos_url":"https://api.github.com/users/isaacs/repos","events_url":"https://api.github.com/users/isaacs/events{/privacy}","received_events_url":"https://api.github.com/users/isaacs/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-03-23T02:23:49Z","updated_at":"2015-03-23T21:58:29Z","closed_at":null,"body":"How are TAP specification changes adopted?  Who votes?\r\n\r\nIs this repository even relevant?  If so, can that information be added to the README.md?"},"comment":{"url":"https://api.github.com/repos/TestAnything/Specification/issues/comments/85221061","html_url":"https://github.com/TestAnything/Specification/issues/17#issuecomment-85221061","issue_url":"https://api.github.com/repos/TestAnything/Specification/issues/17","id":85221061,"user":{"login":"isaacs","id":9287,"avatar_url":"https://avatars.githubusercontent.com/u/9287?v=3","gravatar_id":"","url":"https://api.github.com/users/isaacs","html_url":"https://github.com/isaacs","followers_url":"https://api.github.com/users/isaacs/followers","following_url":"https://api.github.com/users/isaacs/following{/other_user}","gists_url":"https://api.github.com/users/isaacs/gists{/gist_id}","starred_url":"https://api.github.com/users/isaacs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/isaacs/subscriptions","organizations_url":"https://api.github.com/users/isaacs/orgs","repos_url":"https://api.github.com/users/isaacs/repos","events_url":"https://api.github.com/users/isaacs/events{/privacy}","received_events_url":"https://api.github.com/users/isaacs/received_events","type":"User","site_admin":false},"created_at":"2015-03-23T21:58:29Z","updated_at":"2015-03-23T21:58:29Z","body":"I actually did not know most of that history, so this is very helpful, thank you!\r\n\r\nI agree 100% that we need a committee of committed stake-holders.  It's very easy to have big ideas about what would make a good format.  It's another thing entirely to have thousands of people who use your test framework in a CI workflow and will get justifiably upset if you change it on them.\r\n\r\nI would suggest that we approach it somewhat like TC-39 manages JavaScript.  Come up with a list of the most relevant currently maintained and depended-upon TAP implementations from a variety of languages, and let them each nominate a member to be on the committee.  Then, before a proposal can be ratified, there must be at least 2 compliant implementations.\r\n\r\nRegarding your three groups, I think that there is more overlap than one might expect.  I am personally in all three camps.  I maintain a very popular JavaScript tap generating and consuming framework, and I have a lot of users who depend on node-tap's output being consumable by other consumers.  I also maintain a lot of projects where I look at tap output for tests I run, so I like it to be human-readable.  And making it machine-readable means that we can write better reporters that output stuff like spec, or dots, dashboards, or other fancy colorful things, which serves the human-readable goals in other ways.\r\n\r\nI strongly disagree with the idea that we need large breaking changes.  If anything, I'd like to see a \"One TAP\" resolution from this committee similar to TC-39's \"One JavaScript\".  That is, no new proposals should be ratified if they cause significant hardship for parsers that do not understand that new proposal."}}