diff options
-rw-r--r-- | doc/documentation/chapters/preface.texi | 40 |
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 | |||
66 | GNU project, happily agreed to their governance model and became an | 66 | GNU project, happily agreed to their governance model and became an |
67 | official GNU package. | 67 | official GNU package. |
68 | 68 | ||
69 | Within the first year, we created GNU libextractor, a helper library | 69 | Within the first year, we created |
70 | @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 | 71 | 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 | 72 | as well. 2003 saw the emergence of pluggable transports, the ability |
72 | for GNUnet to use different mechanisms for communication, starting | 73 | for GNUnet to use different mechanisms for communication, starting |
73 | with TCP, UDP and SMTP (support for the latter was later dropped due | 74 | 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 | 75 | to a lack of maintenance). In 2005, the project first started to |
75 | evolve beyond the original file-sharing application with a first | 76 | evolve beyond the original file-sharing application with a first |
76 | simple P2P chat. In 2007, we created GNU libmicrohttpd | 77 | simple P2P chat. In 2007, we created |
78 | @uref{https://gnu.org/s/libmicrohttpd, GNU libmicrohttpd} | ||
77 | to support a pluggable transport based on HTTP. In 2009, the | 79 | to support a pluggable transport based on HTTP. In 2009, the |
78 | architecture was radically modularized into the multi-process system | 80 | architecture was radically modularized into the multi-process system |
79 | that exists today. Coincidentally, the first version of the ARM | 81 | 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 | 82 | service was implemented a day before systemd was announced. From 2009 |
81 | to 2014 work progressed rapidly thanks to a significant research grant | 83 | to 2014 work progressed rapidly thanks to a significant research grant |
82 | from the Deutsche Forschungsgesellschaft. This resulted in particular | 84 | from the Deutsche Forschungsgesellschaft. This resulted in particular |
83 | in the creation of the R5N DHT, CADET, ATS and the GNU Name System. | 85 | 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 | 86 | @c So is it secushare or SecuShare? |
85 | social network, resutling in a significant growth of the core team. | 87 | In 2010, GNUnet was selected as the basis for the |
86 | In 2013, we launched GNU Taler to address the challenge of convenient | 88 | @uref{https://secushare.org, SecuShare} online |
87 | and privacy-preserving online payments. In 2015, the pEp project | 89 | social network, resulting in a significant growth of the core team. |
90 | In 2013, we launched @uref{https://taler.net, GNU Taler} to address | ||
91 | the challenge of convenient | ||
92 | and 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 | ||
88 | announced that they will use GNUnet as the technology for their | 96 | announced that they will use GNUnet as the technology for their |
89 | meta-data protection layer, ultimately resulting in GNUnet e.V. | 97 | meta-data protection layer, ultimately resulting in GNUnet e.V. |
90 | entering into a formal long-term collaboration with the pEp | 98 | entering 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 | |||
99 | are focusing on informational self-determination for collaborative | 107 | are focusing on informational self-determination for collaborative |
100 | computing and communication over networks. | 108 | computing and communication over networks. |
101 | 109 | ||
102 | The Internet is shaped as much by code and protocols as by its | 110 | 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 | 111 | associated political processes (IETF, ICANN, IEEE, etc.). |
104 | flaws are similarly not limited to the protocol design. Thus, | 112 | Similarly its flaws are not limited to the protocol design. Thus, |
105 | technical excellence by itself will not suffice to create a better | 113 | 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 | 114 | 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 | 115 | has 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 | |||
116 | that ultimately, the GNU project appoints the GNU maintainer and can | 124 | that ultimately, the GNU project appoints the GNU maintainer and can |
117 | overrule decisions made by the GNUnet maintainer. Similarly, the | 125 | overrule decisions made by the GNUnet maintainer. Similarly, the |
118 | GNUnet maintainer can overrule any decisions made by individual | 126 | GNUnet 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. | ||
119 | developers. Still, in practice neither has happened in the last 20 | 130 | developers. Still, in practice neither has happened in the last 20 |
120 | years, and we hope to keep it that way. | 131 | years, 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. | ||
122 | The GNUnet project is supported by GNUnet e.V., a German association | 136 | 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 | 137 | 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 | 138 | legal entity to hold the copyrights to GNUnet. GNUnet e.V. may also |
125 | choose to pay for project resources, and can collect donations. | 139 | choose to pay for project resources, and can collect donations. |
126 | GNUnet e.V. may also choose to adjust the license of the | 140 | GNUnet e.V. may also choose to adjust the license of the |
127 | software (with the constraint that it has to remain free software). | 141 | 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 | 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 | |||
142 | sufficient. We use a @code{#} for root's shell prompt, a | 156 | 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 | 157 | @code{%} for users' shell prompt, assuming they use the C-shell or tcsh |
144 | and a @code{$} for bourne shell and derivatives. | 158 | and 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? | ||