From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mhall@mhcomputing.net>
Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186])
 by dpdk.org (Postfix) with ESMTP id AF45FCD97
 for <dev@dpdk.org>; Fri,  1 May 2015 22:38:41 +0200 (CEST)
Received: by mail.mhcomputing.net (Postfix, from userid 1000)
 id DBB9580BD84; Fri,  1 May 2015 13:36:58 -0700 (PDT)
Date: Fri, 1 May 2015 13:36:58 -0700
From: Matthew Hall <mhall@mhcomputing.net>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Message-ID: <20150501203658.GA26543@mhcomputing.net>
References: <D1690998.1E825%keith.wiles@intel.com>
 <20150501110914.182dcfb1@urahara>
 <20150501194951.GA25199@mhcomputing.net>
 <20150501195932.GD595@fuloong-minipc.musicnaut.iki.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150501195932.GD595@fuloong-minipc.musicnaut.iki.fi>
User-Agent: Mutt/1.5.23 (2014-03-12)
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] GitHub sandbox for the DPDK community
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 01 May 2015 20:38:42 -0000

On Fri, May 01, 2015 at 10:59:32PM +0300, Aaro Koskinen wrote:
> Projects like GCC, GLIBC, binutils, busybox, etc or what?
> 
> A.

You'll notice all of these are low-level UNIX hacker sorts of tools mostly, 
with the partial exception of busybox. But even that is mainly for embedded 
use. It doesn't mean I don't think they're good and useful, but it does limit 
the possible size of the community in my view.

Since we are talking about how to get the largest widest community possible 
for DPDK, it could require doing things a bit differently from how many 
low-level tools have historically done things.

The most popular projects in Github have up to 80K watchers, and 100K forks. 
This type of popularity and interest is going to be hard to match just doing 
it the older way only. Even Google said so, when they shut down Google Code 
and moved stuff to Github:

http://google-opensource.blogspot.com/2015/03/farewell-to-google-code.html

If we want to shoot for a big audience we have to make sure we have a presence 
where the eyeballs are focused, as well as finding a way to support the 
traditional kernel-style workflow some of the core contributors use.

Matthew.