LWN.net Logo

Ethical consequences ...

Ethical consequences ...

Posted Feb 21, 2013 16:32 UTC (Thu) by rfontana (subscriber, #52677)
In reply to: Ethical consequences ... by Wol
Parent article: FOSDEM: Richard Fontana on copyleft-next

I don't understand. To make this simpler let's forget copyleft-next and suppose the license is the GPL. What is there in pure GPL that prevents you from "PROTECTING" your customers? I don't even know what you mean by "PROTECTING". It seems to be "making sure customers have up-to-date software and source code". What in the GPL prevents you from doing that?


(Log in to post comments)

Ethical consequences ...

Posted Feb 21, 2013 17:01 UTC (Thu) by Wol (guest, #4433) [Link]

So you ignore the point I'm trying to make!

The GPL promptly makes all my hard work in writing the software valueless (certainly in terms of being able to extract an income stream). You're imposing your "software wants to be free" ethic on me, and not respecting my "the labourer is worthy of his hire" ethic.

In my scenario *I* wrote the software, I want to *sell* the software, and I want to make sure that if I fall under a bus my customers won't be left up s**t creek.

Okay, that obviously means I don't buy in to *hard* copyleft, but your attitude is in the "GPL or die" camp. And you're using copyleft to enforce stuff that is outside the realm of copyright, namely you are (in practice) forrbidding copyright licencing agreements. That's exactly the sort of thing that alienates a lot of copyleft-friendly people who your copyleft-next is allegedly aimed at.

Just as the anti-tivoisation clauses in GPL3 alienated a lot people who saw them as stepping outside the realm of copyright and into the realm of enforcing idealism, so this clause to me smacks of exactly the same.

At the end of the day, if I am sole copyright holder (or have a licence from contributors that says I can) and distribute both proprietary and GPL versions, then those other contributors know up front what they're letting themselves in for. And it's a *contract* matter, not a *copyright* matter.

Equally to the point, I (should) know exactly what I as the copyright holder am letting myself in for. Actually, I have seen at first hand what happens when a company tries to convert their product into a dual-licence proprietary/GPL state. Firstly, they would never have touched your licence in a month of sundays. And secondly, it went rather tits-up because they didn't actually understand what they were getting themselves into. But even given that mess, they have a community. If you want to investigate, google "OpenQM". And people, if you find stuff you don't like, PLEASE don't dive in - they are nice people, really!

Cheers,
Wol

Ethical consequences ...

Posted Feb 21, 2013 17:36 UTC (Thu) by rfontana (subscriber, #52677) [Link]

> The GPL promptly makes all my hard work in writing the software
> valueless (certainly in terms of being able to extract an income
> stream). You're imposing your "software wants to be free" ethic on
> me, and not respecting my "the labourer is worthy of his hire"
> ethic.

I believe you may be confusing "free as in freedom" with "free as in
beer". After 25 or so years it is settled that businesses can extract
income streams from GPL-licensed software.

> Okay, that obviously means I don't buy in to *hard* copyleft, but
> your attitude is in the "GPL or die" camp.

No.

> And you're using copyleft
> to enforce stuff that is outside the realm of copyright, namely you
> are (in practice) forrbidding copyright licencing agreements.

No, I'm essentially saying 'if you use a strong copyleft license for
some software you write, then if you also want to use a proprietary
license for derivative works of that software, give everyone else the
right to similarly use a proprietary license for their derivative
works". It's an equality principle. Nothing is forbidden; quite the
opposite. You are saying that it is okay for a company to have the
sole right to do proprietary licensing of a GPL codebase -- that is
obviously forbidding GPL licensees from entering into proprietary
copyright licensing agreements covering *their* derivative works.

> At the end of the day, if I am sole copyright holder (or have a
> licence from contributors that says I can) and distribute both
> proprietary and GPL versions, then those other contributors know up
> front what they're letting themselves in for.

It's not the contributors I'm concerned about here, primarily, though
one problem with the model you describe is it tends to discourage
community contributions.

> Actually, I have seen at first hand what happens when a company
> tries to convert their product into a dual-licence proprietary/GPL
> state. Firstly, they would never have touched your licence in a
> month of sundays.

That's exactly the effect I wish to achieve.

Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds