aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/documentation/chapters/preface.texi40
1 files changed, 28 insertions, 12 deletions
diff --git a/doc/documentation/chapters/preface.texi b/doc/documentation/chapters/preface.texi
index 00e6290f0..3bc38941d 100644
--- a/doc/documentation/chapters/preface.texi
+++ b/doc/documentation/chapters/preface.texi
@@ -66,25 +66,33 @@ immediately. A few months after the first release we contacted the
66GNU project, happily agreed to their governance model and became an 66GNU project, happily agreed to their governance model and became an
67official GNU package. 67official GNU package.
68 68
69Within the first year, we created GNU libextractor, a helper library 69Within the first year, we created
70@uref{https://gnu.org/s/libextractor, GNU libextractor}, a helper library
70for meta data extraction which has been used by a few other projects 71for meta data extraction which has been used by a few other projects
71as well. 2003 saw the emergence of pluggable transports, the ability 72as well. 2003 saw the emergence of pluggable transports, the ability
72for GNUnet to use different mechanisms for communication, starting 73for GNUnet to use different mechanisms for communication, starting
73with TCP, UDP and SMTP (support for the latter was later dropped due 74with TCP, UDP and SMTP (support for the latter was later dropped due
74to a lack of maintenance). In 2005, the project first started to 75to a lack of maintenance). In 2005, the project first started to
75evolve beyond the original file-sharing application with a first 76evolve beyond the original file-sharing application with a first
76simple P2P chat. In 2007, we created GNU libmicrohttpd 77simple P2P chat. In 2007, we created
78@uref{https://gnu.org/s/libmicrohttpd, GNU libmicrohttpd}
77to support a pluggable transport based on HTTP. In 2009, the 79to support a pluggable transport based on HTTP. In 2009, the
78architecture was radically modularized into the multi-process system 80architecture was radically modularized into the multi-process system
79that exists today. Coincidentally, the first version of the ARM 81that exists today. Coincidentally, the first version of the ARM@footnote{ARM: Automatic Restart Manager}
80service was implemented a day before systemd was announced. From 2009 82service was implemented a day before systemd was announced. From 2009
81to 2014 work progressed rapidly thanks to a significant research grant 83to 2014 work progressed rapidly thanks to a significant research grant
82from the Deutsche Forschungsgesellschaft. This resulted in particular 84from the Deutsche Forschungsgesellschaft. This resulted in particular
83in the creation of the R5N DHT, CADET, ATS and the GNU Name System. 85in the creation of the R5N DHT, CADET, ATS and the GNU Name System.
84In 2010, GNUnet was selected as the basis for the SecuShare online 86@c So is it secushare or SecuShare?
85social network, resutling in a significant growth of the core team. 87In 2010, GNUnet was selected as the basis for the
86In 2013, we launched GNU Taler to address the challenge of convenient 88@uref{https://secushare.org, SecuShare} online
87and privacy-preserving online payments. In 2015, the pEp project 89social network, resulting in a significant growth of the core team.
90In 2013, we launched @uref{https://taler.net, GNU Taler} to address
91the challenge of convenient
92and privacy-preserving online payments. In 2015, the
93@c TODO: URL for pEp. Maybe even markup for the E if it renders in
94@c TODO: most outputs.
95@uref{https://pep.org, pEp}@footnote{pretty easy privacy} project
88announced that they will use GNUnet as the technology for their 96announced that they will use GNUnet as the technology for their
89meta-data protection layer, ultimately resulting in GNUnet e.V. 97meta-data protection layer, ultimately resulting in GNUnet e.V.
90entering into a formal long-term collaboration with the pEp 98entering into a formal long-term collaboration with the pEp
@@ -99,9 +107,9 @@ computing has been the core driver of the GNU project. With GNUnet we
99are focusing on informational self-determination for collaborative 107are focusing on informational self-determination for collaborative
100computing and communication over networks. 108computing and communication over networks.
101 109
102The Internet is shaped as much by code and protocols as by its 110The Internet is shaped as much by code and protocols as it is by its
103associated political processes (IETF, ICANN, IEEE, etc.), and its 111associated political processes (IETF, ICANN, IEEE, etc.).
104flaws are similarly not limited to the protocol design. Thus, 112Similarly its flaws are not limited to the protocol design. Thus,
105technical excellence by itself will not suffice to create a better 113technical excellence by itself will not suffice to create a better
106network. We also need to build a community that is wise, humble and 114network. We also need to build a community that is wise, humble and
107has a sense of humor to achieve our goal to create a technical 115has a sense of humor to achieve our goal to create a technical
@@ -116,15 +124,21 @@ follows the governance model of a benevolent dictator. This means
116that ultimately, the GNU project appoints the GNU maintainer and can 124that ultimately, the GNU project appoints the GNU maintainer and can
117overrule decisions made by the GNUnet maintainer. Similarly, the 125overrule decisions made by the GNUnet maintainer. Similarly, the
118GNUnet maintainer can overrule any decisions made by individual 126GNUnet maintainer can overrule any decisions made by individual
127@c TODO: Should we mention if this is just about GNUnet? Other projects
128@c TODO: in GNU seem to have rare issues (GCC, the 2018 documentation
129@c TODO: discussion.
119developers. Still, in practice neither has happened in the last 20 130developers. Still, in practice neither has happened in the last 20
120years, and we hope to keep it that way. 131years, and we hope to keep it that way.
121 132
133@c TODO: Actually we are a Swiss association, or just a German association
134@c TODO: with Swiss bylaws/Satzung?
135@c TODO: Rewrite one of the 'GNUnet eV may also' sentences.
122The GNUnet project is supported by GNUnet e.V., a German association 136The GNUnet project is supported by GNUnet e.V., a German association
123where any developer can become a member. GNUnet e.V. servers as a 137where any developer can become a member. GNUnet e.V. serves as a
124legal entity to hold the copyrights to GNUnet. GNUnet e.V. may also 138legal entity to hold the copyrights to GNUnet. GNUnet e.V. may also
125choose to pay for project resources, and can collect donations. 139choose to pay for project resources, and can collect donations.
126GNUnet e.V. may also choose to adjust the license of the 140GNUnet e.V. may also choose to adjust the license of the
127software (with the constraint that it has to remain free software). 141software (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 142
129 143
130@node General Terminology 144@node General Terminology
@@ -142,3 +156,5 @@ command should/can be issued as root, or if "normal" user privileges are
142sufficient. We use a @code{#} for root's shell prompt, a 156sufficient. We use a @code{#} for root's shell prompt, a
143@code{%} for users' shell prompt, assuming they use the C-shell or tcsh 157@code{%} for users' shell prompt, assuming they use the C-shell or tcsh
144and a @code{$} for bourne shell and derivatives. 158and a @code{$} for bourne shell and derivatives.
159@c TODO: Really? Why the different prompts? Do we already have c-shell
160@c TODO: examples?