{"action":"opened","issue":{"url":"https://api.github.com/repos/rackspace/rack/issues/354","labels_url":"https://api.github.com/repos/rackspace/rack/issues/354/labels{/name}","comments_url":"https://api.github.com/repos/rackspace/rack/issues/354/comments","events_url":"https://api.github.com/repos/rackspace/rack/issues/354/events","html_url":"https://github.com/rackspace/rack/issues/354","id":109191516,"number":354,"title":"README is missing rationale for project's existence","user":{"login":"jasondunsmore","id":53437,"avatar_url":"https://avatars.githubusercontent.com/u/53437?v=3","gravatar_id":"","url":"https://api.github.com/users/jasondunsmore","html_url":"https://github.com/jasondunsmore","followers_url":"https://api.github.com/users/jasondunsmore/followers","following_url":"https://api.github.com/users/jasondunsmore/following{/other_user}","gists_url":"https://api.github.com/users/jasondunsmore/gists{/gist_id}","starred_url":"https://api.github.com/users/jasondunsmore/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jasondunsmore/subscriptions","organizations_url":"https://api.github.com/users/jasondunsmore/orgs","repos_url":"https://api.github.com/users/jasondunsmore/repos","events_url":"https://api.github.com/users/jasondunsmore/events{/privacy}","received_events_url":"https://api.github.com/users/jasondunsmore/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-09-30T22:15:41Z","updated_at":"2015-09-30T22:15:41Z","closed_at":null,"body":"It's customary in the open source world for a project, which is the successor of another project, to lay out a rationale for the transition to the new project.  This is to put users and developers minds at ease, since transitioning libraries often requires a non-trivial amount of effort.  Users will naturally think: \"is this project going to stick around, or will I be doing this work again in a year?\"  Here are a few questions that came to mind when I heard about this project:\r\n\r\nWhy not fix Pyrax? https://github.com/rackspace/pyrax\r\n\r\nWhy not use python so that code from upstream projects can be reused?  This would greatly reduce the overall maintenance burden.  For example, every time a new feature is added to an OpenStack project, support will have to be added in the upstream client AND in this client.\r\n\r\nIn the above scenario, how quickly will support be added to this client?  Support for new features in upstream clients is usually added at the same time or just after the feature lands.\r\n\r\nWhy was Pyrax abandoned, and is this project likely to be abandoned for the same reason?"}}