#24497: Improve documentation for tor relay operators ------------------------------+------------------------ Reporter: arthuredelstein | Owner: (none) Type: defect | Status: new Priority: Medium | Milestone: Component: Webpages/Website | Version: Severity: Normal | Resolution: Keywords: ux-team | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: ------------------------------+------------------------
Comment (by cypherpunks): > That said, depending on how wide we want to expand it, we should find people who are happy to be "in-charge" of keeping their preferred OS instructions up to date. While there are a lot of people who could install Gentoo / Arch / etc.. and write up instructions, if these are not systems people run day-to-day, they may not be aware when things change and the instructions no longer work. I'm happy to be "in-charge" of keeping things maintained for all OSes that I have to keep an eye for ansible-relayor already. I discovered there is one more OS that has apparently a well maintained tor package that is not on the list, I might add that. I also started to work on a OS table that shows what things (related to tor) are available or not. Replying to [comment:29 alison]: > Edit: another idea is that we should have a table of contents, like the support wiki https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam/Support Yes, a ToC is a IMO a must-have (when this content reaches a proper website). > I plan to work on migrating more of this today. I'm waiting for you to finish migrating content, once you are done I'll start working on that wiki page. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24497#comment:30> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs