Re: Request for suggestions of DFSG-free documentation licences

2007-05-28 Thread Adam Borowski
On Sun, May 27, 2007 at 10:15:06AM +1000, Ben Finney wrote:
 The document author, by placing only *some* parts of the work under
 the GPL, is essentially determining for the recipient what parts they
 will find useful to combine with other parts of the software. Prose
 descriptive parts could be combined into the data, for instance; if
 the license does not allow this, an essential freedom is denied.
 
 On the other hand, if the author acknowledges that *any* part of the
 work could be useful for some recipient to combine with other parts of
 the work, *even if the author can't conceive of it initially*, then
 the logical thing to do is to license all parts of the work under the
 same terms.
 
 Further, when parts of a work licensed under GPL are combined into the
 FDL-licensed work, the result is *not redistributable at all*, because
 the GPL says the resulting work must be entirely licensed under GPL,
 which conflicts with the FDL work's license terms.

There are no real solutions except:
* boycotting one of the licenses (easy to tell which one) whenever you have
  the chance to do so (ie, mostly as upstream)
* bashing the FSF until they merge GPL and GFDL

Of course, as a maintainer you usually can't do anything but complain, or
look the other way at contamination incidents.  Which are quite common --
even foo --help is likely to be one.  And looking the other way, while
popular, can't be called the most sound advice...

-- 
1KB // Microsoft corollary to Hanlon's razor:
//  Never attribute to stupidity what can be
//  adequately explained by malice.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: (C) vs ©

2007-05-28 Thread Shriramana Sharma

Thanks to all who replied.

Antti-Juhani Kaijanaho wrote:
Further, whether (C) or ©, isn't it superfluous to use it after the word 
copyright which itself means the same thing?


Yes.


So I can simply avoid using either (C) or © and thus avoid this whole 
problem?


So if the following:

---
Copyright 2007, Company X, Country Y. All rights reserved.
---

will be sufficient, I will use it.

Shriramana Sharma.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: help with crafting proper license header for a dual-licensing project

2007-05-28 Thread Shriramana Sharma
Hello people. One question about the header I recently sent for final 
approval --


The project developers want to distribute a single set of source files 
under both the licenses. They don't want to have to maintain two 
different directories with two different versions of the same files with 
merely the license headers differing.


So this means that the header must be appropriate for both the GPL and 
the Professional License. I presume it is sufficient if it indicates 
that the source file can be used under both licenses. For the GPL the 
disclaimer of warranty is a must, A similar disclaimer is still 
applicable to their Professional License.


So how should I change the latest draft I sent so that the same source 
files can be distributed to both GPL and Professional License users?


Shriramana Sharma.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: (C) vs ©

2007-05-28 Thread Antti-Juhani Kaijanaho
On Sun, May 27, 2007 at 12:38:28PM +0530, Shriramana Sharma wrote:
 So I can simply avoid using either (C) or © and thus avoid this whole 
 problem?

Sorry, I misread your question originally.  You can drop the word Copyright,
but you cannot drop the copyright symbol, if you care about UCC compliance.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: help with crafting proper license header for a dual-licensing project

2007-05-28 Thread Francesco Poli
On Sun, 27 May 2007 14:24:21 -0700 Don Armstrong wrote:

 On Sun, 27 May 2007, Francesco Poli wrote:
  On Sun, 27 May 2007 02:43:41 -0700 Don Armstrong wrote: 
   On Sun, 27 May 2007, Francesco Poli wrote:
[...]
  If you consult a dictionary you won't find any reference to the FSD
  or to the DFSG in the definition of the adjective free.
 
 Of course, but the usage of free there is merely an extension of its
 actual english meaning.[1] We use free in our conversations about
 licensing and software because of the meaning that it already
 posseses, not the other way around.

The first meaning can be:

From The Collaborative International Dictionary of English v.0.48
[gcide]:

  Free \Free\ (fr[=e]), a. [...]
 1. Exempt from subjection to the will of others; not under
restraint, control, or compulsion; able to follow one's
own impulses, desires, or inclinations; determining one's
own course of action; not dependent; at liberty.
[1913 Webster]

From WordNet (r) 2.0 [wn]:

  free
   adj 1: able to act at will; not hampered; not under compulsion or
  restraint; free enterprise; a free port; a free
  country; I have an hour free; free will; free of
  racism; feel free to stay as long as you wish; a
  free choice [ant: {unfree}]

A piece of free software is not able to act at will, nor is it
exempt from subjection to the will of others.
Rather, some important freedoms are granted over a piece of
free software.
So you are right that the technical meaning is related to the
common one, but some interpretation and stretching has to be
done in order to go from the latter to the former.

Likewise, the first meaning of proprietary can be:

From The Collaborative International Dictionary of English v.0.48
[gcide]:

  Proprietary \Pro*prie*ta*ry\, a. [L. proprietarius.]
 Belonging, or pertaining, to a proprietor; considered as
 property; owned; as, proprietary medicine.
 [1913 Webster]
  
From WordNet (r) 2.0 [wn]:

  proprietary
   adj : protected by trademark or patent or copyright; made or
 produced or distributed by one having exclusive rights;
 `Tylenol' is a proprietary drug of which
 `acetaminophen' is the generic form [ant:
{nonproprietary}]

A piece of non-free software belongs to a proprietor, in the sense
that a monopoly over it is held by the copyright holder.
On the other hand free software (even when copyrighted) grants enough
freedoms that everyone has the right to fork it and adapt it to his/her
own needs, even against the will of the original copyright holder: in
this sense we could say that a piece of free software is not really
owned by anyone (even though there are still copyright holders).

A piece of non-free software is aggressively and excessively
protected by trademark or patent or copyright.
Free software can still be protected by copyright, but in a way
that grants enough freedoms to everyone: in this sense it's not
proprietary, because enough actions covered by exclusive rights
are permitted to everyone.

 
  Please bear in mind that we are talking about technical meanings
  that have to be defined in their field: a non-technical dictionary
  won't help.
 
 The word proprietary has a perfectly well defined meaning in this
 field. It means closed or exclusive. That people mistakenly conflate
 it with being non-freeness has little to do with its actual meaning.
 
 Things that are non-proprietary are perfectly capable of being
 non-free. See for example the works in non-free for which we actually
 have source code. They are clearly not proprietary, but are definetly
 not free.

I still cannot see why proprietary should mean with secret source
code: its basic common meaning is owned by a proprietor and does
not refer to closeness or secrecy.

 
  I've sometimes seen the closed/open distinction used to refer to the
  availability of source code (which is a necessary, but
  non-sufficient, condition for freeness).
 
 It can refer to that, but it can also refer to specifications,
 standards, protocols, goods, etc. Exclusivity is nearly a synonym for
 proprietary.

Yes, exclusivity.  When enough actions covered by your exclusive rights
are permitted to everyone (as in Free Software), you have really little
exclusivity left.
That's why I don't think the use of the term proprietary as a
synonym of non-free should be considered so strange or awkward.

[...]
 What you're attempting to do is not comparable; it's inventing new
 definitions for words which are not commonly or historically agreed
 upon.

It's not me.  I'm not trying to invent new definitions, as I am not
the only one who uses the term proprietary as equivalent to
non-free.  Many others seem to do so: one notable example is RMS
and the FSF (I'm certainly *not* claiming that RMS is always right,
he's very far from being always right actually, but, in this regard,
I think his terminology is not bad).


-- 
 

Re: help with crafting proper license header for a dual-licensing project

2007-05-28 Thread Anthony W. Youngman
In message [EMAIL PROTECTED], Francesco 
Poli [EMAIL PROTECTED] writes

I still cannot see why proprietary should mean with secret source
code: its basic common meaning is owned by a proprietor and does
not refer to closeness or secrecy.


Your own words condemn you :-)

This is an accurate description of linux. Linux is owned by a 
proprietor, namely whoever (singular or plural) happens to own the 
copyright(s).


Cheers,
Wol
--
Anthony W. Youngman - [EMAIL PROTECTED]


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]