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
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

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
  • Issues
  • #31526

Closed (moved)
Open
Opened Aug 26, 2019 by Roger Dingledine@arma

make new bridge-campaign alias for phw

phw is about to do a blog post where he was planning to direct new bridge relay operators to mail tor-team with their bridge details.

In the past, when I did a blitz of mails to relay operators and cc'ed tor-team, I got a bunch of dirty looks and requests to unsubscribe, from Tor people who didn't realize they were part of a volunteer support list.

So I am going to make a 'bridge-campaign' alias for him, which goes to him, me, and cohosh. This way we won't spam tor-team.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#31526