{"action":"created","issue":{"url":"https://api.github.com/repos/catapult-project/catapult/issues/1448","labels_url":"https://api.github.com/repos/catapult-project/catapult/issues/1448/labels{/name}","comments_url":"https://api.github.com/repos/catapult-project/catapult/issues/1448/comments","events_url":"https://api.github.com/repos/catapult-project/catapult/issues/1448/events","html_url":"https://github.com/catapult-project/catapult/issues/1448","id":104972676,"number":1448,"title":"Automatically enforce benchmark ownership in tools/perf across Catapult components","user":{"login":"qyearsley","id":3926653,"avatar_url":"https://avatars.githubusercontent.com/u/3926653?v=3","gravatar_id":"","url":"https://api.github.com/users/qyearsley","html_url":"https://github.com/qyearsley","followers_url":"https://api.github.com/users/qyearsley/followers","following_url":"https://api.github.com/users/qyearsley/following{/other_user}","gists_url":"https://api.github.com/users/qyearsley/gists{/gist_id}","starred_url":"https://api.github.com/users/qyearsley/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/qyearsley/subscriptions","organizations_url":"https://api.github.com/users/qyearsley/orgs","repos_url":"https://api.github.com/users/qyearsley/repos","events_url":"https://api.github.com/users/qyearsley/events{/privacy}","received_events_url":"https://api.github.com/users/qyearsley/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/catapult-project/catapult/labels/P2","name":"P2","color":"fbca04"},{"url":"https://api.github.com/repos/catapult-project/catapult/labels/Perf%20Dashboard","name":"Perf Dashboard","color":"207de5"},{"url":"https://api.github.com/repos/catapult-project/catapult/labels/Telemetry","name":"Telemetry","color":"5319e7"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-09-04T21:25:12Z","updated_at":"2015-09-04T21:25:13Z","closed_at":null,"body":"**Issue by [eakuef...@chromium.org](https://code.google.com/u/113455657570966801301/)**\n_2015-04-30T00:02:29.000Z_\n_Originally opened as http://crbug.com/482772_\n\n----\n\nThis is a tracking bug for enforcing benchmark ownership across Catapult components (chiefly, Telemetry and the Performance Dashboard) as described in https://docs.google.com/document/d/1qlbrSRtqZpCyp1R1HCt0xLklMHno-Mvuz5U24QyQKh4/edit"},"comment":{"url":"https://api.github.com/repos/catapult-project/catapult/issues/comments/137856827","html_url":"https://github.com/catapult-project/catapult/issues/1448#issuecomment-137856827","issue_url":"https://api.github.com/repos/catapult-project/catapult/issues/1448","id":137856827,"user":{"login":"qyearsley","id":3926653,"avatar_url":"https://avatars.githubusercontent.com/u/3926653?v=3","gravatar_id":"","url":"https://api.github.com/users/qyearsley","html_url":"https://github.com/qyearsley","followers_url":"https://api.github.com/users/qyearsley/followers","following_url":"https://api.github.com/users/qyearsley/following{/other_user}","gists_url":"https://api.github.com/users/qyearsley/gists{/gist_id}","starred_url":"https://api.github.com/users/qyearsley/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/qyearsley/subscriptions","organizations_url":"https://api.github.com/users/qyearsley/orgs","repos_url":"https://api.github.com/users/qyearsley/repos","events_url":"https://api.github.com/users/qyearsley/events{/privacy}","received_events_url":"https://api.github.com/users/qyearsley/received_events","type":"User","site_admin":false},"created_at":"2015-09-04T21:25:13Z","updated_at":"2015-09-04T21:25:13Z","body":"**Comment by [eakuef...@chromium.org](https://code.google.com/u/113455657570966801301/)**\n_2015-04-30T15:50:10.000Z_\n\n----\n\nAnnie is correct, I'm mostly trying to imply that there should be synergy between the dashboard and Telemetry with regard to enforcing ownership in tools/perf, maybe with a general mechanism that can be applied to other Catapult client developments. I've updated the title of the bug to make it a little more clear.\r\n\r\nI agree (and I think Ned does as well) that the best way to do this will be to export the annotations in JSON somehow, since it's easy to add new metadata to chart JSON."}}