From: Matthew Hall <mhall@mhcomputing.net>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] GitHub sandbox for the DPDK community
Date: Fri, 1 May 2015 13:36:58 -0700 [thread overview]
Message-ID: <20150501203658.GA26543@mhcomputing.net> (raw)
In-Reply-To: <20150501195932.GD595@fuloong-minipc.musicnaut.iki.fi>
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.
next prev parent reply other threads:[~2015-05-01 20:38 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 15:56 Wiles, Keith
2015-05-01 16:45 ` Neil Horman
2015-05-01 17:18 ` Aaro Koskinen
2015-05-04 12:39 ` Qiu, Michael
2015-05-01 17:31 ` Matthew Hall
2015-05-01 17:45 ` Wiles, Keith
2015-05-01 18:48 ` Neil Horman
2015-05-01 19:10 ` Wiles, Keith
2015-05-02 2:59 ` Wiles, Keith
2015-05-03 21:00 ` Neil Horman
2015-05-04 3:51 ` Wiles, Keith
2015-05-04 12:43 ` Qiu, Michael
2015-05-04 17:48 ` Matthew Hall
2015-05-04 18:52 ` Neil Horman
2015-05-05 3:12 ` Wiles, Keith
2015-05-05 3:25 ` Jim Thompson
2015-05-05 13:55 ` Neil Horman
2015-05-05 16:43 ` Wiles, Keith
2015-05-05 17:57 ` John W. Linville
2015-05-05 18:30 ` Wiles, Keith
2015-05-05 18:46 ` John W. Linville
2015-05-05 19:07 ` Neil Horman
2015-05-05 20:15 ` Wiles, Keith
2015-05-06 8:12 ` Panu Matilainen
2015-05-06 8:30 ` Simon Kågström
2015-05-06 9:00 ` Panu Matilainen
2015-05-06 10:37 ` Neil Horman
2015-05-07 15:26 ` John W. Linville
2015-05-01 18:01 ` Wiles, Keith
2015-05-01 18:09 ` Stephen Hemminger
2015-05-01 18:17 ` Wiles, Keith
2015-05-04 20:34 ` Marc Sune
2015-05-05 2:54 ` Wiles, Keith
2015-05-01 19:49 ` Matthew Hall
2015-05-01 19:59 ` Aaro Koskinen
2015-05-01 20:36 ` Matthew Hall [this message]
2015-05-02 11:40 ` Neil Horman
2015-05-02 12:37 ` Thomas F Herbert
2015-05-02 14:07 ` Wiles, Keith
2015-05-02 13:59 ` Wiles, Keith
2015-05-04 21:08 ` Marc Sune
2015-05-05 3:09 ` Wiles, Keith
2015-05-04 6:52 ` Simon
2015-05-04 9:05 ` Marc Sune
2015-05-06 10:11 ` Mcnamara, John
2015-05-06 21:09 ` Thomas Monjalon
2015-05-06 21:37 ` Marc Sune
2015-05-06 23:49 ` Wiles, Keith
2015-05-07 3:37 ` Wiles, Keith
2015-05-12 14:38 ` Thomas Monjalon
2015-05-04 5:08 Wiles, Keith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150501203658.GA26543@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=aaro.koskinen@iki.fi \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).