In article <aj9oop$[EMAIL PROTECTED]>, "Alex Vincent" <[EMAIL PROTECTED]> writes:
>We must not fail, this time. The only way we can fail at this point is to >stop trying, to stop brainstorming. As I said, I'm willing to throw away >the idea of developing tools if we can get policies -- and more importantly, >target experts in the respective fields -- identified first. I've been lurking on this board for the past several weeks and on mozilla.org since, well, probably not too long after it was introduced. :) I would be interested in helping to write documentation. I would be most interested in end-user documentation. I'd also be interested in helping to review documents (i.e., for grammar and usage--and I won't get into that standard spelling debate! <g>) if needed, or possibly make sure they're up-to-date with the changes in newer versions. I also know C++, but I've never looked at the Mozilla source. I know C++, but I'm not an expert Windows C++ programmer! But part of that is because the source, I think, is kind of large--and I'm on dial-up. The other part is that I barely remember how I'd get it, since if I remember when I was going to try that it was kind of complicated. I haven't checked lately. But code documentation probably wouldn't be my interest. I'd have to brush up a LOT, and now I'm focused on learning Java and CSS, and I will be back in classes in just over a week. :) Anyway ... I'm not sure where to start, and I'm sure that your proposed changes will help eliminate some of the complications and questions involved. Still, I'm still willing to help now--but can't seem to figure out where to start. Is there somewhere where the current docs are, and where one can look through them and add as necessary (according to, for example, a list of proposed additions or "growth areas"?) and modify if needed? Thanks, -- Robert M. E-mail from most addresses is blocked (but that is my real address <G>)
