Tor Trac component Metrics/Ooni
Hi OONI people, we briefly talked about this before (in Berlin or Amsterdam, I don't recall): I'd like to move the Metrics/Ooni subcomponent somewhere else, because it's unrelated to what Tor metrics folks are working on. I noticed that the last ticket update in that component was 3 months ago. Is it correct that you're not using Tor's Trac for tracking issues anymore? In that case, would you mind me renaming the component to Archived/Ooni? The tickets would all still be there and accessible by the same ticket numbers! Otherwise, if you still use the component, we could easily justify calling the component Ooni (or OONI) as one top-level component. I guess we should talk to a Trac admin person before doing that, but I don't expect major pushback. What do you think? All the best, Karsten
On 28/04/2017 15:34 +0000, Karsten Loesing wrote:
Hi OONI people,
we briefly talked about this before (in Berlin or Amsterdam, I don't recall):
I'd like to move the Metrics/Ooni subcomponent somewhere else, because it's unrelated to what Tor metrics folks are working on.
I noticed that the last ticket update in that component was 3 months ago. Is it correct that you're not using Tor's Trac for tracking issues anymore? In that case, would you mind me renaming the component to Archived/Ooni? The tickets would all still be there and accessible by the same ticket numbers!
Otherwise, if you still use the component, we could easily justify calling the component Ooni (or OONI) as one top-level component. I guess we should talk to a Trac admin person before doing that, but I don't expect major pushback.
What do you think? Hi Karsten,
Yes I think renaming the trac component to Archived/Ooni is a good idea. We don't currently use trac as our issue tracker, but it's still useful to have the trac tickets around for historical purposes. ~ Artur
On 28.04.17 17:39, Arturo Filastò wrote:
On 28/04/2017 15:34 +0000, Karsten Loesing wrote:
Hi OONI people,
we briefly talked about this before (in Berlin or Amsterdam, I don't recall):
I'd like to move the Metrics/Ooni subcomponent somewhere else, because it's unrelated to what Tor metrics folks are working on.
I noticed that the last ticket update in that component was 3 months ago. Is it correct that you're not using Tor's Trac for tracking issues anymore? In that case, would you mind me renaming the component to Archived/Ooni? The tickets would all still be there and accessible by the same ticket numbers!
Otherwise, if you still use the component, we could easily justify calling the component Ooni (or OONI) as one top-level component. I guess we should talk to a Trac admin person before doing that, but I don't expect major pushback.
What do you think? Hi Karsten,
Yes I think renaming the trac component to Archived/Ooni is a good idea. We don't currently use trac as our issue tracker, but it's still useful to have the trac tickets around for historical purposes.
That was quicker than expected! Thanks! I just made this change. See this ticket which I created for documentation purposes: https://trac.torproject.org/projects/tor/ticket/22097 Let me know if this causes any trouble. It shouldn't, in theory, but if it does, I'll try to help resolve. All the best, Karsten
~ Artur
_______________________________________________ ooni-dev mailing list ooni-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/ooni-dev
participants (2)
-
Arturo Filastò -
Karsten Loesing