Changes between Version 66 and Version 67 of ProjectManagementIdeas


Ignore:
Timestamp:
May 8, 2009, 10:09:38 PM (6 years ago)
Author:
ChrisNelson
Comment:

Explain !IProjectTask

Legend:

Unmodified
Added
Removed
Modified
  • ProjectManagementIdeas

    v66 v67  
    367367(I'm a little out of my depth here, designing for Trac internals I don't understand.  Hopefully, more experienced Trac developers will guide me.  -- Chris)
    368368
    369 To add better project management to Trac in a modular fashion requires defining the interfaces that project management implementations rely on.  We'll name these with a common prefix "IProject".  The 'I' is for "Interface", a common convention in Trac development.  The "Project" might be "PM" or "ProjMgr" or something.  This is certainly open to discussion.
     369To add better project management to Trac in a modular fashion requires defining the interfaces that project management implementations rely on.  We'll name these with a common prefix "IProject".  The 'I' is for "Interface", a common convention in Trac development.  The "Project" might be "PM" or "!ProjMgr" or something.  This is certainly open to discussion.
    370370
    371371== IProjectTask ==
    372372
    373 gdt: why isn't this just tickets?   We need a way to indicate which resources can work on which tasks.
     373Tasks for project management will be based on tickets but an abstract interface allows us to decouple a scheduler or other PM tool from the implementation of non-core ticket features like recording estimates and progress.  One user may choose to implement !IProjectTask on top of !TimeingAndEstimation and another on top of !TracHours.
     374
    374375
    375376== IProjectCalendar ==