From owner-freebsd-testing@freebsd.org Sun Oct 18 02:48:31 2015 Return-Path: Delivered-To: freebsd-testing@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49E50A10328 for ; Sun, 18 Oct 2015 02:48:31 +0000 (UTC) (envelope-from jmmv@meroh.net) Received: from mail-qg0-f52.google.com (mail-qg0-f52.google.com [209.85.192.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0335AD0F for ; Sun, 18 Oct 2015 02:48:30 +0000 (UTC) (envelope-from jmmv@meroh.net) Received: by qgbb65 with SMTP id b65so26564948qgb.2 for ; Sat, 17 Oct 2015 19:48:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=vlrFHgCESWxPHnlWk5vFUhXpjxSbv0r6To1NcO8yngM=; b=JFznpWUYONVoRsgNgLTf0jBnt8RMeCgf9DZdqsaBPRvh12nhomSVAufapO8cQBoRX5 ubOoskCZkrjxKYYGgsiAh8XVftGw9cjYJ/X9HsHRtzpklxBng+V/507Dpe6xKk+a3hmS Ib41GecukGOhp5UaSzufuc+qWMATQgAhvXTtFzEP2ymsuTkbDBoSbR12Z2VVgNnjm9z1 knZmjeD+4XFDtj0fkPI6XmGLEnb2SqISD5P7Pvre1/WFTs1l/SVj4CiySyfwAhIie/LT 4diDhcOSh0aSJz2lL2j2oRY9IgmzWvRoZ2xz6wCxEGk9UzX/dV7uIDhij9Hh4KI+Y74k 12UQ== X-Gm-Message-State: ALoCoQn4wri1qofFFLsc7Srs9F6fTTFPBzRUiHEwfrOuqL+zg9qf/1r8Yf6bPl0CSb/ohAAYk/y6 X-Received: by 10.140.233.130 with SMTP id e124mr29646528qhc.79.1445136503955; Sat, 17 Oct 2015 19:48:23 -0700 (PDT) Received: from ?IPv6:2604:2000:c667:7600:4815:f07:b75a:45a7? ([2604:2000:c667:7600:4815:f07:b75a:45a7]) by smtp.gmail.com with ESMTPSA id b36sm10195598qge.23.2015.10.17.19.48.23 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 17 Oct 2015 19:48:23 -0700 (PDT) Sender: Julio Merino Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3094\)) Subject: Re: kyua and Google Contributor License Agreement From: Julio Merino In-Reply-To: Date: Sat, 17 Oct 2015 22:48:17 -0400 Cc: Brad Davis , "freebsd-testing@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <20150930211156.GL65719@corpmail.liquidneon.com> To: Craig Rodrigues X-Mailer: Apple Mail (2.3094) X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Oct 2015 02:48:31 -0000 > On Oct 1, 2015, at 14:32, Craig Rodrigues wrote: >=20 >=20 >=20 > On Wed, Sep 30, 2015 at 2:11 PM, Brad Davis wrote: > On Wed, Sep 30, 2015 at 01:20:13PM -0700, Craig Rodrigues wrote: >=20 > I am in the same boat, and would love to see if we could just fork it = and > work from there. Could Julio then contribute to the code? >=20 > I don't know all the rules that Google has regarding the CLA and > what Google employees can and cannot contribute to. I'll let Julio = respond. The CLA exists to protect the project, and this is not something = specific to Google. If you ever want to contribute to any major open = source project, you will have to sign a CLA of some form. The FSF has = one; Apache has one; the PSF has one; and a bunch of other projects have = one (see = https://en.wikipedia.org/wiki/Contributor_License_Agreement#Users). The license of the code itself does not say much about the many other = implications a contribution might have. For this reason, and = personally, I see the need to sign a CLA as not-a-bad-thing for the = sanity of the project long-term, even though it might have adverse = consequences in a few cases. In fact, I'm kinda surprised that FreeBSD does not have any kind of = agreement in place. When I joined NetBSD back in the day (oops, 2002), I = was required to sign a contributor agreement. > I really want to avoid forking kyua, because Julio has put a lot of > work into putting things on Github, integrating the kyua github = project > with Travis CI (Continuous Integration), doing releases, etc. I'm afraid that part of the concerns also come from the fact that I = haven't been very responsive lately. Had I dealt with the bugs and = requests in a more timely fashion, you might not see the above as a real = blocker to getting things done... but, as has been the case, I cannot = make promises either. (Spoiler alert: two kids take a ton of time!) If anyone is serious about starting a fork, and wants to do so, please = contact me privately beforehand. I have some thoughts on the = topic/process. > My main concern is that the Google CLA is turning away potential=20 > contributors, and blocking patches that people have already submitted > from going in the kyua tree. Correct me if I'm wrong, but I seem to recall that the issue here was = mostly not with individuals, but with EMC not wanting to sign the = corporate CLA and thus preventing the EMC employees from feeding back = the code. I am not a lawyer, but based on the contents of the CLA, I = fear about the reasons for a company not wanting to sign it... Cheers=