From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id DD5D8C50 for ; Mon, 17 Sep 2018 22:40:02 +0000 (UTC) Received: from mail-qk1-f177.google.com (mail-qk1-f177.google.com [209.85.222.177]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 700D07E2 for ; Mon, 17 Sep 2018 22:40:02 +0000 (UTC) Received: by mail-qk1-f177.google.com with SMTP id f62-v6so9963073qke.2 for ; Mon, 17 Sep 2018 15:40:02 -0700 (PDT) MIME-Version: 1.0 References: <20180917100413.22eac00d@coco.lan> <2072478.UYspZ1xLTN@avalon> <20180917115916.37fd5388@coco.lan> In-Reply-To: <20180917115916.37fd5388@coco.lan> From: Dave Airlie Date: Tue, 18 Sep 2018 08:39:48 +1000 Message-ID: To: mchehab+samsung@kernel.org Content-Type: text/plain; charset="UTF-8" Cc: ksummit Subject: Re: [Ksummit-discuss] [MAINTAINER SUMMIT] community management/subsystem governance List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > This is a valid point: whatever development process is used, drive-by > contributors should be allowed to send e-mails without needing to subscribe > (neither to a moderated list nor to a web-UI). I don't care how the > maintainer will handle such patches, provided that they will be properly > handled. > It really depends on what type of one-off contributor they are. Setting up git send-email isn't trivial for everyone, if you are a gmail user and work for a company that doesn't embrace smtp so much, then having a webui and https git access will be a lot easier for one-off contributions. Beware of thinking our setup with email is in any way simple for a newcomer to setup properly. Dave.