Re: [DISCUSS] Pre New Podling: MEA

Hi tison,

This is an interesting project.

I agree that "MEA" is a short name that may not be descriptive enough
for strong branding.

Regarding the goal of growing the community from the current four
contributors, what are your thoughts and strategy on this?

I would be happy to help in any way if you would like.

Regards,
JB

On Sun, Aug 2, 2026 at 5:20=E2=80=AFPM tison <[email protected]> wrote:
>
> Hi,
>
> I'd like to test the waters for bringing MEA [1] into the Apache Incubato=
r.
>
> [1] https://github.com/fast/mea
>
> MEA (Make Easy Async) is a runtime-agnostic Rust library providing
> synchronization and coordination primitives for asynchronous programs. It
> includes mutexes, read-write locks, semaphores, barriers, condition
> variables, latches, wait groups, channels, and several higher-level
> concurrency utilities.
>
> The intended scope is async synchronization and coordination rather than
> building another async runtime. Applications can use MEA with Tokio or an=
y
> other executors.
>
> I started the project in 2024 and currently maintain it under the Apache
> License 2.0. There are about four contributors (including me) actively
> overseeing the project.
>
> I am considering donating the MEA codebase to the ASF and proposing a new
> podling around it. Before putting together a formal proposal, I'd like to
> ask:
>
> * Is anyone interested in using, contributing to, or joining the initial
> community of such a project?
> * Are there fellow IPMC members interested in serving as Mentors? I can
> take care of the Champion role and help drive the incubation work.
> * Do you have suggestions for a better project name? "MEA" is short and
> generic, but it may not be straightforward for spreading. I am open to
> renaming the project before incubation. Ideally, the new name would be
> distinctive while still suggesting async synchronization or concurrency i=
n
> Rust.
>
> If there is enough interest, I will follow up with a draft proposal.
>
> Best,
> tison.