From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id F2921A04EF; Mon, 25 May 2020 13:58:41 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 261E61D5E0; Mon, 25 May 2020 13:58:41 +0200 (CEST) Received: from mail-il1-f193.google.com (mail-il1-f193.google.com [209.85.166.193]) by dpdk.org (Postfix) with ESMTP id A31AB1D5C1; Mon, 25 May 2020 13:58:39 +0200 (CEST) Received: by mail-il1-f193.google.com with SMTP id 4so17129086ilg.1; Mon, 25 May 2020 04:58:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZmqcWXvB3emFXrNV/u6HM2OfxFneOT3ZOefAzkkZybU=; b=pv1uCMkgVqmyppWp4u/wGz1clJnHzdGc7JUGCGjK9/PyHxLaWTeD9vmLIO3+xDCXv4 zAL8JH0AVHXIGFj4ghbKidjIpKivo1Te7Q5IEGoaoXMfHwVuoUfCVYZhPIZEmVdl17em ReaoggKyQV/2oYGLBefw1291Yh2rTzS+KHcdUdMKrPOeivR8HA824UAMM0FXwcfyfFFP qs9wnnBrl7P8XvJGnP82FAzEbYSV3+kcP2nS0EDby4ZlBjKDmJtifGSp0uhR3qi98N9Z xSzcJ0j5koT6yvJ+d1vmB52Gb16FVwZTODJfYtx6utMJUvIgS+Ac8aYXlzOfofgWnYPW hwZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZmqcWXvB3emFXrNV/u6HM2OfxFneOT3ZOefAzkkZybU=; b=mGIxj3BISs8iwlIVlUrWTkczp9rCHAd/ARSH5S4eBrqMaZNiIg4tmNFCb+WgTTKPOd G6xGZUK8MIvHPiKJxPuj+epu7Y+jthIos+Cbuj2hnyJ+plJM78euEbicfId0f1edQgO4 NN+kcHfsSVWkxSRgIKeOJfC2hSnkmmukrLGjRX1HVXSNMFS9CHlUSd2t6qPdw70zMwTH 6XdlsCZSFB2a1lG4usgkkcL2mS9D7c3HFA7lYrY7CI3dDmf1gyLq7Gm8jArf48WI93UI NsmKdNbFkPxFU0w8B5hrVLiqs8R4dL74lIz1XDnMSWvQmnVRp3UukjgsKs8k82QOYduG m8OA== X-Gm-Message-State: AOAM532Y+/UwZ270ZLzl9kBXxgHxDy/6D8s2B/NzdpFUDGp4UKWKfqEO MAKlRagEGIVL81CdL3v9DbQ8NaxeCSCvGgLCX00= X-Google-Smtp-Source: ABdhPJwTGXtMMNcVOZHZorILKOmBv1ZoIcP1mE/HZXqxhXo9pRILx/i8cc3qKyn6JYInpcfFJhSSfYwAfJG7/A+4HIg= X-Received: by 2002:a05:6e02:589:: with SMTP id c9mr24357756ils.271.1590407918745; Mon, 25 May 2020 04:58:38 -0700 (PDT) MIME-Version: 1.0 References: <98CBD80474FA8B44BF855DF32C47DC35C60FEA@smartserver.smartshare.dk> <6d59a42a-915b-47fc-60e6-94a4600d4bff@intel.com> In-Reply-To: <6d59a42a-915b-47fc-60e6-94a4600d4bff@intel.com> From: Jerin Jacob Date: Mon, 25 May 2020 17:28:22 +0530 Message-ID: To: "Burakov, Anatoly" Cc: =?UTF-8?Q?Morten_Br=C3=B8rup?= , techboard@dpdk.org, dpdk-dev , "Jim St. Leger" Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] Consider improving the DPDK contribution processes X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > I would add a third area: the process itself is arcane and inaccessible. > The current consensus among the community seems to be that IRC + mailing > list are "the most accessible" because "everyone has email" and "getting > on IRC is easy". > > However, the truth is, they aren't "accessible", they are low tech, and > thus *in*accessible to those who aren't veteran command-line Linux > coders. No one uses IRC any more except OSS projects (so a new I agree. Since IRC is not secure, a lot of companies are blocking the 6667 port. Another alternative is to see _slack_ "free public" channels. Some of the cool features of new tools are really useful. like notification, search in chat area(help to create the knowledge base), mobile application support, tons of custom free apps for a specific workflow, etc. > contributor isn't likely to have an IRC set up unless they're already a > habitual contributor to other projects), and sending patches over an > email as opposed to a well-integrated web interface workflow is so alien > to most people that it definitely does discourage new contributions. > > I understand the advantages of mailing lists (vendor independence, > universal compatibility, etc.), but after doing reviews in Github/Gitlab > for a while (we use those internally), going through DPDK mailing list > and reviewing code over email fills me with existential dread, as the > process feels so manual and 19th century to me. Agree. I had a difference in opinion when I was not using those tools. My perspective changed after using Github and Gerrit etc. Github pull request and integrated public CI(Travis, Shippable , codecov) makes collaboration easy. Currently, in patchwork, we can not assign a patch other than the set of maintainers. I think, it would help the review process if the more fine-grained owner will be responsible for specific patch set.