Opened 9 years ago

Closed 9 years ago

Last modified 4 years ago

#1711 closed enhancement (implemented)

Clean up Trac components

Reported by: karsten Owned by: karsten
Priority: Medium Milestone:
Component: Internal Services/Service - trac Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

We should clean up the Trac components a bit. I just tried out renaming components and it seems to work fine as long as we update reports manually.

I already renamed:

  • Tor - Metrics -> Metrics
  • Tor - Torbutton -> Torbutton (and updated report 14)

I suggest we rename the following components:

  • Android (Orbot)-Backend / Core -> Orbot
  • Polipo-Backend / Core -> Polipo
  • Tor - BridgeDB -> BridgeDB
  • Tor - Company -> Company
  • Tor - Distribution -> Distribution
  • Tor - Tor VM -> Tor VM
  • Tor - Tor bundles/installation -> Tor Bundles/installation
  • Tor - Torctl -> Torctl
  • Tor - Torify -> Torify
  • Tor - Website -> Website

This affects reports 8, 10, 11, 12, and 20, as far as I can see.

I'm happy to make the changes unless some objects.

Child Tickets

Change History (10)

comment:1 Changed 9 years ago by nickm

Is it only the reports that need to be updated? I was under the impression that we needed to update Tickets too. If that's not true, renaming seems wise.

But before we rename a lot, we should solve Bug #1713 : I think that Android is currently showing up first because it's alphabetically first. If that alphabetical-order is easy to change, we can just sort components in a good order. If not, we should maybe think of prefixes for components that are "Commonly used" "Less frequently used" and "Rarely used" ; maybe "Core", "Infrastructure" and "Other."

What do others think?

comment:2 Changed 9 years ago by karsten

It looks like only the reports need to be updated. At least I didn't notice anything else breaking when renaming "Tor - Metrics" to "Metrics".

#1713 is solved. There's a new default component "- Select a component" that bug reporters have already happily accepted. Other than that, components are alphabetically ordered.

Do we really want to group components by adding prefixes like "Core", "Infrastructure", etc.? What if we change our mind about the categorization at a later point?

comment:3 Changed 9 years ago by nickm

Well, I'm open to other solutions to the "having many components makes components are hard to find" problem. One possibility is to say "We simply don't have so many components as to make trouble." Another is to try to pick names that users will find easy to understand. I think that the ones you suggest are fine, except that I have no clear idea what "Distribution" means.

comment:4 Changed 9 years ago by karsten

I think "Distribution" is mostly GetTor. We might rename "Tor - Distribution" to "GetTor" and move the non-GetTor tasks to another component.

What are advantages of prefixes (+) vs. no prefixes (-)?

  • We'll avoid having an alphabetically ordered, two whiteboard long list of components. (+)
  • Bug reporters might have a harder time to find a component, because they'll have to understand our categories first. (-)
  • We'll have to agree on a categorization now and hope it won't change that much in the future. If it changes, we'll have to update the reports manually. (-)
  • ... ?

comment:5 Changed 9 years ago by nickm

+1 on renaming Distribution to GetTor.

comment:6 Changed 9 years ago by karsten

Owner: changed from erinn to karsten
Status: newassigned

Unless anybody objects, I'll rename component names as suggested in the original task description (without prefixes), except "Tor Distribution" will be "GetTor".

comment:7 Changed 9 years ago by erinn

I've renamed everything, including switching "Distribution" to "GetTor", and updated the reports. I left "Tor - Tor client" -- what should that be changed to? Just "Tor" or "Tor client" or something else?

I also think "Relay" could be named better, but am not sure what that better may be. Maybe just "Relays"?

comment:8 Changed 9 years ago by karsten

How about "Tor Client" and "Tor Relay"? The tasks that are assigned to either component are in the Tor sources, but the former affect Tor being uses as a client and the latter Tor acting as a relay.

comment:9 Changed 9 years ago by karsten

Resolution: implemented
Status: assignedclosed

Looks like this is already implemented. Thanks! Closing.

comment:10 Changed 4 years ago by qbi

Component: TracService - trac

Move all tickets from trac to "Service - trac" component.

Note: See TracTickets for help on using tickets.