Opened 8 years ago

Closed 7 years ago

#2647 closed task (implemented)

Clean up metrics Git repositories

Reported by: karsten Owned by: karsten
Priority: Medium Milestone:
Component: Metrics/CollecTor Version:
Severity: Keywords:
Cc: phobos, Sebastian Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

There are four official metrics repositories right now:

  • metrics-db: Java program to collect and possibly sanitize metrics data
  • metrics-utils: Java and Python tools to analyze metrics data
  • metrics-web: JSP-based website to aggregate and display statistics
  • metrics: Technical reports and code snippets for past metrics analyses

I didn't use the metrics repository for quite some time now, mostly because it has no useful structure. Instead, I store technical report sources and code snippets on my local hard drive. Dear Trac, this is under the seal of confession, right?

Here's what I'd like to change:

  • Reorganize the metrics repository, so that there's a separate subdirectory for each project (tech report, bug analysis, visualization, etc.). There shall be no shared directories between projects, but instead every project shall be self-contained. One shouldn't have to worry about other projects when changing stuff.
  • Rename the metrics repository to something like metrics-playground, metrics-analysis, or metrics-projects. Calling the repository metrics implies that it's somehow at a higher level than metrics-db, metrics-utils, and metrics-web, which it is not.

Child Tickets

Change History (12)

comment:1 Changed 8 years ago by Sebastian

Renaming repositories is possible, but I'd like you to be sure that that is what you want to do. It will break everyone's clone of that repository. Or are you also intending to rewrite history? In that case, renaming is the appropriate thing to do.

comment:2 Changed 8 years ago by karsten

I want to move and delete a lot of files, and add a bunch of new files. I don't want to rewrite history.

I'm not too concerned about breaking people's clones of this repository, because the last real update was in October 2009. I don't expect anyone but you has a clone, and you only have it because we worked on the counting-users tech report.

comment:3 in reply to:  description ; Changed 8 years ago by karsten

Resolution: implemented
Status: newclosed

Replying to karsten:

  • Reorganize the metrics repository, so that there's a separate subdirectory for each project (tech report, bug analysis, visualization, etc.). There shall be no shared directories between projects, but instead every project shall be self-contained. One shouldn't have to worry about other projects when changing stuff.
  • Rename the metrics repository to something like metrics-playground, metrics-analysis, or metrics-projects. Calling the repository metrics implies that it's somehow at a higher level than metrics-db, metrics-utils, and metrics-web, which it is not.

We now have the new metrics-tasks repository for this purpose. It's organized by Trac task numbers.

I looked through the old metrics repository and found nothing too useful that we need to keep. That stuff is 1.5 years old. The stuff we cared about is now in metrics-db, metrics-web, metrics-utils. The only relevant stuff I found was the tech report on Privacy-preserving Ways to Estimate the Number of Tor Users, which was in my public metrics branch. I added the LaTeX sources to metrics-tasks.

The official metrics repository can go away, as well as my public metrics repository.

Closing.

comment:4 in reply to:  3 ; Changed 8 years ago by rransom

Replying to karsten:

I looked through the old metrics repository and found nothing too useful that we need to keep. That stuff is 1.5 years old. The stuff we cared about is now in metrics-db, metrics-web, metrics-utils. The only relevant stuff I found was the tech report on Privacy-preserving Ways to Estimate the Number of Tor Users, which was in my public metrics branch. I added the LaTeX sources to metrics-tasks.

The official metrics repository can go away, as well as my public metrics repository.

Please archive the repository as a ‘Git bundle’ on archive.tpo.

The following command should work in a clone of the repository:

git bundle create ../metrics-final-archive-bundle.git-bundle --all

(but try cloning from the bundle before you toss the repo!)

comment:5 in reply to:  4 Changed 8 years ago by karsten

Cc: phobos Sebastian added

Replying to rransom:

Please archive the repository as a ‘Git bundle’ on archive.tpo.

The following command should work in a clone of the repository:

git bundle create ../metrics-final-archive-bundle.git-bundle --all

(but try cloning from the bundle before you toss the repo!)

Good idea. I have uploaded the bundle file to ~ on aroides, but I don't know where to put it on archive.tpo. phobos or Sebastian, any thoughts?

comment:6 Changed 8 years ago by karsten

Resolution: implemented
Status: closedreopened

Sebastian, can you delete the official metrics repository as well as my public one? Thanks!

comment:7 Changed 8 years ago by Sebastian

Is the archiving situation taken care of?

comment:8 Changed 8 years ago by karsten

The bundle file is still in my home directory on aroides. I can put it somewhere else. Any suggestions?

comment:9 Changed 8 years ago by Sebastian

nope, but a home dir somewhere seems hardly appropriate

comment:10 Changed 8 years ago by karsten

Right. What's the policy for removing obsolete Git repositories? I uploaded the bundle file here. Please do something appropriate with it. :)

comment:11 Changed 8 years ago by Sebastian

I removed the repository. The people who cared about having the git bundle be available somewhere should figure out where they want it.

comment:12 Changed 7 years ago by karsten

Resolution: implemented
Status: reopenedclosed

Nothing to do here anymore. Closing.

Note: See TracTickets for help on using tickets.