From: Jonathan Larmour <jifl@eCosCentric.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: Commentary on the OPL
Date: Wed, 22 Jun 2005 11:10:00 -0000 [thread overview]
Message-ID: <42B9470C.3050602@eCosCentric.com> (raw)
In-Reply-To: <20050622091904.GW3201@donkey.ma.tech.ascom.ch>
Andrew Lunn wrote:
> On Thu, Jun 16, 2005 at 01:40:31PM +0100, Jonathan Larmour wrote:
>
>>We use the Open Publications Licence for our docs as you know. I've
>>stumbled across this interesting commentary on it. It's quite interesting,
>>to me at least :)...
>
>
> Was there some requirement for FSF that we change license?
Not yet. But they may either try to insist, or at least argue strongly
that we use the FDL. If the latter then we'd have to have a strong belief
that we're using the most appropriate licence. That commentary undermines
some of that belief, to me at least.
Not that the FDL seems very good either. I have concerns, shared by others
on the net, about how "Free" the FDL is. For example, how Free is it in
section 4 <http://www.gnu.org/copyleft/fdl.html>. There's a whole load of
things that restrict freedom there, and a "modification" need only be trivial.
It's very different to the GPL in principle. The GPL is all about the
freedom to modify. The FDL is all about restrictions on that.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
next prev parent reply other threads:[~2005-06-22 11:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 12:38 Jonathan Larmour
2005-06-22 9:19 ` Andrew Lunn
2005-06-22 11:10 ` Jonathan Larmour [this message]
2005-06-22 11:16 ` Andrew Lunn
2005-06-22 11:29 ` Jonathan Larmour
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42B9470C.3050602@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=andrew.lunn@ascom.ch \
--cc=ecos-maintainers@ecos.sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).