Stories
Slash Boxes
Comments
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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 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.