GPL'd software and CLOSED betas

[hums07]

AFAIK, they dont have to make the binary available and if they wish they can disclose the source only upon request. Once requested, they must provide the source to the one who asks for it.

[mevets]

What closed beta are you talking about?

Boxee (boxee.tv). You probably were writing your reply when I posted so hopefully this post sends an instant notification to you.

[t0p]

AFAIK, they dont have to make the binary available and if they wish they can disclose the source only upon request. Once requested, they must provide the source to the one who asks for it.

Yeah right, seems to me some people misunderstand the GPL.

I can create software, license it under the GPL, then choose to distribute it to 1 person, 100 people, or 0 people. My choice. Sure, the people I distribute to can give it to who they like... but I don't have to.

Furthermore, I can take a piece of pre-existing GPL'd software, modify it, then keep it all to myself if I like. Perfectly legal. I don't have to distribute.

[northern lights]

Sure you may keep it to yourself.

However, if you do distribute, I'd interpret the following (section 2, GPL version 2)

You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.

b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.

c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.

such that you have to make at least the source, if not binaries also, accessible to the entire public. If you're certain that's not the case, could you please explain your interpretation? Thank you in advance.

It is indeed questionable how many people have to receive the code/executables and in what function or for what reasons before transfer of code/executables is considerd "distribution"

[txcrackers]

"at no charge" != "publicly accessible to any and all via web-site"

It simply means that you cannot charge for the code. It does not specify how the code is to be distributed. Plus, you have to remember that the GPL actually pre-dates the WWW.

[northern lights]

"at no charge" != "publicly accessible to any and all via web-site"

True. Now this projects members complied to the request to share code. If that hypothetically wouldn't have been the case though that'd be a violation to me.

Plus, you have to remember that the GPL actually pre-dates the WWW.

This particular revision indeed does. But the same section exists in version 3.