sengler/tor-parallel-relay-conn @ 4bbefc2aac2d3770817200700e2a384d966bffe2

Nick Mathewson 765e4364d9 Merge remote-tracking branch 'tor-github/pr/1064' into maint-0.4.1		%!s(int64=5) %!d(string=hai) anos
..
android	ca6682f3f8 Fix spelling mistakes corresponding to ticket #23650	%!s(int64=6) %!d(string=hai) anos
CodeStructure.md	23dc770f87 Add an initial CodeStructure.md file to doc/HACKING.	%!s(int64=6) %!d(string=hai) anos
CodingStandards.md	ac5753d3ca Coding Standards: Document how to find git commits	%!s(int64=5) %!d(string=hai) anos
CodingStandardsRust.md	0ebe290198 Removed the use of expect from CodingStandardsRust	%!s(int64=5) %!d(string=hai) anos
Fuzzing.md	4d3310932a Small fixes to fuzzing documentation.	%!s(int64=7) %!d(string=hai) anos
GettingStarted.md	8d913cc352 doc: make introduction paragraph point to correct data	%!s(int64=7) %!d(string=hai) anos
GettingStartedRust.md	4847e22168 Merge branch 'maint-0.3.2' into maint-0.3.3	%!s(int64=6) %!d(string=hai) anos
HelpfulTools.md	e2512950b6 Improve failure message from check-best-practices	%!s(int64=5) %!d(string=hai) anos
HowToReview.md	cbea334d6b Mention even more about changes files in doc/HACKING	%!s(int64=7) %!d(string=hai) anos
Maintaining.md	5dcd44cbe2 fix some of the typos in Maintaining.md	%!s(int64=5) %!d(string=hai) anos
Module.md	fa2d53aa6a Stop mentioning src/or and src/common in doc/HACKING	%!s(int64=6) %!d(string=hai) anos
README.1st.md	617e0f8d26 added some markdown formatting	%!s(int64=9) %!d(string=hai) anos
ReleasingTor.md	765e4364d9 Merge remote-tracking branch 'tor-github/pr/1064' into maint-0.4.1	%!s(int64=5) %!d(string=hai) anos
Tracing.md	f720a5a439 Fix everything that previously referred to src/or	%!s(int64=6) %!d(string=hai) anos
WritingTests.md	d49133d9ca Mention that we require Python 2.7 or newer	%!s(int64=6) %!d(string=hai) anos

In this directory

This directory has helpful information about what you need to know to hack on Tor!

First, read GettingStarted.md to learn how to get a start in Tor development.

If you've decided to write a patch, CodingStandards.txt will give you a bunch of information about how we structure our code.

It's important to get code right! Reading WritingTests.md will tell you how to write and run tests in the Tor codebase.

There are a bunch of other programs we use to help maintain and develop the codebase: HelpfulTools.md can tell you how to use them with Tor.

If it's your job to put out Tor releases, see ReleasingTor.md so that you don't miss any steps!

For full information on how Tor is supposed to work, look at the files in https://gitweb.torproject.org/torspec.git/tree.

For an explanation of how to change Tor's design to work differently, look at https://gitweb.torproject.org/torspec.git/blob_plain/HEAD:/proposals/001-process.txt.

For the latest version of the code, get a copy of git, and

git clone https://git.torproject.org/git/tor

We talk about Tor on the tor-talk mailing list. Design proposals and discussion belong on the tor-dev mailing list. We hang around on irc.oftc.net, with general discussion happening on #tor and development happening on #tor-dev.

The other files in this HACKING directory may also be useful as you get started working with Tor.

Happy hacking!

XXXXX also describe

doc/HACKING/WritingTests.md

torguts.git

torspec.git

The design paper

freehaven.net/anonbib

XXXX describe these and add links.

README.1st.md

In this directory