Re: DTS WG meeting minutes - 1/12/22

[Bruce Richardson <bruce.richardson@intel.com>]

On Wed, Jan 19, 2022 at 09:25:50PM +0000, Honnappa Nagarahalli wrote:
> Hello, Please find the minutes below. The history of minutes is at [1].
> 
> Thanks, Honnappa
> 
> [1]
> https://docs.google.com/document/d/1E2mkTHNQ5vyln1JvnJTil15cjacUTXP7LXb9K960Vxs/edit?usp=sharing
> 
> Attendees: -------------- Honnappa Nagarahalli Owen Hilyard Lijuan Tu Ali
> Alnubani Vladislav Grishenko
> 
> Agenda: ---------- 1) Review/Carry forward pending action items 2)
> Rotating the chairperson for hosting the meeting 3) Makefile build
> removal from DTS 4) DTS files license to change to SPDX license 5) How do
> we merge the DTS into DPDK - directory structure, compilation time,
> documentation (tooling and directory structure for online documentation)
> 6) Build DTS documentation using Meson
> 
> Minutes: ----------- 1) The chairperson hosting the meeting will be
> rotated going forward. As of now it will be shared between Honnappa,
> Juraj, Lijuan, Lincoln (?), Owen. The rotation will be done in the
> alphabetical order of the first name. However, as agreed, the meeting on
> 1/18 would be hosted by Owen.  2) All the stable releases use Meson
> build. So the makefile build support from DTS can be removed. Makefile
> removal patch is in the DTS community review 3) A quick scan reveals that
> DTS has some files with GPL2 license. A deeper look is required. Is there
> any process we need to follow to change to SPDX? Decided to follow up
> with the DPDK community.  4) Merging DTS into DPDK - Is a bigger
> discussion. Need to agree and fix the python version to use. Differed the
> discussion to future time as it needs more progress in DTS. Will be
> discussed when Lincoln and Juraj are available 5) The DTS user guide and
> DTS test plans are being built using makefile. This needs to be changed
> to using meson build.
>
For this point #5, not knowing the details here, but at a high level, I
wonder if that really needs to be done, if the existing make build of the
doc works ok. As the plan is to move DTS into DPDK repo, presumably the
documentation would also move, and at that point it can just reuse the DPDK
meson build infrastructure for documentation. Is there a compelling reason
to invest in doing this change earlier? For docs rather than code, moving
to meson doesn't generally give much benefit - the only reason we did so in
main DPDK repo was consistency with everything else.

/Bruce