Ian Lynch wrote: > 3.0 Get rid of all redundant code, systematically improve the efficiency
I would make that the number one priority. It might not appear significant to end users, but eliminating all of the duplicate libraries will give OOo some pretty useful features --- stuff that is currently implemented, but unable to be used, due to the plethora of libraries, etc. > document everything so a complete coding beginner could learn how to > contribute. Heck if Sun's coders would stick to the same coding specifications, it would be easier for a new person to contribute code. But when you have to check three string libraries, to verify that the string you called won't be mangled ..... > all that is required is the political will to look a bit beyond next year It isn't political will, as much as it is sheer practicality. I've forgotten how many lines of code there are, but when I specked it out, it looked like a six man month operation. Then there is the lag between the time the new code is incorporated in to the existing code base, and then the bug fixes, because people called libraries that have been removed. But this is something that needs to be done, sooner rather than later. xan jonathon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
