Browse code

Remove vidalia-related docs and downloads

The downloads are horribly outdated, the docs are confusing and long.
Without a proper Vidalia maintainer and someone making packages, this
has no future.

Sebastian Hahn authored on08/02/2015 17:55:35
Showing19 changed files
... ...
@@ -24,7 +24,6 @@ about/volunteers.html.en
24 24
 docs/N900.html.en
25 25
 docs/android.html.en
26 26
 docs/bridges.html.en
27
-docs/debian-vidalia.html.en
28 27
 docs/debian.html.en
29 28
 docs/documentation.html.en
30 29
 docs/faq-abuse.html.en
... ...
@@ -33,7 +32,6 @@ docs/hidden-services.html.en
33 32
 docs/installguide.html.en
34 33
 docs/manual.html.en
35 34
 docs/pluggable-transports.html.en
36
-docs/proxychain.html.en
37 35
 docs/rpms.html.en
38 36
 docs/running-a-mirror.html.en
39 37
 docs/short-user-manual.html.en
... ...
@@ -91,7 +89,6 @@ projects/torbrowser-details.html.en
91 89
 projects/torbrowser.html.en
92 90
 projects/tordnsel.html.en
93 91
 projects/torweather.html.en
94
-projects/vidalia.html.en
95 92
 torbutton/index.html.en
96 93
 torbutton/torbutton-faq.html.en
97 94
 torbutton/torbutton-options.html.en
... ...
@@ -23,10 +23,6 @@ RewriteRule ^tordnsel/dist/(.*) /dist/tordnsel/$1 [R=301,L]
23 23
 # Overview
24 24
 RewriteRule ^overview(.*) /about/overview$1 [R=301,L]
25 25
 
26
-# Vidalia
27
-RewriteRule ^vidalia/dist/(.*) /dist/vidalia/$1 [R=301,L]
28
-RewriteRule ^vidalia(.*) /projects/vidalia [R=301,L]
29
-
30 26
 # Press
31 27
 RewriteRule ^press/$ /press/press [R=301,L]
32 28
 RewriteRule ^press/index.html(.*) /press/press.html$1 [R=301,L]
... ...
@@ -40,7 +40,7 @@ in Tor's early days.</dd>
40 40
 Polipo to Windows.  He currently helps with the libevent
41 41
 bufferevent code.</dd>
42 42
 <dt>Matt Edman</dt>
43
-<dd>Original developer for <a href="<page projects/vidalia>">Vidalia</a>,
43
+<dd>Original developer for Vidalia,
44 44
 a cross-platform Tor Graphical User Interface included in the bundles.</dd>
45 45
 <dt>Geoff Goodell</dt><dd>Started the <a
46 46
 href="https://svn.torproject.org/svn/blossom/trunk/">Blossom project</a>
... ...
@@ -91,12 +91,11 @@ href="http://p56soo2ibjkx23xo.onion/">TorDNSEL code</a>.</dd>
91 91
 <dt>Tomás Touceda, Vidalia Developer</dt>
92 92
 <dd>Worked on maintenance and new development for Vidalia.</dd>
93 93
 <dt>Stephen Tyree</dt><dd> Worked during Google Summer of Code 2009 to
94
-develop a plugin API for <a href="<page projects/vidalia>">Vidalia</a>
94
+develop a plugin API for Vidalia
95 95
 and create a plugin to allow HerdictWeb integration, a project aiming
96 96
 at identifying website inaccessibility using user submissions.</dd>
97 97
 <dt>Camilo Viecco</dt><dd> Worked on
98
-Providing Blossom functionality to Vidalia (<a
99
-href="http://trac.vidalia-project.net/browser/vidalia/branches/exit-country">svn</a>) as part of Google Summer of Code 2008.</dd>
98
+Providing Blossom functionality to Vidalia as part of Google Summer of Code 2008.</dd>
100 99
 <dt>Fred von Lohmann</dt><dd>Fred served on our Board of Directors
101 100
 from 2006 through 2009.</dd>
102 101
 <dt>Shondoit Walker, Build Developer</dt>
... ...
@@ -327,9 +327,6 @@
327 327
     BridgeRelay 1
328 328
     Exitpolicy reject *:*
329 329
     </code></pre></li>
330
-    <li><a href="<page docs/tor-doc-relay>">or using Vidalia</a>:<br>
331
-    <img src="$(IMGROOT)/vidalia-bridges-setup.png" alt="Vidalia's Sharing
332
-    settings page"></li>
333 330
     </ul>
334 331
     </p>
335 332
 
... ...
@@ -346,10 +343,8 @@
346 343
 
347 344
     <p>
348 345
     Your bridge relay will automatically publish its address to the bridge
349
-    authority, which will give it out via https or email as above. You can
350
-    also tell a user about your bridge directly: if you're using Vidalia,
351
-    you can copy-and-paste the bridge address from the Settings window. If
352
-    you're on Linux or BSD, you can construct the bridge address manually
346
+    authority, which will give it out via https or email as above.
347
+    You can construct the bridge address
353 348
     using the <a href="#Understanding">format above</a> (you can find the
354 349
     fingerprint in your Tor log files or in <tt>/var/lib/tor/fingerprint</tt>
355 350
     depending on your platform).
356 351
deleted file mode 100644
... ...
@@ -1,138 +0,0 @@
1
-## translation metadata
2
-# Revision: $Revision$
3
-# Translation-Priority: 3-low
4
-
5
-#include "head.wmi" TITLE="Vidalia: Debian/Ubuntu Instructions" CHARSET="UTF-8"
6
-<div id="content" class="clearfix">
7
-  <div id="breadcrumbs">
8
-    <a href="<page index>">Home &raquo; </a>
9
-    <a href="<page docs/documentation>">Documentation &raquo; </a>
10
-    <a href="<page docs/debian-vidalia>">Vidalia Debian/Ubuntu Instructions</a>
11
-  </div>
12
-  <div id="maincol"> 
13
-<a id="debian"></a>
14
-<a id="packages"></a>
15
-<h2><a class="anchor" href="#debian">Vidalia on Ubuntu or Debian</a></h2>
16
-<br />
17
-
18
-<p>
19
-<b>Do not use the packages in Ubuntu's universe.</b> They are unmaintained
20
-and out of date. That means you'll be missing stability and security
21
-fixes.
22
-</p>
23
-
24
-<p>
25
-You'll need to set up our package repository before you can fetch
26
-Tor. First, you need to figure out the name of your distribution. Here's
27
-a quick mapping:
28
-<ul>
29
-<li> Ubuntu 14.10 is "utopic"</li>
30
-<li> Ubuntu 14.04.* is "trusty"</li>
31
-<li> Ubuntu 13.10 is "saucy"</li>
32
-<li> Ubuntu 13.04 is "raring"</li>
33
-<li> Ubuntu 12.04.* is "precise"</li>
34
-<li> Ubuntu 11.10 is "oneiric"</li>
35
-<li> Ubuntu 11.04 is "natty"</li>
36
-<li> Ubuntu 10.10 or Trisquel 4.5 is "maverick"</li> 
37
-<li> Ubuntu 10.04 or Trisquel 4.0 is "lucid"</li>
38
-<li> Ubuntu 9.10 or Trisquel 3.5 is  "karmic"</li>
39
-<li> Ubuntu 9.04 is "jaunty"</li>
40
-<li> Ubuntu 8.10 is "intrepid"</li>
41
-<li> Ubuntu 8.04 is "hardy"</li> 
42
-<li> Debian Etch is "etch"</li>
43
-<li> Debian Lenny is "lenny"</li>
44
-</ul>
45
-
46
-Then add this line to your
47
-<tt>/etc/apt/sources.list</tt>
48
-file:<br />
49
-<pre>
50
-deb     http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
51
-</pre>
52
-where you substitute the above word (etch, lenny, sid, karmic, jaunty,
53
-intrepid, hardy) in place of &lt;DISTRIBUTION&gt;.
54
-</p>
55
-
56
-<p>
57
-Then add the gpg key used to sign the packages by running the following
58
-commands at your command prompt:
59
-<pre>
60
-gpg --keyserver keys.gnupg.net --recv 886DDD89
61
-gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
62
-</pre>
63
-Now refresh your sources and install Vidalia by running the following
64
-commands at your command prompt:
65
-<pre>
66
-apt-get update
67
-apt-get install vidalia deb.torproject.org-keyring
68
-</pre>
69
-</p>
70
-
71
-<p>
72
-Now Vidalia is installed and running. Move on to <a href="<page
73
-docs/tor-doc-unix>#using">step two</a> of the "Vidalia on Linux/Unix"
74
-instructions.
75
-</p>
76
-
77
-<p style="font-size: small">
78
-The DNS name <code>deb.torproject.org</code> is actually a set of independent
79
-servers in a DNS round robin configuration.  If you for some reason cannot
80
-access it you might try to use the name of one of its part instead.  Try
81
-<code>deb-master.torproject.org</code>,
82
-<code>mirror.netcologne.de</code> or
83
-<code>vidalia.mirror.youam.de</code>.
84
-</p>
85
-
86
-<hr />
87
-
88
-<a id="source"></a>
89
-<h2><a class="anchor" href="#source">Building from source</a></h2>
90
-<br />
91
-
92
-<p>
93
-If you want to build your own debs from source you must first add an
94
-appropriate <tt>deb-src</tt> line to <tt>sources.list</tt>.
95
-<pre>
96
-deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
97
-</pre>
98
-You also need to install the necessary packages to build your own debs and the
99
-packages needed to build Vidalia:
100
-<pre>
101
-apt-get install build-essential fakeroot devscripts qt4-dev-tools qt4-designer libqt4-dev g++ cmake
102
-apt-get build-dep vidalia
103
-</pre>
104
-Then you can build Vidalia in ~/debian-packages:
105
-<pre>
106
-mkdir ~/debian-packages; cd ~/debian-packages
107
-apt-get source vidalia
108
-cd vidalia-*
109
-debuild -rfakeroot -uc -us
110
-cd ..
111
-</pre>
112
-Now you can install the new package:
113
-<pre>
114
-sudo dpkg -i vidalia_*.deb
115
-</pre>
116
-</p>
117
-
118
-<p>
119
-Now Vidalia is installed and running. Move on to <a href="<page
120
-docs/tor-doc-unix>#using">step two</a> of the "Vidalia on Linux/Unix"
121
-instructions.
122
-</p>
123
-
124
-<hr />
125
-
126
-<p>If you have suggestions for improving this document, please <a
127
-href="<page about/contact>">send them to us</a>. Thanks!</p>
128
-
129
-  </div>
130
-  <!-- END MAINCOL -->
131
-  <div id = "sidecol">
132
-#include "side.wmi"
133
-#include "info.wmi"
134
-  </div>
135
-  <!-- END SIDECOL -->
136
-</div>
137
-<!-- END CONTENT -->
138
-#include <foot.wmi>  
... ...
@@ -109,8 +109,6 @@ unsafe?</a></li>
109 109
     <p>Tor Browser (3.x and later):</p>
110 110
 
111 111
     <ul>
112
-    <li><a href="#WhereDidVidaliaGo">Where did the world map (Vidalia)
113
-    go?</a></li>
114 112
     <li><a href="#DisableJS">How do I disable JavaScript?</a></li>
115 113
     <li><a href="#VerifyDownload">How do I verify the download
116 114
     (sha256sums.txt)?</a></li>
... ...
@@ -662,8 +660,7 @@ handle
662 660
     </li>
663 661
 
664 662
     <li>
665
-    <a href="<page projects/vidalia>">Help us make Tor more usable</a>.
666
-We
663
+    Help us make Tor more usable. We
667 664
     especially need people to help make it easier to configure your Tor
668 665
     as a relay. Also, we need help with clear simple documentation to
669 666
     walk people through setting it up.
... ...
@@ -795,11 +792,8 @@ of the
795 792
 configuration
796 793
     to interface with other applications, and generally automating all
797 794
 of
798
-    the difficult and confusing steps inside Tor. We've got a start on
799
-this
800
-    with the <a href="<page projects/vidalia>">Vidalia GUI</a>, but much
801
-more work
802
-    remains &mdash; usability for privacy software has never been easy.
795
+    the difficult and confusing steps inside Tor.
796
+    Usability for privacy software has never been easy.
803 797
     </li>
804 798
 
805 799
     <li>
... ...
@@ -1497,36 +1491,6 @@ href="http://www.crowdstrike.com/community-tools/index.html#tool-79">proposed
1497 1491
     href="https://trac.torproject.org/projects/tor/ticket/8641">working
1498 1492
     on providing it</a>. </p>
1499 1493
 
1500
-    <p>In the meantime, we are providing standalone Vidalia packages for
1501
-    people who still want the map. Windows and Linux versions are <a
1502
-    href="https://people.torproject.org/~erinn/vidalia-standalone-bundles/">
1503
-    available here</a>.</p>
1504
-
1505
-    <p>To use these packages, extract them, then run the startup script.
1506
-    On Windows, this is "Start Vidalia.exe". On Linux, it is start-vidalia.
1507
-    They can be placed in a different directory from TBB (and likely should
1508
-    be). </p>
1509
-
1510
-    <p>This Vidalia package will only run properly if Tor Browser has already
1511
-    been launched. You cannot start it before launching Tor Browser. </p>
1512
-
1513
-    <p>MacOS is still under development, but in the mean time you can modify
1514
-    your TBB 2.x to be a standalone Vidalia (and then use it after starting
1515
-    TBB 3.x) by opening your TBB 2.x vidalia.conf file in an editor and
1516
-    replacing its contents with just these lines:</p>
1517
-
1518
-    <pre>
1519
-    [General]
1520
-    LanguageCode=en
1521
-
1522
-    [Tor]
1523
-    ControlPort=9151
1524
-    TorExecutable=.
1525
-    Torrc=.
1526
-    DataDirectory=.
1527
-    AuthenticationMethod=cookie
1528
-    </pre>
1529
-
1530 1494
     <hr>
1531 1495
 
1532 1496
     <a id="DisableJS"></a>
... ...
@@ -1577,8 +1541,7 @@ href="http://www.crowdstrike.com/community-tools/index.html#tool-79">proposed
1577 1541
 
1578 1542
     <p>
1579 1543
     That's actually a feature, since it's discarding your application-level
1580
-    browser data too. But it sure is a surprising feature, for people who
1581
-    are used to Vidalia's "new identity" behavior.
1544
+    browser data too.
1582 1545
     </p>
1583 1546
 
1584 1547
     <p>
... ...
@@ -1590,12 +1553,6 @@ href="http://www.crowdstrike.com/community-tools/index.html#tool-79">proposed
1590 1553
     to follow progress there.
1591 1554
     </p>
1592 1555
 
1593
-    <p>
1594
-    In the mean time, you can get Vidalia's old "newnym" functionality by
1595
-    attaching a Vidalia to your TBB 3.x. See the instructions <a
1596
-    href="#WhereDidVidaliaGo">above</a>.
1597
-    </p>
1598
-
1599 1556
     <hr>
1600 1557
 
1601 1558
     <a id="ConfigureRelayOrBridge"></a>
... ...
@@ -1612,15 +1569,9 @@ href="http://www.crowdstrike.com/community-tools/index.html#tool-79">proposed
1612 1569
     You can then use TBB independent of that.
1613 1570
     </p>
1614 1571
 
1615
-    <p>
1616
-    Second (simpler option), if you're on Windows, you can fetch the separate
1617
-    "Vidalia relay bundle" or "Vidalia bridge bundle" from the download page
1618
-    and then use that (again you can use TBB independent of it).
1619
-    </p>
1620 1572
 
1621 1573
     <p>
1622
-    Third (complex option), you can either hook your Vidalia up to TBB (as
1623
-    described in the FAQ above) or edit your torrc file (in Data/Tor/torrc)
1574
+    Second (complex option), you can edit your torrc file (in Data/Tor/torrc)
1624 1575
     directly to add the following lines:
1625 1576
     </p>
1626 1577
     <pre>
... ...
@@ -1719,14 +1670,7 @@ on Tor's configuration.
1719 1670
 logs?</a></h3>
1720 1671
 
1721 1672
 <p>
1722
-If you installed a Tor bundle that includes Vidalia, then Vidalia has a
1723
-window called "Message Log" that will show you Tor's log messages. Click
1724
-on "Advanced" to see more details. You can click on "Settings" to change
1725
-your log verbosity or save the messages to a file. You're all set.
1726
-</p>
1727
-
1728
-<p>
1729
-If you're not using Vidalia, you'll have to go find the log files by
1673
+You'll have to go find the log files by
1730 1674
 hand. Here are some likely places for your logs to be:
1731 1675
 </p>
1732 1676
 
... ...
@@ -1823,14 +1767,9 @@ Once you've got Tor Browser up and running, the first question to
1823 1767
 ask is whether your Tor client is able to establish a circuit.
1824 1768
 </p>
1825 1769
 
1826
-<p>If Tor can establish a circuit, the onion icon in
1827
-Vidalia will turn green (and if you're running Tor Browser, it
1828
-will
1829
-automatically launch a browser for you). You can also check in the
1830
-Vidalia
1831
-Control Panel to make sure it says "Connected to the Tor
1832
-network!" under Status. For those not using Vidalia, check your <a
1833
-href="#Logs">Tor logs</a> for
1770
+<p>If Tor can establish a circuit, Tor Browser will
1771
+automatically launch the browser for you. You can also check in the
1772
+<a href="#Logs">Tor logs</a> for
1834 1773
 a line saying that Tor "has successfully opened a circuit. Looks like
1835 1774
 client functionality is working."
1836 1775
 </p>
... ...
@@ -1840,8 +1779,6 @@ If Tor can't establish a circuit, here are some hints:
1840 1779
 </p>
1841 1780
 
1842 1781
 <ol>
1843
-<li>Are you sure Tor is running? If you're using Vidalia, you may have
1844
-to click on the onion and select "Start" to launch Tor.</li>
1845 1782
 <li>Check your system clock. If it's more than a few hours off, Tor will
1846 1783
 refuse to build circuits. For Microsoft Windows users, synchronize your
1847 1784
 clock under the clock -&gt; Internet time tab. In addition, correct the
... ...
@@ -2021,14 +1958,11 @@ few outgoing ports.</a></h3>
2021 1958
 
2022 1959
 <p>
2023 1960
 If your firewall works by blocking ports, then you can tell Tor to only
2024
-use the ports that your firewall permits by adding "FascistFirewall 1"
1961
+use the ports when you start your Tor Browser. Or you can add the ports
1962
+that your firewall permits by adding "FascistFirewall 1"
2025 1963
 to
2026 1964
 your <a href="<page docs/faq>#torrc">torrc
2027
-configuration file</a>, or by clicking "My firewall only lets me connect
2028
-to certain ports" in Vidalia's Network Settings window.
2029
-</p>
2030
-
2031
-<p>
1965
+configuration file</a>.
2032 1966
 By default, when you set this Tor assumes that your firewall allows only
2033 1967
 port 80 and port 443 (HTTP and HTTPS respectively). You can select a
2034 1968
 different set of ports with the FirewallPorts torrc option.
... ...
@@ -2552,11 +2486,11 @@ href="#DefaultExitPorts">restricts</a>
2552 2486
     some due to abuse potential (e.g. mail) and some since
2553 2487
     the Tor network can't handle the load (e.g. default
2554 2488
     file-sharing ports). You can change your exit policy
2555
-    using Vidalia's "Sharing" tab, or by manually editing your
2489
+    by editing your
2556 2490
     <a href="<page docs/faq>#torrc">torrc</a>
2557 2491
     file. If you want to avoid most if not all abuse potential, set it
2558 2492
 to
2559
-    "reject *:*" (or un-check all the boxes in Vidalia). This setting
2493
+    "reject *:*". This setting
2560 2494
 means
2561 2495
     that your relay will be used for relaying traffic inside the Tor
2562 2496
 network,
... ...
@@ -2832,8 +2766,7 @@ service?</a></h3>
2832 2766
 
2833 2767
 <p>
2834 2768
  You can run Tor as a service on all versions of Windows except Windows
2835
- 95/98/ME. This way you can run a Tor relay without needing to always have
2836
- Vidalia running.
2769
+ 95/98/ME.
2837 2770
 </p>
2838 2771
 <p>
2839 2772
 If you've already configured your Tor to be a relay, please note that when
... ...
@@ -3990,9 +3923,8 @@ we
3990 3923
 maintaining
3991 3924
     a relay. We've made a lot of progress with easy configuration in the
3992 3925
 past
3993
-    few years: Vidalia has an easy relay configuration interface, and
3994
-supports
3995
-    uPnP too. Tor is good at automatically detecting whether it's
3926
+    few years:
3927
+    Tor is good at automatically detecting whether it's
3996 3928
 reachable and
3997 3929
     how much bandwidth it can offer.
3998 3930
     </p>
3999 3931
deleted file mode 100644
... ...
@@ -1,55 +0,0 @@
1
-## translation metadata
2
-# Revision: $Revision$
3
-# Translation-Priority: 1-high
4
-
5
-#include "head.wmi" TITLE="Tor Project: Configuring Tor to use a Proxy" CHARSET="UTF-8"
6
-<div id="content" class="clearfix">
7
-  <div id="breadcrumbs">
8
-    <a href="<page index>">Home &raquo; </a>
9
-    <a href="<page docs/documentation>">Documentation &raquo; </a>
10
-    <a href="<page docs/proxychain>">Configuring Tor to use a Proxy</a>
11
-  </div>
12
-  <div id="maincol"> 
13
-    <a id="proxychain"></a>
14
-    <h2><a class="anchor" href="#proxychain">Tor: Configuring Tor to use a Proxy</a></h2>
15
-    <hr>
16
-    
17
-    <p>
18
-      The current version of Tor and the Vidalia Graphical Tor Controller
19
-      support the ability to use any HTTPS or SOCKS proxy to get
20
-      access to the Tor Network.  This means even if Tor is blocked by
21
-      your local network, open proxies can be safely used to connect to
22
-      the Tor Network and on to the uncensored Internet.  A caveat is that
23
-      the open proxy host will see you are using Tor, but it will not be able
24
-      to read your traffic as it is still wrapped in layers of encryption.
25
-    </p>
26
-    
27
-    <p>
28
-      These steps assume you have a functional Tor/Vidalia configuration,
29
-      and you have found a list of HTTPS, SOCKS4, or SOCKS5 proxies. (To
30
-      clarify, an HTTPS proxy is an HTTP proxy that also supports
31
-      CONNECT requests.)
32
-      <ol>
33
-      <li>Open the Vidalia Control Panel, click on Settings.</li>
34
-      <li>Click Network.  Select "I use a proxy to access the Internet".</li>
35
-      <li>On the Address line, enter the open proxy address.  This can be a hostname or IP Address.</li>
36
-      <li>Enter the port for the proxy.</li>
37
-      <li>Generally, you do not need a Username and Password.  If you do, enter the information in the proper fields.</li>
38
-      <li>Choose the Type of proxy you are using, whether HTTP/HTTPS, SOCKS4, or SOCKS5.</li>
39
-      <li>Push the Ok button.  Vidalia and Tor are now configured to use a proxy to access the rest of the Tor Network.</li>
40
-      </ol>
41
-    </p>
42
-    <br><br>
43
-    <img src="$(IMGROOT)/vidalia-proxy.png" alt="Vidalia's Network Proxy settings page">
44
-    <br><br>
45
-    
46
-  </div>
47
-  <!-- END MAINCOL -->
48
-  <div id = "sidecol">
49
-#include "side.wmi"
50
-#include "info.wmi"
51
-  </div>
52
-  <!-- END SIDECOL -->
53
-</div>
54
-<!-- END CONTENT -->
55
-#include <foot.wmi>  
... ...
@@ -33,9 +33,6 @@
33 33
           {'url'  => 'docs/debian',
34 34
            'txt'  => 'Installing Tor on Debian/Ubuntu',
35 35
           },
36
-          {'url'  => 'docs/debian-vidalia',
37
-           'txt'  => 'Installing Vidalia on Debian/Ubuntu',
38
-          },
39 36
           {'url'  => 'docs/rpms',
40 37
            'txt'  => 'Installing Tor on Fedora/CentOS',
41 38
           },
... ...
@@ -17,8 +17,8 @@
17 17
     <li>Roger Dingledine (0x28988BF5 and 0x19F78451) or Nick Mathewson
18 18
     (0x165733EA, or its subkey 0x8D29319A) sign the Tor source code
19 19
     tarballs.</li>
20
-    <li>Erinn Clark (0x63FEE659) signs the Tor Browser Bundles, Vidalia
21
-    bundles, and many other packages. She signs RPMs with her other key
20
+    <li>Erinn Clark (0x63FEE659) signs the Tor Browser Bundles
21
+    and many other packages. She signs RPMs with her other key
22 22
     (0xF1F5C9B5). Andrew Lewman (0x31B0974B, 0x6B4D6475) used to sign
23 23
     packages for RPMs, Windows, and OS X.</li>
24 24
     <li>Tor Project Archive (0x886DDD89) signs the deb.torproject.org
... ...
@@ -26,7 +26,7 @@
26 26
     <br>
27 27
     
28 28
     <p>
29
-    The advanced Tor without any graphical user interface can be installed using <a href="http://brew.sh">the Homebrew package manager</a>. It is most suitable if you want to use Tor as a SOCKS proxy for applications other than web browsing, or run a Tor relay/bridge to help other Tor users. If you use the command-line Tor, you might be interested in <a href="<page projects/arm>">arm</a>, a command-line Tor monitor and alternative to the Vidalia GUI.
29
+    The advanced Tor without any graphical user interface can be installed using <a href="http://brew.sh">the Homebrew package manager</a>. It is most suitable if you want to use Tor as a SOCKS proxy for applications other than web browsing, or run a Tor relay/bridge to help other Tor users. If you use the command-line Tor, you might be interested in <a href="<page projects/arm>">arm</a>, a command-line Tor monitor.
30 30
     </p>
31 31
     
32 32
     <p>If you don't have Homebrew installed, open a terminal window and run:</p>
... ...
@@ -120,8 +120,6 @@
120 120
     <li>Open Finder and click on Applications.</li>
121 121
     <li>Drag /Applications/TorBrowser to the Trash.</li>
122 122
     <li>Remove /Library/Torbutton from your system.</li>
123
-    <li>In your User or home directory, go to Library, remove the Vidalia
124
-    directory</li>
125 123
     </ol>
126 124
     
127 125
     <p>Tor Browser is now completely removed from your system.</p>
... ...
@@ -37,20 +37,13 @@
37 37
     with those operating systems.
38 38
     </p>
39 39
 
40
-    <p>Windows users can use the Vidalia Bridge Bundle, the Vidalia Relay
41
-    Bundle and the Vidalia Exit Bundle, which come preconfigured to run
42
-    Tor as a bridge, a non-exit relay, or an exit relay. Get them from
43
-    the <a href="<page download/download>">download page</a>, and use
44
-    the graphical instructions below for help setting them up.
45
-    </p>
46
-
47 40
     <p>Alas, since Vidalia (a graphical interface for Tor) is <a
48 41
     href="<page docs/faq>#WhereDidVidaliaGo">no longer included</a>
49 42
     in Tor Browser, there are currently no
50
-    easy relay packages for OS X users. One option might be to run
43
+    easy relay packages for Windows and OS X users. One option might be to run
51 44
     Debian in a VM, or use a different means of getting a Tor binary on
52
-    your system (Homebrew, Macports). Please help make this process
53
-    easier!
45
+    your system (Expert Bundle, Homebrew, Macports). Please help make
46
+    this process easier!
54 47
     </p>
55 48
 
56 49
     <hr>
... ...
@@ -59,7 +52,7 @@
59 52
     <br />
60 53
 
61 54
     <p>
62
-    You can set up a relay without using Vidalia if you wish. Tor's
55
+    Tor's
63 56
     configuration file is named 'torrc'. In the Tor Browser folder, it's
64 57
     located at</p>
65 58
     <pre>Data\Tor\torrc</pre>
... ...
@@ -33,9 +33,6 @@
33 33
           {'url'  => 'docs/debian',
34 34
            'txt'  => 'Installing Tor on Debian/Ubuntu',
35 35
           },
36
-          {'url'  => 'docs/debian-vidalia',
37
-           'txt'  => 'Installing Vidalia on Debian/Ubuntu',
38
-          },
39 36
           {'url'  => 'docs/tor-doc-osx',
40 37
            'txt'  => 'Installing Tor on Mac OS X',
41 38
           },
... ...
@@ -72,9 +69,6 @@
72 69
           },
73 70
           {'url'  => 'docs/tor-manual-dev',
74 71
            'txt'  => 'Tor -alpha Manual',
75
-          },
76
-          {'url'  => 'docs/proxychain',
77
-           'txt'  => 'Configuring Tor to use a Proxy Server',
78 72
           }]
79 73
       },
80 74
       {
... ...
@@ -57,45 +57,6 @@ you are used to. Please read the <a href="#warning">full list of warnings</a> fo
57 57
 	  <em>Version <version-torbrowserbundle> - Windows 8, 7, Vista, and XP</em>
58 58
 	  <p>Everything you need to safely browse the Internet. <a href="<page projects/torbrowser>">Learn more &raquo;</a></p>
59 59
 	</div>
60
-<!-- VIDALIA BRIDGE BUNDLE -->
61
-	<div class="package">
62
-	  <div class="downloads">
63
-	    <a class="button" href="<package-win32-bridge-bundle-stable>"><span class="strong">Download</span><span class="normal">Vidalia Bridge Bundle </span></a>
64
-	    <div class="sig">
65
-	      (<a href="<package-win32-bridge-bundle-stable>.asc">sig</a>) <a class="siginfo" href="<page docs/verifying-signatures>">What's This?</a>
66
-	    </div>
67
-	  </div>
68
-
69
-	  <h2>Vidalia Bridge Bundle</h2>
70
-	  <em>Windows 8, 7, Vista, and XP</em>
71
-	  <p>A Vidalia Bundle which is configured to be a <a href="<page docs/bridges>">bridge</a> by default. This helps censored users reach the Tor network.</p>
72
-	</div>
73
-<!-- VIDALIA RELAY BUNDLE -->
74
-	<div class="package">
75
-	  <div class="downloads">
76
-	    <a class="button" href="<package-win32-relay-bundle-stable>"><span class="strong">Download</span><span class="normal">Vidalia Relay Bundle </span></a>
77
-	    <div class="sig">
78
-	      (<a href="<package-win32-relay-bundle-stable>.asc">sig</a>) <a class="siginfo" href="<page docs/verifying-signatures>">What's This?</a>
79
-	    </div>
80
-	  </div>
81
-
82
-	  <h2>Vidalia Relay Bundle</h2>
83
-	  <em>Windows 8, 7, Vista, and XP</em>
84
-	  <p>A Vidalia Bundle which is configured to be a non-exit <a href="<page docs/tor-doc-relay>">relay</a> by default. This helps grow the Tor network.</p>
85
-	</div>
86
-<!-- VIDALIA EXIT BUNDLE -->
87
-	<div class="package">
88
-	  <div class="downloads">
89
-	    <a class="button" href="<package-win32-exit-bundle-stable>"><span class="strong">Download</span><span class="normal">Vidalia Exit Bundle</span></a>
90
-	    <div class="sig">
91
-	      (<a href="<package-win32-exit-bundle-stable>.asc">sig</a>) <a class="siginfo" href="<page docs/verifying-signatures>">What's This?</a>
92
-	    </div>
93
-	  </div>
94
-
95
-	  <h2>Vidalia Exit Bundle</h2>
96
-	  <em>Windows 8, 7, Vista, and XP</em>
97
-	  <p>A Vidalia Bundle which is configured to be an <a href="<page docs/tor-doc-relay>">exit relay</a> by default. <strong>Please read these <a href="https://blog.torproject.org/running-exit-node">tips for running an exit node with minimal harassment</a> before you get started!</strong></p>
98
-	</div>
99 60
 <!-- EXPERT BUNDLE -->
100 61
 	<div class="package">
101 62
 	  <div class="downloads">
... ...
@@ -38,7 +38,7 @@ one role, so combination developer/activists are very welcome.</p>
38 38
 <p>The best way to get noticed as a good developer is to join the community
39 39
 and start helping out. Smart code commits and ideas are welcome anytime.
40 40
 We have a great core group of developers working on the Tor software
41
-itself as well as supporting software like Vidalia, Torbutton, etc. All
41
+itself as well as supporting software like Torbutton, etc. All
42 42
 of our contractors came through volunteering first.</p>
43 43
 
44 44
 <p>Periodically we get new funding to work on more development
... ...
@@ -22,10 +22,9 @@ transifex.com/projects/p/torproject/</a>.
22 22
     <p>
23 23
     The Tor bundles include several different programs, all of which need
24 24
     translation help. In order of importance they are:
25
-    <a href="<page projects/vidalia>">Vidalia</a>,
26 25
     <a href="<page docs/torbutton/index>">Torbutton</a>, and
27 26
     <a href="https://check.torproject.org/">TorCheck</a>.
28
-    You can also help translate the Vidalia help files, the Vidalia installer,
27
+    You can also help translate
29 28
     Torbutton, <a href="<page docs/android>">Orbot</a>, and <a href="<page
30 29
     projects/gettor>">GetTor</a>.
31 30
     </p>
... ...
@@ -36,7 +35,6 @@ transifex.com/projects/p/torproject/</a>.
36 35
     </p>
37 36
 
38 37
     <a id="TTP"></a>
39
-    <a id="TTPVidalia"></a>
40 38
     <h2><a class="anchor" href="#TTP">Using Transifex</a></h2>
41 39
     <hr>
42 40
 
... ...
@@ -156,14 +156,6 @@ meetings around the world.</li>
156 156
         <td>pde, mikeperry</td>
157 157
       </tr>
158 158
 
159
-      <tr>
160
-        <td><a href="#project-vidalia">Vidalia</a></td>
161
-        <td>User Interface</td>
162
-        <td>C++, Qt</td>
163
-        <td>None</td>
164
-        <td></td>
165
-      </tr>
166
-
167 159
       <tr>
168 160
         <td><a href="#project-arm">Arm</a></td>
169 161
         <td>User Interface</td>
... ...
@@ -448,12 +440,6 @@ meetings around the world.</li>
448 440
     more secure.
449 441
     </p>
450 442
 
451
-    <a id="project-vidalia"></a>
452
-    <h3><a href="<page projects/vidalia>">Vidalia</a> (<a
453
-    href="https://gitweb.torproject.org/vidalia.git">code</a>, <a
454
-    href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Vidalia&order=priority">bug
455
-    tracker</a>)</h3>
456
-
457 443
     <p>
458 444
     The most commonly used user interface for Tor. Matt Edman started the
459 445
     project in 2006 and brought it to its current stable state. Development
... ...
@@ -898,10 +884,9 @@ meetings around the world.</li>
898 884
     <br>
899 885
     Likely Mentors: <i>Damian (atagar)</i>
900 886
     <p>
901
-    Relay operators presently have a couple options for monitoring the status
902
-    of their relay: <a
903
-    href="#project-vidalia">Vidalia</a>
904
-    which is a gui and <a href="https://www.atagar.com/arm/">arm</a> which uses
887
+    Relay operators presently have a good option for monitoring the status
888
+    of their relay:
889
+    <a href="https://www.atagar.com/arm/">arm</a> which uses
905 890
     curses. This project would be to make a new kind of monitor specifically
906 891
     for relay operators that provides a status dashboard site on localhost.
907 892
     </p>
... ...
@@ -1698,7 +1683,7 @@ try, or contact isis or sysrqb on IRC to ask for ticket suggestions or advice.
1698 1683
     <br>
1699 1684
     Don't like any of these? Look at the <a
1700 1685
     href="/press/presskit/2008-12-19-roadmap-full.pdf">Tor development
1701
-    roadmap</a> for more ideas, or just try out Tor, Vidalia, and Torbutton,
1686
+    roadmap</a> for more ideas, or just try out Tor and Tor Browser,
1702 1687
     and find out what you think needs fixing.
1703 1688
     Some of the <a href="<spectree>proposals">current proposals</a>
1704 1689
     might also be short on developers.
... ...
@@ -1722,12 +1707,6 @@ try, or contact isis or sysrqb on IRC to ask for ticket suggestions or advice.
1722 1707
     <a href="https://svn.torproject.org/svn/libevent-urz/trunk/">good
1723 1708
     start</a> on this in the summer of 2007.</li>
1724 1709
 
1725
-    <li>We need to actually start building our <a href="<page
1726
-    docs/documentation>#DesignDoc">blocking-resistance design</a>. This involves
1727
-    fleshing out the design, modifying many different pieces of Tor, adapting
1728
-    <a href="<page projects/vidalia>">Vidalia</a> so it supports the
1729
-    new features, and planning for deployment.</li>
1730
-
1731 1710
     <li>We need a flexible simulator framework for studying end-to-end
1732 1711
     traffic confirmation attacks. Many researchers have whipped up ad hoc
1733 1712
     simulators to support their intuition either that the attacks work
1734 1713
deleted file mode 100644
1735 1714
Binary files a/images/vidalia-proxy.png and /dev/null differ
... ...
@@ -7,10 +7,6 @@
7 7
 <define-tag version-win32-bundle-stable whitespace=delete>0.2.4.23</define-tag>
8 8
 <define-tag version-win32-bundle-alpha whitespace=delete>0.2.4.23</define-tag>
9 9
 
10
-<define-tag version-win32-bridge-bundle-alpha whitespace=delete>0.2.4.23-<version-vidalia-stable></define-tag>
11
-<define-tag version-win32-relay-bundle-alpha whitespace=delete>0.2.4.23-<version-vidalia-stable></define-tag>
12
-<define-tag version-win32-exit-bundle-alpha whitespace=delete>0.2.4.23-<version-vidalia-stable></define-tag>
13
-
14 10
 <define-tag version-osx-x86-bundle-stable whitespace=delete>0.2.4.20</define-tag>
15 11
 <define-tag version-osx-x86-bundle-alpha whitespace=delete>0.2.4.20</define-tag>
16 12
 
... ...
@@ -34,7 +30,6 @@
34 30
 <define-tag version-torbrowser-torbutton whitespace=delete>1.5.2</define-tag>
35 31
 <define-tag version-torbrowser-pidgin whitespace=delete>2.7.5</define-tag>
36 32
 <define-tag version-torbrowser-otr whitespace=delete>3.2</define-tag>
37
-<define-tag version-torbrowser-vidalia whitespace=delete>0.2.21</define-tag>
38 33
 <define-tag version-torimbrowserbundle whitespace=delete>1.3.21</define-tag>
39 34
 
40 35
 <define-tag version-torbrowserbundlelinux32 whitespace=delete>4.0.3</define-tag>
... ...
@@ -45,7 +40,6 @@
45 40
 <define-tag version-gnu-torbrowser-tor-components whitespace=delete>libevent-2.0.21-stable, zlib-1.2.8, openssl-1.0.0k</define-tag>
46 41
 <define-tag version-gnu-torbrowser-firefox whitespace=delete>24.2.0esr</define-tag>
47 42
 <define-tag version-gnu-torbrowser-torbutton whitespace=delete>1.5.2</define-tag>
48
-<define-tag version-gnu-torbrowser-vidalia whitespace=delete>0.2.21</define-tag>
49 43
 
50 44
 <define-tag version-torbrowserbundleosx32 whitespace=delete>4.0.3</define-tag>
51 45
 <define-tag version-torbrowserbundleosx64 whitespace=delete>2.3.25-15</define-tag>
... ...
@@ -53,10 +47,6 @@
53 47
 <define-tag version-osx-torbrowser-tor whitespace=delete>0.2.4.19</define-tag>
54 48
 <define-tag version-osx-torbrowser-firefox whitespace=delete>24.2.0esr</define-tag>
55 49
 <define-tag version-osx-torbrowser-torbutton whitespace=delete>1.5.2</define-tag>
56
-<define-tag version-osx-torbrowser-vidalia whitespace=delete>0.2.21</define-tag>
57
-
58
-<define-tag version-vidalia-stable whitespace=delete>0.2.21</define-tag>
59
-<define-tag version-vidalia-alpha whitespace=delete>0.3.1</define-tag>
60 50
 
61 51
 <define-tag version-androidbundle-tor whitespace=delete>0.2.3.10-alpha</define-tag>
62 52
 <define-tag version-androidbundle-orbot whitespace=delete>1.0.7-FINAL</define-tag>
... ...
@@ -67,34 +57,6 @@
67 57
 <define-tag package-win32-stable whitespace=delete>../dist/torbrowser/<version-torbrowserbundledir>/tor-win32-tor-<version-win32-stable>.zip</define-tag>
68 58
 <define-tag package-win32-alpha whitespace=delete>../dist/torbrowser/<version-torbrowserbundlebetadir>/tor-win32-tor-<version-win32-alpha>.zip</define-tag>
69 59
 
70
-<define-tag file-win32-bundle-stable whitespace=delete>vidalia-bundle-<version-win32-bundle-stable>-0.2.21.exe</define-tag>
71
-<define-tag package-win32-bundle-stable whitespace=delete>../dist/vidalia-bundles/<file-win32-bundle-stable></define-tag>
72
-<define-tag file-win32-bundle-alpha whitespace=delete>vidalia-bundle-<version-win32-bundle-alpha>-0.2.21.exe</define-tag>
73
-<define-tag package-win32-bundle-alpha whitespace=delete>../dist/vidalia-bundles/<file-win32-bundle-alpha></define-tag>
74
-
75
-<define-tag file-win32-bridge-bundle-stable whitespace=delete>vidalia-bridge-bundle-<version-win32-bundle-stable>-0.2.21.exe</define-tag>
76
-<define-tag package-win32-bridge-bundle-stable whitespace=delete>../dist/vidalia-bundles/<file-win32-bridge-bundle-stable></define-tag>
77
-<define-tag file-win32-bridge-bundle-alpha whitespace=delete>vidalia-bridge-bundle-<version-win32-bundle-alpha>-0.2.21.exe</define-tag>
78
-<define-tag package-win32-bridge-bundle-alpha whitespace=delete>../dist/vidalia-bundles/<file-win32-bridge-bundle-alpha></define-tag>
79
-
80
-<define-tag file-win32-relay-bundle-stable whitespace=delete>vidalia-relay-bundle-<version-win32-bundle-stable>-0.2.21.exe</define-tag>
81
-<define-tag package-win32-relay-bundle-stable whitespace=delete>../dist/vidalia-bundles/<file-win32-relay-bundle-stable></define-tag>
82
-<define-tag file-win32-relay-bundle-alpha whitespace=delete>vidalia-relay-bundle-<version-win32-bundle-alpha>-0.2.21.exe</define-tag>
83
-<define-tag package-win32-relay-bundle-alpha whitespace=delete>../dist/vidalia-bundles/<file-win32-relay-bundle-alpha></define-tag>
84
-
85
-<define-tag file-win32-exit-bundle-stable whitespace=delete>vidalia-exit-bundle-<version-win32-bundle-stable>-0.2.21.exe</define-tag>
86
-<define-tag package-win32-exit-bundle-stable whitespace=delete>../dist/vidalia-bundles/<file-win32-exit-bundle-stable></define-tag>
87
-<define-tag file-win32-exit-bundle-alpha whitespace=delete>vidalia-exit-bundle-<version-win32-bundle-alpha>-0.2.21.exe</define-tag>
88
-<define-tag package-win32-exit-bundle-alpha whitespace=delete>../dist/vidalia-bundles/<file-win32-exit-bundle-alpha></define-tag>
89
-
90
-<define-tag file-osx-x86-bundle-stable whitespace=delete>vidalia-bundle-<version-osx-x86-bundle-stable>-0.2.21-i386.dmg</define-tag>
91
-<define-tag package-osx-x86-bundle-stable whitespace=delete>../dist/vidalia-bundles/<file-osx-x86-bundle-stable></define-tag>
92
-<define-tag file-osx-x86-bundle-alpha whitespace=delete>vidalia-bundle-<version-osx-x86-bundle-alpha>-0.2.21-i386.dmg</define-tag>
93
-<define-tag package-osx-x86-bundle-alpha whitespace=delete>../dist/vidalia-bundles/<file-osx-x86-bundle-alpha></define-tag>
94
-
95
-<define-tag package-osx-ppc-bundle-stable whitespace=delete>../dist/vidalia-bundles/vidalia-bundle-<version-osx-ppc-bundle-stable>-0.2.21-ppc.dmg</define-tag>
96
-<define-tag package-osx-ppc-bundle-alpha whitespace=delete>../dist/vidalia-bundles/vidalia-bundle-<version-osx-ppc-bundle-alpha>-0.2.21-ppc.dmg</define-tag>
97
-
98 60
 <define-tag file-source-stable whitespace=delete>tor-<version-stable>.tar.gz</define-tag>
99 61
 <define-tag package-source-stable whitespace=delete>../dist/<file-source-stable></define-tag>
100 62
 <define-tag file-source-alpha whitespace=delete>tor-<version-alpha>.tar.gz</define-tag>
101 63
deleted file mode 100644
... ...
@@ -1,138 +0,0 @@
1
-## translation metadata
2
-# Revision: $Revision$
3
-# Translation-Priority: 4-optional
4
-
5
-#include "head.wmi" TITLE="Tor Project: Vidalia" CHARSET="UTF-8"
6
-<div id="content" class="clearfix">
7
-  <div id="breadcrumbs">
8
-    <a href="<page index>">Home &raquo; </a>
9
-    <a href="<page projects/projects>">Projects &raquo; </a>
10
-    <a href="<page projects/vidalia>">Vidalia &raquo; </a>
11
-  </div>
12
-  <div id="maincol">
13
-    <!-- PUT CONTENT AFTER THIS TAG -->
14
-
15
-    <h2>Vidalia</h2>
16
-    <div class="underline"></div>
17
-
18
-    <!-- BEGIN SIDEBAR -->
19
-    <div class="sidebar-left">
20
-    <img src="$(IMGROOT)/Screenshot-Vidalia-Control-Panel.png"
21
-width="261" height="255" alt="Vidalia Control Panel Screenshot"/>
22
-    </div>
23
-    <!-- END SIDEBAR -->
24
-
25
-    <p>
26
-    Vidalia is a cross-platform graphical controller for the
27
-    <a href="<page index>">Tor</a> software, built using the <a
28
-    href="http://qt.nokia.com/">Qt</a> framework. Vidalia runs on most
29
-    platforms supported by Qt 4.3 or later, including Microsoft Windows,
30
-    Apple OS X, and Linux or other Unix variants using the X11 window
31
-    system. It was originally written by Matt Edman, and is currently
32
-    maintained by Tomás Touceda.
33
-    </p>
34
-    <p>
35
-    Vidalia lets you start and stop Tor, see how much bandwidth you are
36
-    consuming, see how many circuits you currently have active, see where
37
-    these circuits are connected on a global map, view messages from
38
-    Tor about its progress and current state, and let you configure your
39
-    Tor client, bridge, or relay with a simple interface.  Included in
40
-    Vidalia is an extensive help system which helps you understand all of
41
-    the options available to you.  All of these features are translated
42
-    into a large number of languages.
43
-    </p>
44
-
45
-    <a id="Downloads"></a>
46
-    <h3><a class="anchor" href="#Downloads">Downloads</a></h3>
47
-
48
-    <p>
49
-    You should simply download Vidalia as part of a <a href="<page
50
-    download/download-easy>">Tor software bundle</a>.
51
-    <b>Users should be using Tor Browser Bundle, not installing Vidalia
52
-    themselves.</b>
53
-    </p>
54
-
55
-    <p> The most recent stable release is <version-vidalia-stable>,
56
-    and the most recent alpha release is <version-vidalia-alpha>.</p>
57
-    <ul>
58
-      <li>
59
-        <a href="<page docs/debian-vidalia>">Instructions for Debian/Ubuntu/Knoppix Repositories</a>
60
-      </li>
61
-      <li>
62
-         <a
63
-href="/dist/vidalia/vidalia-<version-vidalia-stable>.tar.gz">Stable
64
-Source Tarball</a>
65
-        (<a
66
-href="/dist/vidalia/vidalia-<version-vidalia-stable>.tar.gz.asc">sig</a
67
->)
68
-      </li>
69
-      <li>
70
-         <a
71
-href="/dist/vidalia/vidalia-<version-vidalia-alpha>.tar.gz">Alpha
72
-Source Tarball</a>
73
-        (<a
74
-href="/dist/vidalia/vidalia-<version-vidalia-alpha>.tar.gz.asc">sig</a>
75
-)
76
-      </li>
77
-    </ul>
78
-
79
-    <a id="Contribute"></a>
80
-    <h3><a class="anchor" href="#Contribute">Contribute</a></h3>
81
-
82
-    <p>
83
-    Vidalia is always looking for volunteers that want to help in development.
84
-    To start you should first take a look at the
85
-    <a href="<page getinvolved/volunteer>"> volunteer
86
-    page</a> and see if there is something that interests you the most.
87
-
88
-    Vidalia's source code lives now in a <a
89
-    href="https://gitweb.torproject.org/vidalia">Git repository</a>. The
90
-    clone URL is https://git.torproject.org/vidalia. You should get to
91
-    know how Vidalia works internally in order to work with it. To do
92
-    this you should know C++ and Qt.
93
-    </p>
94
-
95
-    <a id="Support"></a>
96
-    <h3><a class="anchor" href="#Support">Support &amp; Development</a></h3>
97
-
98
-    <p>
99
-    If you intend to start coding already, please read and follow the
100
-    <a href="https://gitweb.torproject.org/vidalia.git/tree/HACKING">HACKING
101
-    guide</a>.
102
-    If you have a patch for a feature or a bug fix, first check the
103
-    <a href="https://trac.torproject.org/projects/tor/report/27">tickets that
104
-    are already submitted</a>, if there isn't a suited one for your patch, you
105
-    can submit a <a href="https://trac.torproject.org/projects/tor/newticket">new ticket</a>
106
-    selecting Vidalia as its Component.
107
-    </p>
108
-
109
-    <p>
110
-    If you found a bug or you want a specific feature for future Vidalia releases, please
111
-    file a <a href="https://trac.torproject.org/projects/tor/newticket">new ticket</a>
112
-    selecting Vidalia as its Component.
113
-    </p>
114
-
115
-    <p>
116
-    Most Tor project members use IRC to communicate. You can find Tomás
117
-    in the <i>#vidalia</i> channel at OFTC under the nick chiiph. Please
118
-    get in touch in order to see what everyone's working on, and to
119
-    share what you've been working on or what you want to do. If you
120
-    intend to join the team, it's expected that you stay around IRC,
121
-    either in Vidalia's channel, or <i>#tor-dev</i>.
122
-    </p>
123
-
124
-    <p>
125
-    If you have any doubts about any of the points in here, you can
126
-    <a href="<page about/contact>">contact us</a> about it.
127
-    </p>
128
-
129
-  </div>
130
-  <!-- END MAINCOL -->
131
-  <div id = "sidecol">
132
-#include "side.wmi"
133
-#include "info.wmi"
134
-  </div>
135
-  <!-- END SIDECOL -->
136
-</div>
137
-<!-- END CONTENT -->
138
-#include <foot.wmi>