Opened 7 months ago

Last modified 2 months ago

#32863 new defect

Put an up-to-date web version of the Tor manual somewhere

Reported by: arma Owned by:
Priority: Medium Milestone: Tor: 0.4.5.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: 045-should, 044-can, postfreeze-ok
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

We used to publish
https://2019.www.torproject.org/docs/tor-manual.html.en
but that version of the Tor manual is now obsolete and for archival purposes.

I guess in the glorious future we will have a dev.torproject.org/tor/ that lists things like the Tor manual. Or maybe it should be on support.torproject.org because it is a resource for users (albeit advanced ones), not developers. Maybe it *is* on support.tpo right now, and I just couldn't find it?

In any case, here is a ticket for making progress on actually getting a web version of the manual onto a web page somewhere, ideally automatically kept up to date.

(Once it exists, there is a good argument for adding another htaccess rule to the 2019.www site, redirecting from the man page that nobody should look at it to the one that people should.)

This ticket motivated by discussion in #28526.

Child Tickets

Change History (6)

comment:1 Changed 7 months ago by pili

I think this should go on dev.torproject.org

We plan to kick of this project this month

comment:2 Changed 7 months ago by nickm

I thought that "dev" was for things of interest to developers... but the manual is of interest to both developers and "power users". Is "dev" for that kind of thing too?

comment:3 in reply to:  2 Changed 7 months ago by pili

Replying to nickm:

I thought that "dev" was for things of interest to developers... but the manual is of interest to both developers and "power users". Is "dev" for that kind of thing too?

I see dev as a place for "power users" also, I'm happy to discuss and change my mind :)

The developer portal should be "owned" by each development team at Tor Project so, apart from some standard content that we brainstormed would be useful to have for each development team at Tor Project, this is your space to host any useful information, documentation, etc... that you feel would help anyone to dive deeper into the work your team does.

comment:4 Changed 6 months ago by teor

Keywords: 044-should added
Milestone: Tor: 0.4.4.x-final

I want to make sure that the network team looks at this issue again for Tor 0.4.4.

We have made a lot of changes to the manual in 0.4.3 and 0.4.4.

comment:5 Changed 3 months ago by nickm

Keywords: 045-should 044-can added; 044-should removed
Milestone: Tor: 0.4.4.x-finalTor: 0.4.5.x-final

We need collaboration with website team in order to make this work.

comment:6 Changed 2 months ago by nickm

Keywords: postfreeze-ok added

Mark tickets which are important or safe enough to look at post-freeze for 0.4.4.

Note: See TracTickets for help on using tickets.