apologies / replacement slur :)
zanfur at zanfur.com
Fri Jan 24 15:09:58 PST 2003
I believe the policy applies to all software that has an open source
policy of its own. For instance, the GPL explicitly states that any
derived works must also be open source. The BSD license just says to
give the original authors credit.
So, essentially, I'm saying I agree with you.
On Fri, Jan 24, 2003 at 02:41:31PM -0800, Richard Lotz wrote:
> On Friday, Jan 24, 2003, at 14:30 US/Pacific, Jesse Keating wrote:
> > Actually, there is a company wide non-oss policy. They can't use any
> > open source software, because they are afraid of it seeping into MS
> > code. Pretty much the same reasons as to why most Linux developers
> > wouldn't look at MS code if you put a gun to their head. As soon as
> > you
> > look, you're somewhat poisoned.
> > Just recently I saw a thread where one group wanted to use some open
> > source .NET debugger, since it was far better than any other tool they
> > had access to, yet since it was OSS, they were not allowed to use it.
> > How... funny.
> I thought that policy only applied to GNU software? I actually
> understand, if you're a business that tries to make money of software,
> not wanting to possibly "taint" your code with GNU source. There was
> already evidence of BSD software in 2k, I don't see why MS would
> actually snub there noses at OSS software if the license is such that
> they don't have to acknowledge who wrote the code or give anything back
> at all.
> Richard Lotz
> GPG Key: http://students.washington.edu/rlotz/key.txt
> Fingerprint: 6BD7 C584 7DDC 43FD F0D4 87AB 5A8F 89D5 B3CC 9517
90CF 2E8F 8A96 D0C0 09A2 9CFE C130 6CD4 6DC3 6DCF
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 230 bytes
Desc: not available
Url : http://mailman1.u.washington.edu/pipermail/linux/attachments/20030124/080cfd0f/attachment.bin
More information about the Linux