On 5/27/2013 1:42 PM, Ralph Corderoy wrote:
Hi SonWon,

Imposing narrow interpretations on the usage of open free software
will kill this movement one day.
Precise interpretations of free software licences haven't killed the
`movement' after many years.  They would not be much use if imposed in an
imprecise manner.

The goal should be to prevent open source code from being used to make
money from your hard work, and to give you credit.
I disagree.

The GPL was developed to prevent open source code from being stolen
and resold for commercial gain.
It's been a long time since I read about the history of free software
but I'm pretty sure that wasn't the primary intent.

If your code is being used for financial gain then this is a violation
of free open software concepts.
No it's not.  Software released under GNU GPL can directly be used by
others for financial gain.

If someone improves the code and shares with the community then great,
if not, no worries.
Correct.  Private, non-distributed improvements may remain just that.

I don't feel any loss if they don't share their improvements.  I do
however feel a loss when they take code that was open and free and
turn it into a money making machine.
Cygnus turned GPL'd software into a money-making machine.  As have Red
Hat.  With them the code remained open.

Nit picking every little detail of the GPL over who violated what is
just plain going to destroy this community one day.
You wouldn't be referring to my examination of Chad's actions as to
whether he met 3(b) when distributing, would you?  That's not
nit-picking.  It's fundamental.  Where a violation starts is where it
needs to be fixed.

We can see it happening right now, the way we nitpick over who didn't
or did shared when the real focus should be on those who are involved
with making money off of your hard work.
Hmm, this is ringing familiar bells.

So called developers are using your code to solicit donations.  Valid
developers that freely share their code can't receive credit because
some other comes along and steals their work.  Then the thief uses the
stolen code, claims he developed it first, just to solicit more
donations.  Real developers that want to share their code are driven
underground.
If only the creator had published the source code, or provided a written
offer to it, when distributing.  Then there would be a mark in the sand
to clearly refute the `thief's claims.  Instead, you seem to suggest
that having one's copyright violated allows one to do the same to many
others.  It doesn't.  Someone nicking my wallet doesn't make me immune
from arrest if I become a pickpocket in retaliation.

Stealing your code isn't about one man, one developer, the issues here
are much larger.  This is about the future of open source software.
The real thief's are protected and making money off your open source
code.  If this continues this will one day destroy open source.  This
is all wrong.
IMHO you are not going to switch the focus to this.  It will remain on
Chad's attempted loophole to the GPL v2.  You're wasting your time and
the many subscribers.  Anyone that takes GPL v2'd source, modifies it,
and distributes the binary, and therefore their modified source if
they're complying, should have read the licence and understand money may
be made by others from it.

Cheers, Ralph.

Here's an interesting conundrum:

According to Chad's Google+ account, his newest kernels contain a /sbin/readme with instructions on how to receive source.

From: https://plus.google.com/105084384299106728552/posts/3Vu4JQETSM3

"Any kernels I release to the public in the future will also have full current and correct source code. Any "public" kernel released by me to the general public will have information in /sbin/readme on how to acquire source (since per the GPL I only need to provide source to the programs users - once the program is installed, they can read how to obtain source)."

**once the program is installed**

That strikes me as a huge problem. We previously discussed including /proc/config.gz in the kernel to convey a defconfig, but what about source request instructions? I've never heard of it being kosher to include instructions inside of a binary rather than included along with it.

Even if I were to obtain one of these newer files, my Verizon Galaxy S3 (SCH-I535) is not guaranteed to boot Sprint (SPH-L710) kernels. Most of the files Chad posts in development threads are meant for Sprint and I don't recall ever having a Verizon kernel, although I likely snagged at least one along the way. I can't even be sure his public test kernels with weird names include the readme, just the fancy-labelled more official ones I suppose. If I want an HTC kernel source for a binary I downloaded, I'm out of luck since I wouldn't have the necessary hardware to access the readme.

Therefore, according to Chad, simply downloading an Anthrax binary does not afford me the means to obtain source. Unless the instructions are visible in the zip, I have to either boot the kernel (which may fail and temporarily brick my phone) or somehow magically disassemble it to access that readme file.

This arrangement seems to shrink the pool of theoretical people Chad would willingly provide source to. Here's how I see it.

* You need to be someone unknown to Chad. You can still access his message board by linking your Facebook account for manual approval. I assume that anyone from this list would be denied.

* You need to become a poster in good standing, have a number of useful posts, and wait good long while to be manually verified.

* You need to have the proper phone for each file you download. Assuming the instructions are baking into the kernel binary and not visible in the zip, if you want a Sprint GS3 source, you need a Sprint GS3. If you want an HTC EVO source, you need an HTC EVO.

All of the above is completely unreasonable and serve only to prevent requests, instill loyalty, and force people to prove they have a certain phone.

One final remark, Chris "flastnoles" Bunch, a poster on this list and Anthrax member, was going to request and provide source for a number of kernels before he inexplicably backed out and claimed he was hacked. Somehow these plans were discovered and tied to Chris. If someone hacked him, I find that unacceptable and reprehensible. If not hacked, I kindly ask that he reconsider, follow through on his intentions, and not give into intimidation from anyone who would wish to penalize him for a source request.

- Eric Appleman


Reply via email to