Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • 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.

  • Legacy
  • TracTrac
  • Wiki
    • Org
    • Teams
    • Metricsteam
  • RelaySearch

Last edited by Alexander Færøy Jun 15, 2020
Page history

RelaySearch

Relay Search Development

Quick Links

  • Homepage: https://metrics.torproject.org/rs.html
  • Onion Service: http://rougmnvswfsmd4dq.onion/rs.html
  • Source Browser: https://gitweb.torproject.org/atlas.git/
  • git clone https://git.torproject.org/atlas.git

Projects

  • org/sponsors/SponsorX

Hacking

If you would like to contribute to Relay Search, you can get started by cloning the Git repository from the location in the quick links section at the top of this page. Open index.htmlhttps://onionoo.torproject.org/

By default, new tickets are assigned to the metrics-team metauser. If you are working on an issue, please take ownership of it via the Trac and set the status to accepted. This helps us to avoid duplication of effort.

https://linux.die.net/man/1/git-format-patch

https://github.com/<username>/relay-search/compare/<branch-with-fixes>.patch

If you wish to contribute to Relay Search anonymously through the cypherpunks account, it is acceptable to attach the patches to the ticket.

Please use well-formatted and well-explained commit messages. You can find guidelines and suggestions for commit messages here: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html

All patches must address tickets that are filed in the Trac, and you can find a list of open tickets below. If you find an issue that you would like to produce a patch for that doesn't have a ticket, create a new ticket and set the component to "Metrics/Relay Search". When you link a patch from the Trac, set the ticket status to "needs_review". Once the patch has been reviewed, it will either be set to "merge_ready" or it will be merged straight away and the ticket closed as "fixed". If the reviewer finds that the patch needs more work, the status will be set to "needs_revision".

Anyone may contribute to reviews in the comments, but please do not set tickets to "merge_ready" on patches unless you are already a well known member of the Metrics team. Your comments will be seen by the reviewer and taken into account.

All Tasks in Trac

Active Tasks

TicketQuery(component=Metrics/Relay Search,status=!closed,format=table,order=changetime,desc=true,col=id

Completed Tasks

TicketQuery(component=Metrics/Relay Search,status=closed,format=table,order=changetime,desc=true,col=id

Contact

  • User mailing list: https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
  • User IRC channel: #tor on irc.oftc.net
  • Development mailing list: https://lists.torproject.org/cgi-bin/mailman/listinfo/metrics-team
  • Development IRC channel: #tor-dev on irc.oftc.net

(If you get no response on IRC, you can highlight irl, the current Relay Search maintainer)

Clone repository
  • AnonOnWikiFavs
  • AppArmorForTBB
  • AutomationInventory
  • BadContent
  • BlockingBittorrent
  • CI
  • CamelCase
  • CrowdfundingHS2015
  • FlashProxyFAQ
  • FlashProxyHowto
  • FlashProxyUsability
  • HTTPSEverywhere
    • SSLObservatorySubmission
  • ImportantGoogleChromeBugs
  • InterMapTxt
  • InterTrac
View All Pages