> Overall Structure:
> - about the organization
> - news & events hierarchies
> - software hierarchy for all software released by mozilla.org
> - developer hierarchy subdivided into:
> - Application development
What is an application?
/Checkin, /cvs-access and /review shouldn't be under /moz, because they
apply to most/all mozilla-org hosted software.
Same for instructions on use of the web tools, and the coding guidelines.
"subdirectory structure mimics..." - /distributors has no meaning for any
mozilla.org software other than Mozilla, and /ports has meaning for very
few. Just a note :-)
The news hierarchy will probably be de facto organised by whatever Zope
add-on we use to deal with it.
I reserve the right to make further comments as time goes on ;-)
Remind me what goes in classic?
> - Should press releases also be pulled out into /press/'year'?
No. We make about one a year as it is.
> Testing/Testcases:
> - Where should testcases go?
In the hacking area for the bit of software they relate to.
> - Instructions for running automated tests?
With the testcases.
Gerv
