diff options
Diffstat (limited to 'doc/documentation/chapters/preface.texi')
-rw-r--r-- | doc/documentation/chapters/preface.texi | 67 |
1 files changed, 47 insertions, 20 deletions
diff --git a/doc/documentation/chapters/preface.texi b/doc/documentation/chapters/preface.texi index 00e6290f0..29cf924a2 100644 --- a/doc/documentation/chapters/preface.texi +++ b/doc/documentation/chapters/preface.texi | |||
@@ -12,9 +12,9 @@ all kinds of basic applications for the foundation of a new Internet. | |||
12 | 12 | ||
13 | @menu | 13 | @menu |
14 | * About this book:: | 14 | * About this book:: |
15 | * Contributing to this book:: | ||
15 | * Introduction:: | 16 | * Introduction:: |
16 | * Project governance:: | 17 | * Project governance:: |
17 | * General Terminology:: | ||
18 | * Typography:: | 18 | * Typography:: |
19 | @end menu | 19 | @end menu |
20 | 20 | ||
@@ -37,6 +37,26 @@ The first chapter (``Preface'') as well as the the second | |||
37 | chapter (``Philosophy'') give an introduction to GNUnet as a project, | 37 | chapter (``Philosophy'') give an introduction to GNUnet as a project, |
38 | what GNUnet tries to achieve. | 38 | what GNUnet tries to achieve. |
39 | 39 | ||
40 | @node Contributing to this book | ||
41 | @section Contributing to this book | ||
42 | |||
43 | The GNUnet Reference Manual is a collective work produced by various | ||
44 | people throughout the years. The version you are reading is derived | ||
45 | from many individual efforts hosted on our website. This was a failed | ||
46 | experiment, and with the conversion to Texinfo we hope to address this | ||
47 | in the longterm. Texinfo is the documentation language of the GNU project. | ||
48 | While it can be intimidating at first and look scary or complicated, | ||
49 | it is just another way to express text format instructions. We encourage | ||
50 | you to take this opportunity and learn about Texinfo, learn about GNUnet, | ||
51 | and one word at a time we will arrive at a book which explains GNUnet in | ||
52 | the least complicated way to you. Even when you don't want or can't learn | ||
53 | Texinfo, you can contribute. Send us an Email or join our IRC chat room | ||
54 | on freenode and talk with us about the documentation (the prefered way | ||
55 | to reach out is the mailinglist, since you can communicate with us | ||
56 | without waiting on someone in the chatroom). One way or another you | ||
57 | can help shape the understanding of GNUnet without the ability to read | ||
58 | and understand its sourcecode. | ||
59 | |||
40 | @node Introduction | 60 | @node Introduction |
41 | @section Introduction | 61 | @section Introduction |
42 | 62 | ||
@@ -66,25 +86,31 @@ immediately. A few months after the first release we contacted the | |||
66 | GNU project, happily agreed to their governance model and became an | 86 | GNU project, happily agreed to their governance model and became an |
67 | official GNU package. | 87 | official GNU package. |
68 | 88 | ||
69 | Within the first year, we created GNU libextractor, a helper library | 89 | Within the first year, we created |
90 | @uref{https://gnu.org/s/libextractor, GNU libextractor}, a helper library | ||
70 | for meta data extraction which has been used by a few other projects | 91 | for meta data extraction which has been used by a few other projects |
71 | as well. 2003 saw the emergence of pluggable transports, the ability | 92 | as well. 2003 saw the emergence of pluggable transports, the ability |
72 | for GNUnet to use different mechanisms for communication, starting | 93 | for GNUnet to use different mechanisms for communication, starting |
73 | with TCP, UDP and SMTP (support for the latter was later dropped due | 94 | with TCP, UDP and SMTP (support for the latter was later dropped due |
74 | to a lack of maintenance). In 2005, the project first started to | 95 | to a lack of maintenance). In 2005, the project first started to |
75 | evolve beyond the original file-sharing application with a first | 96 | evolve beyond the original file-sharing application with a first |
76 | simple P2P chat. In 2007, we created GNU libmicrohttpd | 97 | simple P2P chat. In 2007, we created |
98 | @uref{https://gnu.org/s/libmicrohttpd, GNU libmicrohttpd} | ||
77 | to support a pluggable transport based on HTTP. In 2009, the | 99 | to support a pluggable transport based on HTTP. In 2009, the |
78 | architecture was radically modularized into the multi-process system | 100 | architecture was radically modularized into the multi-process system |
79 | that exists today. Coincidentally, the first version of the ARM | 101 | that exists today. Coincidentally, the first version of the ARM@footnote{ARM: Automatic Restart Manager} |
80 | service was implemented a day before systemd was announced. From 2009 | 102 | service was implemented a day before systemd was announced. From 2009 |
81 | to 2014 work progressed rapidly thanks to a significant research grant | 103 | to 2014 work progressed rapidly thanks to a significant research grant |
82 | from the Deutsche Forschungsgesellschaft. This resulted in particular | 104 | from the Deutsche Forschungsgesellschaft. This resulted in particular |
83 | in the creation of the R5N DHT, CADET, ATS and the GNU Name System. | 105 | in the creation of the R5N DHT, CADET, ATS and the GNU Name System. |
84 | In 2010, GNUnet was selected as the basis for the SecuShare online | 106 | In 2010, GNUnet was selected as the basis for the |
85 | social network, resutling in a significant growth of the core team. | 107 | @uref{https://secushare.org, secushare} online |
86 | In 2013, we launched GNU Taler to address the challenge of convenient | 108 | social network, resulting in a significant growth of the core team. |
87 | and privacy-preserving online payments. In 2015, the pEp project | 109 | In 2013, we launched @uref{https://taler.net, GNU Taler} to address |
110 | the challenge of convenient | ||
111 | and privacy-preserving online payments. In 2015, the | ||
112 | @c TODO: Maybe even markup for the E if it renders in most outputs. | ||
113 | @uref{https://pep.foundation/, pEp}@footnote{pretty easy privacy} project | ||
88 | announced that they will use GNUnet as the technology for their | 114 | announced that they will use GNUnet as the technology for their |
89 | meta-data protection layer, ultimately resulting in GNUnet e.V. | 115 | meta-data protection layer, ultimately resulting in GNUnet e.V. |
90 | entering into a formal long-term collaboration with the pEp | 116 | entering into a formal long-term collaboration with the pEp |
@@ -99,9 +125,9 @@ computing has been the core driver of the GNU project. With GNUnet we | |||
99 | are focusing on informational self-determination for collaborative | 125 | are focusing on informational self-determination for collaborative |
100 | computing and communication over networks. | 126 | computing and communication over networks. |
101 | 127 | ||
102 | The Internet is shaped as much by code and protocols as by its | 128 | The Internet is shaped as much by code and protocols as it is by its |
103 | associated political processes (IETF, ICANN, IEEE, etc.), and its | 129 | associated political processes (IETF, ICANN, IEEE, etc.). |
104 | flaws are similarly not limited to the protocol design. Thus, | 130 | Similarly its flaws are not limited to the protocol design. Thus, |
105 | technical excellence by itself will not suffice to create a better | 131 | technical excellence by itself will not suffice to create a better |
106 | network. We also need to build a community that is wise, humble and | 132 | network. We also need to build a community that is wise, humble and |
107 | has a sense of humor to achieve our goal to create a technical | 133 | has a sense of humor to achieve our goal to create a technical |
@@ -116,23 +142,22 @@ follows the governance model of a benevolent dictator. This means | |||
116 | that ultimately, the GNU project appoints the GNU maintainer and can | 142 | that ultimately, the GNU project appoints the GNU maintainer and can |
117 | overrule decisions made by the GNUnet maintainer. Similarly, the | 143 | overrule decisions made by the GNUnet maintainer. Similarly, the |
118 | GNUnet maintainer can overrule any decisions made by individual | 144 | GNUnet maintainer can overrule any decisions made by individual |
145 | @c TODO: Should we mention if this is just about GNUnet? Other projects | ||
146 | @c TODO: in GNU seem to have rare issues (GCC, the 2018 documentation | ||
147 | @c TODO: discussion. | ||
119 | developers. Still, in practice neither has happened in the last 20 | 148 | developers. Still, in practice neither has happened in the last 20 |
120 | years, and we hope to keep it that way. | 149 | years, and we hope to keep it that way. |
121 | 150 | ||
151 | @c TODO: Actually we are a Swiss association, or just a German association | ||
152 | @c TODO: with Swiss bylaws/Satzung? | ||
153 | @c TODO: Rewrite one of the 'GNUnet eV may also' sentences. | ||
122 | The GNUnet project is supported by GNUnet e.V., a German association | 154 | The GNUnet project is supported by GNUnet e.V., a German association |
123 | where any developer can become a member. GNUnet e.V. servers as a | 155 | where any developer can become a member. GNUnet e.V. serves as a |
124 | legal entity to hold the copyrights to GNUnet. GNUnet e.V. may also | 156 | legal entity to hold the copyrights to GNUnet. GNUnet e.V. may also |
125 | choose to pay for project resources, and can collect donations. | 157 | choose to pay for project resources, and can collect donations. |
126 | GNUnet e.V. may also choose to adjust the license of the | 158 | GNUnet e.V. may also choose to adjust the license of the |
127 | software (with the constraint that it has to remain free software). | 159 | software (with the constraint that it has to remain free software)@footnote{For example in 2018 we switched from GPL3 to AGPL3. In practice these changes do not happen very often.} |
128 | |||
129 | |||
130 | @node General Terminology | ||
131 | @section General Terminology | ||
132 | 160 | ||
133 | In the following manual we may use words that can not be found in the | ||
134 | Appendix. Since we want to keep the manual selfcontained, we will | ||
135 | explain words here. | ||
136 | 161 | ||
137 | @node Typography | 162 | @node Typography |
138 | @section Typography | 163 | @section Typography |
@@ -142,3 +167,5 @@ command should/can be issued as root, or if "normal" user privileges are | |||
142 | sufficient. We use a @code{#} for root's shell prompt, a | 167 | sufficient. We use a @code{#} for root's shell prompt, a |
143 | @code{%} for users' shell prompt, assuming they use the C-shell or tcsh | 168 | @code{%} for users' shell prompt, assuming they use the C-shell or tcsh |
144 | and a @code{$} for bourne shell and derivatives. | 169 | and a @code{$} for bourne shell and derivatives. |
170 | @c TODO: Really? Why the different prompts? Do we already have c-shell | ||
171 | @c TODO: examples? | ||