From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
"Bie, Tiwei" <tiwei.bie@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"yuanhan.liu@linux.intel.com" <yuanhan.liu@linux.intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [RFC] proposal of allowing personal/project repos on DPDK.org
Date: Fri, 2 Jun 2017 18:37:40 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891267BA643D3@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <136058706.0Fjdze3SFe@xps>
> Why? Do you need to host a repo on dpdk.org to try a new idea?
>
Prototyping new DPDK-related ideas and sharing them with DPDK community, with some of them likely to eventually make their way into DPDK once accepted and mature enough.
> I am against adding some user repos in this list:
> http://dpdk.org/browse/
> I think the list of official repos must be kept light for good visibility.
We could have a single project called sandbox mentioned in this list; whoever interested, needs to drill down into this one?
>
> But we can imagine a forge for users at a different location like
> http://dpdk.org/users/
> However why not using another public forge for this need?
Easier to share DPDK related ideas on dpdk.org rather than other places.
next prev parent reply other threads:[~2017-06-02 18:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 5:07 Tiwei Bie
2017-06-01 9:36 ` Dumitrescu, Cristian
2017-06-02 0:50 ` Yuanhan Liu
2017-06-02 15:29 ` Thomas Monjalon
2017-06-02 18:37 ` Dumitrescu, Cristian [this message]
2017-06-02 20:37 ` Stephen Hemminger
2017-06-05 7:47 ` Olivier Matz
2017-06-03 2:19 ` Tiwei Bie
2017-06-19 13:29 ` Thomas Monjalon
2017-06-20 6:16 ` Tiwei Bie
2017-06-20 7:21 ` Thomas Monjalon
2017-06-20 7:28 ` Tiwei Bie
[not found] <1085704550.1206846.1496479255188.ref@mail.yahoo.com>
2017-06-03 8:40 ` Manoj Mallawaarachchi
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=3EB4FA525960D640B5BDFFD6A3D891267BA643D3@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=thomas@monjalon.net \
--cc=tiwei.bie@intel.com \
--cc=yuanhan.liu@linux.intel.com \
/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).