RE: Where is BIRT development discussed ??? Re: [birt-dev] Request forpa

["Wenfeng Li" <wli@xxxxxxxxxxx>]

Hi, Dan

I am interested in learning how other open source projects conduct
public code reviews.  Do others use net meeting to broadcast their code
review sessions?  

In BIRT project, the practice has been an existing committer reviews the
patches that is submitted via bugzilla.  The committer will put his/her
comments in bugzilla to indicate any changes is needed on the code and
if the patch has been accepted and checked into the project code base.
Others can also put in comments in bugzilla.  

BIRT project also has a BPS (BIRT Project Spec) process for project
level proposals in wiki.  Preliminary feature spec are added to BIRT's
wiki pages. The community can then add comments to the specification via
wiki. BIRT's Project mgmt committee will decide which BPS is scheduled
for a release based on if the project is within the scope of the project
charter and more importantly if there is a committer signs up to
complete the project within the release timeframe.  For scheduled
projects, a bugzilla is created assigned to a target milestone.  The
majority of design discussion from that point forward is done through
Bugzilla.  You can find the list of projects for each release in BIRT's
project planning page.

User community can also submit feature/enhancement request through
Bugzilla, follow up discussion will happen in the Bugzilla entry.  Small
enh on existing feature will be scheduled by committers based on their
interests and resource. Large enhancement or brand new function area
will go thru the planning process above.

You can also see some discussions about project structure, build
process, release schedule, release coordination messages in the birt-dev
mailing list that are of concern to the general BIRT committer
community.

As a general practice for the BIRT project, we try to follow the dev
process of the Eclipse platform project.  One reason is that they have a
proven track record of producing a successful software as well as
attracting a large user community. The other reason is that we are on
one release train now, so it is easier to synch up with similar process.


Regards,

Wenfeng 
 






-----Original Message-----
From: birt-dev-bounces@xxxxxxxxxxx [mailto:birt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Daniel John Debrunner
Sent: Monday, March 19, 2007 10:00 PM
To: birt-dev@xxxxxxxxxxx
Subject: Where is BIRT development discussed ??? Re: [birt-dev] Request
forpatch review for Bugzilla 176874


I just looked through the archives for birt-dev from the start of this 
year. There have been a lot of checkins to the code, but I couldn't see 
one single discussion or issue raised amongst the committers. This seems

really strange for an open source project. The comments below indicate 
changes are reviewed, but I haven't seen any review comments or feedback

  by any committer or anyone else against any piece of code.

It seems then that the development must be being discussed elsewhere. 
 From a discussion in Jan it seems unlikely the user forums are where it

is happening since comments there indicate most of the committers are 
not active in the user forum. Also the user forum would be a strange 
place for development discussion.

Can anyone provide a link or subscription information to where birt 
development discussions actually happen. Also adding that information to

the community page would be very useful.

Thanks,
Dan.

Daniel John Debrunner wrote:
> Scott Rosenbaum wrote:
>> Dan,
>>
>> The Eclipse Foundation sets the bar fairly high in terms of adding
>> code to
>> the product.  The code has to be Eclipse worthy on the basics, the
code
>> runs, we have appropriate tests, maintains API's, etc.  There are
also
>> additional rules in terms of the code has to be submitted through
>> appropriate channels, it has to meet the intellectual property 
>> requirements,
>> etc.  
> 
> That sounds great, I agree reviewing code is great. It was just the 
> use
> of "we" in "we are reviewing" implied to me that there was some group
of 
>  people somewhere having a discussion about it. Since this is open 
> source I'd assumed that the discussion was happening on some open mail

> list and since it wasn't happening on birt-dev (which seemed the
logical 
> place) I wondered where it was happening.
> 
>> We really appreciate your contribution, we just need to do a bit more
>> work
>> before we can throw it into our platform.
>>
>> Thanks for the contribution,
> 
> Actually it wasn't my contribution, it was from Deepa Remesh, I was 
> just
> confused by the reply.
> 
> Thanks,
> Dan.
> 
> _______________________________________________
> birt-dev mailing list
> birt-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/birt-dev
> 
> 


_______________________________________________
birt-dev mailing list
birt-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/birt-dev