From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22536 invoked by alias); 25 Apr 2010 17:58:33 -0000 Received: (qmail 22528 invoked by uid 22791); 25 Apr 2010 17:58:32 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.44.51) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 25 Apr 2010 17:58:28 +0000 Received: from wpaz24.hot.corp.google.com (wpaz24.hot.corp.google.com [172.24.198.88]) by smtp-out.google.com with ESMTP id o3PHwPV5011452 for ; Sun, 25 Apr 2010 10:58:26 -0700 Received: from pwj3 (pwj3.prod.google.com [10.241.219.67]) by wpaz24.hot.corp.google.com with ESMTP id o3PHwOPl010868 for ; Sun, 25 Apr 2010 10:58:25 -0700 Received: by pwj3 with SMTP id 3so2980014pwj.36 for ; Sun, 25 Apr 2010 10:58:24 -0700 (PDT) Received: by 10.115.81.37 with SMTP id i37mr2899427wal.95.1272218304229; Sun, 25 Apr 2010 10:58:24 -0700 (PDT) Received: from coign.google.com (adsl-71-133-8-30.dsl.pltn13.pacbell.net [71.133.8.30]) by mx.google.com with ESMTPS id b4sm16639056wao.8.2010.04.25.10.58.22 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 25 Apr 2010 10:58:22 -0700 (PDT) To: Chris Lattner Cc: gcc Mailing List Subject: Re: Why not contribute? (to GCC) References: <9FD5A5B2-7195-409C-BA23-5DCF2283FC7D@apple.com> From: Ian Lance Taylor Date: Sun, 25 Apr 2010 18:04:00 -0000 In-Reply-To: (Chris Lattner's message of "Sun\, 25 Apr 2010 07\:55\:16 -0700") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-System-Of-Record: true X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2010-04/txt/msg00726.txt.bz2 Chris Lattner writes: > The key distinction is that contributing to LLVM does not require > you to sign a form (which isn't even publicly available) and mail it > in to a busy and high-latency organization before non-trivial > patches will be accepted. For the record (Chris probably knows this), the exact copyright forms are no longer posted online because in practice it often slowed down the copyright assignment process. Contributors routinely downloaded the wrong form and arranged to have it signed by their employer. When the FSF received the wrong form, they had to request a different form, and the contributors had to go through the signing process again. That is, the forms are not publically available not because they are secret, but to avoid confusion because international law is unavoidably complex. This fear of confusion is based not on hypothesis, but on actual experience. Instead, the process is to fill out a "request for assignment" form--those forms are publically available--and the FSF will send you the correct form. For most contributors, the correct "request for assignment" form may be found here: http://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/Copyright/request-assign.future I agree that this is all far more complex and time consuming than it ought to be. I hope that the SC can work with the FSF to simplify the process. However, the legalities are there for a reason, as seen by the copyright challenge from Unipress long ago and the SCO lawsuit against the Linux kernel. Apple and the University of Illinois are taking a risk by permitting patches without any paperwork. It's a low probability risk, but it's one that the FSF wants to avoid based on actual past experience. Ian