HACKING: minor updates and add to the website

Also, at least add one of the Tor mirrors (the rest will
be discoverable through the mirrors themselves).

diff --git a/Documentation/include.mk b/Documentation/include.mk
index 94278870a34ea9d4c3d7a9be7fd81178461eca86..396a2585527188777417d08d8324dd9e0d7f3fdc 100644 (file)
--- a/Documentation/include.mk
+++ b/Documentation/include.mk
@@ -4,7 +4,8 @@ all::
 
 RSYNC = rsync
 RSYNC_DEST = public-inbox.org:/srv/public-inbox/
 
 RSYNC = rsync
 RSYNC_DEST = public-inbox.org:/srv/public-inbox/

-docs := README COPYING INSTALL TODO $(shell git ls-files 'Documentation/*.txt')
+docs := README COPYING INSTALL TODO HACKING
+docs += $(shell git ls-files 'Documentation/*.txt')

 INSTALL = install
 POD2MAN ?= pod2man
 POD2MAN_OPTS = -v --stderr -d 1994-10-02 -c 'public-inbox user manual'
 INSTALL = install
 POD2MAN ?= pod2man
 POD2MAN_OPTS = -v --stderr -d 1994-10-02 -c 'public-inbox user manual'

diff --git a/HACKING b/HACKING
index a766820957f89748ebd4522efdd9c55a6a94eaff..3c2235a4f2ad3bf023b05839331e1abfff9ff705 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -1,8 +1,14 @@
 hacking public-inbox
 --------------------
 
 hacking public-inbox
 --------------------
 

-Send all patches via to our self-hosting inbox at meta@public-inbox.org
-It is archived at <http://public-inbox.org/meta/>.
+Send all patches and "git request-pull"-formatted emails to our
+self-hosting inbox at meta@public-inbox.org
+It is archived at: https://public-inbox.org/meta/
+and http://hjrcffqmbrq6wope.onion/meta/ (using Tor)
+
+Contributions are email-driven, just like contributing to git
+itself or the Linux kernel; however anonymous and pseudonymous
+contributions will always be welcome.

 
 Please consider our goals in mind:
 
 
 Please consider our goals in mind:
 


@@ -37,5 +43,10 @@ in scripting languages (currently Perl 5).
 Performance should be reasonably good for server administrators, too,
 and we will sacrifice features to achieve predictable performance.
 
 Performance should be reasonably good for server administrators, too,
 and we will sacrifice features to achieve predictable performance.
 

-See design_www.txt and design_notes.txt in the Documentation/ directory
-for design decisions made during development.
+See design_www.txt and design_notes.txt in the Documentation/
+directory for design decisions made during development.
+
+For now, one may optionally subscribe to the mailing list by
+sending an email to: meta+subscribe@public-inbox.org
+(and confirming).  However, reading over the mailing list is
+the least reliable method of reading a public-inbox.

diff --git a/README b/README
index f56d68d2307d284e5b17e5c4db59d3a2838d1767..7618727a93ea67ea2f202ef4347c14cb756223bf 100644 (file)
--- a/README
+++ b/README
@@ -111,6 +111,11 @@ The archives are readable via NNTP or HTTP:
        nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta
        https://public-inbox.org/meta/
 
        nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta
        https://public-inbox.org/meta/
 

+And as Tor hidden services:
+
+       http://hjrcffqmbrq6wope.onion/meta/
+       nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta
+

 You may also clone all messages via git:
 
        git clone --mirror https://public-inbox.org/meta/
 You may also clone all messages via git:
 
        git clone --mirror https://public-inbox.org/meta/