From: Ryan Underwood <nemesis-lists@icequake.net>
To: devel@xfree86.org
Cc: linux-fbdev-devel@lists.sourceforge.net, forum@xfree86.org
Subject: Re: Re: [forum] Re: Announcement: Modification to the base XFree86(TM) license.
Date: Sun, 1 Feb 2004 16:33:35 -0600 [thread overview]
Message-ID: <20040201223335.GB16019@dbz.icequake.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0401311258330.4585-100000@ard.bishopscourt>
[-- Attachment #1: Type: text/plain, Size: 2600 bytes --]
On Sat, Jan 31, 2004 at 01:06:23PM +0000, Andrew C Aitchison wrote:
> > And, have you asked the mgafb driver author about this ?
> >
> > You can hardly complain about lack of back traffic if you didn't ask him
> > about it, and if you did, it would be interesting to this discussion to
> > know what the problems where.
>
> "The Author" ?
> This is open source code; there may be 27 authors of the relevant file.
> In XFree86 code I wouldn't know how to find the author of a file without
> looking at that file. My {limited ,mis}understanding of clean room coding
> makes me wary of reading any source unless I know that its licence will
> allow me to do what I wish.
The only authors that legally matter are the ones listed in the
copyright notices. There are three copyright notices in the matroxfb
stuff: one is Petr, another is Gerd Knorr and the other is Matrox. I'm
sure Petr has a pretty clear idea what he wrote, and I doubt Gerd would
get an attitude with you either over anything he did. Since you haven't
even inquired about it, you don't have much to complain about as I see
it.
> OK. So I've probably been paranoid and lazy, but if the fbdev licence
> had been compatible with the XFree86 one, I would have done the work.
> As it is the bar was raised high enough to stop me.
Or maybe the license incompatibility was simply a convenient way to cop
out of doing some work?
> > > So, for one developer at least, the reason there has been no traffic
> > > from fbdev to XFree86 is *directly* because of the licence issue.
You can't copy and paste code. You _can_ rewrite code. Hardware
interfaces, trivial routines, and problems for which there exist only one
or a few obvious ways of solving them are all examples of where
copyright does not apply. Porting any code from fbdev to a XFree86
driver *will* involve substantial rewriting. I know this because I'm
currently doing it for the mga driver.
> > Yeah, but again, was it so because of a definite will on the fbdev
> > authors part, or because you didn't ask him ?
>
> Isn't the aim of open source licences is to allow people to use the code
> without tracking down the author and obtaining permission ?
No. The aim of open source licenses is to allow people to use the code
_under the terms the author chose_ without tracking down the author and
obtaining extra permissions.
> I can do that with closed source.
I don't see how you have greater freedom with closed source licenses,
but feel free to elaborate.
--
Ryan Underwood, <nemesis@icequake.net>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-02-01 22:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040131113753.GA19133@iliana>
2004-01-31 13:06 ` Re: [forum] Re: Announcement: Modification to the base XFree86(TM) license Andrew C Aitchison
2004-01-31 22:24 ` Benjamin Herrenschmidt
2004-02-01 22:33 ` Ryan Underwood [this message]
2004-02-02 11:41 ` Sven Luther
2004-02-02 13:13 ` Harold L Hunt II
2004-02-02 16:04 ` Sven Luther
2004-02-02 13:59 ` Dr Andrew C Aitchison
2004-02-02 16:11 ` [Linux-fbdev-devel] " Sven Luther
[not found] <20040129115838.A70069@xfree86.org>
[not found] ` <1075423804.12536.28.camel@gaston>
[not found] ` <16410.33783.236964.200047@xf11.fra.suse.de>
2004-01-30 17:32 ` Sven Luther
2004-01-30 19:25 ` Egbert Eich
2004-01-30 22:29 ` Sven Luther
2004-01-31 9:10 ` Andrew C Aitchison
2004-01-31 11:37 ` Sven Luther
2004-01-31 22:07 ` Ryan Underwood
2004-01-31 21:48 ` Mark Vojkovich
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=20040201223335.GB16019@dbz.icequake.net \
--to=nemesis-lists@icequake.net \
--cc=devel@xfree86.org \
--cc=forum@xfree86.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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 NNTP newsgroup(s).