<br><br><div><span class="gmail_quote">On 23/09/2007, <b class="gmail_sendername">Giles Jones</b> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>On 23 Sep 2007, at 15:35, Vincent wrote:<br>><br>><br>> And surely, you mean "someone to hold responsible" instead of<br>> "someone to sue"? Especially if we're talking about an open source
<br>> project...<br>><br><br>Who says you should use open source? </blockquote><div><br>I didn't, but it is an option I presume. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
It's great when it comes to<br>doing free development and community stuff. But when it comes to<br>making money you have to look for the safest, cheapest and highest<br>performing product.<br><br>If you get defrauded of thousands then a simple "I'm sorry" from an
<br>open source developer isn't enough.<br></blockquote></div><br clear="all">No, but having him repay the damages isn't what I'd find comforting either. And anyway, as Ian said: most third parties will have a disclaimer and open source projects are mostly delivered "as is, without warranty of any kind", so you won't have someone to sue anyway. Mistakes happen.