Towards Mozilla 1.0
Tuesday June 26th, 2001
Gervase Markham recently posted his feelings on what a 1.0 release of Mozilla would be. Gerv has sent us the follow-up to that posting, including much of the feedback he received. To read it, click the full article link. Once you have read through it, we welcome you to post your feelings on what you think a 1.0 release would have. [As Gerv says, please don't post your favorite list of bugs, only the criteria for choosing what bugs to fix.]
#65 3 Things Matter: Documentation, Documentation & Do
by ksosez <firstname.lastname@example.org>
Wednesday June 27th, 2001 12:50 PM
You are replying to this message
(Ran out of room in the topic) :)
Anywhere here we go, Before 1.0 is released we *MUST* have better documentation. I don't care if we have to stop all the developers for 24-48 hours and have people take notes while they talk we need better documentation.
I know its hard and not the fun part of development (trust me I have done my fair share of development too and I hate documentating stuff) but in order for Mozilla to continue to be successful we need to have more help for people who want to get involved/patch and this means documentation.
The reason I say this is because the way I view open source projects. Open source projects start very small usually with only a few people working on it, as more people hear about it and get involved they tell there friends and so on. At a certain point you reach a critical mass where so many people are working on it the development starts to out pace any commercial development project on the planet. However Mozilla *cannot* and will *not* reach that point until we have better documentation.
As one of the largest QA contributing people outside of the Mozilla and Netscape organizations I must say its quite frustrating to have people want to help out only to have no way to help them get started coding besides just looking at the code and patching a bug.
In addition if Mozilla is going to be built upon by other organizations (for cool plugins or whatever) we need to have how the internals work documentated or it will be a moot point.
So again i Say.....sit the developers down for 24-48 hours and have them spill how everything works and then throw it up on a webpage and format it as we go along. This will help tremendously, and I am available to take notes. :)