... | ... | @@ -22,17 +22,9 @@ We use [IRC](https://www.torproject.org/about/contact.html.en#irc) for our |
|
|
meetings, we meet on the [OFTC network](https://oftc.net). (See detailed
|
|
|
schedule for which channel; it varies by day.)
|
|
|
|
|
|
| Team Meetings | UTC | CEST | EDT | PDT |
|
|
|
|---------------------------------------------|-------------------------|--------------------|--------------------|--------------------|
|
|
|
| Primary team meeting<br />(in **#tor-meeting**) | Monday 17:00 | Monday 19:00 | **Monday 13:00** | Monday 10:00 |
|
|
|
| Monthly retrospective<br/>(in **#tor-meeting**) | **Tuesday 20:00** | Tuesday 22:00 | Tuesday 16:00 | Tuesday 13:00 |
|
|
|
|
|
|
(~~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.
|
|
|
| Team Meetings | UTC |
|
|
|
|--------------------------------------------------|--------------|
|
|
|
| Primary team meeting<br />(in **#tor-meeting**) | Monday 17:00 |
|
|
|
|
|
|
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.
|
... | ... | @@ -52,10 +44,7 @@ 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:
|
|
|
|
|
|
|
|
|
* [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**.
|
|
|
* [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
|
... | ... | @@ -65,20 +54,21 @@ finalize the discussions on [IRC meetings](./NetworkTeam/MeetingSchedule). |
|
|
### How to find us
|
|
|
|
|
|
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.
|
|
|
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
|
|
|
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
|
|
|
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.
|
|
|
|
|
|
## Becoming a volunteer
|
|
|
|
|
|
Thanks for volunteering with us! This part of our wiki is a collection of
|
|
|
information we believe might be useful for you who wants to help us develop our
|
|
|
tools.
|
|
|
information we believe might be useful for you who wants to help us develop
|
|
|
our tools.
|
|
|
|
|
|
### Getting started
|
|
|
|
... | ... | @@ -87,7 +77,8 @@ how our team work. |
|
|
|
|
|
### Tips on finding a patch to work on
|
|
|
|
|
|
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.
|
|
|
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
|
|
|
|
... | ... | @@ -97,47 +88,22 @@ will help you get started with our code! |
|
|
|
|
|
#### HACKING/
|
|
|
|
|
|
[The HACKING/ folder](https://gitweb.torproject.org/tor.git/tree/doc/HACKING/README.1st.md)
|
|
|
[The HACKING/ folder](https://gitlab.torproject.org/tpo/core/tor/-/blob/main/doc/HACKING/README.1st.md)
|
|
|
has helpful information about what you need to know to hack on Tor!
|
|
|
|
|
|
* First, read [GettingStarted.md](https://gitweb.torproject.org/tor.git/tree/doc/HACKING/GettingStarted.md) to learn how to get a start in Tor development.
|
|
|
* If you've decided to write a patch, [CodingStandards.txt](https://gitweb.torproject.org/tor.git/tree/doc/HACKING/CodingStandards.md) will give you a bunch of information about how we structure our code.
|
|
|
* It's important to get code right! Reading [WritingTests.md](https://gitweb.torproject.org/tor.git/tree/doc/HACKING/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](https://gitweb.torproject.org/tor.git/tree/doc/HACKING/HelpfulTools.md) can tell you how to use them with 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).
|
|
|
|
|
|
#### Doxygen
|
|
|
|
|
|
|
|
|
We use doxygen to generate documentation in html out of our comments on the
|
|
|
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).
|
|
|
|
|
|
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.
|
|
|
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).
|
|
|
|
|
|
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.
|
|
|
|
|
|
## More on Network Team
|
|
|
|
|
|
> :hammer_and_wrench: :warning: These links may be outdated.
|
|
|
> —nickm, 14 August 2020.
|
|
|
|
|
|
### Task Tracking
|
|
|
|
|
|
* [CI Failures](./NetworkTeam/CIFailures)
|
|
|
* [Mainline Merges](./NetworkTeam/MainlineMerges)
|
|
|
* [Backport Merges](./user/teor#Backports:0.5daysperweek)
|
|
|
* [Backports In Testing](./user/teor/HiddenBackports)
|
|
|
* [0.4.3 Release Status](./NetworkTeam/CoreTorReleases/043Status)
|
|
|
* [Bug Triage](./NetworkTeam/BugTriage)
|
|
|
|
|
|
#### Older Releases
|
|
|
|
|
|
* [0.4.1 Release Status](./NetworkTeam/CoreTorReleases/041Status)
|
|
|
* [0.4.0 Release Status](./NetworkTeam/CoreTorReleases/040Status)
|
|
|
|
|
|
### Tor Meetings
|
|
|
|
|
|
### Past Tor Meetings
|
|
|
|
|
|
* [Team meeting at Tor Brussels Meeting 2019](https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsNetworkTeam)
|
|
|
* [Team meeting at Tor Mexico Meeting 2018](https://trac.torproject.org/projects/tor/wiki/org/meetings/2018MexicoCity)
|
... | ... | @@ -155,21 +121,12 @@ Policies: |
|
|
|
|
|
* [Process for deciding what our team policies and processes are](./NetworkTeam/MetaPolicy).
|
|
|
* [Merge Policy](./NetworkTeam/MergePolicy).
|
|
|
* [Committer Policy](./NetworkTeam/CommitterPolicy).
|
|
|
* [Security issue policy](./NetworkTeam/SecurityPolicy)
|
|
|
* [Supported platforms](./NetworkTeam/SupportedPlatforms)
|
|
|
|
|
|
Provisional policies:
|
|
|
|
|
|
* (none right now)
|
|
|
|
|
|
Draft policies:
|
|
|
* [Release Policy (draft)](./NetworkTeam/ReleasePolicy)
|
|
|
|
|
|
Guidelines:
|
|
|
* [Meeting Time Guidelines](./NetworkTeam/MeetingTimeGuidelines).
|
|
|
* [Merge Process](./NetworkTeam/MergeProcess)
|
|
|
* [Backport Process](./NetworkTeam/Backports)
|
|
|
* [Gitlab review Process](./NetworkTeam/GitlabReviews)
|
|
|
|
|
|
Security Releases
|
... | ... | |