Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
T
Team
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • The Tor Project
  • Metrics
  • Team
  • Wiki
    • Legacy wiki
  • Volunteers

Last edited by Gaba Dec 21, 2020
Page history

Volunteers

= Volunteering and Contributing to Metrics The Metrics Team supports a growing codebase for maintaining and analyzing data for an also growing number of data sources. Thus there are limited resources available for supporting projects outside the immediate scope.

This means on one hand //help wanted// and on the other that we cannot help volunteers learn how to help us. So we compiled a few steps below what we think help a volunteer getting started smoothly.

How to contribute

Preparation

Read through the available documentation and take a look at the metrics web sites in order to get an idea what is done here. Starting points:

  • FAQs
  • Metrics Team Page
  • coding style guides
  • depending on what interests you most various protocols, e.g. TorSpec and Onionoo
  • Get up-to-date with tools as well as the languages used in the area you're interested in, see guides.

Typical Work-flow

  1. Pick a task from the metrics-help tagged ones (see [#Wheretohelp table]).
  2. Analyze the problem and add a comment containing the (short) analysis and proposed solution.
  3. We'll discuss the solution with you to make sure things fit before too much code is written.
  4. Provide a patch (see guide doc).
  5. Finally the review and revision //cycle//.
  6. patch merged to Metrics code base.

Where to help

  • Run an independent server instance of one of Metrics products, like
  • Onionoo releases
  • CollecTor releases
  • Use metrics-lib for analyzing Tor data.

  • Enter bugs or feature requests by creating a new Metrics ticket.

  • Help implementing open tasks. These will be tagged as metrics-helpTicketQuery(keywords=metrics-help,status=!closed,format=table,order=changetime,desc=true,col=id

Sites of Metrics' products

  • https://atlas.torproject.org
  • https://collector.torproject.org
  • https://exonerator.torproject.org
  • https://metrics.torproject.org
  • https://onionoo.torproject.org
Clone repository
  • Legacy Wiki
    • ContributorGuide
    • Documentation
    • ExitScannerSurvivalGuide
    • MetricsJavaStyleGuide
    • MetricsPythonStyleGuide
    • ObfuscationSimulationAnalysis
    • OldRoadmaps
    • RelaySearch
    • Volunteers
  • Survival Guides
    • Check
    • Exit Scanner
  • Home
  • timeline