DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: techboard@dpdk.org
Subject: [dpdk-dev] DPDK techboard minutes of February 28
Date: Mon, 26 Mar 2018 14:33:01 +0200	[thread overview]
Message-ID: <6877952.fQbHSe1lST@xps> (raw)

Meeting notes for the DPDK technical board meeting
held on 2018-02-28

Attendees:
- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Konstantin Ananyev
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
- Yuanhan Liu

1/ There was an approval to publish the draft for Windows port in
	https://dpdk.org/browse/draft/dpdk-draft-windows/

2/ The default policy is to host draft code on GitHub,
unless the technical board decides an exception
when the work is significant enough to warrant hosting on dpdk.org.

It is possible to pin 6 GitHub projects from https://github.com/dpdk.
It will allow to give visibility to draft trees.
The naming of such tree should be prefixed:
	"dpdk-draft-X"
The project description in GitHub should highlight its temporary purpose:
	"devel only tree for drafting X feature"

3/ There is an agreement to have 1 active maintainer per dpdk.org tree,
plus 1 backup maintainer.

The trees and their maintainers should be listed at the top of
the MAINTAINERS file.

4/ The progress for the deprecation of the offloads API was discussed.
It was confirmed to try converting all PMDs for 18.05.
The PMD which are late in this conversion could be disabled.
More emails were planned to be sent to make sure nobody missed it.

                 reply	other threads:[~2018-03-26 12:33 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=6877952.fQbHSe1lST@xps \
    --to=thomas@monjalon.net \
    --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).