-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> If it prevents DRM to be implemented and later commercially exploited, it
> may have its place.
Impossible, it's Open Source, we can't prevent anyone from doing
anything they want to the code on their own. Just as you can't prevent
someone from eating carrots for dinner in another country.
> It may still be free but the intent will be damaged.
No, the intent remains the same. Nobody can tarnish the Plucker
name, unless we ourselves tarnish it. Nobody can take Plucker, change it,
and continue to distribute it as "Plucker". They can call it whatever they
want, but it's not hurting Plucker, the proejct, or the Open Source
community, it just hurts their fork of the project.
> But somebody else may do it. In fact plucker code was already stolen and
> sold by Bluesomething. Don't help them - just ignore DRM issues.
They were 100% within their rights to download the code, use the
code, sell the code, and in fact the GPL encourages exactly that. There is
nothing stated in the GPL that says I can't take anyone's GPL software,
package it up with my own name, and begin selling it at any cost, to anyone
I wish, commercially or non-commercially.
This company was, however, NOT within their rights to make changes
to the code which were not contributed back to the project and thus to the
community as a whole. That was the reason for starting the investigation.
d.
perldoc -qa.j | perl -lpe '($_)=m("(.*)")'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.1.92 (GNU/Linux)
iD8DBQE9mFBqkRQERnB1rkoRAgdwAKClIWEi7/i0608HL9xe7GVK7YNPPQCg0lMw
bm1BPHCU4aBYT+F4cgOGZNA=
=/5a8
-----END PGP SIGNATURE-----
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
