LWN.net Logo

Advertisement

E-Commerce & credit card processing - the Open Source way!

Advertise here

Closed betas ...

From:  "Anthony W. Youngman" <Anthony.Youngman@ECA-International.com>
To:  "'letters@lwn.net'" <letters@lwn.net>
Subject:  Closed betas ...
Date:  Thu, 19 Sep 2002 12:24:22 +0100

> That does not stop distributors from doing closed beta tests, however. Corel
> did it. Caldera (oops...SCO Group...) has done it. Lindows has done it. And
> UnitedLinux is doing it. The closed beta period ends on September 23, at
> which point the UnitedLinux beta, with source, will be available to all. In
> the mean time, however, one might wonder how the current closed beta is
> being kept closed. 

The way I'd do it is simple. "United Linux" is a trademark. You sign up to
the beta, you do not damage the trademark by releasing any code that could
be associated with the trademark.

In other words, there's nothing stopping people releasing UL code, provided
they delete all references to UL that are in the code, and they don't
mention UL when they post it wherever. Seeing as deleting references and
acknowledgements is taboo, any reputable developer will then quite happily
keep UL itself closed.

And as someone mentioned in the comments, you simply have code there that is
your own copyright, so that it becomes a breach of copyright to just copy
the UL distro "as is".

(As for open betas being better than closed - no that's not necessarily the
case. Far better start with a closed beta and squash the obvious problems
first, then go open and get the more subtle problems later. There *is*
something known as "overload" :-) The whole *point* of a beta is to find
bugs, and having your bugzilla flooded with hundreds of reports of the same
bug can easily become counter-productive)

Cheers,
Wol

(Log in to post comments)

Closed betas ...

Posted Sep 26, 2002 11:27 UTC (Thu) by rknop (guest, #66) [Link]

That would not be legal under the GPL. Under the GPL, if you distribute code based on the GPLed code, then anybody to whom you distribute it must be able to distribute *that* code.

If they have to modify it by removing your changes (even just some of your changes, e.g. comments with your name in it) before they're allowed to distribute it, then you're in violation of the GPL. You're distributing the code under some other licence that may superficially look the same, but is not, since it's got new restrictions on redistribution.

-Rob

Closed betas ...

Posted Sep 26, 2002 17:13 UTC (Thu) by vonbrand (subscriber, #4458) [Link]

If you need something like a "closed beta", explain the why to the testers, and _ask_ them to keep it quiet for a while. I'm sure most will.

If the problem is bug report overload, restrict the bug reporting to official beta testers, or filter the reports.

Copyright © 2002, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds