|
From: | Julien Hamilton |
Subject: | Re: Octave Task List: proof of concept |
Date: | Thu, 20 Feb 2014 00:14:01 -0500 |
I expected task management (TM) to operate on a higher level than individual
bugs and feature requests. The vision would be to provide a birds-eye view
of where the development of Octave is heading. At the OctaveConf's,
developers often offer their personal views of state of development; TM
could be a dynamic version of those frozen snapshots.
So far, the wiki Projects page is the closest to that vision. Except that
it doesn't intend to follow ongoing projects, such as the GUI and classdef.
For me, a task would include: (0) a list of its components; (1) a list of
all related bug reports; (2) a statement of the intended development goals,
in terms of, e.g., missing functions or test cases to pass; (3) a statement
of what is intentionally put outside the scope; (4) test coverage; (5)
documentation status; (6) live/user/non-automated testing status.
For example:
+ Task: classdef
- Component 0: General (not component-specific)
- Bugs: <link to savannah>
- Goals:
- Outside the scope:
...
- Component 1: properties
...
- Component 2: methods
...
- Component 3: events
...
- Component 4: enumeration
...
+ Task: New GUI/IDE
- Component 0: General (not component-specific)
- Bugs: <link to savannah>
- Goals: cross-platform ...
- Outside the scope: profiler GUI?
...
- Component 1: Editor
...
- Component 2: Command Window
...
I agree the wiki extension is not very compelling, vis-a-vis the existing
tools. So maybe we can focus initially on content, i.e., to try and fill in
the details using existing tools, such as Savannah Tasks and the Wiki.
Another idea is to try and cluster existing bug reports to identify other
ongoing high-level tasks being developed.
Thanks for your time.
cheers,
-Felipe.
[Prev in Thread] | Current Thread | [Next in Thread] |