{"action":"created","issue":{"url":"https://api.github.com/repos/plone/plone.app.tiles/issues/9","repository_url":"https://api.github.com/repos/plone/plone.app.tiles","labels_url":"https://api.github.com/repos/plone/plone.app.tiles/issues/9/labels{/name}","comments_url":"https://api.github.com/repos/plone/plone.app.tiles/issues/9/comments","events_url":"https://api.github.com/repos/plone/plone.app.tiles/issues/9/events","html_url":"https://github.com/plone/plone.app.tiles/issues/9","id":161728713,"number":9,"title":"Deprecate and remove plone.app.tiles registry key?","user":{"login":"datakurre","id":160447,"avatar_url":"https://avatars.githubusercontent.com/u/160447?v=3","gravatar_id":"","url":"https://api.github.com/users/datakurre","html_url":"https://github.com/datakurre","followers_url":"https://api.github.com/users/datakurre/followers","following_url":"https://api.github.com/users/datakurre/following{/other_user}","gists_url":"https://api.github.com/users/datakurre/gists{/gist_id}","starred_url":"https://api.github.com/users/datakurre/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/datakurre/subscriptions","organizations_url":"https://api.github.com/users/datakurre/orgs","repos_url":"https://api.github.com/users/datakurre/repos","events_url":"https://api.github.com/users/datakurre/events{/privacy}","received_events_url":"https://api.github.com/users/datakurre/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/plone/plone.app.tiles/labels/05%20type:%20question","name":"05 type: question","color":"fa00fa"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-06-22T16:30:51Z","updated_at":"2016-06-22T17:41:01Z","closed_at":null,"body":"@jensens @vangheem @hvelarde \r\n\r\nWould you have opinion on plone.app.tiles' ``plone.app.tiles``-registry key?\r\n\r\nI believe, it is supposed to list \"currently enabled tiles\". The only place it's currently used is \"Add new tile\"-form, which has not been used since some early Deco versions. I'm using it on a custom app based on early package versions, but would not mind seeing it go away. I feel it only complicates the stack, because all real use cases seem to require additional ways to define available tiles.\r\n"},"comment":{"url":"https://api.github.com/repos/plone/plone.app.tiles/issues/comments/227820843","html_url":"https://github.com/plone/plone.app.tiles/issues/9#issuecomment-227820843","issue_url":"https://api.github.com/repos/plone/plone.app.tiles/issues/9","id":227820843,"user":{"login":"hvelarde","id":341393,"avatar_url":"https://avatars.githubusercontent.com/u/341393?v=3","gravatar_id":"","url":"https://api.github.com/users/hvelarde","html_url":"https://github.com/hvelarde","followers_url":"https://api.github.com/users/hvelarde/followers","following_url":"https://api.github.com/users/hvelarde/following{/other_user}","gists_url":"https://api.github.com/users/hvelarde/gists{/gist_id}","starred_url":"https://api.github.com/users/hvelarde/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hvelarde/subscriptions","organizations_url":"https://api.github.com/users/hvelarde/orgs","repos_url":"https://api.github.com/users/hvelarde/repos","events_url":"https://api.github.com/users/hvelarde/events{/privacy}","received_events_url":"https://api.github.com/users/hvelarde/received_events","type":"User","site_admin":false},"created_at":"2016-06-22T17:41:01Z","updated_at":"2016-06-22T17:41:01Z","body":"in collective.cover we register tiles in that key and then we use it as a source to create a list of available tiles in the layout editor; how are you going to reimplement this? a vocabulary also?\r\n\r\nhttps://github.com/collective/collective.cover/blob/master/src/collective/cover/vocabularies.py#L53-L72\r\n\r\nI think this is no used anywhere else.\r\n\r\nCC @rodfersou "}}
{"actor":{"display_login":"hvelarde"}}