SCM

[#64] ([Semi-] automatic) maintenance of a target / todo list

Date:
2007-11-08 17:48
Priority:
2
State:
Closed
Submitted by:
Peter Ruckdeschel (ruckdeschel)
Assigned to:
Stefan Theussl (stefan7th)
Product:
None
Operating System:
None
Component:
None
Summary:
([Semi-] automatic) maintenance of a target / todo list

Detailed description
Suppose that in planning a project there has been some
agreement upon a target list of contents to be successively
implemented / included to some envisaged R-package.

To avoid double work, it would be nice if anyone who is
working on one item of the list could signal this to
anyone else who might be interested in doing so.

This could be done by some sort of maintained target / todo
list, where these "signallings" are gathered and which should
be visible to anyone browsing through the R-Forge pages, no
matter if he is subscribed to this project or not.

Subscribers however should get notified by e-mail on
every change of this list.

Now suppose some new collaborator A wants to contribute code;
then he could subscribe to R-forge, see this table, select the
topic to work on; if someone else B is working on it, too,
A could simply contact B by e-mail; else A simply inscribes
(or gets inscribed) into the table.

If someone stops working on some topic this should also be
signalled on this list.

So as far as I can see this could be a generally useful
feature for R-forge, which should not be extremely hard
to implement.

For the moment, we could at least sort of manually maintain
this list, and provided there is not hundreds of volunteers,
I think this should not mean too much effort for the admin ---
but I may get disproved as to this.

Comments:

Message  ↓
Date: 2008-01-24 12:50
Sender: Stefan Theussl

As far as I know are ToDo lists part of the GForge system. Nevertheless we turned that feature off, as we need other (more important) features working properly before going ahead to adapt others (minor important) to R-Forge.

st

Date: 2008-01-23 22:24
Sender: Peter Cowan

Yes, I see what you are suggesting. You could use the feature request tracker to add new goals, but it is not as nice as the milestone features of Trac <http://trac.edgewall.org/>.

For the project I'm working on we keep a file called TODO in the base folder of the package that outlines tasks and who is working on them. It's in the package and thus publicly available, through hard for the average user to find.

Date: 2008-01-23 22:18
Sender: Peter Ruckdeschel

To Peter Cowan's followup:

While it could be maintained much the same way as a bug tracker, a task list is semantically different; it would be made up before actually implementing anything. And a bug is some error in existing code isn't it?

In the mean time I have discovered the possibility to create new trackers as admin of some project (under tab "Admin" go to item "Tracker Admin" under "Tool Admin") ---maybe it has been there for a while and escaped my notice.

So indeed, one could arrange a "Target List Tracker" already...

Date: 2008-01-23 21:41
Sender: Peter Cowan

How would this be different than the bug tracker that already exists?

Attached Files:

Changes

Field Old Value Date By
status_idOpen2019-04-26 10:51gstar
close_dateNone2019-04-26 10:51gstar
priority32008-01-24 12:50stefan7th
assigned_tonone2008-01-24 12:50stefan7th
Thanks to:
Vienna University of Economics and Business Powered By FusionForge