tor-webwml.git

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

3) # Translation-Priority: 4-optional

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

113) <p>