[tor-bugs] #22836 [Metrics/Metrics website]: Parse CollecTor's index.json and provide our own directory listing

[Tor Bug Tracker & Wiki]

#22836: Parse CollecTor's index.json and provide our own directory listing
-------------------------------------+------------------------------
 Reporter:  karsten                  |          Owner:  karsten
     Type:  enhancement              |         Status:  needs_review
 Priority:  Medium                   |      Milestone:
Component:  Metrics/Metrics website  |        Version:
 Severity:  Normal                   |     Resolution:
 Keywords:                           |  Actual Points:
Parent ID:                           |         Points:
 Reviewer:                           |        Sponsor:
-------------------------------------+------------------------------

Comment (by karsten):

 Hmmmmmm. While reviewing #23286 I thought about an alternative c): We move
 the `org.torproject.descriptor.index` package from metrics-lib to
 ''metrics-base'' where we call it `org.torproject.metrics.index` and re-
 use those classes in all code bases relying on metrics-base.

 We might add even more commonly used classes to metrics-base as long as
 they are used by more than one code base. The difference to metrics-lib is
 that metrics-base is not an API to be used by products outside of the
 metrics space. If somebody uses that code, we change something, and their
 code breaks, it's not our fault. In contrast to that, keeping index things
 in metrics-lib and exposing them in the API, and maybe even adding more
 parts in the future, would lead to making it harder to maintain that
 interface in the future.

 On the positive side, I'd be a lot less picky about the model for the
 index package if it's only contained in metrics-base and not in metrics-
 lib.

 What do you think?

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