Point well taken. I was using eBay as an example. The idea is to develop a business-to-business marketplace such as <a href="http://alibaba.com">alibaba.com</a> but with added functionality. We thought it was going to take us much longer because we were going to code the b2b marketplace from scratch but on Sept. 30, 2009 the first open source b2b marketplace was launched (phpb2b). We did not want to reinvent the wheel so we plan on using this open source b2b marketplace. <div>
<br></div><div>So based on these discussions you guys think that there are no problems in keeping the add-ons open source? This software is responsible for millions of dollars of transactions between reliable businesses. Security is a must. That means, if one of the bug contributors decides to exploit a bug they found then we are in big trouble.</div>
<div><br></div><div>-bruno<br><br><div class="gmail_quote">On Wed, Oct 14, 2009 at 10:30 AM, Mackenzie Morgan <span dir="ltr"><<a href="mailto:macoafi@gmail.com">macoafi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On Tuesday 13 October 2009 7:52:45 pm Michael Semcheski wrote:<br>
> On Tue, Oct 13, 2009 at 6:38 PM, Bruno Pierri Galvao<br>
<<a href="mailto:vendicate@gmail.com">vendicate@gmail.com</a>>wrote:<br>
> > If my code modifications have bugs then that is a major security risk so<br>
> > I would have to keep my code modifications closed under a company<br>
> > copyright license. How can I do this? I was talking to a friend and he<br>
> > said that there is a fine line, one can add code in a way that does not<br>
> > affect the GPL code and therefore does not have to be filed under that<br>
> > license. Would you know of such a way?<br>
><br>
> If the bugs are there, then a copyright is not going to keep your data<br>
> secure.<br>
><br>
> If you are using code that was licensed to you under any license, then you<br>
> don't have a copyright on it. And the modifications you make to it do not<br>
> make it a new piece of code that you have a copyright to.<br>
><br>
> But based on the nature of your, I would highly recommend you look into the<br>
> basics of how copyright and licensing works.<br>
<br>
...and to how security-through-obscurity is total bunk and keeping something<br>
closed source does not magically make it less vulnerable to attack<br>
<font color="#888888"><br>
--<br>
Mackenzie Morgan<br>
<a href="http://ubuntulinuxtipstricks.blogspot.com" target="_blank">http://ubuntulinuxtipstricks.blogspot.com</a><br>
apt-get moo<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
wplug mailing list<br>
<a href="mailto:wplug@wplug.org">wplug@wplug.org</a><br>
<a href="http://www.wplug.org/mailman/listinfo/wplug" target="_blank">http://www.wplug.org/mailman/listinfo/wplug</a><br>
</div></div></blockquote></div><br></div>