On 14/03/2008, Robert Godfrey <[EMAIL PROTECTED]> wrote: > All, > > for while now the Qpid [Java] community has been working on two separate > branches - M2[.1] supporting AMQP 0-8/0-9 and trunk supporting AMQP 0-10. > While each group has been working well individually; we have not been > communicating well as a team. We've given each other very little insight > into our planning and scheduling, and we have probably been doing too much > "off-list". > > Going forward we are all in agreement (I believe) that we should be working > off a common code-base from the merge of M2.1 onto trunk. In order for us > to all work effectively together - and to provide a more open community for > others to join in development, I think we should be striving to improve our > transparency. In particular we are all guilty of raising JIRAs, immediately > addressing the issue, and commiting code, without reviewing with the > community first. Given the large number of geographically distributed > individuals who all wish to actively contribute on the Java side we need to > have a process by which we can work together. > > I propose that we attempt to do the following: > > * raise JIRAs for *all* changes that we hope to make (functional and > non-functional). > * have an open regular meeting to discuss new JIRAs and estimate and > prioritize > * ensure all JIRAs are kept up to date with who is working on them and their > current state > * make sure all commits are linked to a JIRA (as we agreed at the December > F2F) > > Further some of us on the M2.1 branch have been holding a regular call to > review each other's commits for the previous week to ensure that all code we > commit meets with our collective standards. We have spotted a number of > issues this way (not limitted to the deltas being committed). > > I would like to open this up to all committers. We will need to agree a > time that is convenient (since all committers I am aware of are in either > Europe or North America this should be possible... when we get committers > from other continents we can vary the times so everyone has their chance to > contribute). All actions from this call should be minuted and put on the > list or the wiki.
I would like to say that it is all very well having a single time when we sit down and code review. That SHOULD NOT meant it is the only time. I would like to see us be more proactive in reviewing commits as they occur. If various groups wish to sit down and review the code independently and report back that is ok by me. But we must remember to be inclusive and a single dial in point is not going to cover that. If review was occurring continually then there would be no need for the weekly call. Something I'm sure we can work towards. > I am sure there are a lot more things that we can do as a community to work > more effectively together, and to make it easier for others to join us (and > I would welcome other suggestions). I think that making public our plans > and process through JIRA and the list would be an excellent first step > however. > > -- Rob > -- Martin Ritchie
