en_contribute.php - gerrit/www.eclipse.org/4diac - Git at Google

 <html>
 <head>
 <?php include 'head.php';?>
 <title>Contributing to Eclipse 4diac</title>
 <meta name="As open source project depends on the support of its userser and contributors. Learn hear how you can contribute to Eclispe 4diac">
 <meta name="keywords" content="how to contribute, develop new featuers, fix bugs, triage bugs, extend documentation, dvelop demo applications">
 </head>

 <body>
 <?php include 'header.html';?>

 <section class="img">
 	<img src="img/community.png"/>
 </section>

 <section class="left">
  <!-- currently empty left section -->
 </section>


 <section class="content">
 	<h1>Contribute</h1>
 	<p>Thanks for your interest to support 4diac. There are multiple ways to contribute.</p>
 	<h2>Documentation, Marketing, and Supporting new Users</h2>
 		<ul>
 			<li>Improve and extend the existing documentation</li>
 			<li>Write new tutorials</li>
 			<li>Support the forums: Answer questions in the different forums</li>
 			<li>Spread the word: link to 4diac, use 4diac logo on your web page, write articles, blog entries, etc.</li>
 		</ul>
 	<h2>Bug Wrangling and Testing</h2>
 		<ul>
 			<li>Find and report bugs to ensure the quality of 4diac.</li>
 			<li>Submit ideas for improvement via <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=4DIAC">4diac's Bugzilla</a>.</li>
 			<li>Review and verify <a href="https://bugs.eclipse.org/bugs/buglist.cgi?list_id=13385396&product=4DIAC&query_format=advanced">reported bugs</a>. Sometimes there is not enough info attached to a bug report or it is hard to reproduce. Trying to reproduce a bug and extending the description is of great value.</li>
 			<li>Rate Bugs, feature requests, and ideas. This helps that we can focus our limited resources on the most important elements first.</li>
 		</ul>
 	<h2>Development</h2>
   		<p>If you are a developer feel free to grab the code and start hacking. You can submit your patch any time when you are ready.</p>
 		<ul>
 			<li>Extend and improve FB library. Having a large set of FBs increases the usability of 4diac for developing control solutions.</li>
 			<li>For ideas where to start your effort have a look at the bugs and features submitted to the <a href="https://bugs.eclipse.org/bugs/buglist.cgi?list_id=13385396&product=4DIAC&query_format=advanced">4diac's issue tracker</a>.</li>
 			<li>For getting started feel free to ask questions in the <a href="http://eclipse.org/forums/eclipse.4diac">4diac discussion forum</a> and in <a href="https://dev.eclipse.org/mailman/listinfo/4diac-dev">4diac's mailing list</a>.</li>
 		</ul>
 		<br>

 	<!--h2>Who's Involved</h2>
 	<table>
 		<tr>
 			<td width="33%"><p>
 				<h3>Project Lead:</h3>
 				<ul><li>Alois Zoitl (fortiss GmbH)</li></ul>
 			</p></td>
 			<td width="46%"><p>
 				<h3>Committers:</h3>
 				<ul>
 					<li>Alois Zoitl (fortiss GmbH)</li>
 					<li>Gerhard Ebenhofer (Profactor GmbH)</li>
 					<li>Martin Melik-Merkumians (TU Wien ACIN)</li>
 					<li>Monika Wenger (fortiss GmbH)</li>
 				</ul>
 			</p></td>
 			<td width="20%"><p>
 				<h3>Mentors:</h3>
 				<ul>
 					<li>Ed Merks</li>
 					<li>Eike Stepper</li>
 				</ul>
 			</p></td>
 		</tr>
 	</table-->
 </section>

 <?php include 'footer.php';?>

 </body>

 </html>
	<html>
	<head>
	<?php include 'head.php';?>
	<title>Contributing to Eclipse 4diac</title>
	<meta name="As open source project depends on the support of its userser and contributors. Learn hear how you can contribute to Eclispe 4diac">
	<meta name="keywords" content="how to contribute, develop new featuers, fix bugs, triage bugs, extend documentation, dvelop demo applications">
	</head>

	<body>
	<?php include 'header.html';?>

	<section class="img">
	<img src="img/community.png"/>
	</section>

	<section class="left">
	<!-- currently empty left section -->
	</section>



	<section class="content">
	<h1>Contribute</h1>
	<p>Thanks for your interest to support 4diac. There are multiple ways to contribute.</p>
	<h2>Documentation, Marketing, and Supporting new Users</h2>
	<ul>
	<li>Improve and extend the existing documentation</li>
	<li>Write new tutorials</li>
	<li>Support the forums: Answer questions in the different forums</li>
	<li>Spread the word: link to 4diac, use 4diac logo on your web page, write articles, blog entries, etc.</li>
	</ul>
	<h2>Bug Wrangling and Testing</h2>
	<ul>
	<li>Find and report bugs to ensure the quality of 4diac.</li>
	<li>Submit ideas for improvement via <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=4DIAC">4diac's Bugzilla</a>.</li>
	<li>Review and verify <a href="https://bugs.eclipse.org/bugs/buglist.cgi?list_id=13385396&product=4DIAC&query_format=advanced">reported bugs</a>. Sometimes there is not enough info attached to a bug report or it is hard to reproduce. Trying to reproduce a bug and extending the description is of great value.</li>
	<li>Rate Bugs, feature requests, and ideas. This helps that we can focus our limited resources on the most important elements first.</li>
	</ul>
	<h2>Development</h2>
	<p>If you are a developer feel free to grab the code and start hacking. You can submit your patch any time when you are ready.</p>
	<ul>
	<li>Extend and improve FB library. Having a large set of FBs increases the usability of 4diac for developing control solutions.</li>
	<li>For ideas where to start your effort have a look at the bugs and features submitted to the <a href="https://bugs.eclipse.org/bugs/buglist.cgi?list_id=13385396&product=4DIAC&query_format=advanced">4diac's issue tracker</a>.</li>
	<li>For getting started feel free to ask questions in the <a href="http://eclipse.org/forums/eclipse.4diac">4diac discussion forum</a> and in <a href="https://dev.eclipse.org/mailman/listinfo/4diac-dev">4diac's mailing list</a>.</li>
	</ul>
	<br>

	<!--h2>Who's Involved</h2>
	<table>
	<tr>
	<td width="33%"><p>
	<h3>Project Lead:</h3>
	<ul><li>Alois Zoitl (fortiss GmbH)</li></ul>
	</p></td>
	<td width="46%"><p>
	<h3>Committers:</h3>
	<ul>
	<li>Alois Zoitl (fortiss GmbH)</li>
	<li>Gerhard Ebenhofer (Profactor GmbH)</li>
	<li>Martin Melik-Merkumians (TU Wien ACIN)</li>
	<li>Monika Wenger (fortiss GmbH)</li>
	</ul>
	</p></td>
	<td width="20%"><p>
	<h3>Mentors:</h3>
	<ul>
	<li>Ed Merks</li>
	<li>Eike Stepper</li>
	</ul>
	</p></td>
	</tr>
	</table-->
	</section>

	<?php include 'footer.php';?>

	</body>

	</html>