From: Thomas Monjalon <thomas@monjalon.net>
To: Tiwei Bie <tiwei.bie@intel.com>
Cc: dev@dpdk.org, techboard@dpdk.org
Subject: Re: [dpdk-dev] [RFC] proposal of allowing personal/project repos on DPDK.org
Date: Tue, 20 Jun 2017 09:21:34 +0200 [thread overview]
Message-ID: <2183495.DK3t6yERKa@xps> (raw)
In-Reply-To: <20170620061618.GA14527@debian-ZGViaWFuCg>
20/06/2017 08:16, Tiwei Bie:
> On Mon, Jun 19, 2017 at 03:29:29PM +0200, Thomas Monjalon wrote:
> > Hi,
> >
> > 01/06/2017 07:07, Tiwei Bie:
> > > We'd like to make a proposal of making DPDK.org allow hosting
> > > some personal/project repos, which could be very useful when
> > > someone wants to try some experimental projects in DPDK.
> >
> > It has been discussed during the last technical board meeting.
> > The board was not convinced by this idea, but would like to better
> > understand what is the problem to be solved with this proposal?
> >
> > If there is something to solve, we could decide one these proposals:
> > 1/ let users free to choose their forge
> > 2/ advise for gitlab
> > 3/ advise for github (and fight to recover the name DPDK)
> > 4/ pay a sysadmin to host and secure our own forge in dpdk.org domain
> >
>
> Anyway, I don't think it's a bad idea to get the name DPDK back
> on github if possible. Any thoughts?
I've already tried to get it two years ago.
I will try again requesting help from the Linux Foundation.
next prev parent reply other threads:[~2017-06-20 7:21 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
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 [this message]
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=2183495.DK3t6yERKa@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=techboard@dpdk.org \
--cc=tiwei.bie@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).