Hi! I took nearly 1 hour this morning to review, confirm, mark duplicated some issues. I think that if many volounters take time to do that, the issue list will be more up-to-date and it will be easy to developpers to focus on issues (more accurate descriptions, etc.)
I think marking duplicates is important, because it is easier to find a specific issue (and maybe to vote for it) when many different descriptions exist. I realized that many issues are waiting for a comment from the issuer, who will probably never reply. What should I do with those issues? Should they be marked as INVALID? After how mush time? I like Jonathon's idea to modularize code. I have some knowledges in C ++, but I don't have time to build the entire OOo product, and not even a machine powerful enough to do that. I'd like to help with some debugging or optimization, but I simply cannot. The only thing I can do is to raise or to confirm some issues, from time to time... Charles. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
