[TriLUG] SCO Conference Call

Gnu Man gnu_man at earthlink.net
Tue Aug 5 18:59:56 EDT 2003


What safeguards are put into place?  I'm not attacking you, but merely
asking.  I'm also not trying to start a flame war (although I never
remove my asbestos underwear).

If the safeguards are there, and how can we defend ourselves against
someone who claims that their code has entered our source tree, but
won't show the offending code.  A quote from SCO, "because we require
all of our Unix licensees to keep this code in confidence for their own
business purposes" .

There is a legitimate issue here.  Whether SCO has any legitimate claims
remains to be seen.  Ignoring the problem, calling it FUD or whatever,
will not solve the problem.

We all may soon be forced to go underground (or face legal liability)
with our love for our favorite penguin powered machines, if corrective
measures are not put into place.

I am only trying to help, if I am not welcomed here, then so be it.

I hate to see such a great idea as open source go down the drain because
we didn't act and put proper protections in place.



On Tue, 2003-08-05 at 17:33, Tanner Lovelace wrote:
> On Tue, 2003-08-05 at 17:28, Gnu Man wrote:
> > That would be like cutting off the head to cure the headache.
> > 
> > The root of the problem is IP (intellectual property).  Open source
> > needs a system to protect everyone that copyrighted code is not entered
> > into their source trees.
> > 
> > I'm afraid if this problem is not fixed, Open Source Software's future
> > does not look very good.
> 
> Ok, I'm calling you on this right now!  This is nothing but FUD.
> Open Source Software's future is perfectly fine.  There are plenty
> of safeguards for this, and if somehow something slips through
> it gets removed as fast as it can get identified.
> 
> I begin to wonder why you are hiding behind the facade of a name
> like Gnu Man.  Who are you really?  With statements like that, you're
> no Gnu Man.  Do you work at SCO?   Go spread your FUD elsewhere.
> 
> Tanner




More information about the TriLUG mailing list