<boardmember id="arthorne" type="committer">

	<name>John Arthorne</name>

	<title>Senior Software Developer, IBM</title>

	<image>arthorne.jpg</image>

	<email>john_arthorne at ca.ibm.com</email>

	<eclipse_affiliation> <![CDATA[
	Eclipse Project and Cloud Development Project PMC; Orion Project co-lead; 
	Eclipse Architecture Council; Committer on Platform, Equinox, e4, Orion, and Flux; 
	EclipseCon Program Committee, 2012-2014 
	
	]]> </eclipse_affiliation>

	<vision>  <![CDATA[
<p>
It is a time of exciting changes for the Eclipse Foundation. The foundation started out over ten years ago 
as a venue for software tool vendors to collaborate. It turns out this "place" that was created for a very specific 
collaboration - its policies, governance, development practices, staff and community - translates very well to many 
different domains. Today there are whole industry sectors, from automotive, to geomatics, aerospace, and large scale 
science labs, that have discovered the value of the Eclipse community as the ideal place to collaborate on software projects. 
Thanks to this new breadth, the foundation is at an all-time high in both membership and active projects. If I am 
re-elected to represent committers on the board, I will work on reducing barriers for these new projects and contributors 
coming on board. I will push on further simplifying and automating development processes to allow committers to focus 
more of their time on coding. 
</p>
<p>
At the same time, the wider software development community continues to equate the Eclipse Foundation with the 
original development tool platform and its widely known IDEs for Java, C, and other languages. The platform has 
suffered from dwindling investment and support over the years, and has suffered in quality, performance, and 
ease of use. The success and reputation of the Eclipse Foundation remains linked to the success of the Eclipse 
Platform, and I believe the Foundation needs to renew its focus on helping the Eclipse Platform improve. If re-elected, 
I will work on the board to help make this happen. This will include continuing to encourage more companies to actively 
contribute to the Platform, and for the Foundation staff to take a more active role in its development. 
</p>
	]]> </vision>

	<bio> <![CDATA[
John has worked on <a href="https://wiki.eclipse.org/Eclipse" target="_blank">Eclipse</a> open source projects for the past 14 years in many different areas. He was the main developer 
on the Eclipse Platform resource model for many years, and designed the platform's concurrency infrastructure. In past years 
he has also worked on on provisioning <a href="https://wiki.eclipse.org/P2" target="_blank">(p2)</a>, <a href="https://wiki.eclipse.org/E4" target="_blank">e4</a>, and overall platform <a href="https://wiki.eclipse.org/API_Central" target="_blank">API quality</a>. His current focus is on building cloud-based 
development tools, as co-lead on both the <a href="https://wiki.eclipse.org/Orion" target="_blank">Orion</a> and <a href="https://wiki.eclipse.org/Flux" target="_blank">Flux</a> projects, as well as co-lead of the <a href="https://wiki.eclipse.org/ECD" target="_blank">Eclipse Cloud Development</a> PMC. John is a 
member of the Eclipse <a href="https://wiki.eclipse.org/Architecture_Council" target="_blank">Architecture Council</a>, <a href="https://wiki.eclipse.org/Eclipse/PMC" target="_blank">Eclipse Project PMC</a>, and the <a href="http://www.eclipse.org/org/foundation/directors.php" target="_blank">Eclipse Foundation Board of Directors</a>. He has also 
served past terms on the <a href="https://wiki.eclipse.org/Planning_Council" target="_blank">Planning Council</a>, and as Chair and member of the EclipseCon Program Committee. John is a Senior Development 
Manager at IBM, based in Ottawa, Canada. 		
	]]> </bio>

	<affiliation> <![CDATA[ 
		IBM Software Lab, Ottawa, Canada
	
	]]>
	</affiliation>

		
</boardmember>