Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [birt-dev] Questions about contributing to BIRT

Hi Paul,
Thanks for your response, see my comments in line below.

Paul Clenahan <pclenahan@xxxxxxxxxxx> wrote:
Thanks for your interest in contributing to the project.  Are you thinking about contributing in any specific area?
No, I am still just trying to learn BIRT, but my question was a general one.
Regarding your specific points:
We'll fix that FAQ question -- it is obviously not complete. You should find this page more useful:, and I will update the FAQ to refer to this page.
I'll let those more actively involved in assigning and working with defects chip in here, but my initial comments on this area would be:
In terms of understanding bugzilla entry assignment, I believe this is accomplished via the bugzilla "Assigned To" field. This indicates that the defect/enhancement has been assigned to an individual. If you wanted to potentially work on an item that is already assigned to someone, then I would have an email discussion with that individual to see if that makes sense.
Would this email be a private one to the individual, or should a cc to the birt-dev mailing list be made too?
For one that is not assigned, you may want to add a comment to the Bugzilla entry that you are working on it.
That makes sense, thanks.

From: birt-dev-bounces@xxxxxxxxxxx [mailto:birt-dev-bounces@xxxxxxxxxxx] On Behalf Of Susan L. Cline
Sent: Thursday, December 14, 2006 8:50 AM
To: birt-dev@xxxxxxxxxxx
Subject: [birt-dev] Questions about contributing to BIRT


I have some questions about how to contribute to BIRT.  I've looked through the information on the community page ( of the web site and outlined the process I believe is required to make a contribution.

1) Select an existing bug to work on, or enter a new bug to add a minor feature.
2) Attach a patch to the bugzilla.
3) Send an email to the birt-dev mailing list asking for a committer to review the patch.

I have questions about this process.

The BIRT Project Charter page,, has a section called Roles.  The definition of developers is 'Users who contribute code or documentation become developers.'

Referring to the information at this location:

the information under the question,
'Q: How can I contribute to the BIRT Project?'
seems pretty straightforward and states that documentation and articles for the web site are welcome, but the next section is confusing.

Q: How can I contribute code to the BIRT Project?
Eclipse has an extensive process for code contributions. (LINK) Briefly, start by completing the (NAME) form required for all code submitters. Then, follow the (STUFF) development process to first submit bugs & patches via Bugzilla.

Is this information out of date, and does the above information supercede this information, or do contributors really need to fill out a form prior to attaching a patch to a bugzilla?  Also, the LINK, NAME, and STUFF words do not link to anything.

The answer to the next question is also confusing:

Q: I'd like to help develop BIRT. How do I do that?
Start with the above process. Eventually, if you're level of participation remains high, and your code is of good quality, the development team can vote to make you a committer. All Eclipse Foundation projects must follow the Eclipse Development Process.

In brief, you have to earn the right to be contributor. On other projects, this was done by submitting code patches, bug fixes, etc. (See above) On the Web Tools project (WTP), there are people that have a related open source project or plug-in and have donated it to the WTP project and became contributor this way.

Do you have to earn the right to be a contributor, or should that be committer?

Developers (as defined above in the Roles section) can attach patches to bugs, but it appears that they can not assign bugs to themselves, is this correct?

How do developers know if someone (either a committer, or another developer) is already working on a bug? Doesn't this mean that two people might be working on the same bug?



Back to the top