lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <orr6o88yrj.fsf@oliva.athome.lsd.ic.unicamp.br>
Date:	Mon, 18 Jun 2007 23:27:12 -0300
From:	Alexandre Oliva <aoliva@...hat.com>
To:	Johannes Stezenbach <js@...uxtv.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Al Viro <viro@....linux.org.uk>,
	Bernd Schmidt <bernds_cb1@...nline.de>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Ingo Molnar <mingo@...e.hu>,
	Daniel Hazelton <dhazelton@...er.net>,
	Greg KH <greg@...ah.com>,
	debian developer <debiandev@...il.com>, david@...g.hm,
	Tarkan Erimer <tarkan@...one.net.tr>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On Jun 18, 2007, Johannes Stezenbach <js@...uxtv.org> wrote:

> On Mon, Jun 18, 2007, Alexandre Oliva wrote:

>> People talk a lot about TiVo here, but do they the faintest idea of
>> how the conversations with TiVo are proceeding?  I thought so...

> Oh, if you know something we don't, could you please fill us in?

Honestly, I don't know either.  But I get an impression that there are
conversations underway.

> And who was it who coined the "Tivoization" term, thus putting
> TiVo into focus?

AFAIK TiVo invented the practice, did they not deserve the credit?

> Hm, you only talk about people who already use free software,
> but I tried to make you aware of the importance of
> _promoting_ free software, i.e. winning new people and
> companies for the free software idea.

Aah, I see.  Indeed, I'd missed that aspect.  Sorry about that.

My take on it is that bringing free loaders in doesn't help us much,
and bringing them in in a way that they don't learn the essential
aspects of the community will hurt the community in the long run.

So they must become aware that respecting others' freedoms is not only
the right thing to do, from a moral and ethical standpoint, but also
that this is precisely what enables our community to thrive, and to
enable everyone to get the best out of the software we cooperate to
develop.

> I think the majority of embedded devices still run proprietary
> RTOSes, and the majority of desktops still run Windows or Mac OS.
> Don't you want to change that?

Sure.  But getting those companies to adopt Free Software in a way
that turns it into non-Free Software doesn't change that in any way.

Of course we might get some additional contributions here and there,
but then more and more users would still be stuck, unable or limited
in the ways and incentives they have to participate in our community.
Permitting this is very short-sighted.  It might bring us apparent
advantages in the short run, but the more such disrespects there are,
the more there will be, and the fewer users will be able to become
developers.  In the end, this may kill the whole process, in a tragedy
of the commons.  In the article linked below, I argue this very point,
comparing how the demand for respecting users' freedoms is what keeps
the free-loaders away and makes the GPL the most cost-effective
license for software development, compared with permissive licenses
and non-Free licenses.  The very same arguments apply to a comparison
between a license that permits tivoization and one that doesn't,
because the latter is more likely to have more contributors to share
the load, and both equally reduce the likelihood of unmergeable forks.
http://www.lsd.ic.unicamp.br/~oliva/papers/free-software/BMind.pdf

> if you raise the entry barrier too high, they won't get started at
> all.

I acknowledge this argument, but I hear the same arguments against the
GPLv2, claiming the barrier is too high, and it's not from people who
believe that tivoization is already prohibited.

> They are aware of the trend towards Linux, but are afraid that the
> obligations of the GPL might be impractical for them.  Then they
> only have the choice to not use Linux, or to use "creative
> workarounds".

Or to respect users' freedoms, enabling/motivating those users to
become developers in our community.

> It's true that what these companies do might have little direct
> benefit for users buying their products, however the long term
> benefits of getting the people in these companies exposed to free
> software ideas, and in contact with the free software community, can
> only be positive

As long as they understand how the community works, be it from the
moral and ethical standpoint, be it from the pragmatic standpoint.  In
both cases, the end result is that they learn that, when they share
and cooperating, respecting users freedoms (enabling and providing
incentive for them to improve the software), everybody wins,
themselves included.

>> So you see, the picture of anti-tivozation is not as bleak as people
>> try to frame it.  In fact, it's not bleak at all.  If one out of 10,
>> maybe even 1 out of 100 vendors start respecting users' freedoms, when
>> faced with anti-tivoization provisions, the community will already win
>> big time, because each vendor is likely to have thousands of
>> customers, some of which will use the freedoms to serve the goals of
>> the community, in the very terms the community claims to care about.

> Does this multiplicator also apply to new companies
> which start using free software for their products?

Of course, even more so!  Then you win not only the contributions from
the user, but also from the company itself, which you didn't have
before.

-- 
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@...dhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@...d.ic.unicamp.br, gnu.org}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ