DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tiwei Bie <tiwei.bie@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Trishan de Lanerolle <tdelanerolle@linuxfoundation.org>
Subject: Re: [dpdk-dev] DPDK & github
Date: Thu, 6 Jul 2017 09:45:23 +0800	[thread overview]
Message-ID: <20170706014522.GA19654@debian-ZGViaWFuCg> (raw)
In-Reply-To: <12616607.9t08ciOrBu@xps>

On Wed, Jul 05, 2017 at 11:48:20PM +0200, Thomas Monjalon wrote:
> Hi,
> 
> Following community requests, the Linux Foundation tried to get
> the ownership of the DPDK account on GitHub which was owned
> by someone.
> Good news, it worked:
> 	https://github.com/dpdk
> Thanks Trishan for the help.
> 
> First of all, it is not planned to use GitHub and its pull request model,
> as the main repository. It should be a read-only mirror.
> 
> If a pull request is created for https://github.com/dpdk/dpdk,
> we should redirect to the mailing list as Linux do with a bot:
> 	https://github.com/ajdlinux/KernelPRBot/blob/master/message.md
> 
> We can discuss how to organize this account for related projects or
> for user repositories. Other ideas are welcome.
> 
> Anticipating the discussion about a bug tracker, it was decided to use
> Bugzilla and configure a workflow friendly with the mailing list.
> As it is not available yet, we can also compare Bugzilla and GitHub.
> 
> Configuring the account for our needs may take time, especially during
> a release period.
> Thanks for your patience.

Great news! Thank you! :-)

Best regards,
Tiwei Bie

      reply	other threads:[~2017-07-06  1:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05 21:48 Thomas Monjalon
2017-07-06  1:45 ` Tiwei Bie [this message]

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=20170706014522.GA19654@debian-ZGViaWFuCg \
    --to=tiwei.bie@intel.com \
    --cc=dev@dpdk.org \
    --cc=tdelanerolle@linuxfoundation.org \
    --cc=thomas@monjalon.net \
    /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).