[dpdk-dev] Next technical board meeting on 2017-12-20

Hemant Agrawal hemant.agrawal at nxp.com
Mon Dec 18 13:45:09 CET 2017


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 at dpdk.org] On Behalf Of
> Richardson, Bruce
> Sent: Tuesday, December 12, 2017 10:57 PM
> To: techboard at dpdk.org
> Cc: dev at 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



More information about the dev mailing list