[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #19616 [Metrics/metrics-lib]: Consider renaming metrics-lib
#19616: Consider renaming metrics-lib
---------------------------------+-----------------------------------
Reporter: iwakeh | Owner: karsten
Type: enhancement | Status: new
Priority: Medium | Milestone: metrics-lib 2.0.0
Component: Metrics/metrics-lib | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
---------------------------------+-----------------------------------
Comment (by karsten):
Ah, I didn't explain my idea of using `org.torproject.metrics.lib` very
well. I feel we're in the process of moving currently separate Metrics
subprojects like CollecTor and Onionoo back to Tor Metrics. We already
started doing that by moving their specifications to the Tor Metrics
website (which we'll need to continue in July). And we put metrics-lib on
the Tor Metrics website as well, making it part of Metrics rather than a
single entity. That's why I implicitly assumed (sorry) that we'll pick a
common naming scheme for packages, too. We already use
`org.torproject.metrics.web` for the website part of metrics-web, so
picking `org.torproject.metrics.lib` seemed logical. We'd have to rename
a few more packages in metrics-web, Onionoo, and so on, but that can
happen after we rename packages in metrics-lib. Another reason is that we
could say that we "control" `org.torproject.metric` as Tor Metrics team
and put all our code bases under that. All in all, I think I prefer
`org.torproject.metrics.lib` from all suggestions above. Except there are
downsides I didn't see?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19616#comment:13>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs