[kepler-dev] [Bug 5173] New: Develop clear criteria for when code in Kepler CORE should be in its own module.

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5173

           Summary: Develop clear criteria for when code in Kepler CORE
                    should be in its own module.
           Product: Kepler
           Version: 2.0.0
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: david.v.welker at gmail.com
        ReportedBy: david.v.welker at gmail.com
         QAContact: kepler-dev at kepler-project.org
   Estimated Hours: 0.0


As of now, we have broken up Kepler into a number of modules. But this breaking
up of Kepler has been ad hoc and not followed a consistent set of guidelines
concerning when code should be in its own module and when it should be grouped
with other code that is somehow related in a common module.

Lack of consistent guidelines make modules harder to understand. Following more
consistent guidelines would make Kepler easier to understand.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.