[tor-bugs] #24036 [Metrics]: Create a unified package naming scheme for all metrics code bases

[Tor Bug Tracker & Wiki]

#24036: Create a unified package naming scheme for all metrics code bases
-------------------------+------------------------------
 Reporter:  karsten      |          Owner:  metrics-team
     Type:  enhancement  |         Status:  needs_review
 Priority:  Medium       |      Milestone:
Component:  Metrics      |        Version:
 Severity:  Normal       |     Resolution:
 Keywords:               |  Actual Points:
Parent ID:               |         Points:
 Reviewer:               |        Sponsor:
-------------------------+------------------------------

Comment (by karsten):

 Replying to [comment:12 iwakeh]:
 > Looks fine.  Some suggestions (that might have been intended, but are
 not listed explicitly):

 Good points!

 > 1) The tickets for renaming packages should be tickets on their own.

 Yes, that's what I meant: 8 new tickets. Otherwise this ticket will become
 crazy!

 > 2) The update of all depending products to the latest metrics-lib are
 the next round of tickets;

 Right. This is also related to #24028, because we wanted to take this
 opportunity to redesign some of the descriptor interfaces. I guess that
 means only 7 new tickets and adding a comment to #24028.

 > 3) next badge are all tickets moving code between products or creating
 new functionality, e.g., creating a util package or Onionoo's JSON API
 etc.  Here an internal order needs to be defined , too.

 Yep. Shouldn't be that difficult, though. We'll build something new in
 metrics-lib and then switch over to using that in dependent code bases.

 > Numbers indicate a suggested order for tackling the tasks&tickets.

 Makes sense.

 I'll create 7 new tickets now and also add a comment to #24028.

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