> --tutorials (crucial, e.g. gschem 2 pcb by Bill Wilson) These, I fear, can only be written by people actually going through the process for the first time. Those of us with experience, and those of us trying to document a procedure we're not using, will likely skip stuff.
> --faq's (the pcb-tips wiki) Someone who has the time and patience to monitor the mailing lists, and distill the wisdom, is needed here. > --manual (deep documentation of pcb) This is where the developers should concentrate their efforts, because nobody knows the software better than they do. > A manual could be written thru a wiki I would suggest that the PCB cvs is the best place for the reference manual. It really needs to be part of the same dev/test/release process as the sources. That was the goal of the EPS export - to make this more feasible; the PCB files themselves are text and can be stored in CVS without hassles; the Makefiles can run pcb in batch mode to generate the kinds of images (png, eps, pdf) we need for the docs (html, dvi, pdf).
