GNIP 29 Code Repository Reorganization

GNIP 28 - Adoption of Twitter Bootstrap CSS Framework

Overview

It is proposed to re-organize the GeoNode core repository to make it more similar to a standard django project layout and make it more friendly to template projects as introduced in Django 1.4

Proposed By

Jeffrey Johnson

Assigned to Release

2.0

State

For Review and Comment

Motivation

Proposal

Re-organize the code repository as follows.

• LICENSE (licensing/copyright info for any components stored in the repo)
• README.rst
• docs/ (may be better under geonode)
  • deploy/
  • developers/
  • intro/
  • users/
• geonode/
  • api/
  • catalog/
    • templates/
  • data/
    • templates/
  • maps/
    • templates/
  • people/
    • templates/
  • search/
    • templates/
  • security/
  • tests.py (generic or top-level tests)
  • setup.py
  • setup.cfg
  • projects/ (sample projects to use via the startproject management comment in Django 1.4)
    • minimal/ (data, security and api)
      • __init__.py
      • manage.py
      • settings.py
      • urls.py
      • local_settings.sample
      • requirements.txt
    • basic/ (minimal + maps, catalog, search, people)
    • social/ (basic + social stuff)
    • … others as appropriate/necessary
    • shared/
      • package/
      • support/
    • submodules/
      • geonode-client/
      • geonode-geoserver-ext/ (may no longer be required once new security subsystem is implemented)
      • geonode-integration/
      • geonode-registry/
      • geonode-monitor/
      • geonode-cloud/
      • geonode-deb/
      • geonode-rpm/
      • etc …

Issues

Testing

Alternatives

Do nothing.

Feedback

Voting