Re: discussion with the FSF: GPLv3, GFDL, Nexenta

2007-06-17 Thread Steve Langasek
On Tue, Jun 05, 2007 at 10:41:46PM +1000, Anthony Towns wrote:
 On Tue, Jun 05, 2007 at 02:09:06AM -0700, Steve Langasek wrote:
  Why doesn't it matter?  If I've been sued because of something I've actually
  done that infringed the license, then surely the DFSG and Debian shouldn't
  be concerned with that (other than the question of whether what I've done is
  something that the DFSG requires of copyright holders); but if I'm being
  sued over something I *didn't* do, [...]

 If you're going to be sued for something you didn't do, and lose because
 in your absence you're assumed to have done it, why not go the whole
 hog and just have them assert you've used/distributed a program you've
 never actually used/distributed?

In a court where a choice of venue clause holds water, in all likelihood the
court will not deem the normal jurisdictional rules to be overridden until
they're shown that you've *accepted* the license.  If the plaintiff can't
show this, the nuisance suit stops there.

If they *can* show this, you get the choices mentioned before.

You might still wind up with summary judgement against you in a foreign
court if the copyright holder fools the judge and you don't have the
resources to contest their claim; but that's more of a gamble, the copyright
holder has to convince a judge both that you've accepted the license and
that you've violated it.

Yes, there is some risk of a nuisance suit when you haven't accepted the
license, but that's our baseline which is unrelated to whether the license
is free.  If distributing code under the license increases the
odds/decreases the cost of a malicious copyright holder being able to pull
this off, and concommitantly increases the odds of a malicious copyright
holder *trying* to pull this off, I don't think that should be ignored.

 AFAICS this is an issue only when there's a not completely trivial
 possibility that you have actually violated the license.

I think it's also an issue when you have a malicious copyright holder who
believes they can convince the /judge/ that there's a possibility.

  * If I get sued in Oregon, I have a wide range of local resources at my
disposal to help me find appropriate legal representation; if I get
sued in Australia, I'm stretching my connections pretty thin to find
and evaluate legal counsel, and this process is going to cost more
time and money on my part (and may leave me with inferior legal
counsel anyway in the end due to logistical issues)

 For Australia, assuming you were being sued over free software stuff
 that you'd be doing in good faith, I think we could do a fairly good
 job helping you out.

Is that going to be the case for anyone who redistributes Debian or
distributes modified versions of packages received from us?

Should a license problem be ignored on the grounds that we think the Free
Software community will stick together in the event the problem clause is
invoked?

  As an analogy, suppose that a license included the following clause:
By distributing the covered work, you agree that the copyright holder can
compel you at any time to play in an on-line black jack tournament at his
website, geekblackjackstars.net, with an initial ante of $100.
  Should Debian consider this to be a free license because the clause won't
  necessarily be invoked and because some people win at blackjack?

 Clearly not. BTW, that site doesn't seem to exist.

And it still doesn't, a whole 10 days later?  Pff, doesn't anybody on these
lists have a sense of entrepreneurship?

 The difference between blackjack and choice of venue is that in one
 case you're being compelled to do something, and in the other you're
 pre-determining an argument. AFAICS that breaks that analogy.

In the blackjack case, you're only being compelled at the copyright holder's
whim.  In the choice of venue case, if there is no restriction preventing
the clause from being invoked on licensees who don't have a legal presence
in the named district, you are also being compelled to appear in court.  The
consequences for refusing to appear in court are different than the
consequences for refusing to play blackjack, but to me they do seem
analogous in that a requirement is being conditionally imposed on the
licensee that has nothing to do with the software itself.

If Debian has competent legal advice to the effect that this choice of venue
language will only take effect for licensees that already have a legal
presence in the named districts, then I withdraw my objection; but I don't
think that's the plain English reading of the clause at hand.

 Two different analogous licenses might be:

   By distributing the covered work, you agree that the copyright holder
   can sue you for violations of the license.

   If you distribute the covered work, the licensor agrees not to sue you
   in any jurisdiction other than Berlin, Germany.

 I'd consider both those to be clearly free. Choice of venue goes 

[MailServer Notification]Attachment Blocking Notification

2007-06-17 Thread do-not-reply
The email you have sent contained one or more prohibited attachments. The 
entire message has been deleted on 6/17/2007 at 5:52:04 AM and was not 
delivered to any of its recipients.

Message details:

Server: MOOSE
Sender: debian-legal@lists.debian.org;
Recipient: [EMAIL PROTECTED];
Subject: Delivery reports about your e-mail
Attachment name: [EMAIL PROTECTED]

The following URL outlines a supported method to workaround this issue.

http://mercury.gartner.com/mercury/infrastructure_solutions/global_telecom/email_attachment_workaround.htm

This e-mail message, including any attachments, is for the sole use of the 
person to whom it has been sent, and may contain information that is 
confidential or legally protected. If you are not the intended recipient or 
have received this message in error, you are not authorized to copy, 
distribute, or otherwise use this message or its attachments. Please notify the 
sender immediately by return e-mail and permanently delete this message and any 
attachments.  Gartner makes no warranty that this e-mail is error or virus 
free.