|Nick Mathewson 80ad374b84 Remove old callgraph scripts; recommend calltool instead.||6 years ago|
|CodingStandards.md||6 years ago|
|Fuzzing.md||6 years ago|
|GettingStarted.md||7 years ago|
|HelpfulTools.md||6 years ago|
|HowToReview.md||7 years ago|
|README.1st.md||7 years ago|
|ReleasingTor.md||6 years ago|
|Tracing.md||6 years ago|
|WritingTests.md||6 years ago|
This directory has helpful information about what you need to know to hack on Tor!
GettingStarted.md to learn how to get a start in Tor
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
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
If it's your job to put out Tor releases, see
that you don't miss any steps!
For full information on how Tor is supposed to work, look at the files in
For an explanation of how to change Tor's design to work differently, look at
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
The other files in this
HACKING directory may also be useful as you
get started working with Tor.
XXXXX also describe
The design paper
XXXX describe these and add links.