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 20B9142907; Mon, 10 Apr 2023 15:42:26 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id EDFA640DDC; Mon, 10 Apr 2023 15:42:25 +0200 (CEST) Received: from forward501b.mail.yandex.net (forward501b.mail.yandex.net [178.154.239.145]) by mails.dpdk.org (Postfix) with ESMTP id 7E01A40A81; Mon, 10 Apr 2023 15:42:25 +0200 (CEST) Received: from mail-nwsmtp-smtp-production-main-60.sas.yp-c.yandex.net (mail-nwsmtp-smtp-production-main-60.sas.yp-c.yandex.net [IPv6:2a02:6b8:c08:8212:0:640:cefe:0]) by forward501b.mail.yandex.net (Yandex) with ESMTP id CEEA85EC01; Mon, 10 Apr 2023 16:42:24 +0300 (MSK) Received: by mail-nwsmtp-smtp-production-main-60.sas.yp-c.yandex.net (smtp/Yandex) with ESMTPSA id MgU7m95Wu0U0-jGtFzMmm; Mon, 10 Apr 2023 16:42:24 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1681134144; bh=bt8e2T5c5wLf5GZ+Apcd28H6s3emWA7rJqDsAIfANHo=; h=From:Subject:In-Reply-To:Cc:Date:References:To:Message-ID; b=WOKNQiS3xHXvc82mXvAn78AC63/9CoBHuN1M8x1GIF1H3nSYk8WozPZL9zgDf45Oa ciqPX8Ue8xTqkkVb79nvP0LyngCRa1bI2gbD2+OpVuRplBKHu352zibfzC4UrErObG f9BXBOoROe/Ymwcsp5poouXHrpJbsc6NTPIfpFq4= Authentication-Results: mail-nwsmtp-smtp-production-main-60.sas.yp-c.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <78f87640-cdc5-6d0e-ab81-0b89520a5bcb@yandex.ru> Date: Mon, 10 Apr 2023 14:42:22 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0 To: jerinj@marvell.com Cc: dev@dpdk.org, techboard@dpdk.org, web@dpdk.org References: <20230213092616.3589932-1-jerinj@marvell.com> Subject: Re: [dpdk-web] [RFC PATCH] process: new library approval in principle Content-Language: en-US From: Konstantin Ananyev In-Reply-To: <20230213092616.3589932-1-jerinj@marvell.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 > rom: Jerin Jacob > > Based on TB meeting[1] action item, defining > the process for new library approval in principle. > > [1] > https://mails.dpdk.org/archives/dev/2023-January/260035.html > > Signed-off-by: Jerin Jacob > --- > content/process/_index.md | 33 +++++++++++++++++++++++++++++++++ > 1 file changed, 33 insertions(+) > create mode 100644 content/process/_index.md > > diff --git a/content/process/_index.md b/content/process/_index.md > new file mode 100644 > index 0000000..21c2642 > --- /dev/null > +++ b/content/process/_index.md > @@ -0,0 +1,33 @@ > ++++ > +title = "Process" > +weight = "9" > ++++ > + > +## Process for new library approval in principle > + > +### Rational > + > +Adding a new library to DPDK codebase with proper RFC and then full patch-sets is > +significant work and getting early approval-in-principle that a library help DPDK contributors > +avoid wasted effort if it is not suitable for various reasons. > + > +### Process > + > +1. 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 TB approval-in-principle. > + > + - Purpose of the library. > + - Scope of the library. I'd probably extend it to: Scope and expected usage models of the library. Apart from that - LGTM. Acked-by: Konstantin Ananyev > + - Any licensing constraints. > + - Justification for adding to DPDK. > + - Any other implementations of the same functionality in other libs/products and how this version differs. > + - Public API specification header file as RFC > + - Optional and good to have. > + - TB may additionally request this collateral if needed to get more clarity on scope and purpose. > + > +2. TB to schedule discussion on this in upcoming TB meeting along with author. Based on the TB > +schedule and/or author availability, TB may need maximum three TB meeting slots. > + > +3. Based on mailing list and TB meeting discussions, TB to vote for approval-in-principle and share > +the decision in the mailing list. > + > -- > 2.39.1