public-inbox 1.1.0-pre1

[public-inbox.git] / HACKING

diff --git a/HACKING b/HACKING
index a766820957f89748ebd4522efdd9c55a6a94eaff..3435775c632b5159617452816bc0ccd757465907 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:
 


@@ -30,12 +36,19 @@ In general, we favor mature and well-tested old things rather than
 the shiny new.
 
 Avoid relying on compiled modules too much.  Even if it is Free,
 the shiny new.
 
 Avoid relying on compiled modules too much.  Even if it is Free,

-compiled code makes packages more expensive to audit, build, and
+compiled code makes packages more expensive to audit, build,

 distribute and verify.  public-inbox itself will only be implemented
 in scripting languages (currently Perl 5).
 
 Performance should be reasonably good for server administrators, too,
 and we will sacrifice features to achieve predictable performance.
 distribute and verify.  public-inbox itself will only be implemented
 in scripting languages (currently Perl 5).
 
 Performance should be reasonably good for server administrators, too,
 and we will sacrifice features to achieve predictable performance.

+Encouraging folks to self-host will be easier with lower hardware
+requirements.
+
+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.