Regards Scott
On 2/05/2009, at 2:56 PM, Adrian Crum wrote:
It's not the same! There is a big difference between "Here's my design, what do you think?" and "I'm interested in refactoring the security framework. Could you help me with the design?"-Adrian --- On Fri, 5/1/09, Scott Gray <scott.g...@hotwaxmedia.com> wrote:From: Scott Gray <scott.g...@hotwaxmedia.com> Subject: Re: Authz API Discussion (was re: svn commit: r770084) To: dev@ofbiz.apache.org Date: Friday, May 1, 2009, 7:49 PM It's exactly the same in fact, we have a design proposed by somebody let's start discussing it. Tear pieces out, replace some, improve others, whatever at least we have a starting point. Regards Scott On 2/05/2009, at 2:37 PM, Adrian Crum wrote:How about we start over and collaborate on a design?Is that so muchdifferent? -Adrian --- On Fri, 5/1/09, Scott Gray<scott.g...@hotwaxmedia.com> wrote:From: Scott Gray<scott.g...@hotwaxmedia.com>Subject: Re: Authz API Discussion (was re: svncommit: r770084)To: dev@ofbiz.apache.org Date: Friday, May 1, 2009, 7:30 PM This discussion is going no where fast, how aboutwe backtrack to Andrew's last email and startactuallydiscussing the design. Nothing is being foistedon anybody.Regards Scott On 2/05/2009, at 2:19 PM, Adrian Crum wrote:--- On Fri, 5/1/09, Anil Patel<anil.pa...@hotwaxmedia.com> wrote:This is one of the big reasons what I loveandhatecommunity driven software. I don't seehowwhat Andrewdid is bad. Even though it was personalcommunication but Iknow Andrew only started after Adrian andJacquesshowedinterest by commenting on the page.The only interest I showed was that I agreedthatOFBiz security could use improvement, and Isuggested he usea third party library. I did not endorse orapprove of hisdesign.Andrew has been actively explaining hisidea allthis time.As I demonstrated in another reply, no he didnot.Only a few days went by between introducing theidea andcommitting code.The work done till date is not blockinganybody,oldsecurity system is still in place. Newsystem isimplementedin example component so its lot easy forhim toexplain andpeople to understand.What if the new work is a bad design? How willwe knowthat until everyone has had time to evaluate it?People have different ways of working incommunity, Joe iscommitter still all the time he createsJira issueanduploads his patch and most of time itssomebodyelse whodoes commits, but that's his way ofworking.If wedon't do what Joe does then why shouldAndrewdo whatAdrian does.As far as I know, Joe submits patches forthings hedoesn't have commit rights to.I don't see any reason why we shouldstartover.Do you see a reason why we shouldn't? Willtheproject suffer immensely if we pause and wait forothers tocomment? Is there some catastrophe looming thatrequires usto rush this through?All the time we talk about making things easysopeople willcontribute, Why do you want to resist aseasonedcontributerfor working. I'll rather have expectcommunitywillsupport. All the time he has been askingpeople totell himsuggestions, wish list etc. Why notsupport himand get moreout of him instead.If we can't invite the community toparticipate -as I suggested - then that only proves what Isuspect - thatthis is a design that is being foisted on thecommunity.-Adrian
smime.p7s
Description: S/MIME cryptographic signature