Hi all,

First, just a quick correction ... Charles was VERY involved in helping
define and drive the project.

I believe where the last flurry of activity ended was a resolution to
proceed in two directions:

1) define requirements for the tool and help shape the vision
2) while requirements are being defined, prototype some 'proof of
concept' ideas that can be reused once the requirements are solidified
enough.

At the time, we didn't have enough developers on the list so perhaps
it's time to take another poll and see what we have in hand?

I'd love to see this project proceed at some measured pace, however we
need involvement from lots of people -- users who would like to see
functionality in the tool and developers who know OOo well enough to
realize the vision of the users.

Claus did a lot of work in starting the requirements discussions by
creating 'issue' entries for each requirement in order to capture
discussions. Can someone take those issues and summarize them in some
sort of requirements document?

Gil


On Thu, 2006-11-30 at 12:27 -0600, [EMAIL PROTECTED] wrote:

> Hi,
> 
> I was involved at perhaps a moderate level some time ago and have been
> quiet mainly to not stifle discussion (not that it is clear that this
> has worked out very well).  Just an observation based on my personal
> history with the list - the activity level is largely what the people
> who are interested in the project make it.  Is there interest in doing
> some real work on the project?  We would need to come to some consensus
> on what functionality would make up a series of development releases,
> and then move forward with actual development.  I'd be happy to work
> requirements,  use cases,  etc. but we need some developers to make
> anything "real".
> 
> Chuck Hunt
> 
> > This message may contain confidential and/or privileged information.
> > If you are not the addressee or authorized to receive this for the
> > addressee, you must not use, copy, disclose, or take any action based
> > on this message or any information herein.  If you have received this
> > message in error, please advise the sender immediately by reply e-mail
> > and delete this message.  Thank you for your cooperation.
> > 
> > 
> > 
> > 

Reply via email to