{"action":"created","issue":{"url":"https://api.github.com/repos/clintjhill/ember-parse-adapter/issues/79","labels_url":"https://api.github.com/repos/clintjhill/ember-parse-adapter/issues/79/labels{/name}","comments_url":"https://api.github.com/repos/clintjhill/ember-parse-adapter/issues/79/comments","events_url":"https://api.github.com/repos/clintjhill/ember-parse-adapter/issues/79/events","html_url":"https://github.com/clintjhill/ember-parse-adapter/issues/79","id":93144499,"number":79,"title":"RFC: Move to ember-parse organization","user":{"login":"jacobthemyth","id":1620230,"avatar_url":"https://avatars.githubusercontent.com/u/1620230?v=3","gravatar_id":"","url":"https://api.github.com/users/jacobthemyth","html_url":"https://github.com/jacobthemyth","followers_url":"https://api.github.com/users/jacobthemyth/followers","following_url":"https://api.github.com/users/jacobthemyth/following{/other_user}","gists_url":"https://api.github.com/users/jacobthemyth/gists{/gist_id}","starred_url":"https://api.github.com/users/jacobthemyth/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jacobthemyth/subscriptions","organizations_url":"https://api.github.com/users/jacobthemyth/orgs","repos_url":"https://api.github.com/users/jacobthemyth/repos","events_url":"https://api.github.com/users/jacobthemyth/events{/privacy}","received_events_url":"https://api.github.com/users/jacobthemyth/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-07-05T20:26:01Z","updated_at":"2015-07-06T19:49:33Z","closed_at":null,"body":"In #69, the session service was brought up, and I think it would be helpful to have other packages besides just the adapter that offer functionality around Parse. For instance, I would argue that file uploads don't really belong in this repo, and probably neither does the user model, since those are separate concerns from an ember-data adapter. I would propose that this project be moved to an organization on GitHub, and that functionality other than the actual ember-data adapter be moved to separate libraries. This would also provide a logical location for a repo for RFCs."},"comment":{"url":"https://api.github.com/repos/clintjhill/ember-parse-adapter/issues/comments/118976658","html_url":"https://github.com/clintjhill/ember-parse-adapter/issues/79#issuecomment-118976658","issue_url":"https://api.github.com/repos/clintjhill/ember-parse-adapter/issues/79","id":118976658,"user":{"login":"joshfester","id":2067688,"avatar_url":"https://avatars.githubusercontent.com/u/2067688?v=3","gravatar_id":"","url":"https://api.github.com/users/joshfester","html_url":"https://github.com/joshfester","followers_url":"https://api.github.com/users/joshfester/followers","following_url":"https://api.github.com/users/joshfester/following{/other_user}","gists_url":"https://api.github.com/users/joshfester/gists{/gist_id}","starred_url":"https://api.github.com/users/joshfester/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joshfester/subscriptions","organizations_url":"https://api.github.com/users/joshfester/orgs","repos_url":"https://api.github.com/users/joshfester/repos","events_url":"https://api.github.com/users/joshfester/events{/privacy}","received_events_url":"https://api.github.com/users/joshfester/received_events","type":"User","site_admin":false},"created_at":"2015-07-06T19:49:33Z","updated_at":"2015-07-06T19:49:33Z","body":"My opinion is that the goal should definitely be to have all the functionality of the Parse JS SDK. However, I think the \"ember way\" of accomplishing this would be to break things out into separate addons. Off the top of my head, here's some ember-parse addons I would be using at my company:\r\n\r\n* ember-data adapter\r\n* ember-cli-deploy-parse\r\n* ember-parse-cloud\r\n* ember-simple-auth-parse\r\n* ember-parse-analytics\r\n\r\nI would love to see an ember-parse-cloud addon that works like [ember-api-actions](https://github.com/truenorth/ember-api-actions) for Cloud Functions. Authentication and session management is something that can (and IMO, should) be handled by something outside of ember-data.\r\n\r\nTo me the grey area is things like ACL's and the special \"Parse\" models (User, File, Geopoint, etc). I would be fine with these things staying in the ember-data adapter, as they are specifically tied to Parse data, and would stay the same across all ember-parse projects.\r\n\r\nThe ember-parse org would be an ecosystem that provides all the functionality of the Parse JS SDK. It would allow developers to incrementally add features to their projects, come up with homegrown solutions for specific use-cases (without having to choose between bloat vs re-inventing the wheel), migrate to Parse from other backends, and (perhaps most importantly) contribute to the ember-parse ecosystem without being intimidated by a large monolithic library.  "}}