blob: a458d72e9f00d1bcf818b19be98a5b569611d513 [file] [log] [blame]
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 transitional//EN">
<title>Eclipse BIRT Community</title>
<link rel="stylesheet" href="../style/compose.css" type="text/css">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<p class="head">BIRT Community</p>
The BIRT newsgroup is for users of the project to ask questions, discuss ideas
and so on. Join in and get involved!
<dl class="arrow-list">
<dt><a href="">Information and Signup</a>
<dd>Guidelines for using the newsgroups. Instructions for signing up.
<dt><a href="news://">news://</a>
<dd>The easiest way to access the newsgroup is using your favorite news reader.
<dt><a href="frameizer.php?page=">
Simple Web Interface</a>
<dd>If you don't have a newsreader, or can't access the NNTP server, use this
simple web interface.
<dt><a href="frameizer.php?page=">
<dd>Eclipse keeps a history of past newsgroup postings for your reference.
BIRT uses Bugzilla to track bugs and enhancements.
<dl class="arrow-list">
<dt><a href="frameizer.php?page=">Sign Up</a>
<dd>Create a Bugzilla account. Learn how to use Bugzilla.
<dt><a href="">
Report a Bug or Enhancement</a>
<dd>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.
BIRT bugs are often associated with a report design. Please attach your design to
your Bugzilla entry.
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&rarr;Show View&rarr;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.
<dt><a href="">
Search Bugs</a>
<dd>Find BIRT-related bugs using the Bugzilla search facility.
<h1>Mailing Lists</h1>
Eclipse provides <a href="">
mailing lists</a> for each project. BIRT provides one general-purpose
<dl class="arrow-list">
<dt><a href="frameizer.php?page=">
(<a href="frameizer.php?page=">archive</a>)
<dd>Notifications to BIRT users about BIRT milestone and stable builds and
other noteworthy information.
BIRT also provides mailing lists for developers contributing to BIRT:
<dl class="arrow-list">
<dt><a href="frameizer.php?page=">
(<a href="frameizer.php?page=">archive</a>)
<dd>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.
<dt><a href="frameizer.php?page=">
(<a href="frameizer.php?page=">archive</a>)
<dd>Discussions about the charting subproject.
<dt><a href="frameizer.php?page=">
(<a href="frameizer.php?page=">archive</a>)
<dd>Discussions about the reporting engine subproject.
<dt><a href="frameizer.php?page=">
(<a href="frameizer.php?page=">archive</a>)
<dd>Discussions about the report designer subproject.
Want to contribute to the BIRT project?
<dl class="arrow-list">
<dt><a href="build/build_instr.html">Build Instructions</a>
<dd>How to download BIRT source and build it.
<dt><a href="project">Project Information</a>
<dd>How the project is structured, who's on the PMC, project roles, etc.
<dt><a href="">Mailing List</a>
<dd>While the newsgroup is for people who use BIRT, the mailing list is for those
who help develop BIRT.
<dt><a href="">
Contribute Fixes</a>
<dd>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.