<page xmlns="http://projectmallard.org/1.0/" xmlns:its="http://www.w3.org/2005/11/its" type="guide" style="task" id="additional-materials" xml:lang="de">

  <info>

    <link type="guide" xref="index#references"/>

    <credit type="author copyright">

      <name>Federico Mena-Quintero</name>

      <email its:translate="no">federico@gnome.org</email>

      <years>2013</years>

    </credit>

    <include xmlns="http://www.w3.org/2001/XInclude" href="cc-by-sa-3-0.xml"/>

    <desc>Andere Richtlinien und Bücher über die Organisation von Projekten der Freien Software</desc>

    <mal:credit xmlns:mal="http://projectmallard.org/1.0/" type="translator copyright">

      <mal:name>Mario Blättermann</mal:name>

      <mal:email>mario.blaettermann@gmail.com</mal:email>

      <mal:years>2016</mal:years>

    </mal:credit>

    <mal:credit xmlns:mal="http://projectmallard.org/1.0/" type="translator copyright">

      <mal:name>Christian Kirbach</mal:name>

      <mal:email>christian.kirbach@gmail.com</mal:email>

      <mal:years>2016</mal:years>

    </mal:credit>

  </info>

  <title>Zusätzliche Materialien</title>

  
Hier sind einige Links zu anderen Materialien, die Sie vielleicht lesen wollen. Sie vermitteln Ihnen einen Einblick in die Arbeitsweise weit verstreuter Teams von Entwicklern freier Software sowie über guten Programmierstil im Allgemeinen.

  <list>

    <item>

	<link href="http://producingoss.com/">Producing Open Source

	Software</link>, by Karl Fogel.  This is a truly excellent

	book of good practices that free software projects should

	follow.  This is about social aspects of the project:

	how to treat contributors, how to organize and moderate

	communication, how to deal with non-profit foundations.  If

	you ask yourself at any time, "how should I deal with

	$human_situation in the project?", this book may provide the

	answer.

    </item>

    <item>

	<link href="http://www.gnu.org/prep/standards/">GNU Coding

	Standards</link>.  This is an old document, but it still has

	lots of excellent advice.  It talks about C coding style,

	issues when dealing with plug-in systems, common option names

	for command-line programs, conventions for Makefiles, and some

	very GNU-ish details like using Texinfo for documentation.

    </item>

    <item>

	<link href="https://www.kernel.org/doc/Documentation/process/coding-style.rst">

	Linux Kernel Coding Style</link>.  Explains the rationale for "big

	indentation", brace placement, concise but unambiguous naming, and

	centralized exit of functions.

    </item>

  </list>

</page>