{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/wg-effectiveness/issues/12","repository_url":"https://api.github.com/repos/w3c/wg-effectiveness","labels_url":"https://api.github.com/repos/w3c/wg-effectiveness/issues/12/labels{/name}","comments_url":"https://api.github.com/repos/w3c/wg-effectiveness/issues/12/comments","events_url":"https://api.github.com/repos/w3c/wg-effectiveness/issues/12/events","html_url":"https://github.com/w3c/wg-effectiveness/issues/12","id":256070895,"number":12,"title":"Shipping is a feature","user":{"login":"paulbrucecotton","id":8301560,"avatar_url":"https://avatars1.githubusercontent.com/u/8301560?v=4","gravatar_id":"","url":"https://api.github.com/users/paulbrucecotton","html_url":"https://github.com/paulbrucecotton","followers_url":"https://api.github.com/users/paulbrucecotton/followers","following_url":"https://api.github.com/users/paulbrucecotton/following{/other_user}","gists_url":"https://api.github.com/users/paulbrucecotton/gists{/gist_id}","starred_url":"https://api.github.com/users/paulbrucecotton/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/paulbrucecotton/subscriptions","organizations_url":"https://api.github.com/users/paulbrucecotton/orgs","repos_url":"https://api.github.com/users/paulbrucecotton/repos","events_url":"https://api.github.com/users/paulbrucecotton/events{/privacy}","received_events_url":"https://api.github.com/users/paulbrucecotton/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2017-09-07T21:07:53Z","updated_at":"2017-09-14T13:19:27Z","closed_at":null,"author_association":"NONE","body":"As Chair of the HME WG I had to convince the Editors and the most active HME WG participants that \"shipping is a feature\".  ALL W3C WG member need to understand this concept.\r\n\r\nBy this I mean \"shipping a specification\" (eg. getting it to CR or PR by a particular date) should be treated like any other feature in the specification and the \"shipping feature\" should be treated on an equal footing with any other feature requests.  All too often WG members want to add new features to a specification at the cost of the \"shipping feature\" and they do not understand the impact of doing this.\r\n\r\nAs a WG progresses along its chartered timeline the \"shipping feature\" starts to become more and more important.\r\n\r\nFor example, in early 2016 I had to inform the HME WG participants that we ran the risk of running out of charter time to finish our MSE and EME specifications.  I basically had to convince the WG participants that the only feature that mattered at that point in time was the \"shipping feature\" or else all the other features would be lost if the WG was closed without finishing its deliverables.  The Editors then started a [triage process](https://lists.w3.org/Archives/Public/public-html-media/2016Mar/0003.html) to move the specs along.\r\n\r\nEventually we did ship both MSE and EME but I was surprised how hard it was to convince HME WG participants that \"shipping is a feature\" even though this culture is very prevalent in many companies that ship software products.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/w3c/wg-effectiveness/issues/comments/329479168","html_url":"https://github.com/w3c/wg-effectiveness/issues/12#issuecomment-329479168","issue_url":"https://api.github.com/repos/w3c/wg-effectiveness/issues/12","id":329479168,"user":{"login":"dontcallmedom","id":216410,"avatar_url":"https://avatars0.githubusercontent.com/u/216410?v=4","gravatar_id":"","url":"https://api.github.com/users/dontcallmedom","html_url":"https://github.com/dontcallmedom","followers_url":"https://api.github.com/users/dontcallmedom/followers","following_url":"https://api.github.com/users/dontcallmedom/following{/other_user}","gists_url":"https://api.github.com/users/dontcallmedom/gists{/gist_id}","starred_url":"https://api.github.com/users/dontcallmedom/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dontcallmedom/subscriptions","organizations_url":"https://api.github.com/users/dontcallmedom/orgs","repos_url":"https://api.github.com/users/dontcallmedom/repos","events_url":"https://api.github.com/users/dontcallmedom/events{/privacy}","received_events_url":"https://api.github.com/users/dontcallmedom/received_events","type":"User","site_admin":false},"created_at":"2017-09-14T13:19:27Z","updated_at":"2017-09-14T13:19:27Z","author_association":"OWNER","body":"there are hardly any groups that haven't switched to github. looking at the [report of my script validating repos](https://w3c.github.io/validate-repos/report.html), and excluding WGs that are dormant, the only groups that haven't switched to github are EXI, Tracking Protection and WebFonts."}}
{"actor":{"display_login":"dontcallmedom"}}