#31852: Rename doc/HACKING/design members to reflect current architectural
division
-------------------------------------------------+-------------------------
Reporter: nickm | Owner: nickm
Type: defect | Status:
| assigned
Priority: Medium | Milestone: Tor:
| 0.4.3.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: network-team-roadmap-november, | Actual Points:
s31-docs |
Parent ID: #29214 | Points:
Reviewer: teor | Sponsor:
-------------------------------------------------+-------------------------
Comment (by teor):
I'd like a discussion of data flow and event flow.
And something about how we test (if that belongs here).
What's remaining after that?
Eventually, I'd like an explanation of config and control and how they are
split between modules. (But that might be our target design.)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/31852#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
