Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1A0A397B8 for ; Tue, 1 May 2012 23:54:57 +0000 (UTC) Received: (qmail 722 invoked by uid 500); 1 May 2012 23:54:56 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 691 invoked by uid 500); 1 May 2012 23:54:56 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 682 invoked by uid 99); 1 May 2012 23:54:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 May 2012 23:54:56 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.212.47] (HELO mail-vb0-f47.google.com) (209.85.212.47) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 May 2012 23:54:48 +0000 Received: by vbbfr13 with SMTP id fr13so54213vbb.6 for ; Tue, 01 May 2012 16:54:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=WCa/KSi1ZkfV9KC2m8xm6brdPJ6ZZxqfsK7gTJ7CAHQ=; b=pP68k93IqzZx0wS90EiFxdIqJ+ikBaZHVCmmqO562k4dWrAlaX0wCpI5OcnWSB3fSp HNezHEHBCgg7ZWuNvSGTkE+o3Wf1Ua7kvAjCmzZnotNYWv8fBLOwd/4/QLkCjb+WCffR W7IJn0//8MYVmS2uPgUAqWRqIVFCCBCKofv3Mutf1qyR8Bm0Qoz1tUKGRIoqUDwZ39ov NTgddriAd1V5A5TRVKUkXupC9zaHc4WXsCjlKY2TOq2pFZmfxMX9myZrfs6j3znqyaPd 3oJSMRyrM7QL6Enf/JDZp1uE9l6VAbMmY1VF6r36k5bJ8g7LgrPVBah6TtdqmAJWJIGl NFog== Received: by 10.52.22.74 with SMTP id b10mr22827328vdf.47.1335916467742; Tue, 01 May 2012 16:54:27 -0700 (PDT) Received: from [192.168.100.108] ([65.215.11.58]) by mx.google.com with ESMTPS id r20sm60235vdg.14.2012.05.01.16.54.25 (version=SSLv3 cipher=OTHER); Tue, 01 May 2012 16:54:26 -0700 (PDT) Message-ID: <4FA077B0.9060503@dot-com-it.com> Date: Tue, 01 May 2012 19:54:24 -0400 From: Jeffry Houser Reply-To: jeffry@dot-com-it.com User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: flex-dev@incubator.apache.org Subject: Re: [MENTORS] Handling Adobe Binaries References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQlA3f7TiGgsUJS+SCY5CGdaoKu55aHYPORkcqLs18yfIZ5dDXaiVIRg2Jb0/vS4OIb3TyNJ On 5/1/2012 6:02 PM, Alex Harui wrote: > On 5/1/12 2:51 PM, "Justin Mclean" wrote: > >> Hi, >> >> Perhaps we can consider this as a fallback? >> >> I was just look at this thread on the Adobe forums [1] where the same issue >> come up before (for creating a Fedora package for the OS Adobe SDK) and it's >> suggests that it may be possible to create our own dummy swc using code like >> so: > If we have to, I will ask about it, but to me, it violates the reverse > engineering clause in the license, and potentially, the copyright as well, > but I am not a lawyer. I am not a lawyer either, but I've been known to play on the Internet and such topics catch my interest at times; so this is my ramble on such things. I, personally, feel that it wouldn't violate the reverse engineer clause because all this stuff is already well documented publicly. We wouldn't be reverse engineering anything; just creating our own thing to the own API. It shouldn't violate copyright; because we are writing our own code from scratch. Unless Adobe wants to claim copyright on the API which is possible. I know I read about a API related lawsuit at one point, but I have no idea what the results were. However, this is all very tricky as we live in a lawsuit happy world; and it makes sense to follow Adobe's guidance on such issues; as I doubt we could win against them (from a funding perspective) and any related wranglings would effectively stunt the project. The first lawyer I hired offered to "send a letter claiming X, Y, and Z" even though there was no legal truth to X, Y, or Z. This was under the assumption that the people said letter was being sent to wouldn't/couldn't hire a lawyer to tell them "this is all a lie." The same concept is used a lot these days w/ "Pre settlement Letters".