diff options
| -rw-r--r-- | spm-slides.tex | 30 |
1 files changed, 30 insertions, 0 deletions
diff --git a/spm-slides.tex b/spm-slides.tex index c0e9883..4938ee7 100644 --- a/spm-slides.tex +++ b/spm-slides.tex @@ -776,6 +776,36 @@ of each software source file. \end{verbatim} } +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +\foilhead{Good precedents} + + +Mailing list address. Keep discussions on-topic and productive. + +Change of development processs. For example, you have to be more careful +about your public image. + +Turnovers. New arrivals. + +Project stability depends on: + +\begin{itemize} +\item Formal policies, written rules. +\item Collective wisdow developed over time. +\item Intangible, ever-evolving agreements. +\end{itemize} + +Healthy turnover won't damage social norms because we have regular {\em transmission effort}. + + + +Children's songs survive for centuries. {\em Greensleeves} (the 16th-century folk tune). + +{\em Classic of Poetry} (China's Book of Songs from 1046–771 BC). + +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 Zero-tolerance policy toward rudeness}. It is unfortunately very |