Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #20643

Closed (moved)
(moved)
Open
Created Nov 12, 2016 by Roger Dingledine@arma

make and maintain a registry of what debs are on deb.tp.o and why

We've accumulated a variety of debs on deb.tp.o, with a variety of maintainers. I think the knowledge of who these people are is not recorded well.

Step one, we should figure out who is in charge of each of the debs that's there. For example, is the pyptlib deb there because of one of the obfs debs? Or is it leftover from something and nobody needs it anymore? Similarly, is tor-arm there because it got brought in as a dependency to...something else that's there?

Then step two, we should write all of that in one place (a page on this wiki? a text file in the deb.tp.o root? someway else?), and make sure that those people know that they have the responsibility to keep their debs up to date, or to decide to take them down when they're no longer needed.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking