Opened 7 years ago

Closed 7 years ago

#6380 closed task (implemented)

Create research.tpo/techreports.html and research.tpo/techreports/ for Tor tech reports

Reported by: karsten Owned by: karsten
Priority: Medium Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Keywords:
Cc: arma, phobos, weasel Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

In #5405 we discuss creating a place to keep track of our tech reports. I'd like to keep the sources in a Git repo (#6378) and put the PDFs on the Tor website. Having an HTML page www.tpo/techreports.html (or similar) for links to tech reports and a directory www.tpo/techreports/ (or similar) for the tech report PDFs would be very useful. How would I upload PDFs to the new directory without adding them to SVN? Thanks!

Child Tickets

Change History (13)

comment:1 Changed 7 years ago by phobos

I propose techreports.torproject.org. I feel the last thing we need is more webpages and subdirectories on the website. Techreports could then be managed in git. The website is managed in svn currently.

comment:2 Changed 7 years ago by karsten

Cc: arma added

A separate website sounds fine. But should we then extend the scope to research.tpo and create a research.tpo/techreports.html and research.tpo/techreports/ directory for PDFs? The new research.tpo could be the new starting point for all research.

comment:3 Changed 7 years ago by phobos

Is this the start of an implementation of #5998 ?

comment:4 in reply to:  3 Changed 7 years ago by karsten

Replying to phobos:

Is this the start of an implementation of #5998 ?

Sure, it could be. I can start a research.tpo with some static HTML/CSS in a Git repo. Want me to do that?

comment:5 Changed 7 years ago by arma

Depending on the color we want for the bike shed, we might later regret having a single shared git repo for both the website html and the pdfs. Some of these pdfs will be big, and "git clone this 500MB thing if you want to edit the research frontpage" will get klunky.

comment:6 Changed 7 years ago by karsten

Agreed, I'd like to avoid adding the PDFs to the research website Git repo. On metrics.tpo, there's a papers/ directory that I use for PDFs. Those PDFs are not in the Git repo. If someone wanted to mirror the website, they'd have to clone the Git repo and copy the PDFs. Probably not the most elegant solution, but one that doesn't require people to clone a 500MB thing. Are there better solutions?

comment:7 Changed 7 years ago by karsten

Cc: phobos added
Owner: changed from phobos to karsten
Status: newassigned
Summary: Create www.tpo/techreports.html and www.tpo/techreports/ for Tor tech reportsCreate research.tpo/techreports.html and research.tpo/techreports/ for Tor tech reports

What's the process for getting a research.tpo website started?

comment:8 Changed 7 years ago by arma

Cc: weasel added
Component: WebsiteTor Sysadmin Team

weasel, can you help us do the parts of this that you can help with?

comment:9 Changed 7 years ago by phobos

I'm confused as to why this is anything more than login to vescum, create the directory, and it gets served up.

comment:10 Changed 7 years ago by phobos

it already exists, i just fixed perms, vescum:/srv/techreports.torproject.org

comment:11 Changed 7 years ago by karsten

So, techreports.tpo, not research.tpo?

I'm fine with that, but didn't you want this to be the start of an implementation of #5998 with one site being "3. researchers who want to see designs, specifications, current research areas, how tor fits into the anonymous communications research field, open research questions and projects (great for masters or PhD thesis)"

comment:12 Changed 7 years ago by arma

Right. I think we should make research.torproject.org, not techreport.torproject.org. As described in the above comments.

comment:13 Changed 7 years ago by karsten

Resolution: implemented
Status: assignedclosed

weasel just moved techreports.tpo to research.tpo on vescum and gave me write access to the htdocs/ directory. Will start from there. Closing. Thanks!

Note: See TracTickets for help on using tickets.