[PATCH 0/5] lib: add pdcp protocol

[Jerin Jacob]

On Wed, Jan 18, 2023 at 10:09 PM Thomas Monjalon <thomas at monjalon.net> wrote:
>
> For such new library, I think we need to vote in techboard to accept it.
> That's a process we had in recent years to keep the project scope in control.


Looks like this process not defined nor documented. In order to bring
clarity for new library acceptance and make life easy for contributors
(also, less forking the DPDK repo),
IMO, we should document the process as there is a lot of effort
involved and send multiple version, and finally it gets rejected due
to various reasons.

I would suggest, some guideline to get started for discussion. I would
suggest taking up this for TB meeting to define it.

1)For new library(new directory under lib/ directory) needs to get
approval from DPDK tech board.
2)Author needs to send any of the following to start the approval process
-Send a write-up on the scope and purpose library. TB may ask for
sending API specification RFC is the scope or purpose is not clear.
OR
-Send RFC with API specification.

If it's above, following  new libraries needs approval. So I suggest
we take approval in coming TB meeting to conclude one way or another.

1) pdcp library (https://patches.dpdk.org/project/dpdk/list/?series=26246)
2) mldev library or device
class(https://patches.dpdk.org/project/dpdk/list/?series=25753)
3) memara (https://patches.dpdk.org/project/dpdk/list/?series=26546)
4) pmu ( started as EAL file and moving to separate library at
https://patches.dpdk.org/project/dpdk/list/?series=26616)

Please add the libraries if I missed something.