Opened 8 years ago

Closed 8 years ago

#7644 closed task (implemented)

Migrate to

Reported by: hellais Owned by: hellais
Priority: Medium Milestone:
Component: Archived/Ooni Version:
Severity: Keywords: ooni_website, SponsorH201208
Cc: aagbsn, weasel, phobos Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


The content that is currently stored on and should be move to ooni.tpo.

I would propose structuring the site as follows:

  • The main site:


This will be generated via a jekyll driven build script ( I need to digg up where this code used to be because it appears to be no longer present on the github repo of ooniprobe

  • The docs:


These shall be generated via sphinx-build via make html. It is unclear from: if this should happen on our local machines or if can automate this on the webserver.

weasel, phobos: ideas?

  • The releases:



Initially we will only be doing one release which will be the .tar.gz of the source code from the git repository.

The priority for these tasks should be in the order stated above.

Weasel: what web server should we be using? Is that already setup?

Child Tickets

Change History (1)

comment:1 Changed 8 years ago by hellais

Resolution: implemented
Status: newclosed

This has been completed.

What is still missing has been split into two separate tickets: and

Note: See TracTickets for help on using tickets.