|
|
1.
|
|
|
translator-credits
|
| Context: |
|
_
|
|
|
Put one translator per line, in the form NAME <EMAIL>, YEAR1, YEAR2
|
|
|
|
|
To prevent privacy issues, this translation is not
available to anonymous users,
if you want to see it, please, log in
first. |
|
|
2.
|
|
|
Federico Mena-Quintero
|
|
|
(itstool) path: credit/name
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/additional-materials.page:10
C/c-coding-style.page:10
C/documentation.page:11
C/index.page:8
C/writing-good-code.page:10
|
|
|
3.
|
|
|
2013
|
|
|
(itstool) path: credit/years
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/additional-materials.page:12
C/c-coding-style.page:12
C/documentation.page:13
C/index.page:10
C/writing-good-code.page:12
|
|
|
4.
|
|
|
Other style guides and books about organizing free software projects
|
|
|
(itstool) path: info/desc
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/additional-materials.page:17
|
|
|
5.
|
|
|
Additional Materials
|
|
|
(itstool) path: page/title
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/additional-materials.page:21
|
|
|
6.
|
|
|
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.
|
|
|
(itstool) path: page/p
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/additional-materials.page:23
|
|
|
7.
|
|
|
<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.
|
|
|
(itstool) path: item/p
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/additional-materials.page:32
|
|
|
8.
|
|
|
<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.
|
|
|
(itstool) path: item/p
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/additional-materials.page:46
|
|
|
9.
|
|
|
<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.
|
|
|
(itstool) path: item/p
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/additional-materials.page:57
|
|
|
10.
|
|
|
Philip Withnall
|
|
|
(itstool) path: credit/name
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/api-stability.page:10
C/async-programming.page:11
C/databases.page:11
C/documentation.page:16
C/file-system.page:11
C/gerror.page:11
C/glist.page:11
C/index.page:21
C/introspection.page:10
C/logging.page:11
C/main-contexts.page:11
C/memory-management.page:10
C/namespacing.page:10
C/parallel-installability.page:18
C/preconditions.page:11
C/threading.page:11
C/tooling.page:10
C/unit-testing.page:10
C/version-control.page:10
C/versioning.page:10
|
