Special Topic Meeting on Weds, July 28, 2010

Agenda

Special Topic Meeting to discuss "GSoC project merging, Trunk Management, and Commit Rights"

In the July 21 DSpace Developer Meeting, there was a lot of discussion around how best to manage merging of "ready" Google Summer of Code (GSoC) projects into DSpace 1.7 code on Trunk. Several different scenarios/options were discussed, which made us realize we really need to bring this to a broader discussion. We've attempted to summarize this discussion on the below wiki page (feel free to add your own comments/suggestions): Managing Release and Integration Cycles

Essentially, a few key issues came up:

1. How liberal or conservative do we want to be with allowing GSoC students to commit/merge "ready" code in preparation for DSpace 1.7? This includes:
   • How liberal/conservative do we want to be about giving students temporary commit rights to Trunk? Or, would we rather they merge their code together elsewhere (e.g. a common branch based on Trunk)?
   • How liberal/conservative do we want to be about allowing for temporary "breakage" of trunk (which could happen as several projects attempt to merge code)?
2. How much extra reviewing do we want of GSoC projects whose Mentors feel the code is "ready" for broader distribution/release in DSpace 1.7? If extra reviewing is warranted, how do we want to ensure this review is done in a timely manner (i.e. in time for DSpace 1.7, as necessary)?

As GSoC is wrapping up soon, this meeting really should concentrate on decisions around GSoC specifically. We obviously can discuss committer rights in general as well as general trunk management. But, the primary goal is to answer these questions pertaining to GSoC project merging. If necessary, we can always schedule a separate meeting to concentrate discussion on general Committer Rights and Modularization/Trunk management.

Meeting Transcript

• Full IRC Transcript will be at - http://www.duraspace.org/irclogs/index.php?date=2010-07-28