Re: [tor-bugs] #25925 [Core Tor/sbws]: Bandwidth scanner parent ticket for SoP planned tasks

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#25925: Bandwidth scanner parent ticket for SoP planned tasks
---------------------------+--------------------------
 Reporter:  juga           |          Owner:  juga
     Type:  defect         |         Status:  assigned
 Priority:  Medium         |      Milestone:
Component:  Core Tor/sbws  |        Version:
 Severity:  Normal         |     Resolution:
 Keywords:                 |  Actual Points:
Parent ID:                 |         Points:
 Reviewer:                 |        Sponsor:
---------------------------+--------------------------

Comment (by teor):

 Replying to [comment:4 juga]:
 > Now that SoP finished, should this ticket be closed?, should the
 remaining opened tickets be made:
 > - childs of a new parent ticket (PF?)

 Some of these tasks are important, and others are not.

 Let's:
 * work out which tasks we need to do
 * find out if any tasks are missing
 * put the tasks we need to do under a new parent ticket

 > - assigned a component (what about having a tor-bwauth component and not
 just keyword?)

 In Core Tor, we have a component for each piece of software. (The DirAuth
 component is for directory authority config changes.)

 "tor-bwauth" is not a component, it's a group of related tasks in
 different components. These tasks are already assigned to Tor, sbws,
 Torflow, and Chutney.

 > - tagged as tor-bwauth?

 Good idea!
 We can also tag them with bwauth-sop-2018 so we know which tasks used to
 be under this ticket.

 > - leave orphan?

 If a task is not important, it can be an orphan.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25925#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs