... | ... | @@ -29,19 +29,14 @@ schedule for which channel; it varies by day.) |
|
|
|
|
|
(~~strikethrough~~ means that most people in that timezone are asleep.)
|
|
|
|
|
|
|
|
|
The **boldfaced** time for a meeting is canonical in its time zone; the other
|
|
|
times are computed and might not be correct for a given location depending on
|
|
|
factors like daylight saving time. The primary meeting will track US daylight
|
|
|
saving time. The canonical Patch Party time is in UTC and will not change with
|
|
|
daylight saving time. The optional catch-up will track European daylight saving
|
|
|
time.
|
|
|
saving time.
|
|
|
|
|
|
If you want to participate, try to show up to the team meeting or patch party.
|
|
|
Either one should be fine, though the primary meeting will be more attended.
|
|
|
(If you need to meet during the optional catch-up, please let people know a few
|
|
|
days in advance.) The meeting times are roughly 8 hours apart in the hopes that
|
|
|
one will be convenient for each pair of time zones.
|
|
|
Or just stop by the `#tor-dev` IRC channel and see who is around!
|
|
|
|
|
|
Also note that these meeting times are not permanent. We sometimes need to
|
|
|
reconfigure them from time to time as developers join, as people's schedules
|
... | ... | @@ -57,31 +52,25 @@ For other type of meetings, see: |
|
|
Besides meeting every week on IRC for status update and team discussions, our
|
|
|
team also uses the following mechanisms to organize our work:
|
|
|
|
|
|
* [Team rotations](./NetworkTeam/TeamRotations): Our rotation calendar - we rotate some 'duties' like bug triage, here you will find all rotation schedule and more information on the work that has to be done.
|
|
|
* [Core Tor Releases](./NetworkTeam/CoreTorReleases): Here is more information about **tor** release schedules, guidelines for release planning and ideas of how we can improve this process.
|
|
|
|
|
|
* [Core Tor Releases](./NetworkTeam/CoreTorReleases): Here is more information about **tor** release schedules, guidelines for release planning, and ideas of how we can improve this process.
|
|
|
* [Filing a ticket](./NetworkTeam/FilingTicketNetworkTeam) for **Core Tor**.
|
|
|
* [Useful ticket queries](./NetworkTeam/UsefulTicketsQueries).
|
|
|
* [Ticket Triage](./NetworkTeam/TicketTriage).
|
|
|
|
|
|
New features starts with
|
|
|
[proposals](https://gitweb.torproject.org/torspec.git/tree/proposals/001-process.txt) - normally we discuss them on [tor-dev@ mailing
|
|
|
[proposals](https://gitweb.torproject.org/torspec.git/tree/proposals/001-process.txt)—normally we discuss them on [tor-dev@ mailing
|
|
|
list](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev) and try to
|
|
|
finalize the discussions on [IRC meetings](./NetworkTeam/MeetingSchedule).
|
|
|
|
|
|
### How to find us
|
|
|
|
|
|
We have what we call 'patch parties' meetings, they are for any volunteer to
|
|
|
come with patches they want to discuss or need review for. [Check out the
|
|
|
meetings information above for more
|
|
|
details](#MeetingsSchedule).
|
|
|
|
|
|
If you want to reach someone from the team between these meetings to ask a
|
|
|
development-related question, just go to **#tor-dev** IRC channel, and somebody
|
|
|
from the team might either be around or appear later and get back to you.
|
|
|
|
|
|
Our asynchronous medium of communication is the [tor-dev@ mailing
|
|
|
list](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev). This list
|
|
|
is public in the sense that anyone can subscribe, send emails and read
|
|
|
is public, in the sense that anyone can subscribe, send emails and read
|
|
|
archives. Feel free to subscribe and just listen if you want, and feel free to
|
|
|
post if you have a question that you think is on topic.
|
|
|
|
... | ... | @@ -98,11 +87,7 @@ how our team work. |
|
|
|
|
|
### Tips on finding a patch to work on
|
|
|
|
|
|
[We have people on rotation triaging bugs every week](./NetworkTeam/TeamRotations), you could look for one of them online and ask for suggestions of what to work on.
|
|
|
|
|
|
Or you can dig it yourself! You are welcome to just create new tickets on
|
|
|
https://gitlab.torproject.org if there is something in particular that you want
|
|
|
to help with or a bug you found and has a patch for.
|
|
|
Have a look at the ~"First Contribution" label on gitlab; it has things that we thought, at some point, would be a good place to begin.
|
|
|
|
|
|
### Tips on finding your way around our code
|
|
|
|
... | ... | @@ -122,34 +107,15 @@ has helpful information about what you need to know to hack on Tor! |
|
|
* If it's your job to put out Tor releases, see [ReleasingTor.md](https://gitweb.torproject.org/tor.git/tree/doc/HACKING/ReleasingTor.md) so that you don't miss any steps!
|
|
|
* A very important part of our development is code review, if you would like to collaborate with this part or want to sharp your skills in this front, check [HowToReview.md](https://gitweb.torproject.org/tor.git/tree/doc/HACKING/HowToReview.md).
|
|
|
|
|
|
#### tor-guts:
|
|
|
|
|
|
The core Tor development team created
|
|
|
[tor-guts](https://gitweb.torproject.org/user/nickm/torguts.git/tree/), a
|
|
|
compilation of chapters that aims to explain the general structure of the Tor
|
|
|
codebase, how it fits together, what functionality is available for extending
|
|
|
Tor, and gives some notes on how Tor got that way.
|
|
|
|
|
|
Some of the things we cover with this documentation:
|
|
|
|
|
|
* [Chapter 01e-os-compat.md](https://gitweb.torproject.org/user/nickm/torguts.git/tree/01e-os-compat.md) covers networking and filesystems functions that helps us wrap differences between various operating systems we support.
|
|
|
* [Chapter 01d-crypto.md](https://gitweb.torproject.org/user/nickm/torguts.git/tree/01d-crypto.md) is dedicated to Lower-level cryptography functionality in Tor, in general Tor code shouldn't be calling crypto library directly (e.g. OpenSSL), this documentation helps developers understand the functions available in src/common/crypto\*.c or src/common/tortls.c that they can use these libraries indirectly.
|
|
|
* [Chapter 01c-time.md](https://gitweb.torproject.org/user/nickm/torguts.git/tree/01c-time.md) cover Tor’s time-related functions, they exist to help developers parse time, or access cached time for when you have to do thousands of call and don’t want to overload the system, or information on how to schedule things.
|
|
|
* [Chapter 01g-strings.md](https://gitweb.torproject.org/user/nickm/torguts.git/tree/01g-strings.md) it's full of functions for manipulating the C string abstraction. It contains some often-missed highlights that will be helpful for developers who learning the ‘tor way’ of doing things in order to collaborate with our code base.
|
|
|
* [Chapter 01b-collections.md](https://gitweb.torproject.org/user/nickm/torguts.git/tree/01b-collections.md) talks about the different collections we have available and how these resources are useful when writing code for Tor.
|
|
|
* [Chapter 01a-memory.md](https://gitweb.torproject.org/user/nickm/torguts.git/tree/01a-memory.md) describes Tor’s functions for memory management. We advise developers to never use 'malloc', 'calloc', 'realloc, or 'free' on their own; always use the variants prefixed with 'tor_'. We also explain Tor’s convention for when the developer is writing their own functions, and some other choices we have made to help collaborators understand them.
|
|
|
#### Doxygen
|
|
|
|
|
|
#### Modules and functions:
|
|
|
|
|
|
We use doxygen to generate documentation in html out of our comments on the
|
|
|
code. With that we have documentation for all the modules in Tor, their data
|
|
|
flows, their intended interactions, and their actual behaviors. As well as
|
|
|
nearly all the functions.
|
|
|
code. We keep an up-to-date version of the generated documentation
|
|
|
online at [https://src-ref.docs.torproject.org](https://src-ref.docs.torproject.org/tor/index.html).
|
|
|
|
|
|
You will find this documentation in two places:
|
|
|
This documentation should cover the overall code structure, data structures, and individual functions. It's a work in progress, but we hope it'll be useful to you.
|
|
|
|
|
|
1. In the source code, at the start of each C file.
|
|
|
1. When you click on individual C files under https://people.torproject.org/~nickm/tor-auto/doxygen/files.html (scroll down to "detailed description").
|
|
|
|
|
|
## More on Network Team
|
|
|
|
... | ... | |