tor-webwml.git

1) ## translation metadata
2) # Revision: $Revision$
3) 
4) #include "head.wmi" TITLE="Tor: Open Positions"
5) 
6) <div class="main-column">
7) 
8) <h2>Tor: Open Positions</h2>
9) <hr />
10) 
11) <p>Tor is hiring! We're looking for self-motivated individuals who are
12) able to work independently and want to help make Tor better.
13) </p>
14) 
15) <p>In particular, we're looking for three categories of people:</p>
16) <ul>
17) <li><a href="#developer">Software Developer</a></li>
18) <li><a href="#activist">Activist/Outreach</a></li>
19) <li><a href="#nonprofit">Nonprofit Development</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>
34) We want you to have good communication and writing skills (in particular,
35) you should know how to keep other project members informed of your
36) progress), and we want you to know how to figure out what needs doing and
37) then take the initiative to do it. Most project members play more than
38) one role, so combination developer/activist/grantwriters are very welcome.
39) </p>
40) 
41) <a id="developer"></a>
42) <h3><a class="anchor" href="#developer">Developer</a></h3>
43) 
44) <p>
45) The best way to get noticed as a good developer is to join the community
46) and start helping out. We have a great core group of developers working
47) on the Tor software itself as well as supporting software like Vidalia,
48) Torbutton, etc.
49) </p>
50) 
51) <p>
52) Periodically we get new funding to work on more development
53) projects.  Your goal should be to get into the list of <a href="<page
54) people>#Core">core project members</a> so we think of you when new
55) funding arrives.
56) </p>
57) 
58) <a id="activist"></a>
59) <h3><a class="anchor" href="#activist">Activist and Outreach</a></h3>
60) 
61) <p>
62) There are a lot of excited people about there who want to help Tor
63) &mdash; by running relays, helping users, writing documentation,
64) working on add-on tools, and so on. We need to keep in touch with
65) all of them, help them work with each other, and help them understand
66) where they can be most useful.
67) </p>
68) 
69) <p>
70) Tor activists should understand Tor's role in the world, and they should
71) be good at explaining to the world why privacy/security/anonymity are
72) important. They should also be well-connected with other groups around
73) the world who care about these issues.
74) </p>
75) 
76) <p>
77) Like the developer positions above, the best way to get noticed
78) for this position is to start helping out: join the <a href="<page
79) documentation>#MailingLists">mailing lists</a> and the <a href="<page
80) documentation>#Support">IRC channel</a>, help clean up our FAQ, and
81) generally be useful. Once we notice you're competent and reliable,
82) we'll add you to the <a href="<page contact>">"tor-assistants"</a> list,
83) and we can see where it goes from there.
84) </p>
85) 
86) <a id="nonprofit"></a>
87) <h3><a class="anchor" href="#nonprofit">Nonprofit development</a></h3>
88) 
89) <p>
90) We need an executive director and/or development director: somebody who
91) can manage relationships with all the other civil liberties and human
92) rights groups out there, work with our current funders, and help us turn
93) potential funders into actual funders. This director would talk to
94) the media as well as manage public relations for Tor.
95) </p>
96) 
97) <p>
98) The ideal candidate will have a range of experience in both nonprofit
99) management and software development, including:
100) </p>
101) 
102) <ul>
103) <li>strong and demonstrated commitment to civil liberties</li>
104) <li>a clear understanding of the open source software development model
105) and experience with open source development communities</li>
106) <li>experience as a manager of a decentralized team, ideally in the
107) nonprofit context</li>
108) <li>ability to develop and implement press and messaging strategies</li>
109) <li>proven nonprofit fund-raising ability</li>
110) </ul>
111) 

112) <p>