From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SNp8V-0007dG-5q for garchives@archives.gentoo.org; Fri, 27 Apr 2012 17:39:15 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D994EE08E0; Fri, 27 Apr 2012 17:39:06 +0000 (UTC) Received: from mail-bk0-f53.google.com (mail-bk0-f53.google.com [209.85.214.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 75ED2E068E for ; Fri, 27 Apr 2012 17:38:32 +0000 (UTC) Received: by bkcjk13 with SMTP id jk13so771849bkc.40 for ; Fri, 27 Apr 2012 10:38:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=/+Wa/j+5lsOv02kC/mBj/+TZkgXMJxv2ERTq8gIfZZg=; b=NdbmEQ9d2cWnr3RWL/eLEkHNiY0eudAj6jkmU3Wt9r2CdY4B4OUvdiDsuh9dsK5kcv JC9NmP429P7E8zj/aNJ/JZbMVJeeqdSM6DIuaZdcJhC6QNjDFEjB+NF1Dlgc1moxu5QR 49LABdWwZTmDRHu45UkBNv4TuC2Al+9MtZnw4MkiA32pnxUFYHSzOdiSXkZlUFiFAxnc nntrjxm68hNWp6OxUmCfVnXN1EAubDa8TkDw/mCVziKKUBPTU8WmdeOp8hKRgUGQg97R KC1FI9Bux6lK9gKtcw5C8K8EHwZZiMPU3D/vYBlaSGQeM7WeVIFtwoByOTuowuUo4pp+ j2+A== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Received: by 10.205.118.139 with SMTP id fq11mr4207949bkc.123.1335548311567; Fri, 27 Apr 2012 10:38:31 -0700 (PDT) Sender: freemanrich@gmail.com Received: by 10.204.226.77 with HTTP; Fri, 27 Apr 2012 10:38:31 -0700 (PDT) In-Reply-To: <1335538634-sup-7655@raeviah> References: <1335519028-sup-4124@raeviah> <1335526185-sup-4610@raeviah> <1335534186-sup-3638@raeviah> <20120427143405.GA20829@linux1> <1335538634-sup-7655@raeviah> Date: Fri, 27 Apr 2012 13:38:31 -0400 X-Google-Sender-Auth: uwPOMsGa8VU6oPDvxr4I2_LfKcY Message-ID: Subject: Re: [gentoo-dev] Re: New license: yEd Software License Agreement From: Rich Freeman To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 449224f2-f87d-4bd3-b53e-bb3b7a3b8af8 X-Archives-Hash: 63eb63158f34d0300e959cc1b6a936bd On Fri, Apr 27, 2012 at 11:33 AM, Amadeusz =C5=BBo=C5=82nowski wrote: > > And this is probably the case when user has to accept a license on the > website. =C2=A0This is URL for zip archive of yEd-3.9.1: > > =C2=A0http://www.yworks.com/en/products_download.php?file=3DyEd-3.9.1.zip > > It directs to website with license text, check-box for accept and > download button. =C2=A0If check-box is not set, following message is show= n: > > =C2=A0"In order to download yEd, it is necessary that you first accept th= e > =C2=A0license terms." > > If check-box is set, client is redirected to the page with actual link to > zip archive. It turns out the vendor is lying - you can download it fine without accepting the license from: http://www.yworks.com/products/yed/demo/yEd-3.9.1.zip No doubt the vendor WANTS users to accept the license first, but it is not "necessary" from a technical standpoint. > > Moreover, I have had email conversation with yWorks representative and > he says that installation files need to be obtained manually by the end > users from their website. > Again, they likely intend for them to be obtained in this manner, but the word "need" is not true from a technical perspective. This brings up a debate that was recently held over deep-linking in bugzilla over a math library. The trustees never took a final vote since the maintainer decided to just implement RESTRICT=3Dfetch. The issue there was about more than just copyright, however, and the trade regulations around munitions do not apply in this case. I don't think we have clear policy around this situation. I see our option= s as: 1. Set RESTRICT=3Dfetch because upstream wants us to and we like to cooper= ate. 2. Set RESTRICT=3Dfetch because even if legally they're on shaky ground upstream could probably waste a lot of our time and money. 3. Set RESTRICT=3Dmirror because legally we think we have the right to do so, and want to stand for our principles and make life easier for our users. The potential upstream responses to doing #3 might be to do nothing, to not like us, to sue us, or to not use a fixed URL to distribute the file so that we have to restrict fetching for technical reasons. Do we as a matter of policy want to respect broken click-through download implementations? Rich