From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id A30CAA00C5; Mon, 31 Oct 2022 11:08:10 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 42CF640223; Mon, 31 Oct 2022 11:08:10 +0100 (CET) Received: from mailgw01.pantheon.sk (mailgw01.pantheon.sk [46.229.239.26]) by mails.dpdk.org (Postfix) with ESMTP id D4FA140151 for ; Mon, 31 Oct 2022 11:08:08 +0100 (CET) Received: from mailgw01.pantheon.sk (localhost.localdomain [127.0.0.1]) by mailgw01.pantheon.sk (Proxmox) with ESMTP id 58A182020C0; Mon, 31 Oct 2022 11:08:08 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pantheon.tech; h=cc:cc:content-type:content-type:date:from:from:message-id :mime-version:reply-to:subject:subject:to:to; s=dkim; bh=Pqj3xYh pgfYdMivDACUlB0/m/6mqf8r2+Vgn82JgZ2I=; b=gWTbJ301fPvrz08/JgzYgo0 F+Hhu6IAwjn8uJH2OzPytMt4noaGnBAN+KrQvMyOcUujDjE3ZlZBn+BAuX39miIa 7k/N8rJXM3Pcwem+Gm0Jif6IVvqizl29AVg0SpD8/hDBCw2K/gTAg31Si6N4QCVN 1xSRq43DQHqfQm+ziaDkryWqbvFxFF+BKj+1tlcQPBaRSW63s5aBSuKhYCRxXmIb G8f/q2t0JXTlu9mdEisqN/4FCGVb2YBI1syvidG1IEf6E/dbo90yQbnuXuY33+l7 ksDM+To8u9MCxaU4IL4kHM7sOilbo8xsqOQcNVsS6+qXHLMwICb8TJ4Lvm1cKKA= = From: =?iso-8859-2?Q?Juraj_Linke=B9?= To: "dev@dpdk.org" CC: Honnappa Nagarahalli , Owen Hilyard , Lijuan Tu Subject: Renaming DTS Thread-Topic: Renaming DTS Thread-Index: AdjtCCsiK6XcBdsrSBq4sG5QU7dyDg== Date: Mon, 31 Oct 2022 10:08:00 +0000 Message-ID: <86702ffab13b42b590ee874affceb9d2@pantheon.tech> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.101.4.10] Content-Type: multipart/alternative; boundary="_000_86702ffab13b42b590ee874affceb9d2pantheontech_" MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --_000_86702ffab13b42b590ee874affceb9d2pantheontech_ Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Hello DPDK devs, As many of you are already aware, we're moving DTS (the testing framework a= long with tests) to DPDK. As part of this effort, we're doing a major refac= toring/rewrite of DTS. What I feel is missing is a discussion of how we sho= uld name the rewritten DTS - not only are the changes big enough but it's a= lso being moved into another community and I think the community should hav= e a say in how we name it. Of course, that discussion could have happened a= s part of the review process of the first patch [0], but that usually focus= es on the code and these big picture issues can get overlooked. With that, here are some proposals: * Change the name altogether, to something like o test_harness o test_framework o test(ing) o integration_test * Use the existing DTS initialism, but change the meaning, possibly= to o DPDK test system o DPDK test solution o DPDK test software o DPDK test scenarios o DPDK test framework/harness and suites. This is a stretch, as it add a = new word that's part of the initialism * Use a new initialism o DTFS, DTH - DPDK test framework and suites, DPDK test harness * Use two directories, one for framework (libs) and the other for t= ests * And of course, stay with DTS and its original meaning - DPDK test= suite DPDK test suite doesn't fully capture what DTS is (it isn't just tests, but= also the framework (libs) that runs them). That is a minor point, but it's= possible there's a better name. It's likely that it's not worth changing t= he name (or the meaning of the initialism) since people are familiar with i= t. If the topic doesn't get traction, we'll stay with the DPDK test suite. = Or maybe change it to DPDK test suites, as there are many different test su= ites. I like using DTS, but maybe changing the initialism to something that means= tests + libs. I don't think my suggestions above capture quite that, but t= here could be something else that does. I actually like DPDK test suites th= e best. Let us know whether you'd like to see a new directory named 'dts' in you re= pository or something completely different! Thanks, Juraj [0] http://patches.dpdk.org/project/dpdk/list/?series=3D25207 --_000_86702ffab13b42b590ee874affceb9d2pantheontech_ Content-Type: text/html; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable

Hello DPDK devs,

 

As many of you are already awar= e, we're moving DTS (the testing framework along with tests) to DPDK. As pa= rt of this effort, we're doing a major refactoring/rewrite of DTS. What I f= eel is missing is a discussion of how we should name the rewritten DTS - not only are the changes big enough but= it's also being moved into another community and I think the community sho= uld have a say in how we name it. Of course, that discussion could have hap= pened as part of the review process of the first patch [0], but that usually focuses on the code and these big= picture issues can get overlooked.

 

With that, here are some propos= als:

·         Change the name altoget= her, to something like

o   test_harness=

o   test_framework

o   test(ing)

o   integration_test

·         Use the existing DTS in= itialism, but change the meaning, possibly to

o   DPDK test system

o   DPDK test solution=

o   DPDK test software=

o   DPDK test scenarios

o   DPDK test framework/har= ness and suites. This is a stretch, as it add a new word that's part of the= initialism

·         Use a new initialism

o   DTFS, DTH - DPDK test f= ramework and suites, DPDK test harness

·         Use two directories, on= e for framework (libs) and the other for tests

·         And of course, stay wit= h DTS and its original meaning - DPDK test suite

 

DPDK test suite doesn't fully c= apture what DTS is (it isn't just tests, but also the framework (libs) that= runs them). That is a minor point, but it's possible there's a better name= . It's likely that it's not worth changing the name (or the meaning of the initialism) since people are familiar with= it. If the topic doesn't get traction, we'll stay with the DPDK test suite= . Or maybe change it to DPDK test suites, as there are many different test = suites.

 

I like using DTS, but maybe cha= nging the initialism to something that means tests + libs. I don't thin= k my suggestions above capture quite that, but there could be something els= e that does. I actually like DPDK test suites the best.

 

Let us know whether you'd like = to see a new directory named 'dts' in you repository or something completel= y different!

 

Thanks,

Juraj

 

[0] http://patches.dpdk.org/project/dpdk/list/?series=3D25207

--_000_86702ffab13b42b590ee874affceb9d2pantheontech_--