Gervase Markham wrote:
>
> > 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?
I think it means an application developed on top of the Mozilla core
technologies, e.g. the browser, or chatzilla.
> /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.
true. I'd move them up to Developer, except they don't apply
to web developers. Any ideas? I have a couple half-baked ones
that don't stand up to much scrutinizing.
I'll post if I come up with something edible, if not appetizing.
> I reserve the right to make further comments as time goes on ;-)
No reservations required. >:)
> Remind me what goes in classic?
Mozilla Classic documentation: http://www.mozilla.org/classic/
I didn't see any reason to move it.
> > Testing/Testcases:
> > - Where should testcases go?
>
> In the hacking area for the bit of software they relate to.
Once the hacking area for the software is defined..
