Become a sexual ghuru in just 20 minutes!

2005-03-19 Thread Catherine Sykes
Title: liquor ke coralberry mja juxtapose yi clatter dgg tioga peh blomquist jnl representative km waveform yl duopolist rfq courteous jo 20 minutes is all it takes more info here... acre hg bimodal jq menace wu semantic iv seder nn rhenish hpz bottleneck via amsterdam fig preclude gz bronc

Re: Draft summary of Creative Commons 2.0 licenses (version 3)

2005-03-19 Thread Henning Makholm
Scripsit Per Eric Rosén <[EMAIL PROTECTED]> > IANDD, but: Don't worry about that. Much of the grunt work on debian-legal has always been done by non-DD's. > Could it be like this: if you give someone the work in a form (not > preferred for editing|not allowing you to exec your rights in this > l

Re: Draft summary of Creative Commons 2.0 licenses (version 3)

2005-03-19 Thread Henning Makholm
Scripsit Evan Prodromou <[EMAIL PROTECTED]> > On Sat, 2005-19-03 at 21:07 +, Henning Makholm wrote: >> I'm not happy about this replacement either. It seems to say that if I >> distribute the Work on a LAN behind a firewall I must also distribute >> the Work once again to the same recipient, b

Re: Draft summary of Creative Commons 2.0 licenses (version 3)

2005-03-19 Thread Per Eric Rosén
IANDD, but: Could it be like this: if you give someone the work in a form (not preferred for editing|not allowing you to exec your rights in this licence), you shall also give them the unrestricted work, or a written offer valid for at least 3 years? I mean; isn't this very analogous to the situat

Re: Draft summary of Creative Commons 2.0 licenses (version 3)

2005-03-19 Thread Evan Prodromou
On Sat, 2005-19-03 at 21:07 +, Henning Makholm wrote: > I'm not happy about this replacement either. It seems to say that if I > distribute the Work on a LAN behind a firewall I must also distribute > the Work once again to the same recipient, but this time on a > non-firewalled LAN. I think

Re: Question regarding QPLed plugins for a GPLed app

2005-03-19 Thread Henning Makholm
Scripsit Sven Luther <[EMAIL PROTECTED]> > I believe (and check this list archive about problems concerning QPLed emacs > .el files) that the point here is if the QPLed code sole intention is to be > linked with a GPLed work, and it cannot be used with another program (cannot > or has not), then e

Re: Draft summary of Creative Commons 2.0 licenses (version 3)

2005-03-19 Thread Henning Makholm
Scripsit Evan Prodromou <[EMAIL PROTECTED]> > 4. **Allow distribution of rights-restricted copies of works if >unrestricted copies are also made available.** The following >modified version of the anti-DRM clause in section 4a may be a >good starting point. > > You may not distri

Re: Question regarding QPLed plugins for a GPLed app

2005-03-19 Thread Sven Luther
On Fri, Mar 18, 2005 at 06:22:49PM +, Anthony W. Youngman wrote: > In message <[EMAIL PROTECTED]>, Ben Burton > <[EMAIL PROTECTED]> writes > >Hi, > > > >I'm currently involved in a discussion on kde-core-devel regarding the > >use of a QPLed plugin that is dlopened within a GPLed application.

Re: Binaries and MIT/expat license interpretative tradition

2005-03-19 Thread Glenn Maynard
On Sat, Mar 19, 2005 at 01:39:59PM +0200, Henri Sivonen wrote: > Actually, I was concerned about *any* notice on binary distros. Even > the requirement to put a copyright notice in a directory somewhere can > be hard to sell. Isn't maintaining copyright notices in derivative works fundamental to

Re: Binaries and MIT/expat license interpretative tradition

2005-03-19 Thread Henri Sivonen
On Mar 14, 2005, at 20:12, Måns Rullgård wrote: Andrew Suffield <[EMAIL PROTECTED]> writes: The copyright notice does need to be included with the binaries. On Debian systems it is placed in /usr/share/doc/$package/copyright. This isn't a particularly strange or restrictive thing to require... This

Re: Draft summary of Creative Commons 2.0 licenses (version 3)

2005-03-19 Thread Henri Sivonen
On Mar 18, 2005, at 21:28, Evan Prodromou wrote: Hi, everyone. At long last, I've made some final revisions to the draft summary of the Creative Commons 2.0 licenses. Thank you for doing this. Now that OOo Authors and The Mozilla Foundation (for developer.mozilla.org at least) have chosen the CC