Great to see more Rust projects to join the incubator! You have my full support.
One question: since it treats runtime agnostic as a core feature, I'm wondering if this feature can be proven statically or this library is tested on various runtime libraries to ensure that? Best, Twice On Tue, Aug 4, 2026, 4:16 PM tison <[email protected]> wrote: > Hi Xuanwo and JB, > > Thanks for your interest! > > > strategy on this > > I'm comparing MEA for Rust to Apache Commons for Java, or CommonsIO, since > MEA focuses mainly on runtime-agnostic sync and coord primitives for Async > Rust. > > Thus, it's easy to see that we can set up benchmarks to improve the > performance of primitives [1], include new primitives [2][3], harden test > coverage and proof of correctness, and advocate more Rust projects to > leverage such a firm async primitives lib, like Apache OpenDAL and Prek > (and thus transitively Apache Airflow and more). > > [1] https://github.com/fast/mea/pull/136 > [2] https://github.com/fast/mea/pull/134 > [3] https://github.com/fast/mea/pull/117 > > > I agree that "MEA" is a short name that may not be descriptive enough for > strong branding. > > I'm considering calling it AnyWake since Wake [4] is a core Async Rust > concept that is runtime-agnostic. But I'm always open to native speakers > for advice. > > [4] https://doc.rust-lang.org/std/task/trait.Wake.html > > > four contributors > > To be clear, they are: > > * tison (me) > * Andy Lok (@andylokandy, we collaborate a lot at https://github.com/fast) > * Yunze Xu (@BewareMyPower, Pulsar PMC member) > * @orthur2 (newly graduated student, I met him offline in Guangzhou) > > Best, > tison. > > > Jean-Baptiste Onofré <[email protected]> 于2026年8月3日周一 11:26写道： > > > 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 PM tison <[email protected]> wrote: > > > > > > Hi, > > > > > > I'd like to test the waters for bringing MEA [1] into the Apache > > Incubator. > > > > > > [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 > > any > > > 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 > > in > > > Rust. > > > > > > If there is enough interest, I will follow up with a draft proposal. > > > > > > Best, > > > tison. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
