Project

General

Profile

Bug #5173

Develop clear criteria for when code in Kepler CORE should be in its own module.

Added by David Welker about 9 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Category:
general
Target version:
Start date:
09/08/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5173

Description

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.

History

#1 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 5173

Also available in: Atom PDF