blob: 53cd9e9d86f6827472215dacaf4441ecb0e64459 [file] [log] [blame]
<boardmember id="aniszczyk" type="committer">
<name>Chris Aniszczyk</name>
<eclipse_affiliation> <![CDATA[
<a href="">Technology</a> and Mylyn PMC Member<br>
<a href="">EGit</a> / JGit Committer<br>
<a href="">Orbit</a> Committer<br>
<a href=""></a> Maintainer<br>
<a href="">EclipseCon</a> Program Committee (2007-2012)<br>
Eclipse Board Committer Representative (2007-2016)
]]> </eclipse_affiliation>
<vision> <![CDATA[
<p>I've been grateful to be a part of the Eclipse community for a decade and honored to have served the committers on the Board for several years in the past. My previous activities on the board I've helped initiative a <a href=“”>code of conduct</a>, update our infrastructure by moving to
<a href="">Git/Gerrit</a>, push the Board to <a href="">embrace social coding at the Foundation</a> as an option for development (see <a href="">Vertx as a case study</a>) and helped push for a simplified the IP process with <a href="">CLAs</a>.
<p>If I'm elected, I want to focus on few concrete tasks to make the lives of committers easier:</p>
<p><b>Push the Eclipse Foundation to create a new individual membership class</b></p>
<p><b>Push the Eclipse Foundation to hire more developers on staff (they recently started to do this)</b></p>
<p><b>Ensure Eclipse processes are transparent and lightweight as possible</b></p>
<p>We have done a lot of work to make Eclipse processes lighter than they have been before, but I believe we can do better. There
are opportunities for more automation and making it easier to do release reviews. We need to keep the quality bar high (including IP cleanliness),
but we need to do our best to not get in the way of projects shipping.</p>
<p><b>Attract new projects and continue to mentor projects at the Eclipse Foundation</b></p>
<p>While I'm not as active on the Eclipse coding front as I've been in the past, I'm almost always one of the first people to volunteer to mentor a new project. I will continue to do my best to grow the Eclipse committer community by attracting and mentoring new projects.</p>
<p>On the whole, my goal has always been to make Eclipse thrive and be transparent as possible about the board's
activities. I really love bringing new projects to the Eclipse ecosystem and mentoring new committers. In the end,
I would be honored to represent committers on the board.</p>
]]> </vision>
<bio> <![CDATA[
Chris Aniszczyk (<a href="">@cra</a>) is a software architect by trade with a
passion for open source and building communities. At Twitter, he was responsible for
creating their open source program and managing their open source efforts. He also has the honor
to sit on the Eclipse Architecture and Planning councils. In a previous life, he traveled the world and
consulted companies on Eclipse technology. He also lead and hacked on many and linux related
projects. In his spare time, you'll find him running, cycling or doing yoga.</p>
]]> </bio>
<affiliation> <![CDATA[