Well I would say that software the passed QA containing malicious code was faulty!
My point was that your company should trust you to judge the quality of the code you're working with - wherever it comes from - and that you should have a reasonably high degree of confidence in Struts code because: 1) You can review the code yourself. 2) Thousands of other developers also review the changes. 3) The committers review changes. 4) Only a small number of people actually have commit access. Good luck with your project! Steve > -----Original Message----- > From: Gregory F. March [mailto:[EMAIL PROTECTED] > Sent: September 11, 2003 8:51 AM > To: Struts Users Mailing List > Subject: Re: YASJR, Part Duex > > > > On Sep 11, 2003, "Steve Raeburn" <[EMAIL PROTECTED]> wrote: > > |Who do they sue if the code you've written in-house is faulty? > > Faulty code was not what I was referring to. Malicious code, hacks, > timebombs, etc. was. In the case of "in house" maliciousness, you lose > your job, lose benefits and legal action will be taken against you. In > the case of external maliciousness, restitution for damages will usually > be sought. > > Quality is another issue, and I can defend struts pretty well on that > front. > > In any case, I think this is digressing. I've gotten some great points > from all of you - thanks!! > > Cheers, > > /greg > > -- > Gregory F. March -=- http://www.gfm.net:81/~march -=- > AIM:GfmNet > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
