All, I wanted to follow up on the results of the discussion during yesterday's Special Topic Meeting on "GSoC Project Merging & Trunk Mgmt".
Essentially, during that meeting we discussed potentially adding two GSoC projects' code to Trunk (for official release in DSpace 1.7): * Unit Testing Project: https://wiki.duraspace.org/display/DSPACE/GSOC10+-+Add+Unit+Testing+to+Dspace * REST API Project: https://wiki.duraspace.org/display/DSPACE/GSOC10+-+DSpace+REST+API In the end, we only came to a consensus on the Unit Testing Project. We held a vote during the meeting, and it was unanimously decided that the Unit Testing Project code should be merged into Trunk before the end of GSoC 2010 (which has a firm "pencils down" on Aug 16). That merging should be performed by the student (Pere Villega), with "sponsorship" of the mentor (Stuart Lewis). "Sponsorship" means that we will give Pere temporary commit rights to Trunk, and if anything goes wrong (which is doubtful), Stuart & Pere will work together to clean things up as necessary. After GSoC completes, Pere's commit rights to Trunk will be removed. More information on the meeting and the decision is available in the meeting notes (and transcript): https://wiki.duraspace.org/pages/viewpage.action?pageId=22020598 If anyone who was unable to attend the meeting has additional comments or concerns, please send a note to this listserv before next week's Developer's meeting (Weds, Aug 4). We will be adding discussion of the REST project to next week's agenda, and hopefully coming to a final decision on that project then. Thanks all, - Tim On 7/22/2010 3:40 PM, Tim Donohue wrote: > All, > > This an early notification of next week's Special Topics Developer > Meeting on the subject of "GSoC project merging, Trunk Management, and > Commit Rights". > > This meeting will take place on Weds, July 28 in the #duraspace IRC > channel at 20:00 UTC. To determine your local time, check the world > clock: > http://www.timeanddate.com/worldclock/fixedtime.html?hour=20&min=0&sec=0&p1=0 > > > == Additional Background Info == > > In yesterday's 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 on the wiki or via email to this list): > > https://wiki.duraspace.org/display/DSPACE/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: > > (1a) 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)? > > (1b) 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)? > > We've thought it best to set aside next week's Developers Meeting for > deeper discussion of these questions. > > 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. > > ---- > > Questions or comments? Let me know or send them to this listserv. > > - Tim ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
