[tor-bugs] #6405 [Trac]: Merge torclient/torrelay/torbridge/etc into one Tor component

[Tor Bug Tracker & Wiki]

#6405: Merge torclient/torrelay/torbridge/etc into one Tor component
-------------------------+--------------------------------------------------
 Reporter:  arma         |          Owner:  nickm   
     Type:  enhancement  |         Status:  assigned
 Priority:  normal       |      Milestone:          
Component:  Trac         |        Version:          
 Keywords:               |         Parent:          
   Points:               |   Actualpoints:          
-------------------------+--------------------------------------------------

Comment(by arma):

 We should come up with a description for how the new policy ought to work.
 For examples:

 - Do we enumerate a set of TorClient, TorBridge, TorHS, TorAuthority, etc
 keywords that we stick to? I worry that using keywords like "bridges" will
 result in helpful-but-confused users doing confusing things. On the other
 hand, having funny-looking component names will cause confusion among
 users and we'll always have to be fixing tickets. On the gripping hand,
 we'll probably be having to fix tickets anyway.

 - Is it reasonable to claim that a Tor-component ticket that doesn't have
 one of these keywords is flawed and should be fixed?

 - Where do we write down our intended plans in a way that bug-reporting
 users might find them?

 - What should we call the new megacomponent? "Tor"?

 You should ask Karsten about his recent experience with doing mass trac
 changes.

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