r5324 - developers/werner/openness

werner at docs.openmoko.org werner at docs.openmoko.org
Mon Jul 27 01:42:10 CEST 2009


Author: werner
Date: 2009-07-27 01:42:09 +0200 (Mon, 27 Jul 2009)
New Revision: 5324

Added:
   developers/werner/openness/odhwdr.tex
Removed:
   developers/werner/openness/oshwdr.tex
Modified:
   developers/werner/openness/Makefile
Log:
- changed title from "Open Source Hardware" to "Open Design Hardware"
- renamed from oshwdr.tex to odhwdr.tex
- one more benefit for non-NDA and assorted style corrections by Dave Ball



Modified: developers/werner/openness/Makefile
===================================================================
--- developers/werner/openness/Makefile	2009-07-24 10:00:16 UTC (rev 5323)
+++ developers/werner/openness/Makefile	2009-07-26 23:42:09 UTC (rev 5324)
@@ -3,22 +3,22 @@
 all:	xpdf
 
 dvi:
-	latex oshwdr
+	latex odhwdr
 
 xdvi:	dvi
-	xdvi oshwdr
+	xdvi odhwdr
 
 pdf:
-	pdflatex oshwdr
+	pdflatex odhwdr
 
 xpdf:	pdf
-	xpdf oshwdr.pdf
+	xpdf odhwdr.pdf
 
 print:	dvi
-	dvips -f oshwdr | lpr
+	dvips -f odhwdr | lpr
 
 print4:	dvi
-	dvips -f oshwdr | mpage -4 | lpr
+	dvips -f odhwdr | mpage -4 | lpr
 
 upload:	pdf
-	scp oshwdr.pdf werner at sita.openmoko.org:public_html/
+	scp odhwdr.pdf werner at sita.openmoko.org:public_html/

Copied: developers/werner/openness/odhwdr.tex (from rev 5314, developers/werner/openness/oshwdr.tex)
===================================================================
--- developers/werner/openness/odhwdr.tex	                        (rev 0)
+++ developers/werner/openness/odhwdr.tex	2009-07-26 23:42:09 UTC (rev 5324)
@@ -0,0 +1,144 @@
+%
+% Audience: component vendors
+%
+% Objectives:
+% - accurately present our needs
+% - understandable (to corporate)
+% - convincing
+%
+% Off-topic:
+% - software requirements
+% - firmware updates
+%
+
+\documentclass[12pt]{article}
+%\usepackage{fullpage}
+\usepackage{a4wide}
+\usepackage[obeyspaces]{url}
+\pagestyle{empty}
+
+\title{Open Design Hardware --- Disclosure Requisites}
+\author{Werner Almesberger \\ \url{werner at openmoko.org}}
+\date{July 26, 2009}
+
+\parindent=0pt
+\parskip=8pt
+\addtolength{\textheight}{10mm}
+
+\begin{document}
+\maketitle
+\thispagestyle{empty}
+
+\framebox[\textwidth][c]{
+\begin{minipage}{0.9\textwidth}
+~\vskip1mm
+\parskip=8pt
+This is a draft. The term ``Open Design Hardware'' and the title
+``Disclosure Requisites'' are both open for discussion, along with
+the rest of the document. This box will be removed in the final
+version.
+
+This short document aims to familiarize component vendors with the concepts
+of Open Design Hardware and to explain the specific needs of OSH. The
+objectives:
+\begin{itemize}
+  \item accurately present our needs
+  \item be understandable (to a corporate readership)
+  \item convince them to provide documentation in a way we can use
+\end{itemize}
+
+Open Source Software and firmware requirements have been deliberately
+excluded to keep this short and because they should/might be covered
+in a separate document.
+\vskip-2mm~
+\end{minipage}}
+\vskip2mm
+
+Open Source Software has proven that an open design process and liberal
+licensing contribute towards enhancing the quality, utility, and overall
+success of software products, and encourage convergence and cooperation
+among projects.
+
+Open Design Hardware is an approach that aims to enhance quality and
+value of hardware products by applying an open design process, in keeping
+with best practices of Open Source Software development.
+
+This document outlines the characteristics and benefits of Open Design
+Hardware and explains the requisites resulting from this on technical
+documentation provided by component vendors.
+
+
+\section{Characteristics}
+
+Open Design Hardware is guided by the following principles:
+
+\begin{itemize}
+  \item Expose the entire design process to public review.
+  \item Invite contributions from anyone willing and able, irrespective
+    of affiliation.
+  \item Distribute the resulting design under an Open license,
+    permitting use and further modification free from royalties.
+\end{itemize}
+
+Examples of Open licenses include the {\em General Public License} (GPL)%
+\footnote{\url{http://www.gnu.org/copyleft/gpl.html}} and the {\em Creative
+Commons Attribution -- Share Alike} license (CC-BY-SA)%
+\footnote{\url{http://creativecommons.org/licenses/by-sa/3.0/}}.
+
+
+\section{Benefits}
+
+Fully disclosing the design and the decision making process leading to it
+brings the following benefits to development and use of the product:
+
+\begin{itemize}
+  \item Enables prospective buyers and developers to participate in
+    ensuring high quality of the product, e.g., through reviews. This also
+    helps to accelerate the produce development process.
+  \item Permits prospective buyers and VARs to conduct a thorough and
+    honest evaluation of the product design, improving their ability
+    to correctly project the product's use and increasing their
+    confidence in choosing the product.
+  \item Lowers the barrier for developers and integrators to add value,
+    either as early as during the design phase or on top of the finished
+    product.
+  \item Protects the investment of buyers, developers, and integrators
+    by enabling them to make corrections, enhancements, and even
+    derivative products without depending on the availability of the
+    original designers and manufacturer.
+  \item Creates the opportunity for other projects to reuse
+    part or all of the design with a minimum of overhead, and to grow
+    synergies by reciprocating.
+\end{itemize}
+
+
+\section{Documentation requisites}
+
+The open hardware development process requires the use of components
+for which the vendor makes technical product documentation available
+under terms that allow public use of the information gathered from it.
+The most common forms of such terms are:
+
+\begin{description}
+  \item[Permissive NDA]~\\
+    Material is provided by the vendor under an NDA tailored to this
+    purpose. The NDA allows open
+    discussion of the design and distribution of the resulting work
+    (schematics, layout, system software) under an Open license.
+  \item[Public access]~\\
+    The vendor publishes data sheets and related material to the public,
+    e.g., on its Web site. Access to this information for Open Design
+    Hardware is then no different from any other use.
+  \item[Redistribution rights]~\\
+    The vendor also grants redistribution rights, allowing projects to
+    ensure that documents remain available even when the vendor no
+    longer supports the product.
+\end{description}
+
+Public access is preferable over a permissive NDA since it limits the
+effort that has to be made on both sides before evaluation can begin,
+reduces the risk of misunderstandings, avoids overhead in the design
+phase, and frees derivative projects from having to negotiate access
+as well.
+
+\end{document}

Deleted: developers/werner/openness/oshwdr.tex
===================================================================
--- developers/werner/openness/oshwdr.tex	2009-07-24 10:00:16 UTC (rev 5323)
+++ developers/werner/openness/oshwdr.tex	2009-07-26 23:42:09 UTC (rev 5324)
@@ -1,142 +0,0 @@
-%
-% Audience: component vendors
-%
-% Objectives:
-% - accurately present our needs
-% - understandable (to corporate)
-% - convincing
-%
-% Off-topic:
-% - software requirements
-% - firmware updates
-%
-
-\documentclass[12pt]{article}
-%\usepackage{fullpage}
-\usepackage{a4wide}
-\usepackage[obeyspaces]{url}
-\pagestyle{empty}
-
-\title{Open Source Hardware --- Disclosure Requisites}
-\author{Werner Almesberger \\ \url{werner at openmoko.org}}
-\date{July 23, 2009}
-
-\parindent=0pt
-\parskip=8pt
-\addtolength{\textheight}{10mm}
-
-\begin{document}
-\maketitle
-\thispagestyle{empty}
-
-\framebox[\textwidth][c]{
-\begin{minipage}{0.9\textwidth}
-~\vskip1mm
-\parskip=8pt
-This is a draft. The term ``Open Source Hardware'' and the title
-``Disclosure Requisites'' are both open for discussion, along with
-the rest of the document. This box will be removed in the final
-version.
-
-This short document aims to familiarize component vendors with the concepts
-of Open Source Hardware and to explain the specific needs of OSH. The
-objectives:
-\begin{itemize}
-  \item accurately present our needs
-  \item be understandable (to a corporate readership)
-  \item convince them to provide documentation in a way we can use
-\end{itemize}
-
-Open Source Software and firmware requirements have been deliberately
-excluded to keep this short and because they should/might be covered
-in a separate document.
-\vskip-2mm~
-\end{minipage}}
-\vskip2mm
-
-Open Source Software has proven that an open design process and liberal
-licensing contribute towards enhancing the quality, utility, and overall
-success of software products, and encourage convergence and cooperation
-among projects.
-
-Open Source Hardware is an approach that aims to enhance quality and
-value of hardware products by applying an open design process, in keeping
-with best practices of Open Source Software development.
-
-This document outlines the characteristics and benefits of Open Source
-Hardware and explains the requisites resulting from this on technical
-documentation provided by component vendors.
-
-
-\section{Characteristics}
-
-Open Source Hardware design is guided by the following principles:
-
-\begin{itemize}
-  \item Expose the entire design process to public review.
-  \item Invite contributions from anyone willing and able, irrespective
-    of affiliation.
-  \item Distribute the resulting design under an Open license,
-    permitting use and further modification free from royalties.
-\end{itemize}
-
-Examples of Open licenses include the {\em General Public License} (GPL)%
-\footnote{\url{http://www.gnu.org/copyleft/gpl.html}} and the {\em Creative
-Commons Attribution -- Share Alike} license (CC-BY-SA)%
-\footnote{\url{http://creativecommons.org/licenses/by-sa/3.0/}}.
-
-
-\section{Benefits}
-
-Fully disclosing the design and the decision process leading to it
-brings the following benefits to development and use of the product:
-
-\begin{itemize}
-  \item Enables prospective buyers and developers to participate in
-    ensuring high quality of the product, e.g., through reviews. This also
-    helps to accelerate the produce development process.
-  \item Permits prospective buyers and VARs to conduct a thorough and
-    honest evaluation of the product design, improving their ability
-    to correctly project the product's use and increasing their
-    confidence in choosing the product.
-  \item Lowers the barrier for developers and integrators to add value,
-    either already during the design phase or on top of the finished product.
-  \item Protects the investment of buyers, developers, and integrators
-    by enabling them to make corrections, enhancements, and even
-    derivative products without depending on the availability of the
-    original designers and manufacturer.
-  \item Creates the opportunity for other projects to reuse
-    part or all of the design with a minimum of overhead, and to grow
-    synergies by reciprocating.
-\end{itemize}
-
-
-\section{Documentation requisites}
-
-The open hardware development process requires the use of components
-for which the vendor makes technical product documentation available
-under terms that allow public use of the information gathered from it.
-The most common forms of such terms are:
-
-\begin{description}
-  \item[Permissive NDA]~\\
-    Material is provided by the vendor under an NDA tailored to this
-    purpose. The NDA allows open
-    discussion of the design and distribution of the resulting work
-    (schematics, layout, system software) under an Open license.
-  \item[Public access]~\\
-    The vendor publishes data sheets and related material to the public,
-    e.g., on its Web site. Access to this information for Open Source
-    Hardware is then no different from any other use.
-  \item[Redistribution rights]~\\
-    The vendor also grants redistribution rights, allowing projects to
-    ensure that documents remain available even when the vendor no
-    longer supports the product.
-\end{description}
-
-Public access is preferable over a permissive NDA since it limits the
-effort that has to be made on both sides before evaluation can begin,
-reduces the risk of misunderstandings, and avoids overhead in the design
-phase.
-
-\end{document}




More information about the commitlog mailing list