[Trac-tickets] [The Trac Project] #2214: Trac as a POW system
The Trac Project
noreply at edgewall.com
Wed Oct 12 22:46:50 CDT 2005
#2214: Trac as a POW system
----------------------------------------------+-----------------------------
Reporter: graeme.christie at team.telstra.com | Owner: richard.shaw at team.telstra.com
Type: task | Status: new
Priority: low | Milestone:
Component: wiki | Version: 0.8.4
Severity: normal | Keywords: POW trac cvs |
----------------------------------------------+-----------------------------
TRAC doesn't quite have the feature set to satisfy the requirements for
the POW. While it does integrate code repositories (subversion, which we
don't use, cvs support coming … one day), bug submissions and a wiki
really nicely, it's not strong on resource (ie developers) allocation,
project prioritisation and project governance (submitting, justify and
approving projects etc) which is the main focus of the POW tool.
This is really a developers tool for developing. The POW is mostly a
managers tool for managing … and it's scope has blown right out beyond
development/systems .. All sorts of teams across IP services want access
to the POW tool for managing all sorts of projects.
I would love to see something like TRAC "hooked into" a POW tool.
E.g.
Assigned POW projects/tasks automatically become TRAC tasks, which can be
updated through TRAC and on completion update the POW etc.
Activity on a POW task can be guaged by examing the TRAC activity
(frequency of code submissions etc).
Not likely we would get the dev resources to do something like this
though.
Cheers,
Graeme
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/2214>
The Trac Project <http://trac.edgewall.com/>
More information about the Trac-Tickets
mailing list