[prev in list] [next in list] [prev in thread] [next in thread] 

List:       taskjuggler-devel
Subject:    Re: [taskjuggler-devel] TUTOS as a storage backend
From:       Dimitri Fontaine <dfontaine () cvf ! fr>
Date:       2005-03-09 14:34:32
Message-ID: 200503091534.33127.dfontaine () cvf ! fr
[Download RAW message or body]

Le Mardi 8 Mars 2005 20:08, Chris Schlaeger a écrit :
> thanks for the offer. I've looked at at the tutos web pages, especially the
> task management. The input data set for the scheduler seems to be very
> different from the TaskJuggler data set, so it looks like it's going to be
> very hard to couple the tools at this level.

As of today the task model of TUTOS is quite a simple one, but we're planning 
to make it evolve, for supporting milestones, task nesting (it's basically 
supported, but not the way you would want it to) and task dependencies.
In the process of changing our task model, I'd see no problem at picking 
yours, which seems to have proved a good one.

> But you might consider 
> converting our XML reports into calendar entries for you calendar database.

In TUTOS 2 the XML output is disabled, but could be redone easily using the 
templating facility... and there's no XML input...

> Regarding the XML-RPC coupling, I'm not sure what you have in mind. Given
> the fundamentally different data representations a bi-directional coupling
> is pretty challenging.

I'm planning to publish TUTOS application level API. That means you could use 
the high level functions (create projects, edit tasks, add timetrack, fill a 
bug report, ...) from an external application, by using e.g. XML-RPC access.

For this to be possible with TaskJuggler, TUTOS would have to be able to 
manage (or at least store) all taskjuggler bits of information.

What I have in mind is to offer TaskJuggler an alternative storage medium. 
Instead of some XML files, which are a great solution when in single user 
mode, we could use the taskjuggler tool for project definition and reports 
and « commit » data to a central server, TUTOS.

In fact I've supposed taskjuggler could be used as a user frontend to TUTOS, 
thus providing an alternative input method for managing projects.
And if this is possible, your taskjuggler users could benefit from a 
centralized solution, where for example a project manager setup the planning, 
then its team members give day to day data about project status (hours 
accounting, tasks completion, ...)

I'm not sure collaboration between our two projects could go further than 
projects planning definition, though... but I'd like to see taskjuggler 
reporting solution usable with an ongoing TUTOS project, containing 
information about scheduled planning and effective one, and resource usage.

Regards,
-- 
Dimitri.
http://dim.tapoueh.org

On peut gagner sa vie en vendant des livres, mais sûrement pas en les
écrivant!
 -- Laurent Chemla, http://www.confessions-voleur.net/

-- 
To unsubscribe, email: taskjuggler-devel-unsubscribe@suse.com
For additional commands, email: taskjuggler-devel-help@suse.com


[prev in list] [next in list] [prev in thread] [next in thread]