{"action":"created","issue":{"url":"https://api.github.com/repos/Becksteinlab/MDSynthesis/issues/38","labels_url":"https://api.github.com/repos/Becksteinlab/MDSynthesis/issues/38/labels{/name}","comments_url":"https://api.github.com/repos/Becksteinlab/MDSynthesis/issues/38/comments","events_url":"https://api.github.com/repos/Becksteinlab/MDSynthesis/issues/38/events","html_url":"https://github.com/Becksteinlab/MDSynthesis/issues/38","id":95351975,"number":38,"title":"Split off MDSynthesis core into another package?","user":{"login":"dotsdl","id":1326811,"avatar_url":"https://avatars.githubusercontent.com/u/1326811?v=3","gravatar_id":"","url":"https://api.github.com/users/dotsdl","html_url":"https://github.com/dotsdl","followers_url":"https://api.github.com/users/dotsdl/followers","following_url":"https://api.github.com/users/dotsdl/following{/other_user}","gists_url":"https://api.github.com/users/dotsdl/gists{/gist_id}","starred_url":"https://api.github.com/users/dotsdl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dotsdl/subscriptions","organizations_url":"https://api.github.com/users/dotsdl/orgs","repos_url":"https://api.github.com/users/dotsdl/repos","events_url":"https://api.github.com/users/dotsdl/events{/privacy}","received_events_url":"https://api.github.com/users/dotsdl/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/Becksteinlab/MDSynthesis/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":13,"created_at":"2015-07-16T05:13:46Z","updated_at":"2015-07-20T06:04:14Z","closed_at":null,"body":"Since the basic structure of MDSynthesis isn't entirely specific to molecular dynamics simulation, I think it might make sense to break the core out into a separate package. I'd been considering this for a while, but today I was contacted by someone with a use-case outside of MD, and I think it would be of benefit to MDSynthesis' core development to make it more general.\r\n\r\nI've started a repository for this work here: https://github.com/dotsdl/datreant\r\n\r\nIs anyone opposed to this? One thing to to note is that  ``datreant`` is BSD 3-clause licensed, making its use more permissive than MDSynthesis, which is GPLv2 (same as [MDAnalysis](https://github.com/MDAnalysis/mdanalysis)). I technically need permission from everyone that has contributed code so far to make this change.\r\n\r\nP.S. Opinions on the name are welcome. I wanted something that included 'dat' to indicate 'data', and some kind of word to indicate 'trees' (as in directory trees). An old D&D woodland creature ('treant') came to mind. :D"},"comment":{"url":"https://api.github.com/repos/Becksteinlab/MDSynthesis/issues/comments/122772404","html_url":"https://github.com/Becksteinlab/MDSynthesis/issues/38#issuecomment-122772404","issue_url":"https://api.github.com/repos/Becksteinlab/MDSynthesis/issues/38","id":122772404,"user":{"login":"dotsdl","id":1326811,"avatar_url":"https://avatars.githubusercontent.com/u/1326811?v=3","gravatar_id":"","url":"https://api.github.com/users/dotsdl","html_url":"https://github.com/dotsdl","followers_url":"https://api.github.com/users/dotsdl/followers","following_url":"https://api.github.com/users/dotsdl/following{/other_user}","gists_url":"https://api.github.com/users/dotsdl/gists{/gist_id}","starred_url":"https://api.github.com/users/dotsdl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dotsdl/subscriptions","organizations_url":"https://api.github.com/users/dotsdl/orgs","repos_url":"https://api.github.com/users/dotsdl/repos","events_url":"https://api.github.com/users/dotsdl/events{/privacy}","received_events_url":"https://api.github.com/users/dotsdl/received_events","type":"User","site_admin":false},"created_at":"2015-07-20T06:04:13Z","updated_at":"2015-07-20T06:04:13Z","body":"> Can you then think of containers in a much broader sense as really any kind of URI — I am thinking of a framework that allows one to organize all kinds of resources such as online databases, local files, etc.\r\n\r\n@orbeckst I think this is possible, and I don't think it's a challenge for the front-end API. One could imagine having Containers in a PostgreSQL database somewhere and giving a full URI instead of a filesystem location with something like\r\n\r\n```\r\nimport datreant as dtr\r\nc = dtr.Container('postgresql://username:password@hostname:port')\r\n```\r\n\r\nPerhaps the way [odo](http://odo.readthedocs.org/en/latest/uri.html) implements this would be of help if this is something we wish to pursue.\r\n\r\n@cing I remember those things in kindergarten, but not sure how I feel about 'cubby'. I agree that 'datreant' works, and I like it over 'pytreant', too. :D\r\n\r\nSeeing no other complaints, and now having permission to split the core out with a different license, I'm happy now to call this issue closed!"}}