The reality is there no motivation for anyone to create a review systems, otherwise it would be in place even with all we have, no one has taken the lead to be the review coordinator
to hans that is using the svn to his customers, I see this the cart before the horse. if you have developed and tested in your own svn then a patch submitted once it is supplied to the client, and checked out. ========================= BJ Freeman http://bjfreeman.elance.com Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=93> Specialtymarket.com <http://www.specialtymarket.com/> Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Linkedin <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro> Adam Heath sent the following on 3/11/2010 8:57 AM: > Tim Ruppert wrote: >> +1 - and thanks for laying it out Ean. I guess the only question remains is >> what stops us from moving in this direction if we can achieve exactly what >> Ean's talking about? This sounds like something that would allow all of us >> the ability to manage the pieces we want to without polluting the code base >> with internal initiatives. >> >> Alas, I do feel like this might be a huge departure for many - but this >> seems like it might fix many of the contentious issues that waste a ton of >> time around here. > > It's unfortunate, but even tho Ean and I have be evangelizing ofbiz, I > can't recommend at the time it's use for managing ofbiz code. > > Right now, ofbiz has a single source for any changes. svn on apache. > If suddenly we start going the distributed route, then were will > official changes come from? Who will step up to be responsible for > pulling code from everyone else? I don't think there is anyone in > this community who is willing to spend this huge amount of time, just > being a code aggregator. It's an expensive position. >
