Documentation files

Usual documentation files for every software release, including TODO.

diff --git a/ChangeLog b/ChangeLog
new file mode 100644 (file)
index 0000000..0c15c86
--- /dev/null
+++ b/ChangeLog
@@ -0,0 +1,4 @@
+2006-09-26  Thadeu Lima de Souza Cascardo  <cascardo@minaslivre.org>
+
+       * Version 0.1 is released.
+

diff --git a/INSTALL b/INSTALL
new file mode 120000 (symlink)
index 0000000..06d2001
--- /dev/null
+++ b/INSTALL
@@ -0,0 +1 @@
+/usr/share/automake-1.7/INSTALL
\ No newline at end of file

diff --git a/NEWS b/NEWS
new file mode 100644 (file)
index 0000000..29923a6
--- /dev/null
+++ b/NEWS
@@ -0,0 +1,7 @@
+NEWS for improxy
+
+* Version 0.1
+
+- This is our first pre-alpha release. There is not much use to the
+software besides verifying which hosts are connecting to which
+servers.

diff --git a/TODO b/TODO
new file mode 100644 (file)
index 0000000..930caeb
--- /dev/null
+++ b/TODO
@@ -0,0 +1,34 @@
+A list of TODO items that should be more detailed in a ROADMAP,
+perhaps.
+
+Next soon releases:
+
+* Support SRV DNS record lookups.
+* Support TLS connections.
+* Identify user identities and log that.
+* Block based on sender/destination JID.
+
+
+Later releases:
+
+* Allow online configuration of addresses to block accepting HTTP
+connections, perhaps. Jabber commands would be nice too.
+* Support other protocols.
+* Distinguish between types of data/messages and block based on them.
+* Support other criteria for blocking, like time/day of day/week.
+* Archive data transmitted and allow administrator to read it.
+
+
+Protocol messing:
+
+* Start TLS for clients that don't and even send them an invalid
+certificate if they don't check if it's a valid one (all configurable
+by administrator)
+* Intercept archive configuration and use it for the proxy archiving
+feature itself.
+
+
+Protocol updates?
+
+* Design and publish JEP to allow non-transparent proxies.
+* Design and publish JEP for proxy configuration.
\ No newline at end of file