Opened 7 years ago

Closed 7 years ago

#6625 closed defect (fixed)

Documentation: DirServ Spec version 1 link broken, 404

Reported by: bastik Owned by: phobos
Priority: Medium Milestone:
Component: Webpages/Website Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

On https://www.torproject.org/docs/documentation.html.en#DesignDoc you place https://gitweb.torproject.org/torspec.git?a=blob_plain;hb=HEAD;f=dir-spec-v1.txt at "The specifications aim to give developers enough information to build a compatible version of Tor: (point 2, the second link)", which returns a 404.

I can't see v1 in torspec.git (root?), while specs with no version number is there and version 2 as well.

v1 has been placed in "attic" [whatever that is] (https://gitweb.torproject.org/torspec.git/tree/HEAD:/attic)

https://gitweb.torproject.org/torspec.git/blob/HEAD:/attic/dir-spec-v1.txt

The "folder" named "attic" contains two obsolete specs and "bridge specs", which I assume are not obsolete yet. While I don't know what attic is and bet that "bridges-spec" is an up-to-date spec, I suggest to create a "folder" called "obsolete" and move all obsolete specs there, while moving bridges-spec.txt to torspec.git (root?).

Should I create another ticket for the second part? I put this together because I figured out why it was returning a 404 and where the file is now. When fix the link, move the files, but forget to update the link it's broken again.

Child Tickets

Change History (4)

comment:1 Changed 7 years ago by phobos

How would you like svn commit access to fix up all of this yourself?

comment:2 Changed 7 years ago by bastik

I don't know SVN at all. (Nor do I know git, which is a different pair of shoes)

It seems to require a client as far as I could find out. Seems there is no GUI, don't use CLI much, almost never, but guess the documentation would tell me how to use it.

I don't know what LDAP is. I'm not a developer.

"you need to run htdigest -c tor.passwd.tmp 'Tor subversion repository' $username and provide them with the contents of the tor.passwd.tmp file." That sounds complicated.

I tried to browse the SVN for Tor, but couldn't see how it works. I can see the changes or the descriptions, but don't have a clue how to see the actual code for it.

I don't think I would perform well on this. I'd manage to make torproject.org return a 404. :) (I know somebody would look at it, beforehand)

Basically I'm telling you that I'm not comfortable with it. I'm sorry, but I'm afraid that this is not my thing.

(Money doesn't fix this, but what would be required to ease the pain of the work that is involved fixing this?)

comment:3 Changed 7 years ago by phobos

Ok. It sounds like giving you svn commit access isn't going to work. There are gui clients, but if svn baffles you, then reading/writing the raw wml and patching it probably isn't going to work well either.

comment:4 in reply to:  description Changed 7 years ago by arma

Resolution: fixed
Status: newclosed

Replying to bastik:

On https://www.torproject.org/docs/documentation.html.en#DesignDoc you place https://gitweb.torproject.org/torspec.git?a=blob_plain;hb=HEAD;f=dir-spec-v1.txt at "The specifications aim to give developers enough information to build a compatible version of Tor: (point 2, the second link)", which returns a 404.

I can't see v1 in torspec.git (root?), while specs with no version number is there and version 2 as well.

v1 has been placed in "attic" [whatever that is] (https://gitweb.torproject.org/torspec.git/tree/HEAD:/attic)

https://gitweb.torproject.org/torspec.git/blob/HEAD:/attic/dir-spec-v1.txt

I fixed it by removing the link from the documentation page. That spec is indeed no longer in use anywhere.

The "folder" named "attic" contains two obsolete specs and "bridge specs", which I assume are not obsolete yet. While I don't know what attic is and bet that "bridges-spec" is an up-to-date spec, I suggest to create a "folder" called "obsolete" and move all obsolete specs there, while moving bridges-spec.txt to torspec.git (root?).

bridges-spec isn't really a spec so much as some documentation I wrote long ago. It isn't particularly useful anymore, compared to the html files I wrote afterwards.

Thanks!

Note: See TracTickets for help on using tickets.