[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Request for GR: clarifying the license text licensing / freeness issue



On Mon, Apr 23, 2007 at 12:37:16PM +1000, Ben Finney wrote:
> > Yes, the social contract says that the Debian system and all of its
> > components will be fully free; but for all practical intents and
> > purposes (heh), the accompanying license texts are as much a
> > "component" of the "system" as is the media the system is
> > distributed on.
> 
> I don't see the relevance of this. If you're referring to the
> GPL-specific exception for source code

No, I'm not, I'm referring to the second sentence in the document,
'We promise that the Debian system and all its components will be free
according to these guidelines.'.

> > Yes, you can't do without it, but you also can't start obsessing on
> > it because the matter can soon get absurd after that. (There is no
> > free hardware to run it on, oh my!)
> 
> When hardware is something distributable by the Debian project as part
> of Debian, then this might be relevant; it isn't an issue with current
> technology.
> 
> License texts *are* distributed by Debian, now, under terms that are
> non-free. This behaviour doesn't match the Social Contract.

Sure, they are technically being distributed, but not as something
the social contract cares about. (Pardon the personification.)

> > Lawyers would likely ask us - what would be the legal purpose of
> > addressing this concern?
> 
> Why would lawyers ask us that, and why are their questions about the
> Social Contract germane here? It's not a legally-binding document.

My point exactly. There is no reason to apply the "we must clarify
everything and anything in order to not get sued" legal logic.

> > Trying to "clarify" the social contract by elaborating on peripheral
> > things that aren't immediately obvious, is basically nitpicking, and
> > it shouldn't be done.
> 
> I would think thazt *only* things which are immediately obvious are
> exempt from the need for clarification. Anything else needs to at
> least be considered on its merits, and not dismissed because it's "not
> immediately obvious".

It is being considered on its merits, it's not dismissed because it's
"not immediately obvious", but because it's "nitpicking".

> > Also, nobody cares for statements that can be normalized to 'you can
> > do all this, except that, that, that, and that', and those should
> > also be avoided if we want readers to take the spirit of the
> > document seriously.
> 
> I don't see how that's at all true. Contrariwise, I would hope you
> agree that a document that says "we will always do this, and never do
> that", but which is routinely violated in practice, is one that
> readers will not take seriously.

Except that we seem to disagree on whether the obligatory distribution of
licenses, regardless of their own license, falls under the "that" which we
promised never to do.

-- 
     2. That which causes joy or happiness.



Reply to: