Ahh also with my own +1. 😝 On Tue, Aug 18, 2026 at 9:34 PM Twice <[email protected]> wrote: > > Thank you all! I'll announce the result soon. > > Best, > Twice > > On Mon, Aug 17, 2026 at 2:15 PM Alin Jerpelea <[email protected]> wrote: > > > > +1 binding > > > > Best regards > > Alin J > > > > On Mon, 17 Aug 2026, 03:54 hulk, <[email protected]> wrote: > > > > > +1 binding > > > > > > On Mon, 17 Aug 2026 at 00:31, Orthur Black <[email protected]> wrote: > > > > > > > > +1 (non-binding) > > > > > > > > > > > > On Fri, Aug 14, 2026 at 10:45 AM Xuanwo <[email protected]> wrote: > > > > > > > > > +1 binding > > > > > > > > > > On Fri, Aug 14, 2026, at 22:41, tison wrote: > > > > > > My +1 binding > > > > > > > > > > > >> First, Initial Source said "The crate will retain its name", which > > > > > >> reads ambiguously now that the rebrand to `asyncband` is done. > > > > > >> Given > > > > > >> that `mea` has 5M+ downloads and existing downstream users pinning > > > it, > > > > > >> it would help to write down the plan: deprecate it, keep publishing > > > > > >> pointer releases to the new crate, yank it, or something else... > > > > > >> and > > > > > >> who ends up owning that name. > > > > > > > > > > > > The rebrand has been done at [1]. The proposed PPMC would reach out > > > to > > > > > all > > > > > > downstream projects and help them to migrate to the new asyncband > > > crate. > > > > > > The plan has been answered here and it's quite straightforward. I > > > don't > > > > > > think we should spend time on writing it down but instead working on > > > the > > > > > > concrete migration work. > > > > > > > > > > > > You may help in opendal's migration from mea 0.6.7 to asyncband > > > > > > 0.6.7 > > > > > since > > > > > > they are logically identical. > > > > > > > > > > > > [1] https://github.com/fast/asyncband/pull/149 > > > > > > > > > > > >> Second, Documentation still points at https://docs.rs/mea; should > > > be > > > > > >> https://docs.rs/asyncband, and community also links to > > > > > > > > > > > > Where do you find a pointer to https://docs.rs/mea? You may find it > > > is > > > > > "The > > > > > > API documentation of Asyncband is hosted at > > > https://docs.rs/asyncband"; > > > > > on > > > > > > the proposal now. > > > > > > > > > > > >> https://crates.io/crates/asyncband/reverse_dependencies. > > > > > > > > > > > > I kept https://crates.io/crates/mea/reverse_dependencies because it > > > > > shows > > > > > > the current downstream status. The migration to asyncband has been > > > under > > > > > > processed. This should be the proper intermediate representation. > > > > > > > > > > > >> Third, Git Repositories has the gitbox URL as > > > > > >> https://gitbox.apache.org/asf/repos/asyncband , the usual form is > > > > > >> https://gitbox.apache.org/repos/asf/asyncband.git > > > > > > > > > > > > Updated. > > > > > > > > > > > >> Lastly, contributor counts don't line up: The background says "four > > > > > >> active contributors", Community says "Contributors: 9", and Core > > > > > >> Developers names four people. Worth aligning so the numbers tell > > > > > >> one > > > > > >> story. > > > > > > > > > > > > Take Apache Answer you serve as a PMC member as an example. Answer > > > has > > > > > 111 > > > > > > contributors on the GitHub contributor graph [2] and now includes 18 > > > > > > committers and a PMC of 14 members. Why do you think these numbers > > > should > > > > > > be aligned? It is a common community status. > > > > > > > > > > > > [2] https://github.com/apache/answer/graphs/contributors?all=1 > > > > > > > > > > > > If you really want a concrete explanation: The other 5 contributors > > > make > > > > > > 1~2 commits randomly. Andy has one commit from the Git history, but > > > he > > > > > > spent adequate time in design discussion and review. I count on him > > > for > > > > > > several significant decisions. > > > > > > > > > > > > Best, > > > > > > tison. > > > > > > > > > > > > > > > > > > mingcheng <[email protected]> 于2026年8月14日周五 22:11写道： > > > > > > > > > > > >> +1 (non-binding) > > > > > >> > > > > > >> The project is well discussed and addressed the naming concern, so > > > I'm > > > > > >> in favour of accepting it. A few things worth fixing during or > > > > > >> right > > > > > >> after the vote which none of them were blocking: > > > > > >> > > > > > >> > Right now, we have four active contributors and the crate has > > > > > >> > been > > > > > >> downloaded more than 5M times. > > > > > >> > > > > > >> First, Initial Source said "The crate will retain its name", which > > > > > >> reads ambiguously now that the rebrand to `asyncband` is done. > > > > > >> Given > > > > > >> that `mea` has 5M+ downloads and existing downstream users pinning > > > it, > > > > > >> it would help to write down the plan: deprecate it, keep publishing > > > > > >> pointer releases to the new crate, yank it, or something else... > > > > > >> and > > > > > >> who ends up owning that name. > > > > > >> > > > > > >> Second, Documentation still points at https://docs.rs/mea; should > > > be > > > > > >> https://docs.rs/asyncband, and community also links to > > > > > >> https://crates.io/crates/asyncband/reverse_dependencies. > > > > > >> > > > > > >> Third, Git Repositories has the gitbox URL as > > > > > >> https://gitbox.apache.org/asf/repos/asyncband , the usual form is > > > > > >> https://gitbox.apache.org/repos/asf/asyncband.git > > > > > >> > > > > > >> Lastly, contributor counts don't line up: The background says "four > > > > > >> active contributors", Community says "Contributors: 9", and Core > > > > > >> Developers names four people. Worth aligning so the numbers tell > > > > > >> one > > > > > >> story. > > > > > >> > > > > > >> Best, > > > > > >> mingcheng > > > > > >> > > > > > >> On Fri, Aug 14, 2026 at 8:16 PM Twice <[email protected]> wrote: > > > > > >> > > > > > > >> > Hi everyone, > > > > > >> > > > > > > >> > Following the discussion thread > > > > > >> > (https://lists.apache.org/thread/f31qd3jm3odomjwy3lqkk21coyqsr9xs), > > > I > > > > > >> > call for a formal vote to accept Asyncband into the Apache > > > Incubator. > > > > > >> > > > > > > >> > As a reminder, the Asyncband proposal is here: > > > > > >> > > > > > > >> > > > > > > > > https://cwiki.apache.org/confluence/spaces/INCUBATOR/pages/446071349/Asyncband+Proposal > > > > > >> > > > > > > >> > Please cast your vote: > > > > > >> > > > > > > >> > [ ] +1, Accept Asyncband into the Apache Incubator > > > > > >> > [ ] 0, I don't care > > > > > >> > [ ] -1, Do not accept Asyncband into the Apache Incubator, > > > because ... > > > > > >> > > > > > > >> > The vote will remain open for at least 72 hours, and only votes > > > from > > > > > >> > the Incubator PMC members are binding. Votes from everyone are > > > > > >> > welcome. > > > > > >> > > > > > > >> > Thanks! > > > > > >> > > > > > > >> > Best wishes, > > > > > >> > Twice > > > > > >> > > > > > > >> > > > > --------------------------------------------------------------------- > > > > > >> > To unsubscribe, e-mail: [email protected] > > > > > >> > For additional commands, e-mail: > > > [email protected] > > > > > >> > > > > > > >> > > > > > > >> > > > > > > > > > > -- > > > > > Xuanwo > > > > > > > > > > https://xuanwo.io/ > > > > > > > > > > > > > > > > > -- > > > Best Regards, > > > - Hulk Lin > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
