I'm standing by at this point as stuff outside of my field of competence is being discussed and pcb is on its way.
I was wondering if it could be useful to start creating shared documentation that the group could contribute, to be completed steb by step in order for these docs to be usable when the device is ready to be released and thus reducing downtime.
Examples: BOM, requirements and manual.
- The BOM could be a spreadsheet with all the parts and their suppliers, alternative suppliers, price; different tabs cover the same parts different zones. Guys from different areas will fill the fields with reference to local sellers.
- Requirements: to make this machine, you will need this and this, the following programs, and these are the download links...
- Manual: the manual will be written in International English end revised by the group (under supervision).
Sw developers can throw raw descriptions of the functionalities into the Manual doc and later give feedback if needed to the people making the polished version.
Different tabs will contain the various translations in progress (Spanish, French...).
The advantage being that those doc can be modified by people without creating numberless posts on this list (with supervisors standing).
Fine-tuning the procedures, the improvement could be continuous and give us the documents almost effortlessly at the time they are needed.
The platform will be Google Docs, for practical reasons.
I could create the above docs and facilitate operations and be in charge of something BUT other competent supervisors and helpers MUST volunteer. Can't be a one-man task.
Waiting for opinions on the above
Raf
Bob Benedict, KD8CGH