blob: aa76d6a960fab1812f2cbea646f60fef22135a84 [file] [log] [blame]
require_once( $_SERVER['DOCUMENT_ROOT'] . "birt/common/config.php");
$PagePart = new PagePart();
<!DOCTYPE html>
<html lang="en">
/* Set Page Level Meta Details */
$metaTitle = "Community";
$metaKeywords = "Eclipse,BIRT,Java,Java EE,Web,RCP,Data,Visualization,Reports,Reporting,Embed,Rich-Client,Dashboards";
$metaAuthor = "";
$metaDescription = "BIRT is an open source technology platform used to create data visualizations and reports that can be embedded into rich client and web applications.";
$ogTitle = "Eclipse BIRT Project Home";
$ogImage = "";
$ogDescription = "BIRT is an open source technology platform used to create data visualizations and reports that can be embedded into rich client and web applications.";
//only use following if you know what you are doing - else just leave them as is.
$robotsIndex = "index"; // ** *Only usable values are 'index', 'noindex'
$robotsFollow = "follow"; // ***Only usable values are 'follow', 'nofollow'
$canonicalTag = ""; //this is a canonical tag used for duplicate content *** DO NOT USE UNLESS YOU KNOW WHAT YOU ARE DOING *** Default is blank! ex:
# Generate Meta Info
echo $PagePart->getMetaInfo($metaTitle, $metaKeywords, $metaAuthor, $metaDescription, $ogTitle, $ogImage, $ogDescription, $robotsIndex, $robotsFollow, $canonicalTag);
<?php echo $PagePart->getAfterBody(); ?>
<div style="background-color:#f4f4f4;">
<div class="content-area">
<div class="content-area-inner" style="padding-top:40px;">
<div class="actu-eclipse-side-menu">
<?php echo $PagePart->getSideMenu(); ?>
<div class="dev-main eclipse-main">
<div class="eclipse-main-container">
<h1 class="eclipse-title-main">Community</h1>
<div class="topic-menu topic-menu-right">
<div class="topic-menu-title">Section Contents</div>
<li><a href="#newsgroup">Newsgroup</a></li>
<li><a href="#bugzilla">Bugzilla</a></li>
<li><a href="#externalresources">External Resources</a></li>
<li><a href="#mailinglists">Mailing Lists</a></li>
<li><a href="#contributions">Contributions</a></li>
<a name="newsgroup"></a>
<h2 class="topic-section-header padding-top-small">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! There is also a forum area to search and ask questions on the <a href="" target="_blank">BIRT Developer Center</a>.
<ul class="eclipse-list">
<li><a href="" target="_blank">Information and Signup</a> - Guidelines for using the newsgroups. Instructions for signing up.</li><br />
<li><a href="news://" target="_blank">news://</a> - The easiest way to access the newsgroup is using your favorite news reader.</li><br />
<li><a href="" target="_blank">Simple Web Interface</a> - If you don't have a newsreader, or can't access the NNTP server, use this simple web interface.</li><br />
<li><a href="" target="_blank">Archive</a> - Eclipse keeps a history of past newsgroup postings for your reference.</li><br />
<li><a href="" target="_blank">BIRT Newsgroup Archives</a> - Search for previously asked questions.</li>
<a name="bugzilla"></a>
<h2 class="topic-section-header padding-top-small">Bugzilla</h2>
<p>BIRT uses Bugzilla to track bugs and enhancements.
<ul class="eclipse-list">
<li><a href="" target="_blank">Sign Up</a> - Create a Bugzilla account. Learn how to use Bugzilla.</li><br />
<li><a href="" target="_blank">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.</li>
<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.</p>
<p><a href="" target=_blank">Search Bugs</a> - Find BIRT-related bugs using the Bugzilla search facility.</p>
<a name="externalresources"></a>
<h2 class="topic-section-header padding-top-small">External Resources</h2>
<ul class="eclipse-list">
<li><a href="" target="_blank">BIRT Developer Center (BDC)</a> is a developer site where BIRT users can find guides and documentation, share ideas, technical tips and code snippets, as well as download software, documentation and examples.</li><br />
<li><a href="" target="_blank">BDC DevShare</a> - Browse the repository of developer-contributed report designs, code samples, tutorials and articles.</li><br />
<li><a href="" target="_blank">BDC Forums</a> - Ask questions or search through past posts to find the answer(s) that you're looking for regarding BIRT.</li>
<li><a href="" target="_blank">BDC Design Guides</a> - Access guides and documentation for creating BIRT designs.</li><br />
<li><a href="" target="_blank">BDC Deployment Guides</a> - Access guides and documentation for deploying BIRT applications.</li><br />
<li><a href="" target="_blank">BIRT World</a> is a blog covering all things related to BIRT with frequent contributions from Jason Weathersby and Scott Rosenbaum</li>
<a name="mailinglists"></a>
<h2 class="topic-section-header padding-top-small">Mailing Lists</h2>
<p>Eclipse provides <a href="" target="_blank">mailing lists</a> for each project. BIRT provides one general-purpose list:
<ul class="eclipse-list">
<li><a href="" target="_blank">birt-news</a> (<a href="" target="_blank">archive</a>) - Notifications to BIRT users about BIRT milestone and stable builds and other noteworthy information.</li>
<p>BIRT also provides mailing lists for developers contributing to BIRT:
<ul class="eclipse-list">
<li><a href="" target="_blank">birt-dev</a> (<a href="" target="_blank">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. contributors and committers. Topics include PMC meeting minutes, source code structure, CVS management, and integration among the various BIRT components. Suggestions on how to improve the website or wiki are also welcome. Note: This mailing list receives numerous check-in and build notices. If you are not interested in these notifications setting up a filter in your email client will allow you to delete these messages or filter to a different folder for reading at a later time.</li><br />
<li><a href="" target="_blank">birt-charting-dev</a> (<a href="" target="_blank">archive</a>) - Discussions about the charting subproject.</li><br />
<li><a href="" target="_blank">birt-report-engine-dev</a> (<a href="" target="_blank">archive</a>) - Discussions about the reporting engine subproject.</li><br />
<li><a href="" target="_blank">birt-report-designer-dev</a> (<a href="" target="_blank">archive</a>) - Discussions about the report designer subproject.</li>
<a name="contributions"></a>
<h2 class="topic-section-header padding-top-small">Contributions</h2>
<ul class="eclipse-list">
<li><a href="/birt/documentation/building-birt.php">Build Instructions</a> - How to download BIRT source and build it.</li><br />
<li><a href="/birt/about/project-organization/">Project</a> - How the project is structured, who's on the PMC, project roles, etc.</li><br />
<li><a href="" target="_blank">Mailing List</a> - While the newsgroup is for people who use BIRT, the mailing list is for those who help develop BIRT.</li><br />
<li><a href="/birt/about/project-organization/contributors.php">Contribute Fixes and Code</a> - Interested in joining the BIRT project as a contributor? Maybe you found a bug and made a patch to the source code to address this, or perhaps you would like to make significant contribution in a specific area. This page provides more information on how to contribute code to the project.</li>
<?php echo $PagePart->getFooter(); ?>