I agree strongly with Reiner that this new functionality would need to
be discreet. From what I'm seeing it sounds very un-GTD, so it's
outside the scope of what I see Tracks as. The great thing about open
source is that you can add it, though! As long as we can work in the
functionality without complicating Tracks for the rest of us, it seems
fine to me.
As for task dependencies, that stalled for a few months. I've still
got some code, but I never came up with a good UI for how to deal with
arbitrary dependencies. I was mostly sketching out the infrastructure
for it to be as general as possible, but the only manifestation would
be setting projects to only show one action at a time (complete tasks
in order).
On Dec 23, 2008, at 11:37 PM, Reinier Balt wrote:
Hi Keith,
I remember a discussion about being able to see another users todos
with Joseph Method (tristil @ g mail dot com) but I don’t know if
that resulted in any code.
1) I think we could combine subprojects with the goals request.
In a way it’s the same (as responsibilities can be considered a
goal). Personally I manage subprojects using tags and use the tag
view to see all todos related to the complete project. I agree on
what you say about sub-actions. I think implementing convert-todo-to-
project will help people who run into these use cases
2) I don’t know what you mean with dependencies. Eric Allen is
working on todo-dependencies. You really need to think this one
through as there are a lot of infrastructure items to this. Like a
notification system. Also the gui part seem tricky to me. But then
again, who doesn’t like a challenge :-)
I think that for both 1) and 2) we need to be carefull on the gui
side. Tracks is all about being simple and flexible so you can use
it the way you want (and not dictated by some strict workflow).
Also, the gui currently is getting really crowded and is in need of
simplification. I think that it is important that new functions like
these should only be noticed if you use them, i.e. if you don’t use
them, you don’t see anything of it.
Reinier
Van: [email protected] [mailto:[email protected]
] Namens Keith Gaddis
Verzonden: zaterdag 20 december 2008 21:43
Aan: [email protected]
Onderwerp: [Tracks-discuss] subprojects, multi-user, and delegation
functionality
Is anyone actively working on functionality to cover subprojects or
multi-user interaction along the lines of delegation and watching
someone else's actions/projects? These are high-priority items for
me, and if no one else is working on them, I'd like to take a crack
at it, or work with someone to avoid duplication of effort. I've
seen tickets in Trac for these functions, but they don't seem to be
updated recently (there's also multiple tickets covering each, so i
may be missing the active ticket).
Here are my implementation thoughts:
1) subprojects: this can be really simple. All that really needs
to be done is add a 'parent' field to the project model and make
some UI updates. Projects with null parents correspond to top-level
projects, which can be thought of as areas of responsibility.
subprojects have another projectid assigned to them for a parent.
hiding a project cascades down the tree, marking it visible flows up
the tree. One of the tickets mentions sub-actions, which i think is
kind of a corruption of the metaphor--actions should by definition
be discrete pieces of work or steps to be taken, not aggregations of
them.
this would also make it really easy to implement conversion of an
action to a project, setting the parent id to the original action's
project, which is also something I'd really like to see, though its
far lower on my priority list.
2) multi-user functions
first i'd like to implement 'watches', which would allow one user to
view the projects, actions, and notes of another user. further down
the line it could be used to implement notifications and
dependencies. The watch UI would allow a watching user to copy a
project definition to his own list of projects, and optionally its
child actions/projects.
second step in this would be to allow a user to delegate an action
or project to another user. To do so, it would seem like all you
would need to do is reassign the user_id. As a first go-round it
would fit my purposes merely to allow any user to delegate to any
other, but it could be implemented in such a way as to allow a
delegation to follow a request/accept model.
So now that I've laid out what I'd like to work on, does anyone have
any thoughts about it? Is anyone else working on this or similar
functionality, or in a different direction?
Best regards,
Keith
_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
