name mode size
gsoc10-proposal-dnselRewrite.html 100644 19.92kB
gsoc10-proposal-metrics.pdf 100644 66.36kB
gsoc10-proposal-soat.txt 100644 8.02kB
gsoc11-proposal-armGtkFrontend.pdf 100644 104.89kB
gsoc11-proposal-blockingResistance.pdf 100644 148.97kB
gsoc11-proposal-metadataToolkit.pdf 100644 76.67kB
gsoc12-proposal-stemImprovements.html 100644 25.56kB
To quickly get set up simply do the following... 1. Get the website's build dependencies. % sudo apt-get install wml asciidoc 2. Configure where to find your tor git repository. It needs this to make the manual page. % git clone % cd webwml % cp Makefile.local.sample Makefile.local [ change the TORGIT in Makefile.local to point to your tor git repo ] 3. Make the website. % make You should now be able to point your browser at the locally generated site... file:///home/atagar/Desktop/tor/webwml/getinvolved/volunteer.html.en -------------------------------------------------------------------------------- Troubleshooting -------------------------------------------------------------------------------- * The build fails with "Invalid object name". If you get an error like... ---- Contents of STDERR channel: --------- fatal: Invalid object name 'tor-'. asciidoc: FAILED: manpage document title is mandatory No manpage because of asciidoc error or file not available from git at /tmp/wml.zwcq0q/wml.30867.tmp1.wml line 415. This means your tor repository is out of date. Update your tor git repository. -------------------------------------------------------------------------------- More detailed instructions from Roger -------------------------------------------------------------------------------- Here are the instructions I sent David Fifield when he asked about editing the website. I hope they are useful for you too! --Roger Copy Makefile.local.sample to Makefile.local in your webwml/ directory. Point TORGIT to a tor git. Then apt-get install wml and (alas) probably a shocking number of other debs. Then you can type 'make' and it will build the website for you locally. It's probably a smart move to see whether 'make' works before you git commit any changes to the wml files. You can edit docs/en/pluggable-transports.wml (and that is the right source file to edit, not the html). But go take a look at that file. You'll notice it has a bunch of tags like <version-torbrowserbundle>. If you're just bumping version numbers, you probably just want to change the definition of those tags. They're in include/versions.wmi (Every once in a while you may need to edit pluggable-transports.wml too -- generally when you change the file name so drastically that just changing the versions.wmi tags isn't enough.) Pushes to the master branch of the git repository will cause the website to get re-built and published. Pushing to the staging branch will update Alas, isn't in version control. You write to it by ssh'ing to and going to /srv/ and then sticking your stuff there. When you want it to go live, you run "static-update-component" on dist-master. Weasel has hopes that somebody will write some scripts to make maintaining packages in dist/ less awful -- automatically check that they have signatures and that the sigs match, that the items on the website are in fact in dist, only allow certain people to put files in certain places, etc. One day! :)