spm-slides.tex: Starting a New Project 2

1 files changed, 12 insertions, 4 deletions

diff --git a/spm-slides.tex b/spm-slides.tex
index 2a5c412..e10a4bc 100644
--- a/spm-slides.tex
+++ b/spm-slides.tex
@@ -1066,7 +1066,7 @@ Spread your project's name.  Own your project's name in as many of the relevant
 \end{itemize}
 
 
-{\bf Have a clear mission statement}.  Concrete, limiting and {\em short}.   Should be prominently placed on the front page.   For example, Hadoop (a distributed computing software which is able sort 1TB data on 910 nodes in less than 4 minutes).
+{\bf Have a clear mission statement}.  Concrete, limiting and {\em short}.   Should target at specific audience.  Should be prominently placed on the front page.   For example, Hadoop (a distributed computing software which is able sort 1TB data on 910 nodes in less than 4 minutes).
 
 https://hadoop.apache.org/
 
@@ -1161,7 +1161,7 @@ Release notes:  \url{http://wiki.inkscape.org/wiki/index.php/Release\_notes}
 
 {\bf Development status should always reflect reality}.
 Conservativism pays off in the long run; it's always better for the
-software to be more stable than the user expected than less.  Alpha (first release, with known bugs).  Beta (serious known bugs fixed, asking users for detailed feedback).
+software to be more stable than the user expected than less.  Alpha (first release, with known bugs).  Beta (serious known bugs fixed, asking users for detailed feedback).  Production.
 
 {\bf Downloads}.  Downloadable as source code.   Conforming to standard build and installation methods.
 Otherwise, someone visits a web site, downloads the software, tries to build it, fails, gives up and goes away.
@@ -1350,7 +1350,13 @@ Children's songs survive for centuries.  {\em What child is this (1865)?  Greens
 People instinctively look for social norms when they first join a group.
 
 
-{\bf Avoid private discussions}. As slow and cumbersome as public discussion can be, it's almost always preferable in the long run. {\em If there's no reason for it to be private, it should be public.}  * The discussion will help train and educate new developers.   *  The discussion will train you in the art of explaining technical issues to people who are not as familiar with the software as you are.   * There are smart people out there to contribute.
+{\bf Avoid private discussions}. As slow and cumbersome as public discussion can be, it's almost always preferable in the long run. {\em If there's no reason for it to be private, it should be public.}
+
+The discussion will help train and educate new developers.
+
+The discussion will train you in the art of explaining technical issues to people who are not as familiar with the software as you are.
+
+There are smart people out there to contribute.
 
 {\bf Zero-tolerance policy toward rudeness}.  It is unfortunately very
 easy, and all too typical, for constructive discussions to lapse into
@@ -1365,7 +1371,9 @@ or private, from someone that they behaved inappropriately.
 
 {\bf Codes of Conduct}.
 
-\url{https://www.contributor-covenant.org/version/1/4/code-of-conduct}
+\href{https://ubuntu.com/community/code-of-conduct}{Ubuntu Code of Conduct}
+
+\href{https://www.contributor-covenant.org/version/1/4/code-of-conduct}{Contributor Covenant}
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 \foilhead{Code review}