From ee761d3ab60193d972e9153a500ce8bb688e6a04 Mon Sep 17 00:00:00 2001
From: Hui Lan <lanhui@zjnu.edu.cn>
Date: Tue, 9 Apr 2019 09:45:41 +0800
Subject: spm-slides.tex: added more examples of developer guidelines

---
 spm-slides.tex | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

(limited to 'spm-slides.tex')

diff --git a/spm-slides.tex b/spm-slides.tex
index 573a0e5..6a2f6d1 100644
--- a/spm-slides.tex
+++ b/spm-slides.tex
@@ -702,9 +702,14 @@ index 84e3f68..fd54c16 100644
 pointers to forums * instructions on how to report bugs and submit patches 
 * some indication of how development is usually done and how decisions are 
 made — is the project a benevolent dictatorship (veto power), a democracy, 
-or something else.  Example: 
-\url{https://wiki.documentfoundation.org/Development}.  Contrast Developer 
-Guidelines with Developer Documentation.
+or something else.  Good examples: 
+\begin{itemize}
+\item \url{https://wiki.documentfoundation.org/Development}.  
+\item \url{https://subversion.apache.org/docs/community-guide/}
+\item \url{https://www.apache.org/foundation/how-it-works.html}
+\item \url{https://www.apache.org/foundation/voting.html}
+\end{itemize}
+Contrast Developer Guidelines with Developer Documentation.
 
 {\bf Documentation.}  Maintain FAQs (both online and in the
 distribution). There needs to be something for people to read, even if
-- 
cgit v1.2.1

