On Sun, Dec 17, 2006 at 06:23:32PM -0500, Timothy Miller wrote:
>
> (3) Going with the spirit of being an educational project, not to
> mention good engineering practices, I think we should document this in
> fine detail. It should be documented to the point that people with no
> experience in hardware design can follow along and make sense of it,
> and those with hardware design experience could code a new one in a
> week. We can start with more comments, but diagrams, ODF documents
> (and PDFs of those), and sort-of tutorials would be good to have.
This recalls discussions a year or so ago about what file formats
OGP should choose for its documentation. What Tim said here is along the
lines I've been thinking.
If the members approve, I'd like to try writing a page for the wiki
on documentation policy. I suggest these principles:
1. Whenever possible, formal standards, manuals, drawings, and other
documentation that represents the finished work of the Project shall be
edited in file formats that comply with published open standards. In
general, formats that are recognized as open standards by other open source
hardware and software projects, or by governments, are acceptable to OGP.
OGP specifically recognizes as open standards:
Plain ASCII or UTF-8 text
ODF (ISO 26300)
PDF
2. OGP respectfully requests that e-mail on the main mailing list be plain
text when possible.
3. OGP recognizes that its members and contributors are volunteers, and
will use the tools and formats they find necessary in their work. We don't
attempt to set policy for files created for temporary use, or for current
communication among project participants.
Would we be justified in including DXF as a recognized standard
format?
_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)
