[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 iwakeh):

 Replying to [comment:6 karsten]:
 > This seems like a fine topic for a pad discussion. Just some quick
 thoughts here:

 Yes, that would make sense.  We should collect and sort a little more on
 the ticket here before using the pad, though.  That gives more time to
 think through suggestions more thoroughly, as you also suggested.

 >  - iwakeh, regarding your first comment, I agree that, right now,
 CollecTor is the only application that creates index files. My suggesion
 was to move that functionality to metrics-lib in order to use it in other
 applications, too, in this case metrics-web. See my (*1) above.

 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.

 >  - irl and iwakeh, I think you're talking about the same thing, which is
 an Onionoo JSON API. That's what I meant in my (*8) above, and I'm aware
 that we discussed this long ago and dropped it on the floor. It might make
 more sense now. We just need to be very clear that providing another API
 in metrics-lib means we cannot make changes as quickly as we can right
 now. Major releases of metrics-lib and 1-month delays required for
 backward-incompatible changes, and all that. Still worth discussing if it
 helps avoid writing code twice.

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

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