Hi all, Here is the meeting notes for the last DPDK technical board meeting held on 2017-04-10.
Please note that meetings are open to all to attend. Any topics to be referred to the tech board for discussion at that meeting should be emailed to techbo...@dpdk.org. Normally, it's a bi-weekly meeting. Member attendees: - Bruce Richardson - Hemant Agrawal - Jan Blunck - Jerin Jacob - Konstantin Ananyev - Thomas Monjalon - Yuanhan Liu 1. General Meeting Admin ------------------------ TB came to an agreement that this meeting will be chaired all members in alphabet order by first name. Thus, excluding those already have done the chair once, Hemant Agrawal will be the next chair. He will send a date poll for next meeting later. Thomas will create a page at dpdk.org to collect links to next meeting agenda as well as all meeting minutes. 2. Divergence between DPDK/Linux PF/VF implementations ------------------------------------------------------ TB has no objections about the divergence between DPDK/Linux PF/VF implementations. But following guides are highly suggested to follow: - clear document on the divergence - the situation when some features are not supported by some particular PFs should be gracefully handled It's no longer a mandatory to work with the Linux kernel community to get the required functionality upstream. Instead, it becomes a recommended practice. The design guide will be updated, to adapt to above new policies: http://dpdk.org/doc/guides/contributing/design.html#pf-and-vf-considerations 3. Representative for the DPDK governance board ----------------------------------------------- TB decided to rotate the representative role again in alphabet order by first name. The switch happens quarterly. Also, there is a backup. The backup is the one next in the alphabet list. If a representative finds that it is too much of a burden for him to attend regular gov meeting calls. He can give a pass to his chance. 4. Scope of cmdline and cfgfile libraries in DPDK ------------------------------------------------- It was partially discussed due to limited time, thus there weren't too many agreements. Some rough thoughts were: - we only want one lib for one particular function: no alternatives. - we should try to avoid reinventing the wheels. The DPDK build system should be improved to work better with external dependencies. The discussion will be continued in the next TB meeting. 5. Community questions/issues ----------------------------- Discussion postponed to the next TB meetings.
