if you would like to join the team and the time of the meeting does not work for you- please let me know! i, and @sgrif, the leads of the team are very amenable to changing the schedule to fit the needs of folks.
that being said, team based work is how the Rust project works and has worked for a very long time. i agree that it does indeed create limitations but those limitations are indeed the limitations of the human condition. a condition i also find frustrating but have yet to be able to solve on my own.
inevitably, the work must be done. it must be done by a set of folks with shared context with a reliability and trust that it will get done. this will require sync communication on some level. it’s true that indeed this does limit types of participation but it attempts to limit it in a practical way, an unlimited number of asynchronously proposed features does not naturally turn into a coherent product.
the team is young and currently requires sync communication. virtually every team on the rust project has a sync component, and this is largely due to the desire for a coherent product. it’s possible that we will get to a place where we can operate completely asynchronoulsy, but we aren’t there yet. in fact, in my experience, most open source projects aren’t there yet. that being said, we want to accommodate as many folks as possible.
one of my largest jobs in rust thus far has been making the project more accessible. i’ll be the first to say we aren’t there yet. however, structure and, yes, synchronous communication are some of the best first building blocks i’ve encountered and implemented.
in the end, the work must get done. the product must be coherent. we’re working with a team based structure for now and that will change as the team evolves. i’m sorry that you feel excluded, i’d like to learn more about how to better include you.
i will say tho, that constantly fielding asynchronous calls for action from folks who don’t share context and understanding, doesn’t scale. at the moment, communicating that context and understanding is difficult due to understaffing. it’s a chicken and egg situation and we are doing our best. i’m deeply sorry you feel harmed by this. if there’s any way i can help do let me know, but also know that i am also trying to protect team members from harm when i direct action to these synchronous calls. the crates.io team is largely volunteers and to be completely frank i think the calls from the community have been unfairly overwhelming for the team and i am genuinely seeking to shield them in hopes that it improves their experience and productivity. if the team is constantly reacting to contextless calls for action, the team cannot act proactively.
i hope we can agree that acting proactively is the best move to take. i know the team needs to improve its ability to communicate context. the whole rust team does, to be honest. these are large problems that i haven’t seen any open source project do successfully at scale. these are open questions that we are solving on the fly now. we care a lot but it’s just actually not super easy. please feel free to shoot us a message with ideas. i am available personally to also discuss it.
