linux-kernel - Re: Gerrit (was Re: HTC Dream aka. t-mobile g1 support)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <a55d774e0906121542g182d4814udd66c2d1ebf57cf5@mail.gmail.com>
Date:	Fri, 12 Jun 2009 15:42:21 -0700
From:	Brian Swetland <swetland@...gle.com>
To:	Shawn Pearce <sop@...gle.com>
Cc:	Pavel Machek <pavel@....cz>,
	Stefan Schmidt <stefan@...enfreihafen.org>,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	kernel list <linux-kernel@...r.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@...ts.arm.linux.org.uk>,
	Greg KH <greg@...ah.com>, Chris Dibona <cdibona@...gle.com>,
	Daniel Berlin <dannyb@...gle.com>
Subject: Re: Gerrit (was Re: HTC Dream aka. t-mobile g1 support)

On Fri, Jun 12, 2009 at 3:38 PM, Shawn Pearce<sop@...gle.com> wrote:
> On Fri, Jun 12, 2009 at 15:22, Pavel Machek <pavel@....cz> wrote:
>> On Fri 2009-06-12 14:50:21, Brian Swetland wrote:
>> > Gerrit is a git patch review system that we (Google/Android) use for
>>
>> Unfortunately, it seems quite unsuitable for kernel.
>>
>> Do I understand it right that to submit kernel patches I'd have to
>> agree to "contributors agreement", and give up my copyright? No,
>> sorry, I don't think I want to do that.
>
> No.  The contributor agreement used by review.source.android.com is a stronger version of the Developers Certificate of Origin normally used by kernel
> contributors.
> For the actual agreement text see[1], but the basic principle is the same.
>  No assignment of copyright, only assignment of license for redistribution,
> which is what the GPL asks anyway.  It also contains a patent provision,
> similar to what the Apache License contains, to protect the project leads
> from submarine patent infringement by code contributed by a patent holder.
> [1] https://review.source.android.com/static/cla_individual.html

When we first discussed the CLA, I raised this concern (that the
mainline kernel folks would not be thrilled by another system in
addition to Signed-off-by), and was informed that we should not have
to require CLA acceptance for contributions to the kernel/... trees.
I'm not sure if Gerrit is setup to handle this yet.

We will always happily accept kernel patches via email/mailinglist,
per the standard linux kernel development model.

Brian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/