Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • If SCO gets resoundingly slapped down by the time OSCON rolls around, it'd seem a bit like beating a dead horse. (Unless you have a Terribly Clever fallback plan, of course :)
    • Not to mention that there really is nothing to be said that hasn't already been said about this whole thing. Most of the open source people in the press sound like a bunch of vapid idiots who won't get any points from the audience they claim this case is alienating. Maybe gather a class action suit at oscon but a panel? It's like preaching to the choir.

    • Actually, I think the case exposes some weaknesses with open source software in the area of patents and PR. Who rebuts SCO claims if SCO goes after Linus instead of IBM? What legal position are the users and creators of open source software in with respect to patent claims?

      Even if this is all magically resolved by OSCON (and don't forget that lawyer time is the opposite of internet time), there's still a lot of post-mortem work to be done.


  • Do it (Score:5, Insightful)

    by ziggy (25) on 2003.05.29 14:36 (#20618) Journal
    I say go for it. The issue with SCO may be resolved by the time OSCon rolls around, but the fundemental issues are bigger still.

    It's nice that we've had a ~30 year run in Open Source with minimal legal troubles. The BSD lawsuit is probably the biggest and most important one, but at the end of it all, AT&T and UCBerkeley were both honorable citizens and let it just go away.

    SCO is possibly the first instance of a bad player coming onto the scene and making noise about the origin of the sources in a big, important project. There will be more bad actors in the future, so understanding what the issues are is going to be increasingly more important. (Put it this way; I don't want my name in the credits of some open source project if Microsoft decides that it misappropriated Shared Source bits.)

    So while the facts of the SCO case make for an interesting soap opera, but the core issues behind the case (and preventing future soap operas, er, court cases) are something I'd like to hear more about at OSCon.

  • Kismet (Score:3, Funny)

    by yudel (1014) on 2003.05.29 15:27 (#20622) Homepage Journal
    Let me point out that OSCON is No SCO spelled backwards, almost.
  • Tiemann (Score:4, Interesting)

    by rjray (1649) on 2003.05.29 18:00 (#20628) Homepage Journal

    Though I rarely shill my old employer these days, there are generally a large number of Red Hat names at the con, usually including Michael Tiemann.

    While it is true that the panel could teeter on the brink of "preaching to the choir", and for that matter the issue may be settled by then, another factor to consider is that the attendance of OSCON is becoming broader and broader. It's not unrealistic to think that there may be a good-sized audience for whom the panel is truly informative.



  • Ransom Love is my neighbor, and probably has all kinds of interesting things to say about this.