www/server/standards proprietary-guidelines.html

[Félicien PILLOT]

CVSROOT:        /web/www
Module name:    www
Changes by:     Félicien PILLOT <felandral>    19/10/20 03:41:09

Modified files:
        server/standards: proprietary-guidelines.html 

Log message:
        Add more guidelines (www-discuss "Pending malware items")

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/proprietary-guidelines.html?cvsroot=www&r1=1.2&r2=1.3

Patches:
Index: proprietary-guidelines.html
===================================================================
RCS file: /web/www/www/server/standards/proprietary-guidelines.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- proprietary-guidelines.html 2 Nov 2015 15:13:44 -0000       1.2
+++ proprietary-guidelines.html 20 Oct 2019 07:41:09 -0000      1.3
@@ -16,25 +16,38 @@
 <ol>
 <li>Read the article in its entirety.</li>
 
-<li>Try to focus on the key point of the article, and how it relates to
-the category it belongs.</li>
+<li>Be clear and concise.</li>
 
-<li>If an entry belongs to multiple categories, consider writing a
-slightly changed version for each category so that it highlights the
-aspect that relates to that particular category.</li>
-
-<li>Try to word the text in a way that respects the core values of free
-software (such as <a href="/philosophy/words-to-avoid.html">using certain
-expressions with care</a>).</li>
+<li>Try to focus on the key point of the article, and how it relates
+to the category it belongs.</li>
 
-<li>Try to clarify any serious misconceptions spread by the article, if
-there are any.</li>
+<li>Talk about facts, not opinions, sentiments nor speculations.</li>
 
-<li>Be clear and concise.</li>
+<li>Talk about programs, not services nor devices. However, when a
+nonfree program depends on service(s) or device(s) to run, mention
+it.</li>
+
+<li>Don't quote the article sentences, but reformulate it to make our
+point visible.</li>
+
+<li>Emphasis the fact that the injustice is a consequence of the
+program being nonfree (so users don't control it and can't modify
+it). For example: first, describe the malicious functionality, then,
+highlight the user's inability to bypass it.</li>
+
+<li>When an entry belongs to multiple categories you can write a
+slightly changed version for each category &mdash;if needed&mdash; so
+that it highlights the aspect that relates to that particular
+category.</li>
+
+<li>Try to word the text in a way that respects the core values of
+free software (such as <a href="/philosophy/words-to-avoid.html">using
+certain expressions with care</a>), and clarify any serious
+misconceptions spread by the article.</li>
 
 <li>Ask the GNU webmasters
-<a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>
-if there are any doubts.</li>
+<a href="mailto:address@hidden";>&lt;address@hidden&gt;</a> (or
+via our discuss mailing list) if there are any doubts.</li>
 </ol>
 </div><!-- for id="content", starts in the include above -->
 <!--#include virtual="/server/footer.html" -->
@@ -93,7 +106,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2015/11/02 15:13:44 $
+$Date: 2019/10/20 07:41:09 $
 <!-- timestamp end -->
 </p>
 </div>