No commit message

cernohlideasfor12.md

@@ -7,6 +7,21 @@ preferred way for discussing any issues related to the CERN OHL.
 
 # Current list of things to look at for the next version
 
+### Concerns about the definition of "Documentation"
+
+  - From the updates@lists.openhardwaresummit.org mailing list: "I think
+    that you might want to patch a "hole" in the definition of
+    "Documentation" that allows people to distribute essentially
+    unusable/unmodifiable forms of documentation, such as a photograph
+    of the PCB layout. This adds teeth to your viral provision,
+    otherwise I can claim I modified the documentation (both in content
+    and format) and here is my out-of-focus, impossible to really use
+    photo of the result. GPLv2 and v3 uses: The “source code” for a work
+    means the preferred form of the work for making modifications to
+    it."
+
+### Concerns about the "notification of changes" (3.3d) clause
+
   - 3.3d deals with the obligation of the licensees to send a
     notification to the licensors every time they make a modification
     they want to publish/distribute. It has been noted that, in version
@@ -24,14 +39,4 @@ preferred way for discussing any issues related to the CERN OHL.
     it turns into a "orphaned work". See
     http://en.wikipedia.org/wikis/Orphan_works for an intro to the
     subject."
-  - From the updates@lists.openhardwaresummit.org mailing list: "I think
-    that you might want to patch a "hole" in the definition of
-    "Documentation" that allows people to distribute essentially
-    unusable/unmodifiable forms of documentation, such as a photograph
-    of the PCB layout. This adds teeth to your viral provision,
-    otherwise I can claim I modified the documentation (both in content
-    and format) and here is my out-of-focus, impossible to really use
-    photo of the result. GPLv2 and v3 uses: The “source code” for a work
-    means the preferred form of the work for making modifications to
-    it."