Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "BIRT/FAQ/Birt Project"

< BIRT‎ | FAQ
(Project Source)
Line 1: Line 1:
Back to [[BIRT/FAQ|BIRT FAQ Index]]
+
{{Backlink|BIRT/FAQ}}
 +
 
 
== Release Schedule ==
 
== Release Schedule ==
 
=== Q: What is the BIRT release schedule? ===
 
=== Q: What is the BIRT release schedule? ===
Line 68: Line 69:
 
Eclipse is an active, growing community with new top-level projects being created at a lively pace. The BIRT PMC has an active dialog with these other projects to understand where BIRT can leverage existing or proposed functionality. With a community as dynamic as Eclipse, we adjust our plans to incorporate new functionality as the community evolves.
 
Eclipse is an active, growing community with new top-level projects being created at a lively pace. The BIRT PMC has an active dialog with these other projects to understand where BIRT can leverage existing or proposed functionality. With a community as dynamic as Eclipse, we adjust our plans to incorporate new functionality as the community evolves.
  
[[Category:FAQ]]
+
[[Category:BIRT]]
 +
[[Category:BIRT FAQ]]

Revision as of 11:05, 29 March 2007

< To: BIRT/FAQ

Release Schedule

Q: What is the BIRT release schedule?

The latest BIRT release schedule can be found on the BIRT Project Development Plan pages.

Project Source

Q: Where can I find the BIRT project source?

BIRT source is in the Eclipse CVS system. Full information for obtaining and building the source is available on the BIRT Build page.

Q: I'm behind a firewall and cannot access CVS. Is there another way to access the source?

Eclipse provides an HTML interface into CVS. Be sure to select the BIRT Project to see the BIRT sources.

Q: How do I build BIRT?

Complete instructions are available on the Build page.

Q: How do I run BIRT JUnit Tests?

Please follow instructions on Build-Junit page.

Contribution

Q: How can I contribute to the BIRT Project?

BIRT is an open source project and seeks contributions in many areas:

  • Answer questions in the newsgroup. – As BIRT grows, new people will come to BIRT and ask questions that more experienced users have already answered. A great way to "give back" to the BIRT community is to answer such questions.
  • Try out new builds & features and report suggestions & problems. – BIRT uses an incremental development process: "release early and often." If you're adventerous, try out new builds & features and let us know about bugs, or ways to improve the product.
  • Platform, driver, app server and other integration issues. – The team tests BIRT on a set of plaforms identified in the Project Plan. If you work on a different platform, please try BIRT and report any problems that you find. File bugs using Bugzilla. Please be as specific as possible, since the development team does not have access to your platform.
  • Examples. – Examples help users quickly see what BIRT can do, show how to accomplish tasks, and help the development team visualize how BIRT is used in practice. You can contribute a static example (HTML output of a report), a report design, a code example and more. Please let us know on the newsgroup that you've got an example and we'll work with you to get it onto the web site.
  • Articles. – Articles can include how-to, tutorials, case studies, or brief notes about how to solve a particular problem, integrate with a particular bit of sofware and so on. Please let us know via the newsgroup and we'll work with you to get it onto the web site.
  • Bug fixes. – If you discover a problem or enhancement, and have the time & skills to track down the problem and find a fix; you can submit the fix to the development team as a Bugzilla entry.

Q: How can I help develop BIRT by contributing code?

Interested in joining the BIRT project as a code 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.

Eclipse has an extensive process for code contributions and you can find more information on this topic on the How to Contribute to the BIRT Project page.

In brief, you have to earn the right to be Committer. This is done by submitting code patches, bug fixes, etc. or by making a significant contribution in some other way.

Q: Which codeline do I check out from CVS to create my patch?

Instructions about which codeline to use, and contributing to already released versions of BIRT are available on the Which Codeline page.

Futures

Q: How do I find out what the BIRT Project Team is working on next?

The development team publishes Development Plans for all upcoming releases to keep the community informed and provide a mechanism for feedback.

In addition, the Eclipse Bugzilla system is used to track all projects, big and small, that are being worked on for the BIRT project. You can query the Bugzilla system to find out what is assigned to any particular BIRT release.

Q: What other projects might fit within the BIRT project?

The BIRT Project has chosen to focus on reporting for the initial releases. Other possible projects could expand BIRT into many of the dimensions of Business Intelligence:

  • Data Modeling tools for defining schemas, meta data.
  • ETL (Extract, Transform, Load) tools for creating and maintaining the data warehouse.
  • APIs and Frameworks to build business-user query tools for with flexible ad hoc access to data.
  • Analysis tools that enable power-users to slice-and-dice the same data.

Q: How does the BIRT project relate to TPTP, Data Tools, etc.

Eclipse is an active, growing community with new top-level projects being created at a lively pace. The BIRT PMC has an active dialog with these other projects to understand where BIRT can leverage existing or proposed functionality. With a community as dynamic as Eclipse, we adjust our plans to incorporate new functionality as the community evolves.

Back to the top