/usr/share/help/el/programming-guidelines/additional-materials.page is in gnome-devel-docs 3.28.0-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 | <?xml version="1.0" encoding="utf-8"?>
<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="el">
<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>Other style guides and books about organizing free software
projects</desc>
<mal:credit xmlns:mal="http://projectmallard.org/1.0/" type="translator copyright">
<mal:name>Ελληνική μεταφραστική ομάδα GNOME</mal:name>
<mal:email>team@gnome.gr</mal:email>
<mal:years>2016</mal:years>
</mal:credit>
<mal:credit xmlns:mal="http://projectmallard.org/1.0/" type="translator copyright">
<mal:name>Θάνος Τρυφωνίδης</mal:name>
<mal:email>tomtryf@gnome.org</mal:email>
<mal:years>2016</mal:years>
</mal:credit>
</info>
<title>Επιπρόσθετο υλικό</title>
<p>
Here we give you links to other materials that you may want to
read. These will teach you a lot about how to work on large
distributed teams of free software developers, and about good
programming style in general.
</p>
<list>
<item>
<p>
<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 <em>social aspects</em> 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.
</p>
</item>
<item>
<p>
<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.
</p>
</item>
<item>
<p>
<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.
</p>
</item>
</list>
</page>
|