DPDK patches and discussions
 help / color / mirror / Atom feed
From: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
To: jerinj@marvell.com
Cc: dev@dpdk.org, techboard@dpdk.org, web@dpdk.org
Subject: Re: [dpdk-web] [RFC PATCH] process: new library approval in principle
Date: Mon, 10 Apr 2023 14:42:22 +0100	[thread overview]
Message-ID: <78f87640-cdc5-6d0e-ab81-0b89520a5bcb@yandex.ru> (raw)
In-Reply-To: <20230213092616.3589932-1-jerinj@marvell.com>

> rom: Jerin Jacob <jerinj at marvell.com>
> 
> 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 <jerinj at marvell.com>
> ---
>  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 <konstantin.v.ananyev@yandex.ru>

> +   - 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


  parent reply	other threads:[~2023-04-10 13:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13  9:26 jerinj
2023-03-01  8:28 ` Jerin Jacob
2023-03-03 18:25 ` Thomas Monjalon
2023-03-15 13:47   ` Jerin Jacob
2023-03-30 12:48     ` Jerin Jacob
2023-04-17 13:33       ` Jerin Jacob
2023-04-24 22:31         ` Thomas Monjalon
2023-04-10 13:42 ` Konstantin Ananyev [this message]
2023-04-19 15:40 ` Kevin Traynor
2023-04-20 10:17   ` Jerin Jacob
2023-05-18 13:21 ` [dpdk-dev] [PATCH v1] doc: process for " jerinj
2023-06-06 16:06   ` Jerin Jacob
2023-07-20  6:33   ` Jerin Jacob
2023-07-20  8:03   ` Ferruh Yigit
2023-07-25 10:19     ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=78f87640-cdc5-6d0e-ab81-0b89520a5bcb@yandex.ru \
    --to=konstantin.v.ananyev@yandex.ru \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=techboard@dpdk.org \
    --cc=web@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).