[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:  new
 Priority:  Medium       |      Milestone:
Component:  Metrics      |        Version:
 Severity:  Normal       |     Resolution:
 Keywords:               |  Actual Points:
Parent ID:               |         Points:
 Reviewer:               |        Sponsor:
-------------------------+------------------------------

Comment (by karsten):

 Replying to [comment:7 iwakeh]:
 > Yes, I understand that.  What I tried to say above is that Collector's
 index package only contains code regularly producing index files, i.e.,
 only code that facilitates configuration and scheduling.  The index-file
 generation is based on metrics-lib already. Thus, no code needs to be
 moved from CollecTor.  metrics-lib contains all index-json producing code
 and would be ready to be used elsewhere as is.

 Ah, okay. Makes sense.

 > Yes, but the question would also be where to add it.  Onionoo or
 metrics-lib?  (for the pad discussion)

 Agreed, fine question! My idea was to stuff anything into metrics-lib that
 will be shared, to have a single dependency. But I also thought about
 keeping things in Onionoo and depending on it. However, that latter
 approach might not scale, with metrics-web then depending on metrics-lib,
 Onionoo, ExoneraTor, and so on. But: pad discussion!

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