DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: [dpdk-dev] Next technical board meeting on 2017-12-20
Date: Mon, 18 Dec 2017 12:45:09 +0000	[thread overview]
Message-ID: <AM2PR04MB0753B31786336D413390150D890E0@AM2PR04MB0753.eurprd04.prod.outlook.com> (raw)

The next techboard meeting will take place on 2017-12-20  i.e. this Wednesday, at 3pm UTC. 

Meeting place: IRC #dpdk-board

Please send on any items requiring techboard attention.

Regards,
/Hemant

> -----Original Message-----
> From: techboard [mailto:techboard-bounces@dpdk.org] On Behalf Of
> Richardson, Bruce
> Sent: Tuesday, December 12, 2017 10:57 PM
> To: techboard@dpdk.org
> Cc: dev@dpdk.org
> Subject: [dpdk-techboard] Minutes of technical board meeting 2017-12-06
> 
> Attendees:
> Bruce, Hemant, Jerin, Konstantin, Olivier, Thomas, Yuanhan
> 
> Absent:
> Stephen, Jan
> 
> Due to discontinued involvement in DPDK, Jan has now resigned from the
> technical board.
> The tech board wishes to thank him for his contributions to DPDK and tech-
> board over the last few years and wish him well in his other endeavours.
> The topic of a possible replacement for Jan on the tech-board will be
> discussed at the next meeting.
> 
> Topic: Management of old patches in patchwork
> * Unanimous agreement that old patches should be rejected in patchwork
>   after a reasonable period, set initially at 3 releases (9 months).
> * After a release, all patches dated older than 3 releases previously,
>   e.g. after 17.11, any patches submitted before the release of 17.02,
>   will be marked as rejected and a mail reply sent to the appropriate
>   mailing list thread informing people of the same.
> * To have patches reconsidered for future inclusion, a new version of
>   the patches should be submitted to the mailing list.
> 
> * Bruce to update the documentation with this new policy.
> * Thomas to request support from patchwork and DPDK community to
>   automate/script the implementation of this policy.
> 
> Topic: Licensing
> * No major updates. Discussion in progress on a number of items that
>   need relicensing or exceptions.
> 
> Topic: Technical Board Voting
> * For charter changes the governing board requires a 2/3 majority. The
>   technical board has no such special case for charter or policy
>   changes.
> * Following brief discussion, most seemed happy with the current
>   situation where a simple majority suffices for such decisions.
> 
> Next Meeting:
> * 2017-12-20 @ 3pm UTC
> * Hemant to chair discussion

                 reply	other threads:[~2017-12-18 12:45 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=AM2PR04MB0753B31786336D413390150D890E0@AM2PR04MB0753.eurprd04.prod.outlook.com \
    --to=hemant.agrawal@nxp.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
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).