{"action":"created","issue":{"url":"https://api.github.com/repos/SciTools/iris-extras/issues/7","labels_url":"https://api.github.com/repos/SciTools/iris-extras/issues/7/labels{/name}","comments_url":"https://api.github.com/repos/SciTools/iris-extras/issues/7/comments","events_url":"https://api.github.com/repos/SciTools/iris-extras/issues/7/events","html_url":"https://github.com/SciTools/iris-extras/issues/7","id":107664769,"number":7,"title":"Repo structure","user":{"login":"rhattersley","id":917914,"avatar_url":"https://avatars.githubusercontent.com/u/917914?v=3","gravatar_id":"","url":"https://api.github.com/users/rhattersley","html_url":"https://github.com/rhattersley","followers_url":"https://api.github.com/users/rhattersley/followers","following_url":"https://api.github.com/users/rhattersley/following{/other_user}","gists_url":"https://api.github.com/users/rhattersley/gists{/gist_id}","starred_url":"https://api.github.com/users/rhattersley/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rhattersley/subscriptions","organizations_url":"https://api.github.com/users/rhattersley/orgs","repos_url":"https://api.github.com/users/rhattersley/repos","events_url":"https://api.github.com/users/rhattersley/events{/privacy}","received_events_url":"https://api.github.com/users/rhattersley/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-09-22T08:13:07Z","updated_at":"2015-09-22T09:53:21Z","closed_at":null,"body":"re: #1, #5, and #6\r\n\r\ncc @bjlittle, @niallrobinson, @cpelley, and @pelson\r\n\r\nThe `iris-extras` repo has got the ball rolling for \"non-core Iris functionality\" which is great. Now that we've got some real examples we can take the next step in figuring out how to structure/manage it all. Our options are (please suggest other options as appropriate I can add them to the list):\r\n\r\n1. One repo, `iris-extras`, with a single `setup.py`. All projects installed, versioned, and released together.\r\n2. One repo, `iris-extras`, with a directory for each \"project\". Each directory contains its own `setup.py`. Projects installed independently but versioning and releases unclear.\r\n3. A repo for each group of related project, e.g. `iris-regrid`. Groups of projects installed, versioned, and released independently, but within a group all projects are managed together.\r\n4. A repo for each project, e.g. `iris-agg-regrid`. Each project is installed, versioned, and released independently.\r\n\r\nNB. To some extent we can combine options, e.g. things start in (1) but then progress to (4) at some point. Perhaps projects become independent if they require dependencies that aren't already mandatory for Iris."},"comment":{"url":"https://api.github.com/repos/SciTools/iris-extras/issues/comments/142231182","html_url":"https://github.com/SciTools/iris-extras/issues/7#issuecomment-142231182","issue_url":"https://api.github.com/repos/SciTools/iris-extras/issues/7","id":142231182,"user":{"login":"cpelley","id":2071643,"avatar_url":"https://avatars.githubusercontent.com/u/2071643?v=3","gravatar_id":"","url":"https://api.github.com/users/cpelley","html_url":"https://github.com/cpelley","followers_url":"https://api.github.com/users/cpelley/followers","following_url":"https://api.github.com/users/cpelley/following{/other_user}","gists_url":"https://api.github.com/users/cpelley/gists{/gist_id}","starred_url":"https://api.github.com/users/cpelley/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cpelley/subscriptions","organizations_url":"https://api.github.com/users/cpelley/orgs","repos_url":"https://api.github.com/users/cpelley/repos","events_url":"https://api.github.com/users/cpelley/events{/privacy}","received_events_url":"https://api.github.com/users/cpelley/received_events","type":"User","site_admin":false},"created_at":"2015-09-22T09:53:21Z","updated_at":"2015-09-22T09:53:21Z","body":"I agree, though I have preference for option (3).  Option (4) does not have strong negative implications for workflow/releases.  Potentially there is not much difference in workflow and deployment between (3) and (4) though for those who visit the github SciTools, (3) might reduce the 'repository namespace' compared to (4) which is a plus.\r\n\r\n(2) could work... but I think there is more to document in terms of workflow and structure (1) would have the undesirable (unnecessary) dependencies between project releases.  This could offer problem for 'projects' which are dependent on time critical releases."}}