phoenix/community/index.php - gerrit/www.eclipse.org/birt - Git at Google

 <?php

 Header("Location: /birt/community/");																										require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php");	require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php"); 	require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php"); 	$App 	= new App();	$Nav	= new Nav();	$Menu 	= new Menu();		include($App->getProjectCommon());    # All on the same line to unclutter the user's desktop'

 	#
 	# Begin: page-specific settings.  Change these.
 	$pageTitle 		= "BIRT Community";
 	$pageKeywords	= "";
 	$pageAuthor		= "";

 	# Add page-specific Nav bars here
 	# Format is Link text, link URL (can be http://www.someothersite.com/), target (_self, _blank), level (1, 2 or 3)
 	# $Nav->addNavSeparator("My Page Links", 	"downloads.php");
 	# $Nav->addCustomNav("My Link", "mypage.php", "_self", 3);
 	# $Nav->addCustomNav("Google", "http://www.google.com/", "_blank", 3);

 	# End: page-specific settings
 	#

 	require "../birt.inc";
 	$linkToTop				= linkToTop();


 	# Paste your HTML content between the EOHTML markers!
 	$html = <<<EOHTML

 <div id="maincontent">
 	<div id="midcolumn">

 		<h1><a name="top"></a>$pageTitle</h1>

 		<blockquote>
 			<ul>
 				<li><a href="#newsgroup">Newsgroup</a></li>
 				<li><a href="#bugzilla">Bugzilla</a></li>
 				<li><a href="#mailing_lists">Mailing Lists</a></li>
 				<li><a href="#contributions">Contributions</a></li>
 			</ul>
 		</blockquote>

 		<h2><a name="newsgroup"></a>Newsgroup</h2>
 		<p>
 			The BIRT newsgroup is for users of the project to ask questions, discuss ideas and so on. Join in and get involved!
 		</p>
 		<ul class="midlist">
 			<li>
 				<a href="http://www.eclipse.org/newsgroups">Information and Signup</a>

 				Guidelines for using the newsgroups. Instructions for signing up.
 			</li>
 			<li>
 				<a href="news://news.eclipse.org/eclipse.birt">news://news.eclipse.org/eclipse.birt</a>

 				The easiest way to access the newsgroup is using your favorite news reader.
 			</li>
 			<li>
 				<a href="http://www.eclipse.org/newsportal/thread.php?group=eclipse.birt">
 				Simple Web Interface</a>

 				If you don't have a newsreader, or can't access the NNTP server, use this
 				simple web interface.
 			</li>
 			<li>
 				<a href="http://dev.eclipse.org/newslists/news.eclipse.birt/maillist.html">
 				Archive</a>

 				Eclipse keeps a history of past newsgroup postings for your reference.
 			</li>
 			<li>
 				<a href="http://www.eclipse.org/search/search.cgi?q=&cmd=Search%21&form=extended&wf=574a74&ps=10&m=all&t=5&ul=%2Fnewslists%2Fnews.eclipse.birt&wm=wrd&t=News&t=Mail">Search the BIRT Newsgroup archives</a> for previously asked questions.
 			</li>
 		</ul>
 		<p>
 			BIRT charting APIs are described elsewhere. (Not yet available.)
 		</p>
 		$linkToTop
 		<hr class="clearer" />

 		<h2><a name="bugzilla"></a>Bugzilla</h2>
 		<p>
 			BIRT uses Bugzilla to track bugs and enhancements.
 		</p>
 		<ul class="midlist">
 			<li>
 				<a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=BIRT">
 				Report a Bug or Enhancement</a>

 				When reporting a bug, please give the exact steps to reproduce the problem.
 				Please explain what went wrong, and what you expected to happen. For an enhancement,
 				please explain how you'd use the new feature.
 				<p>
 				BIRT bugs are often associated with a report design. Please attach your design to
 				your Bugzilla entry.
 				</p><p>
 				If you encounter a problem such as "An error occurred", or failure to open views or
 				editors, please attach your Eclipse log file. To see the exception, use
 				Window?Show View?Other. Open the PDE Runtime group and choose Error Log.
 				Within the error log window, find the BIRT exception (if any) that just occurred.
 				Double click on the error in question and you'll see a stack trace. Paste that
 				into your bug report, preferably as a file attachment.
 			</li>
 			<li>
 				<a href="https://bugs.eclipse.org/bugs/query.cgi?product=BIRT">
 				Search Bugs</a>

 				Find BIRT-related bugs using the Bugzilla search facility.
 			</li>
 		</ul>
 		$linkToTop
 		<hr class="clearer" />

 		<h2><a name="mailing_lists"></a>Mailing Lists</h2>
 		<p>
 			Eclipse provides <a href="http://www.eclipse.org/mail/index.html"> mailing lists</a> for each project. BIRT provides one general-purpose list:
 		</p>
 		<ul class="midlist">
 			<li>
 				<a href="http://dev.eclipse.org/mailman/listinfo/birt-news">
 				birt-news</a>
 				(<a href="http://dev.eclipse.org/mhonarc/lists/birt-news/maillist.html">archive</a>)

 				Notifications to BIRT users about BIRT milestone and stable builds and
 				other noteworthy information.
 			</li>
 		</ul>
 		<p>
 			BIRT also provides mailing lists for developers contributing to BIRT:
 		</p>
 		<ul class="midlist">
 			<li>
 				<a href="http://dev.eclipse.org/mailman/listinfo/birt-dev">
 				birt-dev</a>
 				(<a href="http://dev.eclipse.org/mhonarc/lists/birt-dev/maillist.html">archive</a>)

 				Development discussions about BIRT of interest to all BIRT
 				committers. Topics include PMC meeting minutes, source code structure,
 				CVS management, and integration among the various BIRT components.
 			</li>
 			<li>
 				<a href="http://dev.eclipse.org/mailman/listinfo/birt-charting-dev">
 				birt-charting-dev</a>
 				(<a href="http://dev.eclipse.org/mhonarc/lists/birt-charting-dev/maillist.html">archive</a>)

 				Discussions about the charting subproject.
 			</li>
 			<li>
 				<a href="http://dev.eclipse.org/mailman/listinfo/birt-report-engine-dev">
 				birt-report-engine-dev</a>
 				(<a href="http://dev.eclipse.org/mhonarc/lists/birt-report-engine-dev/maillist.html">archive</a>)

 				Discussions about the reporting engine subproject.
 			</li>
 			<li>
 				<a href="http://dev.eclipse.org/mailman/listinfo/birt-report-designer-dev">
 				birt-report-designer-dev</a>
 				(<a href="http://dev.eclipse.org/mhonarc/lists/birt-report-designer-dev/maillist.html">archive</a>)

 				Discussions about the report designer subproject.
 			</li>
 		</ul>
 		$linkToTop
 		<hr class="clearer" />

 		<h2><a name="extending"></a>Extending BIRT</h2>
 		<p>
 			Want to contribute to the BIRT project?
 		</p>
 		<ul class="midlist">
 			<li>
 				<a href="/birt/phoenix/build/buildInstructions.php">Build Instructions</a>

 				How to download BIRT source and build it.
 			</li>
 			<li>
 				<a href="/birt/phoenix/project">Project Information</a>

 				How the project is structured, who's on the PMC, project roles, etc.
 			</li>
 			<li>
 				<a href="http://www.eclipse.org/mail">Mailing List</a>

 				While the newsgroup is for people who use BIRT, the mailing list is for those
 				who help develop BIRT.
 			</li>
 			<li>
 				<a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=BIRT">
 				Contribute Fixes</a>

 				The first step in contributing to BIRT is to learn the code, and there is no
 				better way to do that then to fix some bugs or add a minor feature. Contribute the
 				code back to the project by attaching it to a Bugzilla entry. Let the team know
 				about the fix via the mailing list.
 			</li>
 		</ul>
 		$linkToTop
 		<hr class="clearer" />

 	</div>
 </div>


 EOHTML;


 	# Generate the web page
 	$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
 ?>
	<?php

	Header("Location: /birt/community/"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php"); $App = new App(); $Nav = new Nav(); $Menu = new Menu(); include($App->getProjectCommon()); # All on the same line to unclutter the user's desktop'

	#
	# Begin: page-specific settings. Change these.
	$pageTitle = "BIRT Community";
	$pageKeywords = "";
	$pageAuthor = "";

	# Add page-specific Nav bars here
	# Format is Link text, link URL (can be http://www.someothersite.com/), target (_self, _blank), level (1, 2 or 3)
	# $Nav->addNavSeparator("My Page Links", "downloads.php");
	# $Nav->addCustomNav("My Link", "mypage.php", "_self", 3);
	# $Nav->addCustomNav("Google", "http://www.google.com/", "_blank", 3);

	# End: page-specific settings
	#

	require "../birt.inc";
	$linkToTop = linkToTop();


	# Paste your HTML content between the EOHTML markers!
	$html = <<<EOHTML

	<div id="maincontent">
	<div id="midcolumn">

	<h1><a name="top"></a>$pageTitle</h1>

	<blockquote>
	<ul>
	<li><a href="#newsgroup">Newsgroup</a></li>
	<li><a href="#bugzilla">Bugzilla</a></li>
	<li><a href="#mailing_lists">Mailing Lists</a></li>
	<li><a href="#contributions">Contributions</a></li>
	</ul>
	</blockquote>

	<h2><a name="newsgroup"></a>Newsgroup</h2>
	<p>
	The BIRT newsgroup is for users of the project to ask questions, discuss ideas and so on. Join in and get involved!
	</p>
	<ul class="midlist">
	<li>
	<a href="http://www.eclipse.org/newsgroups">Information and Signup</a>

	Guidelines for using the newsgroups. Instructions for signing up.
	</li>
	<li>
	<a href="news://news.eclipse.org/eclipse.birt">news://news.eclipse.org/eclipse.birt</a>

	The easiest way to access the newsgroup is using your favorite news reader.
	</li>
	<li>
	<a href="http://www.eclipse.org/newsportal/thread.php?group=eclipse.birt">
	Simple Web Interface</a>

	If you don't have a newsreader, or can't access the NNTP server, use this
	simple web interface.
	</li>
	<li>
	<a href="http://dev.eclipse.org/newslists/news.eclipse.birt/maillist.html">
	Archive</a>

	Eclipse keeps a history of past newsgroup postings for your reference.
	</li>
	<li>
	<a href="http://www.eclipse.org/search/search.cgi?q=&cmd=Search%21&form=extended&wf=574a74&ps=10&m=all&t=5&ul=%2Fnewslists%2Fnews.eclipse.birt&wm=wrd&t=News&t=Mail">Search the BIRT Newsgroup archives</a> for previously asked questions.
	</li>
	</ul>
	<p>
	BIRT charting APIs are described elsewhere. (Not yet available.)
	</p>
	$linkToTop
	<hr class="clearer" />

	<h2><a name="bugzilla"></a>Bugzilla</h2>
	<p>
	BIRT uses Bugzilla to track bugs and enhancements.
	</p>
	<ul class="midlist">
	<li>
	<a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=BIRT">
	Report a Bug or Enhancement</a>

	When reporting a bug, please give the exact steps to reproduce the problem.
	Please explain what went wrong, and what you expected to happen. For an enhancement,
	please explain how you'd use the new feature.
	<p>
	BIRT bugs are often associated with a report design. Please attach your design to
	your Bugzilla entry.
	</p><p>
	If you encounter a problem such as "An error occurred", or failure to open views or
	editors, please attach your Eclipse log file. To see the exception, use
	Window?Show View?Other. Open the PDE Runtime group and choose Error Log.
	Within the error log window, find the BIRT exception (if any) that just occurred.
	Double click on the error in question and you'll see a stack trace. Paste that
	into your bug report, preferably as a file attachment.
	</li>
	<li>
	<a href="https://bugs.eclipse.org/bugs/query.cgi?product=BIRT">
	Search Bugs</a>

	Find BIRT-related bugs using the Bugzilla search facility.
	</li>
	</ul>
	$linkToTop
	<hr class="clearer" />

	<h2><a name="mailing_lists"></a>Mailing Lists</h2>
	<p>
	Eclipse provides <a href="http://www.eclipse.org/mail/index.html"> mailing lists</a> for each project. BIRT provides one general-purpose list:
	</p>
	<ul class="midlist">
	<li>
	<a href="http://dev.eclipse.org/mailman/listinfo/birt-news">
	birt-news</a>
	(<a href="http://dev.eclipse.org/mhonarc/lists/birt-news/maillist.html">archive</a>)

	Notifications to BIRT users about BIRT milestone and stable builds and
	other noteworthy information.
	</li>
	</ul>
	<p>
	BIRT also provides mailing lists for developers contributing to BIRT:
	</p>
	<ul class="midlist">
	<li>
	<a href="http://dev.eclipse.org/mailman/listinfo/birt-dev">
	birt-dev</a>
	(<a href="http://dev.eclipse.org/mhonarc/lists/birt-dev/maillist.html">archive</a>)

	Development discussions about BIRT of interest to all BIRT
	committers. Topics include PMC meeting minutes, source code structure,
	CVS management, and integration among the various BIRT components.
	</li>
	<li>
	<a href="http://dev.eclipse.org/mailman/listinfo/birt-charting-dev">
	birt-charting-dev</a>
	(<a href="http://dev.eclipse.org/mhonarc/lists/birt-charting-dev/maillist.html">archive</a>)

	Discussions about the charting subproject.
	</li>
	<li>
	<a href="http://dev.eclipse.org/mailman/listinfo/birt-report-engine-dev">
	birt-report-engine-dev</a>
	(<a href="http://dev.eclipse.org/mhonarc/lists/birt-report-engine-dev/maillist.html">archive</a>)

	Discussions about the reporting engine subproject.
	</li>
	<li>
	<a href="http://dev.eclipse.org/mailman/listinfo/birt-report-designer-dev">
	birt-report-designer-dev</a>
	(<a href="http://dev.eclipse.org/mhonarc/lists/birt-report-designer-dev/maillist.html">archive</a>)

	Discussions about the report designer subproject.
	</li>
	</ul>
	$linkToTop
	<hr class="clearer" />

	<h2><a name="extending"></a>Extending BIRT</h2>
	<p>
	Want to contribute to the BIRT project?
	</p>
	<ul class="midlist">
	<li>
	<a href="/birt/phoenix/build/buildInstructions.php">Build Instructions</a>

	How to download BIRT source and build it.
	</li>
	<li>
	<a href="/birt/phoenix/project">Project Information</a>

	How the project is structured, who's on the PMC, project roles, etc.
	</li>
	<li>
	<a href="http://www.eclipse.org/mail">Mailing List</a>

	While the newsgroup is for people who use BIRT, the mailing list is for those
	who help develop BIRT.
	</li>
	<li>
	<a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=BIRT">
	Contribute Fixes</a>

	The first step in contributing to BIRT is to learn the code, and there is no
	better way to do that then to fix some bugs or add a minor feature. Contribute the
	code back to the project by attaching it to a Bugzilla entry. Let the team know
	about the fix via the mailing list.
	</li>
	</ul>
	$linkToTop
	<hr class="clearer" />

	</div>
	</div>


	EOHTML;


	# Generate the web page
	$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
	?>