... | ... | @@ -35,10 +35,36 @@ The following are our goals for 2020 |
|
|
* Sponsor 58 - [Tor Browser Security, Performance, & Usability Improvements](https://gitlab.torproject.org/groups/tpo/-/milestones/11)
|
|
|
* Sponsor 30 - [Empowering Communities in the Global South to Bypass Censorship](https://gitlab.torproject.org/tpo/anti-censorship/trac/-/issues/31265)
|
|
|
|
|
|
## Triaging Tickets
|
|
|
|
|
|
We are triaging tickets three times a week, rotating the role between people in the team.
|
|
|
|
|
|
Starting on November 23rd:
|
|
|
|
|
|
- Monday: sysrqb
|
|
|
- Wednesday: acat
|
|
|
- Friday: geko
|
|
|
|
|
|
The criteria to include tickets in a specific milestone are:
|
|
|
|
|
|
- bugs that must be fixed (include security, regression or crash bugs)
|
|
|
- tickets that have been roadmapped before becasue they are part of a sponsored project
|
|
|
- tickets that are very fast to fix (around 1 hour)
|
|
|
|
|
|
|
|
|
The process we are using for triaging tickets is:
|
|
|
|
|
|
1. filter out all tickets not in the milestone sort out by creation date
|
|
|
2. for each new ticket:
|
|
|
- add related labels (for example add an UX label to tickets that needs UX/UI help and the same for other teams)
|
|
|
- if it fits the criteria written above then add it to the right milestone
|
|
|
|
|
|
|
|
|
## Becoming a volunteer
|
|
|
|
|
|
The best way to get involved is to visit our weekly IRC meeting (see above). Tell us your background and interests and we will find a project for your to get started.
|
|
|
|
|
|
|
|
|
## Archive
|
|
|
|
|
|
https://trac.torproject.org/projects/tor/wiki/org/teams/ApplicationsTeam |
|
|
\ No newline at end of file |