On Nov 20, 2005, at 8:59 AM, Edward Summers wrote:
On Nov 19, 2005, at 1:09 PM, James Howison wrote:
Probably I'm crazy.
If you're crazy, then so am I. It seems odd to me as well.
David sent me his thoughts on explaining some of this. As he's in
Australia, I hope he won't mind if I try clear this up a bit by just
forwarding his note, with some slight additions. FWIW, we're not the
only OOo project to be experiencing some of these challenges. OOo is a
huge, complex application, and while it is open source, the people that
are paid to understand it in depth work for Sun.
Anyway, from David (speaking for both of us of course):
James,
James you are not crazy. The situation is quite simple. We have been
waiting on some Sun people for assistance not because we need to wait
for a Sun employee, but because we have not had a volunteer in our
project who understood Openoffice internals or its development process
well enough to proceed by ourselves.
Like any other Open Source project, we could have, at any any stage in
the past couple of years, checked out the OpenOffice source code,
rebuilt it with bibliographic enhancements, and started using it.
There are several reason way this has not happened yet. One reason is
simply that we have not been ready as we were designing the
bibliographic formating engine and working out the changes necessary.
But also we have not had anyone volunteer their time who had the
interest, knowledge or skills to actually do development work on OOo
internals.
We are hoping that by using Sun's experts to set up the workspace and
then work with us to understand the details of what needs to be done,
we can write up detailed task descriptions that we will be able to
attract some skilled C++ programmers to take on some of these
programming tasks.
David
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
