Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sbws
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • sbws
  • Issues
  • #28099
Closed
Open
Created Oct 18, 2018 by teor@teor

Make a policy for adding new sbws relay keys

Split from legacy/trac#28085 (moved):

I think we should also come up with some policy to add/remove key/values. Even if all the ones we have so far seem useful, we are not using it.

I don't understand. Do you mean:

There are some keys in the spec that are not in the code. Or There are some keys in the code that are not in the spec. Or There are some keys in the spec and the code that are not being used by anyone.

For instance, do we have tickets of cases where these key/values were needed/requested?.

When we find this information, we should update the spec so it tells us why we need each value.

Assignee
Assign to
Time tracking