tor-webwml.git

1) ## translation metadata
2) # Revision: $Revision$

3) # Translation-Priority: 4-optional

4) 

5) #include "head.wmi" TITLE="Tor: Open Positions" CHARSET="UTF-8"

6) 
7) <div class="main-column">
8) 
9) <h2>Tor: Open Positions</h2>
10) <hr />
11) 

12) <p>Tor is hiring!  We're looking for self-motivated individuals who are

13) able to work independently and want to help make Tor better.  These are
14) short-term contract positions ranging from one to three months.</p>

15) 

16) <p>In particular, we're looking for a few people:</p>

17) <ul>

18) <li><a href="#vidaliadev">Vidalia Developer</a></li>

19) <li><a href="#windowsdev">Microsoft Windows Developer</a></li>

20) </ul>
21) 
22) <p>Working on Tor is rewarding because:</p>
23) <ul>
24) <li>You can work your own hours in your own locations. As long as you
25) get the job done, we don't care about the process.</li>
26) <li>We only write free (open source) software. The tools you make won't
27) be locked down or rot on a shelf.</li>
28) <li>You will work with a world-class team of anonymity experts and
29) developers on what is already the largest and most active strong anonymity
30) network ever.</li>
31) </ul>
32) 

33) <p>We want you to have good communication and writing skills (in particular,

34) you should know how to keep other project members informed of your
35) progress), and we want you to know how to figure out what needs doing and
36) then take the initiative to do it. Most project members play more than

37) one role, so combination developer/activist are very welcome.</p>

38) 

39) <p>The best way to get noticed as a good developer is to join the community
40) and start helping out. Smart code commits and ideas are welcome anytime.
41) We have a great core group of developers working on the Tor software
42) itself as well as supporting software like Vidalia, Torbutton, etc. All
43) of our contractors came through volunteering first.</p>
44) 
45) <a id="vidaliadev"></a>
46) <h3><a class="anchor" href="#vidaliadev">Vidalia Developer</a></h3>

47) <p><a href="https://www.torproject.org/vidalia/">Vidalia</a> is the cross-platform graphical user interface to Tor written
48) in C++ using the Qt libraries.  It is used by millions of people
49) successfully.  Our current developer is a volunteer and otherwise
50) occupied with finishing his PhD.  We're looking for someone who knows
51) C++, Qt, and would like to kickstart development on the next generation
52) of Vidalia.  Some suggested next steps involve:</p>

53) <ul>

54) <li>Implementing the KDE Marble interface into Vidalia for better and
55) more accurate mappings of relays to countries.  Plus, it just looks
56) cool.</li>
57) <li>Implementing the ability to click a country and instruct Tor to
58) either start or end circuits in that country.</li>
59) <li>Work on bug fixes and enhancements as suggested by users.</li>
60) <li>Give Vidalia the ability to control the http proxy included, to
61) start, stop, and possibly configure either privoxy, polipo, or an http
62) shim we ship in the combined bundles of tor, vidalia, and polipo.</li>
63) <li>Possibly re-design the Vidalia interface to have different modes for
64) different levels of user sophistication.  Many users see a button or a
65) setting and feel they have to change it.  The defaults are set to ensure
66) users are sufficiently anonymous.  How can we better hide the complexity
67) of Tor configurations?</li>

68) </ul>
69) 
70) <a id="windowsdev"></a>
71) <h3><a class="anchor" href="#windowsdev">Microsoft Windows Developer</a></h3>

72) <p>This person needs to be very familiar with Windows at a system and
73) network level.  We're looking or someone to help make Tor on Windows
74) more compatible and work more reliably as a relay.
75) There are a number of projects relating to Windows that current need a
76) skilled developer:</p>

77) <ul>

78) <li>Develop a Tor network shim to redirect all traffic through Tor.
79) OpenVPN has a network layer device for Windows that redirects traffic
80) through the OpenVPN connection.  Is this the model Tor should be using?
81) Or is there something else that may work better?</li>
82) <li>Tor relays under non-server editions of Windows run into WSAENOBUFS
83) problems after a short while.  This problem is described in detail in <a
84) href="https://trac.torproject.org/projects/tor/ticket/98">bug ticket
85) 98</a>.  So far, there are no solutions. We think libevent 2.0 with its
86) bufferevents code will help solve the problem.</li>

87) </ul>

88) 

89) <p>Periodically we get new funding to work on more development

90) projects.  Your goal should be to get into the list of <a href="<page
91) people>#Core">core project members</a> so we think of you when new

92) funding arrives.</p>