On Jul 5, 12:47*am, "impossible" <impossi...@nospam.net> wrote:
>
> You didn't answer the questions.
>
> (1) Do you accept that most customers do not understand their obligations
> under the GPL?
I am happy to take 'Open Logic's' release at its face value. I also
note that MPAA, RIAA and BSA frequently tell similar horror stories
about how many people are pig ignorant of the meaning of copyright.
My answer is 'no', but would be 'yes' if 'most' is changed to 'many'.
>
> (2) *Do you think that a customer's choice of software might be different if
> they understood that the supposedly "free" software they picked does not
> belong to them? That they cannot freely distribute it to others without
> adhering to the GPL's licensing restrictions?
An 'end user' customer generally could not care less as long as the
product works. In any event the end user is not breaching the GPL and
the GPL does not forbid an 'end use' customer from running allegedly
'tainted' code. Moreover the FSF and other GPL copyright assignees
have no bother with such end users. AFAIK no 'end user' (ie someone
who merely runs the code) has ever been sued or even sent a warning
letter for an alleged GPL breach.
A similar sort of survey would also show that most people using Micro
$oft products are pig ignorant of the terms and conditions of the
EULA. They are just not interested. They do not want to know - it
would give them the screaming heebies jeebies. For example how many
ordinary users know that the EULA forbids the 'benchmarking' of Micro
$oft products.
So my answer to your question is 'no'.
> *The information about the open source licensing mess happens to come from a
> study by an open source support company. Deal with it!
>
> http://www.tmcnet.com/usubmit/2010/06/30/4879060.htm
>
'Open Logic' never claimed that there is an 'open source licencing
mess'. The release merely stated that many makers of hardware and
software products using GPL'd code are ignorant of the requirements of
the GPL. If the GPL were a 'licencing mess', Micro$oft's EULA would be
a far greater licencing mess.
It is no problem with the licence whether it be the GPL or Micro$oft's
EULA if people treat the licence as a joke. This does not mean that
people should stop using the product.
>
> > In general usage in this context 'proprietary' is a term of art
> > meaning not 'open source' code. This is clear to everyone except
> > 'Impossible' whose arguments depend on muddying the waters.
>
> LOL. As I've noted many a time, Larry D'Loserites are hopelessly confused
> about the meaning of property.
You are just a sick puppy with this sort of personal abuse.
> But your attempt now to fob off proprietary
> rights as a "term of art" is a new one. We all eagerly await your reference
> to a reputable legal source whop is prepared to back you up on that
> ridiculous comment.
OK, in my previous posts, for 'proprietary' read 'closed source'. If I
have misled you by my inaccurate use of the term 'proprietary' I
apologise. No one else seems to have been misled by my alleged
inaccuracy.
>
> Are you seriously claiming that open source *developers do not have certain
> exclusive, proprietary rights over the software they create? If not, then
> why on earth would anyone be "obligated", as you you put it, to respect the
> term and conditions of the GPL or any other license under which that
> software is released?
No I am not. Open source writers who release their software under GPL
or other licences do reserve all rights except as licenced. I do agree
however that some people and manufacturers do treat the GPL as a joke.
Many however include Micro$oft do take the GPL and similar licences
very seriously indeed.
This disposes of your other 'angels dancing on a pinhead' type
arguments.
Basically, you are trying to build a big house of cards on a shaky
foundation in your whole set of arguments.
The conclusions are quite simple:
1. End users need have no concern if the GPL'd code they are running
had been 'tainted' in some way.
2. Makers of hardware and software that uses GPL'd code in breach of
licencing conditions risk being 'pinged' by FSF, the Busybox creators,
etc.
3. Such makers can readily comply with the GPL while protecting their
commercial interests.
4. Even if a maker is 'pinged' by FSF, etc, but is then co-operative,
the consequences are much, much milder than the consequences of being
'pinged' by the BSA.