At 12:13 04.12.2002 +0100, you wrote:
Ceki Gülcü wrote:
At 11:06 04.12.2002 +0100, Nicola Ken Barozzi wrote:
IANAL and not the one to decide.
IIRC IIUC the board, &&|| board members have said to use the full
version till version 2.0 arrives.
Well, as far as I know, there is no permission to use a reference to
the license although there is no explicit prohibition either.
You mean that everything can be done if it's not prohibited explicitly?
Come on, what's this, a policed community?
I was trying to convey that the word "should" has different meanings. It
can be interpreted as a recommendation or alternatively as an
obligation. For example,
1) One should brush one's teeth. Otherwise, you'll get bad
teeth. However, not brushing your teeth does not make you a bad
citizen.
2) One should be respectful of others. Being disrespectful or violent
makes you a bad citizen.
In 1) SHOULD is a recommendation whereas in 2) SHOULD really means MUST.
Thus, in the sentence, "we should use include the license in each
file," does SHOULD mean MUST or is it just a recommendation?
You are free to take my word for it, or if you deem it necessary, go ask
directly and eventually report back.
Michael A. Smith actually went to the board a few weeks ago. I did not
see a closure. As long as an ASF official (board, PMC) does not
officially take a position on this, or until there is an official
document on this topic, one should not make absolute affirmations.
My words: "Currently we should use the full version."
Should or must? :-)
To stop this once and for all, since it seems that having a short license
is very important for some (still don't know why), I've sent a request for
clarification to the board too.
The license (version 1.1) is 41 lines long whereas the copyright notice
plus the reference to the license is just 7 lines.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
--
Ceki
TCP implementations will follow a general principle of robustness: be
conservative in what you do, be liberal in what you accept from
others. -- Jon Postel, RFC 793
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
