From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 31439A0526;
	Wed, 22 Jul 2020 11:09:31 +0200 (CEST)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id 11B2B1BFD4;
	Wed, 22 Jul 2020 11:09:31 +0200 (CEST)
Received: from mail-io1-f65.google.com (mail-io1-f65.google.com
 [209.85.166.65]) by dpdk.org (Postfix) with ESMTP id BCF23199BC;
 Wed, 22 Jul 2020 11:09:28 +0200 (CEST)
Received: by mail-io1-f65.google.com with SMTP id v6so1795133iob.4;
 Wed, 22 Jul 2020 02:09:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to
 :cc; bh=exx549mZ4wZOuIYlwAsfFQ2NeFKjTPKmMjh6ey7W1ok=;
 b=RnFxGDpKj2xMwfsF7n92aveEFYP0RMg86ClO9K93d3z6+AO218Dk2qrGUAxv82LOhC
 PgWPLLh3cWKdeFCNRKvHWAo5Z27LHxmBEr9KL2qIXi1n3Er1s9BZhvUOMBmih0ScBJsf
 qWggScdSB5b/CkHdk1yl3xvk+fRrUuzFeWJiFdvhhvjyXfWfO8UR9r/66v54+Ze3pXcV
 M+U8Yjbb88e9kGzOJh+xmD94MSZUnAGartJ/egKDd0xnLlRjXBgW6gFUhtrkdQKSzETf
 1b5ZQ3Xn3WqIOHYwDsuuDfa7w+nnUNjWWiiJGXXpONVD+er4zASBZvEujsGXTHRRHUXk
 6r6g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=exx549mZ4wZOuIYlwAsfFQ2NeFKjTPKmMjh6ey7W1ok=;
 b=oLJbqaHzZEPddS4T9AWb/RPlCpJsjpukNAWrGejNz2gk+ZfJqtrBL5+tybFbY1X5Ot
 jZW1UXPteTWsU1SEuZC8rezwbsPh3OWoKn9RR2QyklITDHCECBOhfKy21FlmPwpzECah
 NteRFN+8jaV0wouvUVk7t9LOl7nDrOBMF6q97s4vwLXt035Eoi7rn9YSL8C9cvTybUGm
 uqm6+WqoJvlfoxkpm2Qk162b1rDViYYOmPEAisL4MilQYtIVjKkUN34gznDJ5boiB0yL
 SIexu4/Rsb1ktA9SVujpRnJUwc+s2HwHM4qubjwEGQmzN+rsFjVWKXygI7W9Ewpf1uc+
 sdyw==
X-Gm-Message-State: AOAM531mSSLPegtPZQs7qZje5Jb9b4UUzm1wuBNHJW63CrxDmId+uRzS
 PU7M5yrHRG7/VWJ2Ktjwm25hPbLcIK0w3AOpWU0=
X-Google-Smtp-Source: ABdhPJxPqwgevJJ5Kb1mkepsAjedqBLiVqIJSfuc8ygozmjn2PEVcJDIPC8GdgUl2Kz7Eu7vDPPCzgV65UAPP+Zpyq4=
X-Received: by 2002:a02:840e:: with SMTP id k14mr35827187jah.133.1595408968125; 
 Wed, 22 Jul 2020 02:09:28 -0700 (PDT)
MIME-Version: 1.0
References: <20200306164104.15528-1-aostruszka@marvell.com>
 <1734533.zqhfolzEdB@thomas>
 <CALBAE1NGmZ_yrmKNroj6JYAG=JztgUWr2qaO=M2juVTta2hcpw@mail.gmail.com>
 <3669914.27dMEtFVk2@thomas>
In-Reply-To: <3669914.27dMEtFVk2@thomas>
From: Jerin Jacob <jerinjacobk@gmail.com>
Date: Wed, 22 Jul 2020 14:39:12 +0530
Message-ID: <CALBAE1Pmig0-RawsxFvMy6sA0oXcf3guj-VBN_xcLtJVJGkOfQ@mail.gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "Andrzej Ostruszka [C]" <aostruszka@marvell.com>,
 =?UTF-8?Q?Morten_Br=C3=B8rup?= <mb@smartsharesystems.com>, 
 Stephen Hemminger <stephen@networkplumber.org>, dpdk-dev <dev@dpdk.org>,
 techboard@dpdk.org
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [dpdk-dev] [PATCH v2 1/4] lib: introduce IF Proxy library
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On Wed, Jul 22, 2020 at 2:26 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 22/07/2020 10:45, Jerin Jacob:
> > On Wed, Jul 22, 2020 at 6:10 AM Thomas Monjalon <thomas@monjalon.net> wrote:
> >
> > > > In addition may I ask your opinion on the changes that are required
> > > > before the library can be accepted?
> > >
> > > Very few contributors take time to look at it.
> > > Clearly we want this feature. We really want it,
> > > but we are not able to dedicate enough time for its review (blaming myself).
> > > That's why I Cc the techboard to try a new process:
> > >
> > > For such feature requiring a community design,
> > > and not having enough feedback to progress in a timely manner,
> > > I propose drafting the design in a Technical Board meeting
> > > (a regular or specific one).
> >
> > Since the patch series already have the documentation for library[1],
> > example application [2]
> > in addition to the implementation.
> > For everyone's benefit, it would good to know what is the expectation
> > of draft design so that one can create
> > such a document as part of the new process and it can apply for new
> > another library.
> >
> > [1] http://patches.dpdk.org/patch/71953/
> > [2] http://patches.dpdk.org/patch/71956/
>
> I don't understand Jerin.
> What is your question?
> Are you proposing to include a design document as part of the patches?

No

> In my opinion, the cover letter is a good place to explain a design.

Agree.

Currently, In the patch series already have the design[1] in the cover
letter and documentation[2]
[1]
http://mails.dpdk.org/archives/dev/2020-June/171070.html
[2]
http://patches.dpdk.org/patch/71953/

Thomas, I did not understand the expectation of "I propose drafting
the design in a Technical Board meeting".
You mean, Techboard will define/draft the design? or Are you expecting
anything from the patch submitter otherthan
participating in the discussion.
The description is not clear, Hence I am asking.


>
>