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 A35DA42C40; Tue, 6 Jun 2023 18:06:44 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7C5DA4067B; Tue, 6 Jun 2023 18:06:44 +0200 (CEST) Received: from mail-pf1-f177.google.com (mail-pf1-f177.google.com [209.85.210.177]) by mails.dpdk.org (Postfix) with ESMTP id 743C540223; Tue, 6 Jun 2023 18:06:42 +0200 (CEST) Received: by mail-pf1-f177.google.com with SMTP id d2e1a72fcca58-6549df4321aso3748561b3a.2; Tue, 06 Jun 2023 09:06:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686067601; x=1688659601; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=qt5CJl9CZ4Oie7O2U/x3sgcv9R9TOf9ILjdcUlktfQ4=; b=QFQWR4Ev2+HiXo4C4v1YDM0vqc9D9xKtx+ZGoFrJuBPYmV2bhj/oT5SE20FXNgF38C a7zZi66JUAG0uONVmfEeCN88XSTXp5PLW8xCfVZ+UV9b0TaXPzL6H/ekwssiVZvYhMwg tjALSjFtO0Fcv7oDtpYEH27YD11it7rrhRBzk3RF8ncVn5XItzBAK7ELzJtIM+h1vCfa 9hRsTOVQll42bjaQ0tXmHAu9q2YWaVilnJccuWg1c+mwLPWBq8JhJYdQKKUaCgmk6WqD hgCTiVVAngsD8NVVd3HHGwrVjJig/gmgdo4jRoo10TqRUH3aDEnKlPhmrODTiol2iNEY A7Hw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686067601; x=1688659601; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=qt5CJl9CZ4Oie7O2U/x3sgcv9R9TOf9ILjdcUlktfQ4=; b=k+HLO+i332VyKQ702eIxwAAewp/DZx+p+4Z0dr22cGReZ/mWY0R389z5v6SD2fWIWw v05Exb9IJk3Bg3CWI8SyAlw8W3x4tYTZzhiwOv2Fm9Tyix3fPPHIgbLUw97+c2lPYRFV 1ulbJxkvVwVEUntSlqsU3VdeEPbySnod5JsjcxrfMW0iRx2IdwF3th8gLAILiUmC0Bxp DR8I2Er58Yqbth5J5KVe6M7iik6ucn6lzOxbcipZgubKU12h7u8Ie3SUQHzXqO863ky6 STfu7xLmQ66tAwn82aOxCm/6dpXeUTtn6YFx8w60OOTrA+IkOwwT/FYW25XgnR2KO2UT qJHw== X-Gm-Message-State: AC+VfDzlHy9L2OZcCwZEl9Ql5T12FmtSf0zbPneHJgAy0PUYTsYQyBwI GlIns7qDzKmMgMTb4Rmg/j6eW10vP/CGnWYl4Dw= X-Google-Smtp-Source: ACHHUZ7FaIh/OJ4oXbYznUFjEI1ajx+XOfM/iVN0VqTBHqhcw/C3468Cko61irRbdPLjifcxgec4NAQw7E+YyViYZ5w= X-Received: by 2002:a05:6a20:1456:b0:10a:e9ff:808d with SMTP id a22-20020a056a20145600b0010ae9ff808dmr283097pzi.0.1686067601498; Tue, 06 Jun 2023 09:06:41 -0700 (PDT) MIME-Version: 1.0 References: <20230213092616.3589932-1-jerinj@marvell.com> <20230518132139.1350234-1-jerinj@marvell.com> In-Reply-To: <20230518132139.1350234-1-jerinj@marvell.com> From: Jerin Jacob Date: Tue, 6 Jun 2023 21:36:13 +0530 Message-ID: Subject: Re: [dpdk-dev] [PATCH v1] doc: process for new library approval in principle To: jerinj@marvell.com Cc: dev@dpdk.org, thomas@monjalon.net, david.marchand@redhat.com, ferruh.yigit@amd.com, techboard@dpdk.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 On Thu, May 18, 2023 at 6:52=E2=80=AFPM wrote: > > From: Jerin Jacob > > Based on techboard meeting[1] action item, defining the process for a > new library approval in principle. > > [1] > https://mails.dpdk.org/archives/dev/2023-January/260035.html > > Signed-off-by: Jerin Jacob > --- > RFC..v1: > - Fix the review comments by Konstantin, Keven, Thomas at > http://patches.dpdk.org/project/dpdk/patch/20230213092616.3589932-1-jerin= j@marvell.com/ Ping for review. > > doc/guides/contributing/index.rst | 1 + > doc/guides/contributing/new_library.rst | 48 +++++++++++++++++++++++++ > 2 files changed, 49 insertions(+) > create mode 100644 doc/guides/contributing/new_library.rst > > diff --git a/doc/guides/contributing/index.rst b/doc/guides/contributing/= index.rst > index 7a9e6b368e..ef627329f1 100644 > --- a/doc/guides/contributing/index.rst > +++ b/doc/guides/contributing/index.rst > @@ -18,3 +18,4 @@ Contributor's Guidelines > vulnerability > stable > cheatsheet > + new_library > diff --git a/doc/guides/contributing/new_library.rst b/doc/guides/contrib= uting/new_library.rst > new file mode 100644 > index 0000000000..7dde8cbe64 > --- /dev/null > +++ b/doc/guides/contributing/new_library.rst > @@ -0,0 +1,48 @@ > +.. SPDX-License-Identifier: BSD-3-Clause > + Copyright(c) 2023 Marvell. > + > +Process for new library approval in principle > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > + > +Rationale > +--------- > + > +Adding a new library to DPDK with proper RFC and then full patch-sets is= significant work. > +In order to save effort, developers will get an early approval in princi= ple, or early feedback in > +case the library is not suitable for various reasons. > + > +Process > +------- > + > +#. When a contributor would like to add a new library to DPDK code base,= the contributor must send > + the following items to DPDK mailing list for technical board approval= -in-principle. > + > + * Purpose of the library. > + * Scope of work: outline the various additional tasks planned for thi= s library, such as > + developing new test applications, adding new drivers, and updating = existing applications. > + * Expected usage models of the library. > + * Any licensing constraints. > + * Justification for adding to DPDK. > + * Any other implementations of the same functionality in other librar= ies/projects and how this > + version differs. > + * Public API specification header file as RFC. > + > + * Optional and good to have. > + * Technical board may additionally request this collateral if nee= ded to get more clarity > + on scope and purpose. > + * Any new library dependencies to DPDK. > + > +#. Technical board to schedule discussion on this in upcoming technical = board meeting along with > + author. Based on the technical board schedule and/or author availabil= ity, technical board may > + need a maximum of **five** technical board meeting slots. > + > +#. Based on mailing list and technical board meeting discussions, techni= cal board to vote and share > + the decision in the mailing list. The decision outcome can be any of = the following. > + > + * Approved in principal > + * Not approved > + * Further information needed > + > +#. Once technical board approves the library in principle, it is safe to= start working on the > + implementation. However, the patches will need to meet the usual qual= ity criteria in order to be > + effectively accepted. > -- > 2.40.1 >