DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "techboard@dpdk.org" <techboard@dpdk.org>
Cc: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] minutes of meeting 2020-09-25
Date: Mon, 28 Sep 2020 17:39:01 +0100
Message-ID: <e2aae10a-5e9d-f5d5-748e-f093a1f06aaa@intel.com> (raw)
In-Reply-To: <2fbbe214-421b-ebf8-5893-98bebf78a345@intel.com>

Members Attending:
-------------------

     Bruce Richardson
     Ferruh Yigit (Chair)
     Honnappa Nagarahalli
     Jerin Jacob
     Kevin Traynor
     Konstantin Ananyev
     Maxime Coquelin
     Stephen Hemminger
     Thomas Monjalon

The technical board meetings takes place every second Wednesday on 
https://meet.jit.si/DPDK, at 3pm UTC.
(Trial runs on jitsi, backup on IRC channel #dpdk-board)
Meetings are public and DPDK community members are welcome to attend.

#1 All ABI/API breaks without deprecation note requires techboard approval.
    Please cc the techboard mail list to ask for the approval.

#2 Patchwork review process enhancement agreed on principal, target is
    to highlight the reviewer of the patch and where a patch stuck.
    * After v20.11 a work-group will start the technical investigation.
    * For now Jerin leading the work-group, will ask Ali to join it.

#3 Security process issues, there are open security issues.
    * Ferruh will gather all open issues.
    * Stephen will find resource to address them.

#4 Asks from governing board
    a) Prepare list of requirements / tasks for Technical writer.
       * Bruce/Thomas prepared a draft
       * Waiting comments from techboard members until next Wednesday.

    b) Decide whether to extend contract of work on unit tests at UNH
       * Agreed on principal to do more unit test work at UNH
       * How to define, who to define test cases are still an open
       * The request to all tech-board members is to join the CI meeting

    c) Requiring unit tests for contributions
       * A work-group will provide feedback about DTS and its usability on next
         techboard meeting (2020-10-07)
       * Work-group led by Honnapa, other members Stephen, Ferruh/Bruce, Jerin
         * Can ask UNH to involve

Other items deferred for next meeting.
---

Next meeting will be on 2020-10-07, and will be chaired by Honnappa.

           reply	other threads:[~2020-09-28 16:39 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <2fbbe214-421b-ebf8-5893-98bebf78a345@intel.com>]

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=e2aae10a-5e9d-f5d5-748e-f093a1f06aaa@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git