Changes

Page history
Apply conversion script to all *.md files. authored by Alexander Hansen Færøy's avatar Alexander Hansen Færøy
Show whitespace changes
Inline Side-by-side
org/teams/NetworkTeam/TeamRotations.md
View page @ a1a4b621
== Team rotation ==
## Team rotation
[[TOC]]
(The calendar below was autogenerated from a script at https://people.torproject.org/~nickm/rotations.py , also attached to this page. Please feel free to trade assignments with other people!)
=== Calendar ===
### Calendar
'''March, 2019'''
**March, 2019**
||= Week of =||= Bug triage =||= CI+Coverity =||
||= 2019-03-04 =|| nickm || ahf ||
||= 2019-03-11 =|| teor || asn ||
||= 2019-03-18 =|| ahf || catalyst ||
||= 2019-03-25 =|| asn || dgoulet ||
|= Week of =|= Bug triage =|= CI+Coverity =|
|--------------------|--------------------|--------------------|
|= 2019-03-04 =| nickm | ahf |
|= 2019-03-11 =| teor | asn |
|= 2019-03-18 =| ahf | catalyst |
|= 2019-03-25 =| asn | dgoulet |
'''April, 2019'''
**April, 2019**
||= Week of =||= Bug triage =||= CI+Coverity =||
||= 2019-04-01 =|| catalyst || mikeperry ||
||= 2019-04-08 =|| dgoulet || nickm ||
||= 2019-04-15 =|| mikeperry || teor ||
||= 2019-04-22 =|| nickm || ahf ||
||= 2019-04-29 =|| teor || asn ||
|= Week of =|= Bug triage =|= CI+Coverity =|
|--------------------|--------------------|--------------------|
|= 2019-04-01 =| catalyst | mikeperry |
|= 2019-04-08 =| dgoulet | nickm |
|= 2019-04-15 =| mikeperry | teor |
|= 2019-04-22 =| nickm | ahf |
|= 2019-04-29 =| teor | asn |
'''May, 2019'''
**May, 2019**
||= Week of =||= Bug triage =||= CI+Coverity =||
||= 2019-05-06 =|| ahf || catalyst ||
||= 2019-05-13 =|| asn || dgoulet ||
||= 2019-05-20 =|| catalyst || mikeperry ||
||= 2019-05-27 =|| dgoulet || nickm ||
|= Week of =|= Bug triage =|= CI+Coverity =|
|--------------------|--------------------|--------------------|
|= 2019-05-06 =| ahf | catalyst |
|= 2019-05-13 =| asn | dgoulet |
|= 2019-05-20 =| catalyst | mikeperry |
|= 2019-05-27 =| dgoulet | nickm |
'''June, 2019'''
**June, 2019**
||= Week of =||= Bug triage =||= CI+Coverity =||
||= 2019-06-03 =|| mikeperry || teor ||
||= 2019-06-10 =|| nickm || ahf ||
||= 2019-06-17 =|| teor || ahf ||
||= 2019-06-24 =|| ahf || catalyst ||
|= Week of =|= Bug triage =|= CI+Coverity =|
|--------------------|--------------------|--------------------|
|= 2019-06-03 =| mikeperry | teor |
|= 2019-06-10 =| nickm | ahf |
|= 2019-06-17 =| teor | ahf |
|= 2019-06-24 =| ahf | catalyst |
'''July, 2019'''
**July, 2019**
||= Week of =||= Bug triage =||= CI+Coverity =||
||= 2019-07-01 =|| asn || dgoulet ||
||= 2019-07-08 =|| catalyst || mikeperry ||
||= 2019-07-15 =|| dgoulet || nickm ||
||= 2019-07-22 =|| mikeperry || teor ||
||= 2019-07-29 =|| nickm || ahf ||
|= Week of =|= Bug triage =|= CI+Coverity =|
|--------------------|--------------------|--------------------|
|= 2019-07-01 =| asn | dgoulet |
|= 2019-07-08 =| catalyst | mikeperry |
|= 2019-07-15 =| dgoulet | nickm |
|= 2019-07-22 =| mikeperry | teor |
|= 2019-07-29 =| nickm | ahf |
=== Active Weekly roles ===
'''Bug triage''':
### Active Weekly roles
**Bug triage**:
* See the [https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/BugTriage Bug Triage guide]. It's a work in progress!
* See the [Bug Triage guide](https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/BugTriage). It's a work in progress!
* Minimal version: once every day you're working...
* Make sure that all [https://trac.torproject.org/projects/tor/report/66 '"- Select a component" tickets'] get a component.
* Make sure that all [https://trac.torproject.org/projects/tor/report/69 tickets in "Core Tor/Tor"] and [https://trac.torproject.org/projects/tor/report/71 tickets in "Core Tor/sbws"] get a milestone.
* Label as needs_review any tickets that got a patch ([https://trac.torproject.org/projects/tor/report/65 Tor recently modified tickets], [https://trac.torproject.org/projects/tor/report/73 sbws recently modified tickets] or [https://trac.torproject.org/projects/tor/timeline?daysback=4&authors=&tag_query=&ticket=on&ticket_details=on&sfp_email=&sfph_mail=&update=Update timeline for the last 4 days])
* Make sure that all ['"- Select a component" tickets'](https://trac.torproject.org/projects/tor/report/66) get a component.
* Make sure that all [tickets in "Core Tor/Tor"](https://trac.torproject.org/projects/tor/report/69) and [tickets in "Core Tor/sbws"](https://trac.torproject.org/projects/tor/report/71) get a milestone.
* Label as needs_review any tickets that got a patch ([Tor recently modified tickets](https://trac.torproject.org/projects/tor/report/65), [sbws recently modified tickets](https://trac.torproject.org/projects/tor/report/73) or [timeline for the last 4 days](https://trac.torproject.org/projects/tor/timeline?daysback=4&authors=&tag_query=&ticket=on&ticket_details=on&sfp_email=&sfph_mail=&update=Update))
* Adding/Removing keywords to properly classify the ticket
'''Coverity response'''
**Coverity response**
* Try to fix any newly reported issues from coverity scan. If they're not immediately obvious, see if they're a possible security issue. If not, open a ticket. If so, escalate.
* To escalate, send an encrypted email to network-team-security@lists.torproject.org (the list key is on the keyservers signed by many of us on the list).
* Include the CID in the ticket summary, and tag the ticket with "coverity".
'''CI response'''
**CI response**
* Once each day you're working:
* Check the [wiki:org/teams/NetworkTeam/CIFailures] summary page
* Check the [org/teams/NetworkTeam/CIFailures](org/teams/NetworkTeam/CIFailures) summary page
* Make sure that all the travis-ci, appveyor, and jenkins Tor and sbws CI is passing on master and all supported maint branches:
* https://travis-ci.org/torproject/tor/branches
* https://ci.appveyor.com/project/torproject/tor/history
......@@ -82,13 +87,13 @@
* For Travis or Appveyor: Core Tor/Tor
* For Jenkins: Internal Services/Jenkins
* If it is a compile or test failure, file a ticket against Core Tor/Tor or Core Tor/sbws
* Before you file a ticket, check the [https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~tor-ci tor-ci] or [https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~sbws-ci sbws-ci] keywords. If you file a ticket, tag it with tor-ci or sbws-ci.
* Before you file a ticket, check the [tor-ci](https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~tor-ci) or [sbws-ci](https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~sbws-ci) keywords. If you file a ticket, tag it with tor-ci or sbws-ci.
=== Long-term roles ===
### Long-term roles
'''Release Maintainers'''
**Release Maintainers**
The current maintainers are [wiki:org/teams/NetworkTeam/CoreTorReleases#Current listed beside each release].
The current maintainers are [listed beside each release](./org/teams/NetworkTeam/CoreTorReleases#Current).
Details of the duties and processes on maintaining the Tor code base can be found here:
* https://gitweb.torproject.org/tor.git/tree/doc/HACKING/Maintaining.md
......@@ -96,13 +101,13 @@ Details of the duties and processes on maintaining the Tor code base can be foun
* https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/Backports
* https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/ReleasePolicy
'''Assigners of Reviews'''
**Assigners of Reviews**
* Once a week, assign needs_review tickets in Tor and sbws to team members
* Currently dgoulet and asn
=== ===
'''Team observer'''
###
**Team observer**
* Sit in other teams' weekly meetings
* Maybe read their ticket updates, etc?
......@@ -110,25 +115,26 @@ Details of the duties and processes on maintaining the Tor code base can be foun
* eg TBB, Metrics, UX, Community, OONI, Anti-Censorship
* Currently gaba
=== Roles that __everybody__ will play weekly ===
Every week each of us will spend __some__ time on each of this tasks.[[BR]]
### Roles that __everybody__ will play weekly
Every week each of us will spend __some__ time on each of this tasks.
'''15 minutes bug fixes'''
**15 minutes bug fixes**
* When there are new bugs that can be fixed in 15 minutes, fix them.
* If there are new patches that can be merged in 15 minutes, merge them
* "15 minutes" is an arbitrary interval.
'''Community person'''
**Community person**
* Interacts with user questions, finding answers if they don't know them. Helps out new volunteers with patches, etc.
* Easy tickets: https://trac.torproject.org/projects/tor/query?status=needs_review&component=Core+Tor%2FTor&col=id&col=summary&col=status&col=reviewer&order=priority
'''Design Meetings'''
**Design Meetings**
* Identifies open design proposals that need more work, and organizes meetings (if needed) to move them forward.
'''Frontline tech support (#tor, tor-relays@)'''
**Frontline tech support (#tor, tor-relays@)**
* Keep an eye on places where people ask tech support questions.
* Try to help with helping them.
......
......