On Jan 2, 2008 11:12 AM, Sean B. Palmer wrote:
> the question being the fairly subtle one of whether unqualified
> permission to modify a file *entails* modification of copyright
> notices.
Ah, this may in fact be irrelevant!
"The phrase /above copyright notice/ is somew
hat I know
how to make, and ask friends and people on debian-legal and so on...
In other words, if you have evidence that's better than mine, please
do tell me!
--
Sean B. Palmer, http://inamidst.com/sbp/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
7;t be able to know that now since you weren't
patient enough to find out :-)
> Have they fixed that google bug where you can hide whole
> threads by sending a known spam body [&c.]
This is off-topic for this list as far as I understand, but I've not
heard of this bug before
hanks to everyone for that; and sorry to spoil your bad reputation :-)
--
Sean B. Palmer, http://inamidst.com/sbp/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ndates the preservation of copyright notices...
No, it says the "above copyright notice and this permission notice"
only. When you're using a LICENSE.txt file, that means the content of
the LICENSE.txt file only. It doesn't say anything about anything
else.
> Disclaimers: IANAL, TINLA, IANADD, TINASOTODP.
Same here! :-)
--
Sean B. Palmer, http://inamidst.com/sbp/
package they apply to are retained and
preserved.
> http://www.eff.org/deeplinks/archives/001398.php
> http://www.epic.org/privacy/gmail/faq.html
> http://www.gmail-is-too-creepy.com/
> http://mjr.towers.org.uk/blog/2006/google
Well at least you're not forced to use Google Mail.
N
us email in this thread.
I would need to delete a single clause to, I think, make it fully
compatible with my requirements. Is it DFSG compatible in your
opinion? It doesn't seem to be widely used, sadly.
--
Sean B. Palmer, http://inamidst.com/sbp/
--
To UNSUBSCRIBE, email to [EMAIL
port List-Post and
> other common mailing list behaviours? You're the user, after all.
Because I don't know that it's common, and I don't mind the behaviour
myself (I think that good clients should drop duplicates).
Thanks,
--
Sean B. Palmer, http://inamidst.com/sb
On Dec 30, 2007 5:51 PM, Sean B. Palmer <[EMAIL PROTECTED]> wrote:
> A = Allows short statement of application
> B = Preserves copyright statements and notices
> C = Allows distribution without full license text
> D = License is or may be fixed to exclude later versions
An
hat the following might be okay:
* * *
Copyright 2007, Sean B. Palmer, inamidst.com
Released to the public under the CDDL, v1.0 only.
* * *
But that column C failure is a shame. Note that though every single
common license failed column C, some licenses such as the AFL 3.0 do
pass that column.
ed under the Academic Free License version 3.0'
- http://opensource.org/licenses/academic.php
So I could use that as follows:
* * *
#!/bin/sh
# Copyright 2007, Sean B. Palmer, inamidst.com
# Licensed under the Academic Free License version 3.0.
[&c.]
* * *
And now you can make modif
nes have to be 70 column long?
Nobody; but Guido van Rossum says they must be 79 columns :-)
Really the difference comes down to the following:
* * *
Copyright 2007, Sean B. Palmer, inamidst.com
Released to the public under the Example License.
* * *
Compared to:
* * *
Copyright 2007, Sean B
ect the notice. Please read my badly explained
requirements carefully :-)
Probably I'm just hoping for the moon, but maybe someone can help me out here?
Thanks,
--
Sean B. Palmer, http://inamidst.com/sbp/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
13 matches
Mail list logo
