From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id 760E25A81 for ; Fri, 16 Jan 2015 20:01:15 +0100 (CET) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 9997F80C79C; Fri, 16 Jan 2015 10:58:52 -0800 (PST) Date: Fri, 16 Jan 2015 10:58:52 -0800 From: Matthew Hall To: Thomas Monjalon Message-ID: <20150116185852.GA29426@mhcomputing.net> References: <20150114122352.63ef79eb@urahara> <2507392.XzU56ErIKp@xps13> <20150116172017.GE27496@hmsreliant.think-freely.org> <2188823.ZBC1oOX6oS@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2188823.ZBC1oOX6oS@xps13> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] Why nothing since 1.8.0? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2015 19:01:15 -0000 On Fri, Jan 16, 2015 at 07:18:19PM +0100, Thomas Monjalon wrote: > I'd like to try solving the review challenge first and see what else can be > done after that. Step by step. FWIW, I know the kernel guys seem to really love it, but not everybody else has much fun trying to do the reviews reading huge patch emails. I lose a lot of context trying to stare at them in mutt 80x25 console etc. It would be nice if we could have a visual interface with syntax highlighting and comment capabilities, that's easier to read through quickly and clearly, like ReviewBoard, GitHub Pull Request UI, etc. If it had email integration to reply to the patch threads that'd be great too. Also if we had some branches available where conceptually related changes are grouped, somebody could check out the branch with some feature they wanted to try, get all the related patches, integrate with their app of choice, and see if the app works successfully with the new feature. Some of these things like DPDK, it isn't obvious how the feature will help or hurt, until you write some code against it and/or benchmark it first, because some of these features are kind of complicated. Another thing... if we had some kind of wiki page, where some of the backend coders could mark themselves as maintainers of all the different features they work on, and more client-side network stack guys like me could express interest in certain features, we could connect the two sides so any given guy knows who can review his bugfix he found, or try out his new patchset to see if it works well in an app. Matthew.