Hi all,
Now that Claus is a co-leader of this project we have had some discussion about how to proceed.
In the first instance, what we have decided is that Claus will take the lead on the definition of the requirements for this project while I will take the lead on the development of the tool.
Although there is really not enough crystallization around the specific requirements to produce even a prototype, I believe we have some smaller ideas that are amenable to some 'proof-of-concept' implementations.
I'll let Claus elaborate more on his vision for the specification of the tool's requirements, however let me explain what I mean by 'proof-of-concept'.
>From an architectural perspective, I think it would be valuable to be able to add functionality dynamically to the tool (estimation widgets, scheduling engines, etc.). We should probably investigate what facilities in OOo provide a framework for such dynamic behaviour and perhaps implement an small example of this.
Furthermore, we need to discuss topics such as implementation language, implementation process, etc.
Best regards,
Gil
