aboutsummaryrefslogtreecommitdiff
path: root/content/about
diff options
context:
space:
mode:
Diffstat (limited to 'content/about')
-rw-r--r--content/about/_index.md6
-rw-r--r--content/about/about.md42
-rw-r--r--content/about/contribute.md80
3 files changed, 0 insertions, 128 deletions
diff --git a/content/about/_index.md b/content/about/_index.md
deleted file mode 100644
index 1489631..0000000
--- a/content/about/_index.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: About
-date: 2019-06-22
-type: page
-draft: false
----
diff --git a/content/about/about.md b/content/about/about.md
deleted file mode 100644
index 5a97f85..0000000
--- a/content/about/about.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: "About"
-draft: false
-date: 2019-08-02
----
-
-The Ouroboros project is a decentralized packet network implementation
-started by Sander Vrijders and Dimitri Staessens. It stems from our
-deep interest in computer networks, trying to solve some long standing
-problems in IP networks such as achieving clean fragmentation, routing
-scalability, efficient congestion control and simple
-multicast. Instead of trying to tackle these issues in isolation, we
-subscribe to the view that the entire TCP/IP design is *fundamentally*
-broken, and a holistic approach is needed to build efficient packet
-networks.
-
-In addition, a lot of the design is inspired by Edward Snowdens
-revelations and his call to [drastically improve end-user security and
-privacy](https://www.theatlantic.com/politics/archive/2014/05/edward-snowdens-other-motive-for-leaking/370068/)
-on the internet.
-
-### Licenses
-
-Ouroboros is [free
-software](https://www.gnu.org/philosophy/free-sw.html). The libraries
-are available under the [GNU Lesser Public License (LGPL) version
-2.1](https://www.gnu.org/licenses/old-licenses/lgpl-2.1.html). The
-daemons are available under the [GNU Public License (GPL) version
-2](https://www.gnu.org/licenses/old-licenses/gpl-2.0.html). The tools
-are availabe under the [3-Clause BSD
-License](https://opensource.org/licenses/BSD-3-Clause).
-
-Ouroboros logos © Dimitri Staessens. All Rights Reserved.
-
-### Disclaimer
-
-Ouroboros is distributed in the hope that it will be useful, but without
-any warranty; without even the implied warranty of merchantability or
-fitness for a particular purpose.
-
-At present, Ouroboros should be considered an advanced research
-prototype.
diff --git a/content/about/contribute.md b/content/about/contribute.md
deleted file mode 100644
index 5dbe7ad..0000000
--- a/content/about/contribute.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: Contact
-date: 2019-06-22
-draft: false
----
-
-General discussion and support
-------------------------------
-
-For general discussion of Ouroboros,
-[subscribe](https://www.freelists.org/list/ouroboros) to our mailing
-list: [ouroboros@freelists.org](mailto:ouroboros@freelists.org).
-
-For day-to-day discussions, join our IRC chat:
-[\#ouroboros](irc://irc.freenode.net/ouroboros).
-
-Contact us on twitter: @ODecentralize
-
-Contributing code
------------------
-
-Contributions should be sent as patches to the mailing list, using your
-real name and real e-mail address.
-
-The git repository contains three branches:
-
-- master: Contains the most stable version of Ouroboros.
-- testing: Contains tested code but may still contain bugs.
-- be: Contains untested but compiling code.
-
-New development is done against the 'be' branch of the git repository.
-The testing and master branches take only bugfixes.
-
-Bug reporting
--------------
-
-Please report all bugs [here](/bugzilla). When reporting a bug, please
-do the following:
-
-1. Provide a description of the bug. How did you get it and which
- version of Ouroboros were you using? Which Operating System are you
- on?
-2. Provide as much technical information as possible (system logs,
- debug traces, \...).
-3. If possible, provide a minimal code example to reproduce the bug.
-4. If you can provide a bugfix, provide it against the HEAD of the most
- stable branch where the bug is present and send the patch to the
- mailing list.
-
-Todo list
----------
-
-We are currently looking for
-
-- Testing and bugfixing.
-- Integration testing for the build system beyond the "make check"
- unit tests.
-- People that are interested in setting up some nodes to establish a
- global testing layer.
-- Non-blocking flow allocation: Allow specifying a {0, 0} timespec to
- return immediately and use fevent() to know when the flow is ready
- (or allocation failed).
-- Asynchronous IPC over the UNIX sockets. For each command to the
- IRMd, we create a UNIX socket, send the request and wait for the
- response. This could be changed so that there is only a single UNIX
- socket that is used for all messaging. This would simplify parallel
- querying of the IPCPs and speed up flow allocation. The far-future
- option is to ditch UNIX sockets and bootstrap Ouroboros local IPC
- over itself.
-- ECDH-AES encryption using libssl and/or libgcrypt. The goal is to
- support both libraries so that we have a fallback should major bugs
- be discovered in one of them.
-- Customized packet serialization to remove the dependency on Google
- Protocol Buffers. We like GPB, but it's not perfect. Importing
- .proto files may give rise to multiple definitions and we found no
- way to solve that.
-- Caching for the DHT.
-- Cross-compilation to OpenWRT (musl).
-- Ported applications! If you want to add native Ouroboros support for
- your applications, just let us know and we will help you out!