{"action":"opened","issue":{"url":"https://api.github.com/repos/overstreetce/django-mailing-list/issues/4","labels_url":"https://api.github.com/repos/overstreetce/django-mailing-list/issues/4/labels{/name}","comments_url":"https://api.github.com/repos/overstreetce/django-mailing-list/issues/4/comments","events_url":"https://api.github.com/repos/overstreetce/django-mailing-list/issues/4/events","html_url":"https://github.com/overstreetce/django-mailing-list/issues/4","id":100634040,"number":4,"title":"Directory structure is confusing ","user":{"login":"barbour-em","id":8905795,"avatar_url":"https://avatars.githubusercontent.com/u/8905795?v=3","gravatar_id":"","url":"https://api.github.com/users/barbour-em","html_url":"https://github.com/barbour-em","followers_url":"https://api.github.com/users/barbour-em/followers","following_url":"https://api.github.com/users/barbour-em/following{/other_user}","gists_url":"https://api.github.com/users/barbour-em/gists{/gist_id}","starred_url":"https://api.github.com/users/barbour-em/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/barbour-em/subscriptions","organizations_url":"https://api.github.com/users/barbour-em/orgs","repos_url":"https://api.github.com/users/barbour-em/repos","events_url":"https://api.github.com/users/barbour-em/events{/privacy}","received_events_url":"https://api.github.com/users/barbour-em/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-08-12T20:58:24Z","updated_at":"2015-08-12T20:58:24Z","closed_at":null,"body":"Currently, the directory structure is highly nested resulting in similar dir names, `manage.py` being in a subdir not the root, and just general confusion. If it ends up that only some parts of this code will be dropped into the main `COS-Site` effort, this will not be an issue but if we choose to use parts of this as an `INSTALLED_APP` in that site, this should probably be resolved. \r\n\r\nMore realistically, the hierarchy should look something more like the typical Django project:\r\n```python\r\ntestproject/\r\n├── __init__.py\r\n├── manage.py\r\n├── mysite1\r\n│   ├── __init__.py\r\n│   ├── models.py\r\n│   ├── tests.py\r\n│   └── views.py\r\n├── settings.py\r\n└── urls.py\r\n``` \r\n\r\nAgain, a low priority but something to begin thinking about\r\n"}}