DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jan Blunck <jblunck@infradead.org>
To: dev <dev@dpdk.org>, techboard <techboard@dpdk.org>
Subject: [dpdk-dev] Minutes of techboard meeting 2017-08-09
Date: Sun, 27 Aug 2017 09:17:33 -0400	[thread overview]
Message-ID: <CALe+Z01uGUQvxYk6zkTAVteQgWCdDH=kNH+kO_MEiZR=ubzD1w@mail.gmail.com> (raw)

Member attendees:
-  Bruce Richardson
- Hemant Agrawal
- Jan Blunck
- Jerin Jacob
- Konstantin Ananyev
- Stephen Hemminger
- Yuanhan Liu


- How we want the developers to use the github.com/dpdk? Do we want to
get pull requests also from github?

We only want to maintain it as a mirror for dpdk. No other change in
process (no pull-requests). The techboard voted for 8:0 on this topic.

- What about enabling github bugtracker (issues) ?

Nobody requested to enable the github bugtracker support (issues) or
volunteered to investigate this further. Kevin Traynor pointed out
that it might be worth to talk to Ian Stokes since he tried to setup
the github bugtracker for OVS-dpdk.


Next meeting chair will be Jerin Jacob.

Thanks,
Jan

                 reply	other threads:[~2017-08-27 13:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CALe+Z01uGUQvxYk6zkTAVteQgWCdDH=kNH+kO_MEiZR=ubzD1w@mail.gmail.com' \
    --to=jblunck@infradead.org \
    --cc=dev@dpdk.org \
    --cc=techboard@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).