Pere and everyone else, This is the challenge, we committers actually need your help in getting the changes into the HEAD as much as we need to review those changes, we do not have the resources to complete your merges for you and one of the requirements we discussed this year was assuring that students participated in the entire process and that a final deliverable should include a final integration into the correct projects/trunks at locations where appropriate. If you want to get the "Real DSpace Committer Experience" its just not "I'm done, throw it over the wall", we've been there and done that for the last three years and now know the failure points.
With great power comes great responsibility, Mark On Thu, Jul 22, 2010 at 8:33 AM, Pere Villega <pere.vill...@enovation.ie> wrote: > Hi, > > first of all, sorry for not attending the meeting, I completely forgot! :) > > On the GSoC part, I think it may be easier if we do the merge in our GSoC > repositories against a specific revision of SVN. That way, we can store the > code there, properly merged and working, and then applying the patches to > upgrade from that revision to whatever is HEAD would be really easy for > committers. > > Best regards, > Pere Villega > > > Pere Villega > Software Engineer, > Enovations Solutions, > The Friary, Bow St, Dublin 7 > Direct +353 1 865 6472 > Main : +353 1 602 4784 > Fax: +353 1 865 6207 > www.enovation.ie > ***Winners of the 'Open Source Project of the Year' award at the ICT > Excellence Awards 2008**** > On Thursday 22 July 2010 15:49:03 Tim Donohue wrote: >> Hi Robyn, >> >> Thanks for the thoughts, though I worry we are in a place of "circular >> dependencies" here. >> >> Essentially, the discussion of Committers rights that came up in >> yesterday's Dev Mtg was the result of trying to determine how best to >> begin to merge some GSoC projects (those which are deemed "ready" for >> broader release) into Trunk in preparation for DSpace 1.7. >> >> Mark Diggory's proposal was to actually have GSoC students help with >> that code merge into Trunk. But, as students are not "Committers", they >> currently cannot be given rights to Trunk (under our current >> 'policies'). The idea was to bring this up as a broader question, as a >> Special Topic meeting next week, and try and determine what to do in >> this scenario. Obviously, this proposal then leads to other questions of >> how we may view committer rights. >> >> On the other hand, you are correct that looking at Modularization & >> Asynchronous releases also affects committer rights discussions. >> Unfortunately, because GSoC is beginning to wrap up, we need to make a >> decision on the GSoC question soon, if we want the students' involvement. >> >> So -- I'm agreeing with you on your point -- but also realizing the >> tight time constraints on GSoC. We may be forced to make a decision on >> the GSoC parts first, and then revisit committer rights again during >> discussions of modularization & asynchronous releases. >> >> If anyone else has other ideas on all this, I'd love to hear them! >> >> - Tim >> >> >> SideNote: for those who want to catch up on this discussion, see the >> notes/transcript from our Dev Mtg yesterday: >> https://wiki.duraspace.org/display/DSPACE/DevMtg+2010-07-21 >> >> On 7/22/2010 3:19 AM, TAYLOR Robin wrote: >> > Having completely forgotten about yesterdays developers meeting (doh >> > !) I just read the log and was interested in the chat about committer >> > rights etc. I don't want to preempt any further discussion but just >> > wanted to say that it might be logical to have the discussion about >> > modularisation and asynchronous releases before the discussion on >> > committing to trunk. The envisaged shape of the svn repo might affect >> > how we view committer rights eg if Sword lived in its own module with >> > its own release cycle then people might be less concerned about an >> > individual with an interest in Sword having commit rights just to >> > that module. >> > >> > Cheers, Robin. >> > >> > >> > Robin Taylor Main Library University of Edinburgh Tel. 0131 6513808 >> >> --------------------------------------------------------------------------- >> --- This SF.net email is sponsored by Sprint >> What will you do first with EVO, the first 4G phone? >> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >> _______________________________________________ >> Dspace-devel mailing list >> Dspace-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/dspace-devel > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Dspace-devel mailing list > Dspace-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-devel > -- Mark R. Diggory Head of U.S. Operations - @mire http://www.atmire.com - Institutional Repository Solutions http://www.togather.eu - Before getting together, get t...@ther ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
