Roger Dingledine commited on 2012-06-04 21:52:03
              Zeige 2 geänderte Dateien mit 137 Einfügungen und 90 Löschungen.
            
| ... | ... | 
                      @@ -0,0 +1,134 @@  | 
                  
| 1 | 
                        +## translation metadata  | 
                    |
| 2 | 
                        +# Revision: $Revision$  | 
                    |
| 3 | 
                        +# Translation-Priority: 3-low  | 
                    |
| 4 | 
                        +  | 
                    |
| 5 | 
                        +#include "head.wmi" TITLE="Tor Project: Jobs (core developer)" CHARSET="UTF-8"  | 
                    |
| 6 | 
                        +<div id="content" class="clearfix">  | 
                    |
| 7 | 
                        + <div id="breadcrumbs">  | 
                    |
| 8 | 
                        + <a href="<page index>">Home » </a>  | 
                    |
| 9 | 
                        + <a href="<page about/overview>">About » </a>  | 
                    |
| 10 | 
                        + <a href="<page about/jobs>">Jobs</a>  | 
                    |
| 11 | 
                        + </div>  | 
                    |
| 12 | 
                        + <div id="maincol">  | 
                    |
| 13 | 
                        +<h1>The Tor Project is looking for another dedicated core developer!</h1>  | 
                    |
| 14 | 
                        +  | 
                    |
| 15 | 
                        +<p>  | 
                    |
| 16 | 
                        +Your job would be to work on all aspects of the main Tor network daemon  | 
                    |
| 17 | 
                        +and other open-source software.  | 
                    |
| 18 | 
                        +This would be a contractor position for 2012 (starting as soon as you're  | 
                    |
| 19 | 
                        +ready and with plenty of work to keep you busy), with the possibility of  | 
                    |
| 20 | 
                        +2013 and beyond.  | 
                    |
| 21 | 
                        +</p>  | 
                    |
| 22 | 
                        +  | 
                    |
| 23 | 
                        +<p>  | 
                    |
| 24 | 
                        +Any candidate must:  | 
                    |
| 25 | 
                        +</p>  | 
                    |
| 26 | 
                        +  | 
                    |
| 27 | 
                        +<ul>  | 
                    |
| 28 | 
                        +<li>Have extensive experience in C, and several other programming  | 
                    |
| 29 | 
                        + languages. At least 5 years experience with C is probably necessary  | 
                    |
| 30 | 
                        + for the level of expertise we want; most people would need more.</li>  | 
                    |
| 31 | 
                        +<li>Have a solid understanding of issues surrounding secure C programming.</li>  | 
                    |
| 32 | 
                        +<li>Be comfortable working from home (or wherever your preferred  | 
                    |
| 33 | 
                        + Internet connection is).</li>  | 
                    |
| 34 | 
                        +<li>Be familiar and experienced with nonblocking, event-driven networking  | 
                    |
| 35 | 
                        + programs.</li>  | 
                    |
| 36 | 
                        +<li>Be comfortable and experienced with interacting with users online.</li>  | 
                    |
| 37 | 
                        +<li>Be comfortable and experienced with driving the entire lifecycle  | 
                    |
| 38 | 
                        + of a new feature in an existing piece of software, from design to  | 
                    |
| 39 | 
                        + implementation to testing.</li>  | 
                    |
| 40 | 
                        +<li>Be comfortable and experienced getting code and design reviewed,  | 
                    |
| 41 | 
                        + and reviewing the code and design of others.</li>  | 
                    |
| 42 | 
                        +<li>Be comfortable with transparency: as a non-profit, everything we do  | 
                    |
| 43 | 
                        + is in public, including your name and pay rate.</li>  | 
                    |
| 44 | 
                        +</ul>  | 
                    |
| 45 | 
                        +  | 
                    |
| 46 | 
                        +<p>  | 
                    |
| 47 | 
                        +An ideal candidate would also:  | 
                    |
| 48 | 
                        +</p>  | 
                    |
| 49 | 
                        +  | 
                    |
| 50 | 
                        +<ul>  | 
                    |
| 51 | 
                        +<li>Know enough of the basics of cryptography in order to understand  | 
                    |
| 52 | 
                        + how to implement our protocols and discuss changes to them. (Actually  | 
                    |
| 53 | 
                        + implementing block ciphers and stuff like that isn't necessary.)</li>  | 
                    |
| 54 | 
                        +<li>Know enough about networking in order to understand how to implement  | 
                    |
| 55 | 
                        + our protocols and discuss changes to them.</li>  | 
                    |
| 56 | 
                        +<li>Have experience with high-performance networking code.</li>  | 
                    |
| 57 | 
                        +<li>Have experience with open-source software development, including  | 
                    |
| 58 | 
                        + working with distributed teams across different time-zones containing  | 
                    |
| 59 | 
                        + employees and volunteers of differing skill levels over email and IRC.</li>  | 
                    |
| 60 | 
                        +<li>Have basic familiarity with distributed version control systems.</li>  | 
                    |
| 61 | 
                        +<li>Have contributed significant chunks of code to multiple  | 
                    |
| 62 | 
                        + open-source projects in the past.</li>  | 
                    |
| 63 | 
                        +<li>Genuinely be excited about Tor and our values.</li>  | 
                    |
| 64 | 
                        +</ul>  | 
                    |
| 65 | 
                        +  | 
                    |
| 66 | 
                        +<p>  | 
                    |
| 67 | 
                        +Being a core Tor developer includes triaging,  | 
                    |
| 68 | 
                        +diagnosing, and fixing bugs; looking for and resolving security  | 
                    |
| 69 | 
                        +issues; and working collaboratively with coworkers and volunteers  | 
                    |
| 70 | 
                        +on implementing new features and protocol changes at every stage from  | 
                    |
| 71 | 
                        +design to maintenance. We'd also need help making our code more scalable,  | 
                    |
| 72 | 
                        +testable, and maintainable. Sometimes, we need to drop everything and  | 
                    |
| 73 | 
                        +scramble to implement last-minute anticensorship schemes, or to deploy  | 
                    |
| 74 | 
                        +urgent security updates. You'd also be reviewing other people's code and  | 
                    |
| 75 | 
                        +designs, and looking for ways to improve it. For an idea of the  | 
                    |
| 76 | 
                        +breadth and depth of the work you'd be doing, have a look at <a  | 
                    |
| 77 | 
                        +href="https://gitweb.torproject.org/tor.git/blob/HEAD:/ChangeLog">the  | 
                    |
| 78 | 
                        +ChangeLog file from the Tor source distribution</a>.  | 
                    |
| 79 | 
                        +</p>  | 
                    |
| 80 | 
                        +  | 
                    |
| 81 | 
                        +<p>  | 
                    |
| 82 | 
                        +Other notes:  | 
                    |
| 83 | 
                        +</p>  | 
                    |
| 84 | 
                        +  | 
                    |
| 85 | 
                        +<ul>  | 
                    |
| 86 | 
                        +<li>Tor developers don't have an office; you can work from wherever you  | 
                    |
| 87 | 
                        + want, in basically any country. You'll need to be comfortable in  | 
                    |
| 88 | 
                        + this environment! We coordinate via IRC, email, and bug trackers.</li>  | 
                    |
| 89 | 
                        +<li>Academic degrees are great, but not required if you have the right  | 
                    |
| 90 | 
                        + experience.</li>  | 
                    |
| 91 | 
                        +<li>We only write free (open source) software, and we don't believe in  | 
                    |
| 92 | 
                        + software patents.</li>  | 
                    |
| 93 | 
                        +</ul>  | 
                    |
| 94 | 
                        +  | 
                    |
| 95 | 
                        +<p>  | 
                    |
| 96 | 
                        +How to apply:  | 
                    |
| 97 | 
                        +</p>  | 
                    |
| 98 | 
                        +  | 
                    |
| 99 | 
                        +<ul>  | 
                    |
| 100 | 
                        +<li>Link to a sample of code you've written in the past that you're  | 
                    |
| 101 | 
                        + allowed to show us.</li>  | 
                    |
| 102 | 
                        +<li>Provide a CV explaining your background, experience, skills, and  | 
                    |
| 103 | 
                        + other relevant qualifications.</li>  | 
                    |
| 104 | 
                        +<li>List some people who can tell us more about you: these references  | 
                    |
| 105 | 
                        + could be employers or coworkers, open source projects, etc.</li>  | 
                    |
| 106 | 
                        +<li>Email the above to jobs at torproject.org.</li>  | 
                    |
| 107 | 
                        +</ul>  | 
                    |
| 108 | 
                        +  | 
                    |
| 109 | 
                        +<p>  | 
                    |
| 110 | 
                        +About the company:<br>  | 
                    |
| 111 | 
                        + The Tor Project is a US 501(c)(3) non-profit dedicated to research,  | 
                    |
| 112 | 
                        + development, and education about online anonymity and privacy. The Tor  | 
                    |
| 113 | 
                        + network's 3000 volunteer relays carry 14 Gbps for upwards of half a million  | 
                    |
| 114 | 
                        + daily users, including ordinary citizens who want protection from identity  | 
                    |
| 115 | 
                        + theft and prying corporations, corporations who want to look at a  | 
                    |
| 116 | 
                        + competitor's website in private, people around the world whose Internet  | 
                    |
| 117 | 
                        + connections are censored, and even governments and law enforcement. Tor has  | 
                    |
| 118 | 
                        + a staff of 13 paid developers, researchers, and advocates, plus many dozen  | 
                    |
| 119 | 
                        + volunteers who help out on a daily basis. Tor is funded in part by  | 
                    |
| 120 | 
                        + government research and development grants, and in part by individual and  | 
                    |
| 121 | 
                        + corporate donations.  | 
                    |
| 122 | 
                        +</p>  | 
                    |
| 123 | 
                        +  | 
                    |
| 124 | 
                        + </div>  | 
                    |
| 125 | 
                        + <!-- END MAINCOL -->  | 
                    |
| 126 | 
                        + <div id = "sidecol">  | 
                    |
| 127 | 
                        +#include "side.wmi"  | 
                    |
| 128 | 
                        +#include "info.wmi"  | 
                    |
| 129 | 
                        + </div>  | 
                    |
| 130 | 
                        + <!-- END SIDECOL -->  | 
                    |
| 131 | 
                        +</div>  | 
                    |
| 132 | 
                        +<!-- END CONTENT -->  | 
                    |
| 133 | 
                        +#include <foot.wmi>  | 
                    |
| 134 | 
                        +  | 
                    
| ... | ... | 
                      @@ -10,100 +10,13 @@  | 
                  
| 10 | 10 | 
                        <a href="<page about/jobs>">Jobs</a>  | 
                    
| 11 | 11 | 
                        </div>  | 
                    
| 12 | 12 | 
                        <div id="maincol">  | 
                    
| 13 | 
                        -<h1>The Tor Project is looking for another dedicated core developer!</h1>  | 
                    |
| 13 | 
                        +<h1>The Tor Project is looking for more great developers!</h1>  | 
                    |
| 14 | 14 | 
                         | 
                    
| 15 | 
                        -<p>  | 
                    |
| 16 | 
                        -Your job would be to work on all aspects of the main Tor network daemon  | 
                    |
| 17 | 
                        -and other open-source software.  | 
                    |
| 18 | 
                        -This would be a contractor position for 2012 (starting as soon as you're  | 
                    |
| 19 | 
                        -ready and with plenty of work to keep you busy), with the possibility of  | 
                    |
| 20 | 
                        -2013 and beyond.  | 
                    |
| 21 | 
                        -</p>  | 
                    |
| 22 | 
                        -  | 
                    |
| 23 | 
                        -<p>  | 
                    |
| 24 | 
                        -Any candidate must:  | 
                    |
| 25 | 
                        -</p>  | 
                    |
| 26 | 
                        -  | 
                    |
| 27 | 
                        -<ul>  | 
                    |
| 28 | 
                        -<li>Have extensive experience in C, and several other programming  | 
                    |
| 29 | 
                        - languages. At least 5 years experience with C is probably necessary  | 
                    |
| 30 | 
                        - for the level of expertise we want; most people would need more.</li>  | 
                    |
| 31 | 
                        -<li>Have a solid understanding of issues surrounding secure C programming.</li>  | 
                    |
| 32 | 
                        -<li>Be comfortable working from home (or wherever your preferred  | 
                    |
| 33 | 
                        - Internet connection is).</li>  | 
                    |
| 34 | 
                        -<li>Be familiar and experienced with nonblocking, event-driven networking  | 
                    |
| 35 | 
                        - programs.</li>  | 
                    |
| 36 | 
                        -<li>Be comfortable and experienced with interacting with users online.</li>  | 
                    |
| 37 | 
                        -<li>Be comfortable and experienced with driving the entire lifecycle  | 
                    |
| 38 | 
                        - of a new feature in an existing piece of software, from design to  | 
                    |
| 39 | 
                        - implementation to testing.</li>  | 
                    |
| 40 | 
                        -<li>Be comfortable and experienced getting code and design reviewed,  | 
                    |
| 41 | 
                        - and reviewing the code and design of others.</li>  | 
                    |
| 42 | 
                        -<li>Be comfortable with transparency: as a non-profit, everything we do  | 
                    |
| 43 | 
                        - is in public, including your name and pay rate.</li>  | 
                    |
| 44 | 
                        -</ul>  | 
                    |
| 45 | 
                        -  | 
                    |
| 46 | 
                        -<p>  | 
                    |
| 47 | 
                        -An ideal candidate would also:  | 
                    |
| 48 | 
                        -</p>  | 
                    |
| 49 | 
                        -  | 
                    |
| 50 | 
                        -<ul>  | 
                    |
| 51 | 
                        -<li>Know enough of the basics of cryptography in order to understand  | 
                    |
| 52 | 
                        - how to implement our protocols and discuss changes to them. (Actually  | 
                    |
| 53 | 
                        - implementing block ciphers and stuff like that isn't necessary.)</li>  | 
                    |
| 54 | 
                        -<li>Know enough about networking in order to understand how to implement  | 
                    |
| 55 | 
                        - our protocols and discuss changes to them.</li>  | 
                    |
| 56 | 
                        -<li>Have experience with high-performance networking code.</li>  | 
                    |
| 57 | 
                        -<li>Have experience with open-source software development, including  | 
                    |
| 58 | 
                        - working with distributed teams across different time-zones containing  | 
                    |
| 59 | 
                        - employees and volunteers of differing skill levels over email and IRC.</li>  | 
                    |
| 60 | 
                        -<li>Have basic familiarity with distributed version control systems.</li>  | 
                    |
| 61 | 
                        -<li>Have contributed significant chunks of code to multiple  | 
                    |
| 62 | 
                        - open-source projects in the past.</li>  | 
                    |
| 63 | 
                        -<li>Genuinely be excited about Tor and our values.</li>  | 
                    |
| 64 | 
                        -</ul>  | 
                    |
| 65 | 
                        -  | 
                    |
| 66 | 
                        -<p>  | 
                    |
| 67 | 
                        -Being a core Tor developer includes triaging,  | 
                    |
| 68 | 
                        -diagnosing, and fixing bugs; looking for and resolving security  | 
                    |
| 69 | 
                        -issues; and working collaboratively with coworkers and volunteers  | 
                    |
| 70 | 
                        -on implementing new features and protocol changes at every stage from  | 
                    |
| 71 | 
                        -design to maintenance. We'd also need help making our code more scalable,  | 
                    |
| 72 | 
                        -testable, and maintainable. Sometimes, we need to drop everything and  | 
                    |
| 73 | 
                        -scramble to implement last-minute anticensorship schemes, or to deploy  | 
                    |
| 74 | 
                        -urgent security updates. You'd also be reviewing other people's code and  | 
                    |
| 75 | 
                        -designs, and looking for ways to improve it. For an idea of the  | 
                    |
| 76 | 
                        -breadth and depth of the work you'd be doing, have a look at <a  | 
                    |
| 77 | 
                        -href="https://gitweb.torproject.org/tor.git/blob/HEAD:/ChangeLog">the  | 
                    |
| 78 | 
                        -ChangeLog file from the Tor source distribution</a>.  | 
                    |
| 79 | 
                        -</p>  | 
                    |
| 80 | 
                        -  | 
                    |
| 81 | 
                        -<p>  | 
                    |
| 82 | 
                        -Other notes:  | 
                    |
| 83 | 
                        -</p>  | 
                    |
| 84 | 
                        -  | 
                    |
| 85 | 
                        -<ul>  | 
                    |
| 86 | 
                        -<li>Tor developers don't have an office; you can work from wherever you  | 
                    |
| 87 | 
                        - want, in basically any country. You'll need to be comfortable in  | 
                    |
| 88 | 
                        - this environment! We coordinate via IRC, email, and bug trackers.</li>  | 
                    |
| 89 | 
                        -<li>Academic degrees are great, but not required if you have the right  | 
                    |
| 90 | 
                        - experience.</li>  | 
                    |
| 91 | 
                        -<li>We only write free (open source) software, and we don't believe in  | 
                    |
| 92 | 
                        - software patents.</li>  | 
                    |
| 93 | 
                        -</ul>  | 
                    |
| 94 | 
                        -  | 
                    |
| 95 | 
                        -<p>  | 
                    |
| 96 | 
                        -How to apply:  | 
                    |
| 15 | 
                        +<p>Specifically, we're looking for the following people currently:  | 
                    |
| 97 | 16 | 
                        </p>  | 
                    
| 98 | 17 | 
                         | 
                    
| 99 | 18 | 
                        <ul>  | 
                    
| 100 | 
                        -<li>Link to a sample of code you've written in the past that you're  | 
                    |
| 101 | 
                        - allowed to show us.</li>  | 
                    |
| 102 | 
                        -<li>Provide a CV explaining your background, experience, skills, and  | 
                    |
| 103 | 
                        - other relevant qualifications.</li>  | 
                    |
| 104 | 
                        -<li>List some people who can tell us more about you: these references  | 
                    |
| 105 | 
                        - could be employers or coworkers, open source projects, etc.</li>  | 
                    |
| 106 | 
                        -<li>Email the above to jobs at torproject.org.</li>  | 
                    |
| 19 | 
                        +<li><a href="<page about/jobs-coredev>">Core developer</a></li>  | 
                    |
| 107 | 20 | 
                        </ul>  | 
                    
| 108 | 21 | 
                         | 
                    
| 109 | 22 | 
                        <p>  | 
                    
| 110 | 23 |