gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNUnet-SVN] [gnunet] branch master updated: motivational changes to dis


From: gnunet
Subject: [GNUnet-SVN] [gnunet] branch master updated: motivational changes to disclaimer README.1st
Date: Thu, 04 Jan 2018 15:30:48 +0100

This is an automated email from the git hooks/post-receive script.

lynx pushed a commit to branch master
in repository gnunet.

The following commit(s) were added to refs/heads/master by this push:
     new b4f6c5a8b motivational changes to disclaimer README.1st
b4f6c5a8b is described below

commit b4f6c5a8b521d4942d19f5a34929bebaa60a6210
Author: psyc://loupsycedyglgamf.onion/~lynX 
<ircs://psyced.org/youbroketheinternet>
AuthorDate: Wed Jan 3 14:50:24 2018 +0000

    motivational changes to disclaimer README.1st
---
 README.1st                   | 27 +++++++++++++++++----------
 doc/documentation/index.html | 14 ++++++++------
 2 files changed, 25 insertions(+), 16 deletions(-)

diff --git a/README.1st b/README.1st
index d55709779..19880de63 100644
--- a/README.1st
+++ b/README.1st
@@ -1,8 +1,14 @@
-The following is a list of issues with GNUnet 0.11.0 that will need to
-be addressed before we might consider GNUnet usable.  Please keep this
-list in mind when trying out GNUnet 0.11.0!  Help would of course be
-welcome, an estimate of how much work is needed and the main impact
-are given with each item.
+WARNING!
+=======
+
+The following is a list of issues with GNUnet 0.11.0 that will need
+to be addressed before we might consider GNUnet deployable to larger
+audiences. Please keep this in mind when trying out GNUnet 0.11.0!
+
+GNUnet may however work fine for applications that aren't impeded by
+these known deficiencies. Help would of course be welcome to reduce
+this list, so an estimate of how much work is needed and the main 
+impact are given with each item.
 
 
 ats:
@@ -56,8 +62,8 @@ described above should also enable us to create more 
systematic tests.
 
 hello:
 * The current code may leak LAN IPs (in particular IPv6 with
-MAC) globally. We have started to put in some privisions to tag
-addresses as loopback/LAN/WAN, but need to systemtically ensure
+MAC) globally. We have started to put in some provisions to tag
+addresses as loopback/LAN/WAN, but need to systematically ensure
 that addresses are only propagated in a useful scope and avoid
 leaking "sensitive" address data globally.
 [3-6 PM, privacy]
@@ -122,7 +128,7 @@ correctness]
 util:
 * Event loop instantiations for various event loops (like glib,
 libev, libevent, etc.) should be created (and tested).  This
-will applications to be built with GNUnet using those various
+allows applications to be built with GNUnet using those various
 styles of event loop handling.  General support for abstracting
 the event loop is new in 0.11.0, we just need to make broader use
 of it. [1-3 PM, performance, usability]
@@ -185,9 +191,10 @@ gns:
 
 
 multicast:
-* implementation currently trivial and under-tested
+* implementation currently "trivial" (aka doing round-robin, not multicast)
+  and under-tested
 
-* still uses old NTR-style API, needs to transition to MQ API
+* still uses old NTR-style API, needs to transition to MQ API [DONE]
 
 
 psyc:
diff --git a/doc/documentation/index.html b/doc/documentation/index.html
index 0c3b04e9d..660544ced 100644
--- a/doc/documentation/index.html
+++ b/doc/documentation/index.html
@@ -1,12 +1,14 @@
 <title>GNUnet - GNUnet Manuals and Handbooks</title>
 <h2>GNUnet - GNUnet Manuals and Handbooks</h2>
 
-<address>GNUnet e.V.</address>
-<address>Fakultät für Informatik -- I8</address>
-<address>Technische Universität München</address>
-<address>Boltzmannstraße 3</address>
-<address>85748 Garching</address>
-<address>GERMANY</address>
+<blockquote><address>
+GNUnet e.V.<br/>
+Fakultät für Informatik -- I8<br/>
+Technische Universität München<br/>
+Boltzmannstraße 3<br/>
+85748 Garching<br/>
+GERMANY<br/>
+</address></blockquote>
 
 <p>The following handbooks and manuals are available:</p>
 

-- 
To stop receiving notification emails like this one, please contact
address@hidden



reply via email to

[Prev in Thread] Current Thread [Next in Thread]