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 4F8B64298A; Wed, 19 Apr 2023 17:40:11 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 479D541141; Wed, 19 Apr 2023 17:40:11 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id F125640A79 for ; Wed, 19 Apr 2023 17:40:09 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1681918809; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=pvD80ZIPNyHeYYJKEBQsdejjzNhzn0o9+fYNLWtApCc=; b=X9QPFe9e9O0eyw64UdE+qTV57Y9hHDEpF0KAjGXJGhAexuqRodNb6xOodVYecqopUOM3Ah ljsb9eDdvW5mw4zibVT/QNIuzl7IBZ5HUn095Qzo4dxj1rj0ysq2TuTgnorHTLE5rjplj6 54GiGbdjTHxlBqxxpHe7N9c3WhJuxaY= Received: from mail-wm1-f72.google.com (mail-wm1-f72.google.com [209.85.128.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-46-STN9sZHfOFeW-i8j2GE9cw-1; Wed, 19 Apr 2023 11:40:08 -0400 X-MC-Unique: STN9sZHfOFeW-i8j2GE9cw-1 Received: by mail-wm1-f72.google.com with SMTP id 5b1f17b1804b1-3f1754de18cso13348045e9.1 for ; Wed, 19 Apr 2023 08:40:07 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681918806; x=1684510806; h=content-transfer-encoding:in-reply-to:subject:from:references:cc:to :content-language:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=pvD80ZIPNyHeYYJKEBQsdejjzNhzn0o9+fYNLWtApCc=; b=kubuXmK8J8ac+i/6rPdAjWSEFOopP871oXMM26cXO+3CzgcDFN3D4lkMVsyHy6S9u0 kBow2UPYKHVF3b9alRdIUmNJ77rj0UaorJtHgtLeoeEPK+/jzXYzJrmgI+N4hJ5ExGlY 5jqVmcuDt+2IfYhOLOaYYVEIInpDHAjmywyqtqgWa8lqb5MKLWVuDJ+x1masjLerISOO JegngtsPpPqvy8vjBSGu2XX1QA0MU5td9KywUBo8jtC68uG3bhMmsuTL+NLs3MvjvPWJ ZHEQQ86RwB+wfKV8oT7p+DeJGahwEjGyLPJtheF+/LlDHrB+MQCILhWOono622yUxnNi l7og== X-Gm-Message-State: AAQBX9cay6alSmsmSzP8TwMiWtuiQz7JQont2iM9P9uKtGs2gIihkVek w1zIxxUuHETo6XWi0df2euxyqKDblZeqD7dtPdWsRNCqb9jHkgTuVovoAC1MH57fnS1Y2Okl9Q6 eu6c= X-Received: by 2002:adf:e402:0:b0:2ce:9f35:59b9 with SMTP id g2-20020adfe402000000b002ce9f3559b9mr5046736wrm.17.1681918806419; Wed, 19 Apr 2023 08:40:06 -0700 (PDT) X-Google-Smtp-Source: AKy350b8XLBgpBpOKqsviDC/gqoz+uIdNeSUPyRTlGI0+JPvAMS1N6TwSqmSlza/Z2fSCCPy/hlCvQ== X-Received: by 2002:adf:e402:0:b0:2ce:9f35:59b9 with SMTP id g2-20020adfe402000000b002ce9f3559b9mr5046723wrm.17.1681918806065; Wed, 19 Apr 2023 08:40:06 -0700 (PDT) Received: from [192.168.0.36] ([78.19.110.151]) by smtp.gmail.com with ESMTPSA id f12-20020adffccc000000b002d45575643esm16016372wrs.43.2023.04.19.08.40.05 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 19 Apr 2023 08:40:05 -0700 (PDT) Message-ID: <4b900b49-eb2c-f315-9784-c667175d25bb@redhat.com> Date: Wed, 19 Apr 2023 16:40:04 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.1 To: jerinj@marvell.com, web@dpdk.org Cc: dev@dpdk.org, techboard@dpdk.org References: <20230213092616.3589932-1-jerinj@marvell.com> From: Kevin Traynor Subject: Re: [dpdk-web] [RFC PATCH] process: new library approval in principle In-Reply-To: <20230213092616.3589932-1-jerinj@marvell.com> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: web@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK website maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: web-bounces@dpdk.org On 13/02/2023 09:26, jerinj@marvell.com wrote: > From: 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. > + - Any licensing constraints. > + - Justification for adding to DPDK. > + - Any other implementations of the same functionality in other libs/products and how this version differs. - Dependencies (Need to know if it's introducing new dependencies to the project) > + - 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. > + How about having three outcomes: - Approval in principal - Not approved - Further information needed