{"action":"opened","issue":{"url":"https://api.github.com/repos/promises-aplus/promises-spec/issues/184","labels_url":"https://api.github.com/repos/promises-aplus/promises-spec/issues/184/labels{/name}","comments_url":"https://api.github.com/repos/promises-aplus/promises-spec/issues/184/comments","events_url":"https://api.github.com/repos/promises-aplus/promises-spec/issues/184/events","html_url":"https://github.com/promises-aplus/promises-spec/issues/184","id":60640100,"number":184,"title":"logo and keywords","user":{"login":"vitaly-t","id":5108906,"avatar_url":"https://avatars.githubusercontent.com/u/5108906?v=3","gravatar_id":"","url":"https://api.github.com/users/vitaly-t","html_url":"https://github.com/vitaly-t","followers_url":"https://api.github.com/users/vitaly-t/followers","following_url":"https://api.github.com/users/vitaly-t/following{/other_user}","gists_url":"https://api.github.com/users/vitaly-t/gists{/gist_id}","starred_url":"https://api.github.com/users/vitaly-t/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vitaly-t/subscriptions","organizations_url":"https://api.github.com/users/vitaly-t/orgs","repos_url":"https://api.github.com/users/vitaly-t/repos","events_url":"https://api.github.com/users/vitaly-t/events{/privacy}","received_events_url":"https://api.github.com/users/vitaly-t/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-03-11T10:47:33Z","updated_at":"2015-03-11T10:47:33Z","closed_at":null,"body":"In your documents you mention that a compliant Promises/A+ library may display a logo and use a keyword on NPM.\r\n\r\nAnd what about libraries that feature use of Promises/A+, i.e. libraries that expose its interface via any of the existing Promises/A+ implementations?\r\n\r\nAny similar provision for such libraries? May/should they use the same keyword on NPM? May/should they use the same logo?"}}