Re: [tor-talk] How does Tor REALLY work?

[casey dunham <casey.dunham@xxxxxxxxx>]

It seems that the tor Doxygen isn't published anywhere? From this
http://www.bitchx.com/log/tor-o/tor-o-25-May-2010/tor-o-25-May-2010-00.php

it looks like it hasn't been kept up to date. Maybe that would be a
good first step? Getting the doxygen up to date and in  a publicly
accessible place?

On Tue, Mar 8, 2011 at 3:27 PM, casey dunham <casey.dunham@xxxxxxxxx> wrote:
> Right, so the methodology used in keeping the code doc updated is important.
>
> Also, it wouldn't have to be a tome to start with. I think it would be
> handy just to describe some of the high level functionality like you
> just did earlier. So when someone wants to get started with looking at
> the code they can at least get a high level overview of where things
> live and how they interact.
>
> Keeping in mind that nothing is ever going to replace just rolling up
> your sleeves and diving in, but at least you wouldn't have to dive in
> blindfolded. In my experience every code base has a lot of code that
> while important, most people don't really need to look at or touch to
> be productive.
>
> On Tue, Mar 8, 2011 at 1:52 PM, Nick Mathewson <nickm@xxxxxxxxxxxxx> wrote:
>> On Tue, Mar 8, 2011 at 8:27 AM, casey dunham <casey.dunham@xxxxxxxxx> wrote:
>>> I've got a bunch of notes from perusing the source code trying to understand it.
>>>
>>> It sounds like it would be a great project for someone that is just
>>> getting into Tor and already knows C (I hope I didn't just volunteer
>>> myself for the project...)
>>>
>>> My question would be, how likely is it that the architecture that you
>>> just described would be changing anytime soon?
>>
>> No guarantees, I'm afraid, but fortunately (?) the rate of change is
>> limited to how fast people can code.  Anybody who's interested in
>> trying to do something like this would either need to resign
>> themselves to an ongoing process of keeping their work up to date, or
>> resign themselves to having it become out-of-date as development moves
>> on.
>> _______________________________________________
>> tor-talk mailing list
>> tor-talk@xxxxxxxxxxxxxxxxxxxx
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
>>
>
_______________________________________________
tor-talk mailing list
tor-talk@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk